Pricing

Priced on the shape of the work.

We do not publish a rate card, because the same feature can cost very different amounts in different products. Here is how we arrive at a number, and what it covers.

Engagement models

Three ways to work with us

The model follows the work. Many engagements start as one and move to another as the product matures.

Fixed scope

For projects with a clear brief and deadline.

How it is priced
A fixed price, billed by milestone
Best when
The scope is defined and unlikely to change
You see
A working demo every week

Dedicated team

A senior squad embedded with your product org.

How it is priced
A monthly retainer
Best when
The product is live or still taking shape
You see
Full ownership of an area, steered week by week

Augmentation

Specific roles added to your existing team.

How it is priced
By role and duration
Best when
You have a working team and a skills gap
You see
Engineers, designers, or SREs working inside your process

What moves the number

Six things that decide the cost

  1. How clear the scope is

    A defined brief can be priced as a fixed scope. Work that is still being discovered is better run as a team with a monthly budget.

  2. The shape of the team

    Which roles the work needs and for how long: engineering, design, infrastructure.

  3. The timeline

    A tighter deadline needs more people working in parallel, which adds cost and coordination.

  4. Integrations

    Each outside system, such as payments, identity, or legacy data, adds work that is hard to see up front.

  5. Reliability and compliance

    Uptime targets, audits, and regulated data shape both the architecture and the testing.

  6. What happens after launch

    Whether we keep operating and supporting the product, or hand it over to your team.

Always included

What every engagement covers.

These are part of how we work, whichever model you choose.

See our capabilities

  1. Discovery before code

    A focused discovery sprint to align on outcomes, scope, and risk before any code is written.

  2. Weekly demos

    You see progress every Friday and steer course every Monday.

  3. Tested, reviewed code

    Automated tests on what matters, and code review on every change.

  4. An honest handoff

    Production support, observability, and a handoff plan so your team owns what we ship.

Getting a number

From first message to a proposal.

  1. Tell us about the project Send a brief, or a few lines on the problem. We reply within one business day.
  2. A short call to understand the work Goals, constraints, and what success looks like for you.
  3. A proposed shape, with a price Scope, team, timeline, and cost, in a form you can say yes or no to.

Start a project

Want a number for your project?

Tell us what you are building. We respond within one business day.

Start a project See our work