Engagement models

Clear ways to work together, and what drives cost

No surprises: you know what you get at every stage, how it's billed and what would change the estimate.

Get a project estimate What drives cost

01Models

Four ways to engage

E/01

Discovery sprint

Start here when the idea is clear but the scope is not.

Length
Usually 1–2 weeks
Billing
Fixed fee, agreed upfront

You get

  • Workshops with the people who will use the software
  • User flows and a clickable prototype
  • Architecture and integration notes
  • A written scope and fixed estimate for the build
E/02

Project build

For a defined product or release with a clear finish line.

Length
Weeks to a few months
Billing
Fixed price per milestone

You get

  • A named lead and a small dedicated team
  • Weekly demos and written updates
  • Staging environment you can test
  • Launch, handover notes and source code in your repository
E/03

Dedicated team

For ongoing product work where priorities change month to month.

Length
Monthly, rolling
Billing
Monthly, by team size

You get

  • Developers, designer and QA as your extended team
  • Your backlog, your rituals, your tools
  • Monthly planning and reporting
  • Scale up or down with notice
E/04

Support plan

For live software that needs to stay patched, fast and online.

Length
Monthly, rolling
Billing
Monthly, by scope and response time

You get

  • Monitoring, backups and security updates
  • Agreed response times for issues
  • A small monthly allowance for improvements
  • Clear reporting on what was done

02What drives cost

Six things that move an estimate

When we send an estimate, it shows how each of these affects your project, so you can decide what belongs in the first release.

User roles

Each kind of user (customer, staff, admin, partner) adds screens, permissions and testing.

Integrations

Payment gateways, ERPs, maps, messaging and legacy systems each need careful work and testing.

Platforms

Web only, or web plus iOS and Android. A shared codebase helps, but app-store releases add work.

Data & migration

Moving years of spreadsheets or an old database into the new system is a project of its own.

AI & automation

Model choice, evaluation and safeguards depend on how accurate and private the results must be.

Polish & scale

A first release for 50 users and a platform for 50,000 need different levels of design and engineering.

03FAQ

Questions about working with us

Why not give a price right away?

Two projects described in the same sentence can differ ten times in effort. A short discovery lets us give a written estimate we can stand behind, instead of a number that changes later.

Is the discovery sprint worth it if we already have specs?

If your specs are detailed we can review them in a shorter, lighter discovery. The aim is the same: a shared understanding of scope before money is committed to the build.

How do payments work?

Project builds are usually billed by milestone; dedicated teams and support plans monthly. Exact terms are set out in the agreement for each project.

What if priorities change mid-project?

They often do. We re-plan openly: swap features of similar size within a milestone, or agree a change with its cost before work starts.

Can we start small?

Yes. Many clients start with a discovery sprint or a single release, and decide on the next step once they have seen how we work.

Next step

Tell us what you want to build.

Share the goal, rough budget and timing. We reply with questions, a next step, or an invitation to a short call. NDA on request.

Get a project estimate WhatsApp us
Get a project estimate