Skip to content

Process

01 — 05

Five steps, and you always know which one you're on.

Most of what makes a web project stressful isn't the work. It's not knowing what's happening. So here is exactly how it goes, before you've spent a rupee.

  1. 01

    Conversation

    Day one

    A call or a WhatsApp thread. You describe what you need, we tell you honestly whether we are the right studio for it. Including when the answer is no.

    • What the site or product has to achieve
    • Rough budget and timeline
    • Whether we are a fit, said plainly
  2. 02

    Scope & proposal

    2–3 days

    A written proposal. What is included, what it costs, what it takes, and what happens if the scope changes. One document. No surprises later.

    • Fixed scope with a fixed price
    • Milestones and payment schedule
    • Explicit list of what is not included
  3. 03

    Design

    1–3 weeks

    We design before we build, because changing a drawing costs a fraction of changing a build. You see and approve everything before development starts.

    • Key screens designed to the pixel
    • Two rounds of revisions included
    • Nothing is built until you sign off
  4. 04

    Build

    2–8 weeks

    Development against the approved design, on a staging link you can check at any point. Weekly updates. No radio silence.

    • A live staging URL from week one
    • Weekly written progress notes
    • Testing across real devices, not just a desktop browser
  5. 05

    Launch & after

    Ongoing

    We handle the launch, hand over everything in your name, and stay reachable. A care plan is available, never automatic.

    • Deployment, domains and analytics configured
    • Code and accounts handed over to you
    • Optional care plan for what comes next

How we work

We would rather lose a project at the proposal stage than deliver one that doesn't work. That single preference explains almost everything else about how we run things.

What we hold to

  1. 01

    Design first, always

    Every decision gets made on the page before it is made in code. Cheaper, faster, and the result is better.

  2. 02

    Fast is a feature

    Performance is not a phase at the end. It shapes the stack, the imagery and the build from day one.

  3. 03

    You own everything

    Code, accounts, domains, content. Handed over in your name. No hostage-taking, no lock-in.

  4. 04

    Say the hard thing

    If a request will hurt the result, we will tell you before we take the money, not after.

Replies within one working day

Ready when you are.

Step one costs nothing and takes about twenty minutes.

Start a project See the work