Skip to content
Manan Devs
Book a Free Call

How I Work

Starting a project takes one call.

No retainers to sign before we have spoken, and no invoice before you know exactly what you are buying. Here is every step between that first call and a product you own, and what you can expect from each one.

Book a Free Strategy CallOr send the brief in writing

  1. A 30-minute call

    • What you need
    • Who it is for
    • The real deadline
    • A plain answer on fit

    Free, no pitch deck. You describe what you need, I ask the awkward questions early — who it is for, what already exists, what the real deadline is — and say plainly whether I am the right person for it.

    The questions I ask on the call

    • Who is it for, and what do they use today instead?
    • What already exists: designs, code, content, a domain, accounts?
    • What is the real deadline, and what happens if it moves?
    • Who else needs to agree before any work starts?
    • What would make this a success six months after launch?

    You do not need a pitch deck or a specification. A link, a rough idea and the problem you are trying to solve are enough. If I am not the right person for the job, I say so on the call, and why.

  2. A written plan and a fixed price

    • What gets built
    • In what order
    • The stack it runs on
    • A fixed price

    Before anything is committed you get the scope in writing: what gets built, in what order, the stack it runs on, the timeline, and the price. If the scope changes later, that document is what we change.

    What the written plan covers

    • Scope: the pages and features that are in, and the ones that are explicitly out.
    • Order: what gets built first, and why that order.
    • Stack: the framework, hosting, data, sign-in and payments it runs on.
    • Timeline: milestones, each with the date its preview goes live.
    • Price: one fixed number for the scope above.

    If the scope changes later, we change the document first: the new scope, and whatever that does to the timeline and the price, in writing, before the work changes.

  3. Build in the open

    • Preview URL in week one
    • Reviewable increments
    • Try it on your phone
    • Progress you can see

    There is a deployed preview URL from the first week, so you are never waiting to see progress. Work lands in reviewable increments and you can try each one on your own phone rather than reading a status report.

    What "reviewable increments" means in practice

    • Each increment is something you can click, not a percentage on a status report.
    • The preview URL stays the same for the whole project, so there is one link to bookmark.
    • Every update comes with a short note: what changed, and what to try.
    • Your feedback goes into the next increment rather than piling up for the end.

    We talk on a call when it helps and in writing the rest of the time, on WhatsApp, email or Fiverr, whichever you already use. I am based in Pakistan (PKT, UTC+5) and work with clients in any time zone.

  4. Launch, then hand over properly

    • Deployment and domains
    • Repository and accounts
    • A short walkthrough
    • Ongoing support

    Deployment, domains, analytics and the metadata that makes the site findable. You get the repository, the accounts and a short walkthrough of how to run and change it — then ongoing support if you want it.

    What launch and handover include

    • Deployment to production, with your domain connected.
    • Analytics set up, so you can see how many people visit and where they come from.
    • The metadata that makes the site findable: titles, descriptions, social previews and a sitemap.
    • The repository and every account the project runs on, handed to you.
    • A short walkthrough of how to run it and how to change it.

    After launch I can stay on for bug fixes, performance work and new features, as and when you need them, or on an ongoing basis if the product changes often. The terms are agreed in writing, like everything else.

How long it usually takes

Landing page
1–2 weeks
Web app, dashboard or SaaS MVP
3–8 weeks

The firm timeline for your project is in the written plan, before anything starts.

Common questions

How long does it take to build a SaaS MVP or website?

It depends on the scope. A landing page usually takes 1–2 weeks, and a web app, dashboard or SaaS MVP usually takes 3–8 weeks. You get a firm timeline in the written plan before anything starts, and a deployed preview from the first week.

How much does it cost to build a SaaS MVP or website?

Every project gets a fixed price, agreed in the written plan after our first call. You know the full cost before the work starts, and if the scope changes, we change that document rather than send a surprise invoice.

Do you offer support after launch?

Yes. After launch I can stay on for bug fixes, performance work and new features — as and when you need them, or on an ongoing basis if the product changes often.