IST

Start a project

DWG S-00 · India → worldwide

Studio —an independent design‑engineering studio, hands‑on.

When you hire Crayont you get the people who design and code it: on the first call, in the Figma file and in the pull requests. Specialists join by name when the work needs them.

Start a projectHow a project runs
Drawing
S-00 · Crayont
Practice
Design + code
Base
India · --:-- IST
Clients
Worldwide
Headcount
1 + named specialists
Scale
1 : 1

S-01 · Principles

Six principles. All checkable.

Each one links to the page where you can check it. If a principle can't be checked, it doesn't belong here.

  1. P-01 · Clause 1 of 6

    Numbers over adjectives

    We don't say fast. We show the numbers, measured and dated.

    Check it · See the measured work

  2. P-02 · Clause 2 of 6

    No hand-offs, first call to last commit

    The people who scope your project design it and write the code. Specialists join by name when the work needs them.

    Check it · How collaboration works

  3. P-03 · Clause 3 of 6

    Specified before designed

    Every project starts with a written spec and agreed tolerances, so 'done' is never a matter of opinion.

    Check it · Read the process

  4. P-04 · Clause 4 of 6

    Fast is a feature

    Performance and accessibility are designed in from the first commit, not patched in before launch.

    Check it · Performance & care

  5. P-05 · Clause 5 of 6

    You own everything

    Code, accounts, designs and documentation are yours at handover. No lock-in, no hostage hosting.

    Check it · What you get at hand-over

  6. P-06 · Clause 6 of 6

    We build our own products

    Crayont Labs keeps our advice grounded in what it costs to run software, not just to ship it.

    Check it · See Crayont Labs

S-02How collaboration works

One studio. Named specialists.

No mystery subcontractors. When a project needs more than one pair of hands, you know who, and why, before work starts.

Bill of materials · per project
ItemRoleJoinsQty
01CrayontDesign + codeEvery project, first call to last commit1
023D artistModels, textures, art directionWhen 3D assets go beyond what code can generate0–1
03CopywriterWords, naming, launch copyWhen the words need a specialist, not just an editor0–1
04Backend engineerAPIs, data, infrastructureWhen the data layer outgrows the front-end0–1
  1. R-01

    You meet the makers first.

    Every project starts on a call with the people who will design it and write its code.

  2. R-02

    Specialists are named in the spec.

    If the work needs a 3D artist, a copywriter or a backend engineer, the spec says who, what they own and for how long — before you sign.

  3. R-03

    You keep one point of contact.

    The same people stay on the project from the first call to the last commit, and after launch.

  4. R-04

    You own what they make.

    [Founder to confirm] Every specialist assigns their work to you at hand-over.

S-03Tools & stack

Tools chosen for the numbers they ship.

A short list, used deeply. Existing stacks are fine for web-app work.

Tools: Astro, TypeScript, React, Tailwind CSS, GSAP, Three.js, GLSL, Lenis, Figma, Vercel, Headless CMS. Measurement: Lighthouse, web-vitals, Search Console, WCAG 2.2 AA, Schema.org, Redirect maps, Design tokens, Performance budgets.

Stack by group, and why each group is chosen
GroupStackWhy
G-01DesignFigma · design tokens · type and motion systems built in codeThe design system lives in the codebase, so what you approve is what ships.
G-02Front-endAstro · TypeScript · React where interactivity needs it · Tailwind CSSAstro sends no JavaScript by default, so pages paint first and only the parts that move load code.
G-03Motion & 3DGSAP · Three.js · custom GLSL shaders · Lenis3D loads after the content, only on devices that can run it, with a static fallback.
G-04PlatformVercel · a headless CMS your team can edit · your existing stack for web-app workAccounts are set up in your name, so hand-over is a transfer, not a migration.
G-05MeasurementLighthouse · web-vitals · Google Search Console · accessibility checksEvery tolerance in the spec has a tool that measures it, and a date next to the result.

S-04Location

India, working worldwide.

We work from India on IST (UTC+5:30, no daylight saving). This is how that lines up with your working day, calculated live in your browser.

  • IndiaUTC+5:30 · IST
    --:--Studio

    10:00–19:00Studio hours, ISTCalls until 22:00 by arrangement[Founder to confirm hours]

  • LondonUTC+1
    --:--

    5 h 30 m overlap13:30–19:00 IST+3 h by arrangement

  • New YorkUTC−4
    --:--

    30 min overlap18:30–19:00 IST+3 h by arrangement

  • DubaiUTC+4
    --:--

    8 h 30 m overlap10:30–19:00 IST+30 min by arrangement

  • SingaporeUTC+8
    --:--

    5 h 30 m overlap10:00–15:30 IST

Offsets follow each city's daylight-saving rules on the day you read this. Your working day is assumed to be 09:00–18:00 local. Replies to email within one working day.

S-05 · Work with Crayont

Work with Crayont.

Start with a 30-minute call. You'll get an honest yes, no or "not yet" within one working day, and a written spec before anything is designed.

Start a projectHow a project runs

Or write to [email protected]

Revisions · DWG S-00
RevDescriptionDateStatus
01Your projectTodayOpen

Approved by: you, after reading the spec.