01 Process

How we work, from first call to launch

A Tailwebs project starts with a call, then a discovery sprint that turns your idea into ranked features, wireframes and a clickable prototype. You get scope, price and timeline in writing. A team member is assigned within 10 days of approval, and the team builds with 200+ AI agents working alongside the engineers.

Book your first callSee the four steps
Illustration: four stepping stones from a phone call to a launch flag

02 The four steps

Four steps, each ending in something you can check.

You are never committed to more than the next step. The discovery sprint is the small, fixed-price start before any build commitment.

  1. Call

    What happens
    We understand the goal: who it is for, what you have so far and what has to be true for it to work.
    What you get
    A clear next step, whether or not it's with us.
    How long
    30 minutes, free and with no obligation

  2. Discovery sprint

    What happens
    Workshops, user research, a prioritised feature list, wireframes, a clickable prototype and a build estimate.
    What you get
    A clickable prototype and an exact build estimate, before any build commitment.
    How long
    2–3 weeks · ₹1.5–3 lakh

  3. Proposal

    What happens
    Scope, price and timeline in writing, as a fixed-scope project or a monthly team (see pricing).
    What you get
    A written proposal to say yes or no to. Mutual NDA on request (how NDAs work).
    How long
    Within 3 working days of the discovery sprint

  4. Build and launch

    What happens
    The build includes analytics from day one. For WAC and Aadhar India, the same team took the product from idea to scale.
    What you get
    Your product launched, with app store submission handled.
    How long
    MVP builds typically run 8–14 weeks

03 By service

Where the steps change, by service.

For these services, one of the steps above changes shape.

04 Communication

How we keep you in the loop.

Working with a remote team goes well when you know who to ask, when you will see progress and which hours you share.

01

Who you talk to

  • A named lead on our side, plus the people building your product.
02

Progress and tools

  • A weekly demo and a written update.
  • A shared board, a chat channel and access to the repository.
03

Working hours

05 People and AI

50+ people and 200+ AI agents: who does what.

Our delivery process is AI-heavy: fewer developers, and a lot of AI working alongside them on the repetitive work.

Our 50+ people

  • Plan, design, build and launch your product.
  • Work with 200+ AI agents in the delivery process.

The AI agents

  • Take first drafts of code, tests and documentation.

Where people decide

  • An engineer reviews everything before it goes into the product.

06 Testing

How releases and AI features get checked.

Testing an AI feature means checking its answers, not only its screens, before release and after launch.

  • 01/03

    Every release

    How we check
    Automated tests run on every build, another engineer reviews each change, and QA checks the release on the devices and browsers your users have.
  • 02/03

    AI features, before release

    How we check
    In our own products: every assistant Tailwebs Operator builds passes red-team probes before it goes live.
  • 03/03

    AI features, after launch

    How we check
    The NFTR Assistant, in the NITI Aayog Frontier Tech Repository portal we built, answers from the knowledge base, cites its sources and reports the questions it could not answer to admins.

    More on AI chatbot development.

07 Handover

What you hold at handover, and after.

At handover you hold the source code in your repository, the documentation and the credentials, and your team gets a walkthrough session.

Fixed-price projects get a 30-day bug-fix warranty after launch, and ongoing care runs through the Care and Growth plan (see pricing). The exact wording is under ownership and support.

Handover · at launchDraft terms
  1. Source code in your repository
  2. Documentation
  3. Credentials handover
  4. A walkthrough sessionFor the team that will run the product.
  5. 30-day bug-fix warrantyFixed-price projects: defects against the agreed scope are fixed free.
  6. Ongoing careThrough the Care and Growth plan.

08 FAQ

Questions about the process.

How long does it take from first call to launch?
For an MVP, about 2–3 weeks of discovery and then 8–14 weeks of build after the proposal is approved.
Can I start with a trial or proof of concept?
Yes. The discovery sprint is a small fixed-price start (₹1.5–3 lakh) that ends in a clickable prototype and an exact build estimate.
How often will I see progress?
Every week, with a demo and a written update.
How do you test AI features before release?
Every assistant Tailwebs Operator builds passes red-team probes before it goes live. After launch, the NFTR Assistant we built reports the questions it could not answer to admins, so gaps show up.
Can the MVP grow into a full product?
Yes. The next stage usually runs as a monthly product squad.