How we price and engage

Software development engagement models, explained plainly

There are four ways to work with Zero One Creation: a fixed-scope project, time and materials, a dedicated team or a monthly retainer. Most larger projects start with a paid discovery workshop.

This page explains how each software development engagement model works, who it suits, how changes are handled and how billing runs. We don't publish prices; after a call we send a written proposal with a customised quotation.

Compare the models
  • Written scope before any build
  • Code and IP assigned to you

Where most projects start

The discovery workshop: a paid, short first step

Before anyone can quote a complex product honestly, someone has to understand it. Discovery is that work, done properly and written down. We run working sessions with your team, map users and journeys, look at the systems the product must connect to and name the risks early.

The fee is agreed before it starts. You keep everything it produces, whether you build with us, with your own team or with someone else. Read more about what a software discovery phase covers.

Small, well-defined projects such as a brochure website often skip a formal workshop. The first call and a written proposal are enough.

What you leave with

  • A written scopeFeatures, user roles and acceptance criteria.
  • A prioritised planWhat goes in the first release and what can wait.
  • An architecture outlineTechnology, data, integrations and hosting.
  • A clickable prototypeWhere the flow needs testing before it is built.
  • A phased quotationFor the build, in the model that suits it.

The four models

How each engagement model works in practice

Each model answers the same five questions: how it works, who it suits, how scope changes are handled, how billing runs and what you get.

01

Fixed-scope project

One agreed scope, one quotation, one timeline.

Best for: Websites, MVPs with a settled feature list, and clearly defined modules where the budget has to be known before work starts.

How it works
We write down the features, screens, integrations and acceptance criteria, then quote for exactly that. Development runs in short sprints against the agreed scope, and you review progress on a preview link throughout.
Scope changes
New ideas go into a change log rather than straight into the build. We estimate each one in writing and you decide: add it now, move it to a later phase, or swap it for something of similar size. Nothing changes the price without your written approval.
Billing rhythm
Milestone-based. Payments are tied to stages you can see and review, such as kick-off, design sign-off, build stages and launch. The exact milestones are agreed in the proposal.
What you get
  • A written scope with acceptance criteria
  • A fixed quotation and a dated plan
  • Design, build, testing and launch
  • Source code, documentation and handover
02

Time and materials

You pay for the work done and steer it sprint by sprint.

Best for: Products whose requirements will change as you learn, ongoing feature work on an existing product, and integrations with unknowns that can't be priced honestly upfront.

How it works
We agree a rate card and an estimate for the work in view, then plan sprint by sprint with you. You see what was done, what is next and how the estimate is holding up at every review.
Scope changes
Change is expected. You reprioritise the backlog at each sprint planning, and we re-estimate the remaining work so you can see the effect on time and budget before you commit to it.
Billing rhythm
Monthly, against the agreed rates, with a summary of the work done in the period. A monthly cap or a budget review point can be written into the proposal.
What you get
  • Freedom to change priorities every sprint
  • A visible backlog and running estimate
  • Regular demos on a preview link
  • Budget controls you set
03

Dedicated team

Our engineers working inside your team, on your roadmap.

Best for: Companies with their own product owner or engineering lead and a roadmap that runs for months rather than weeks.

How it works
Frontend, backend, mobile, design, DevOps or QA people work only on your product, in your tools and rituals. Your team sets priorities; ours adds capacity and engineering judgement.
Scope changes
You own the backlog, so priorities change whenever you decide. Changing the size or mix of the team is planned with notice terms agreed in the contract.
Billing rhythm
Monthly, per team member, for the agreed period. The team, the period and the notice terms are set out in the proposal.
What you get
  • The same people, learning your product
  • Work in your repositories and tools
  • Capacity that grows or shrinks with the roadmap
  • Product direction that stays with you
04

Monthly retainer

Ongoing care and growth work for a live product.

Best for: Live websites and apps that need keeping healthy, and growth work such as SEO and App Store Optimization that builds month on month.

How it works
A defined monthly scope: maintenance (updates, monitoring, backups and small fixes), search engine optimisation, App Store Optimization, or a block of improvement time. Each month starts with a short plan and ends with a report of what was done.
Scope changes
Priorities inside the retainer are agreed at the start of each month. Larger pieces of work that fall outside it are scoped and quoted separately, so the retainer stays predictable.
Billing rhythm
Monthly, for the agreed retainer scope. Any minimum term is set out in the proposal.
What you get
  • A predictable monthly scope
  • A monthly plan and a report of the work
  • One team that knows your product
  • Larger changes quoted separately

Side by side

Software development pricing models compared

The same seven questions, answered for each model. Discovery sits before all of them, so it isn't a column.

Comparison of fixed scope, time and materials, dedicated team and monthly retainer engagement models
QuestionFixed scopeTime and materialsDedicated teamMonthly retainer
ScopeAgreed in writing before work startsEvolves sprint by sprintYour roadmap, your backlogA defined monthly scope
Budget certaintyHighest: one agreed quotationEstimate, with caps if you want themKnown monthly cost per personKnown monthly cost
Room to changeThrough written change requestsEvery sprintWhenever you reprioritiseMonth to month, within scope
Who sets prioritiesAgreed upfront, then usYou, with our adviceYouAgreed each month
Billing rhythmMilestonesMonthlyMonthlyMonthly
Your time neededSign-offs at key stagesSprint planning and reviewsDay-to-day product directionA monthly check-in
Typical fitWebsites, MVPs, defined modulesEvolving products, integrationsTeams scaling a productLive sites and apps, SEO, ASO

Not sure which applies? Tell us about the project and we'll recommend a model in the proposal, with the reasons written down.

The most common question

Fixed price vs time and materials: how to choose

The honest answer depends on how much you already know. If the scope is settled, a fixed price protects your budget. If it isn't, a fixed price forces both sides to guess, and someone pays for the guess. There is a longer guide to fixed price vs time and materials on our blog.

Choose a fixed price when

  • You can describe every screen and rule today
  • The budget has to be approved once, upfront
  • The deadline is fixed by something outside the project
  • You'd rather give sign-offs than run sprint planning

Choose time and materials when

  • You expect to learn from users and change direction
  • The work depends on systems nobody has opened yet
  • You want to reprioritise every couple of weeks
  • You have someone who can make product decisions quickly

Many projects combine the two

A phased path keeps budgets predictable where they can be and flexible where they need to be.

  1. 01.

    Discovery

    A fixed fee to define the product and its risks.

  2. 02.

    First release

    A fixed-scope build of what the first users need.

  3. 03.

    What comes next

    Time and materials, a dedicated team or a retainer, once real usage guides the roadmap.

What affects cost

What actually drives the cost of a software project

The engagement model changes how you pay, not what the work involves. These are the things that decide the size of a quotation, whichever model you choose. We send a customised quotation after a call, with each driver explained.

  • Scope and features

    How many screens, user roles and workflows the product needs, and how much logic sits behind each one.

  • Business rules

    Approvals, pricing rules, permissions and edge cases take more time than the screens that show them.

  • Integrations

    Payment gateways, CRMs, ERPs, accounting tools and third-party APIs, and how well documented each one is.

  • Platforms

    Web only, or web plus Android and iOS apps, and whether the apps can share one cross-platform codebase.

  • Design depth

    Adapting a proven layout costs less than original design work, prototypes and a full design system.

  • Data migration

    Moving records out of spreadsheets or an old system, cleaning them and checking nothing was lost.

  • Security and compliance

    Audit logs, role-based access, data-protection requirements and reviews your organisation asks for.

  • Timeline

    A compressed deadline needs more people working in parallel, which adds coordination as well as hours.

  • Support after launch

    Hosting, monitoring, updates and improvements once the product is live, usually as a retainer.

Same in every model

Your code, your IP, under NDA

Whichever model you choose, ownership works the same way. You should be able to walk away at any point with everything you paid for. Our security and data protection page covers access, credentials and hosting in more detail.

  • NDA before the details

    We sign a non-disclosure agreement before you share detailed requirements, data or access. We can sign yours or share ours.

  • IP assigned to you

    Our contract assigns the intellectual property in the work we build for you to your company. The terms are in the proposal, in plain language.

  • Code in your repository

    Source code lives in a repository your organisation owns, with full history. You can see every change as it lands.

  • Accounts in your name

    Cloud hosting, domains, app store listings and third-party services are set up in your accounts, so nothing leaves with us.

Tell us what you're building. We'll recommend the model and put it in writing.

A call to understand the work, then a written proposal with scope, engagement model, milestones and a customised quotation.

Before you talk to us

Frequently asked questions

What are software development engagement models?

An engagement model is the commercial and working arrangement behind a project: how scope is set, who decides priorities, how changes are handled and how billing works. We offer four: fixed-scope projects, time and materials, dedicated teams and monthly retainers, with a paid discovery workshop as the usual starting point for larger or less defined work.

Fixed price vs time and materials: which is cheaper?

Neither is cheaper by default. A fixed price gives budget certainty but includes allowance for the risk of an agreed scope. Time and materials bills only the work done, but the total moves with your decisions. When the scope is clear, fixed price is usually the calmer choice. When it isn't, time and materials avoids paying for guesses.

What are your payment terms?

Fixed-scope projects are billed against milestones, such as kick-off, design sign-off, build stages and launch. Time and materials, dedicated teams and retainers are billed monthly. The exact schedule for your project, including whether an advance is due at kick-off, is agreed in the proposal before any work starts.

Why don't you publish prices?

Because the same request can mean very different products. A price list would either overcharge simple projects or leave out what complex ones need. After a call, we send a written proposal with a scope and a customised quotation. Our cost guides and project planner explain the drivers if you want to prepare first.

Is the discovery workshop paid, and do we have to continue with you?

Yes, discovery is paid, because it is real work by senior people: workshops, research, a written scope and an architecture outline. The fee is agreed before it starts. The outputs are yours to keep, and you are free to build with us, with your own team or with someone else.

Can we switch models during a project?

Yes. A common path is a fixed-scope first release followed by time and materials or a retainer once the product is live. Any switch is agreed in writing, with the new scope, rhythm and billing set out clearly.

How do you handle scope changes on a fixed-price project?

Every new request goes into a change log. We estimate it in writing, and you decide whether to add it, defer it to a later phase or swap it for something of similar size. The price only changes when you approve a change in writing.

Who owns the code and intellectual property?

You do. Our contract assigns the intellectual property in the work we build for you to your company, and the code lives in a repository your organisation owns. Hosting, domains and app store accounts are set up in your name.

Will you sign our NDA?

Yes. We sign an NDA before you share detailed requirements, data or system access. We are happy to review and sign yours, or to share ours.

Do you work with companies outside India?

Yes. We agree overlap hours with your timezone, sign NDAs, assign intellectual property to you and prepare proposals in your currency. The engagement models and billing rhythms are the same.

Get a tailored proposal

Share the project. We'll suggest how to engage.

A few lines about what you need, your timeline and any constraints is enough to start. We reply with questions or a time for a call, then a written proposal.

We use your details only to reply to this enquiry. See our privacy policy.