Skip to content
Book a call

Start where you’re stuck.

Tell us what’s going on and we’ll match it to a shape: a monthly retainer, a scoped project, or an embedded team. The prices are printed right here — pick the line that sounds like you.

Book a callSee the three shapes
Sound familiar?

Trusted partner

To product and engineering teams, from seed to enterprise.

“There’s always a next thing.”

A monthly retainer

Best for ongoing work nobody can put an end date on: too fluid to price as a fixed project, not big enough to embed a team. Name a budget and we’ll tell you what it buys, or name the outputs and we’ll put a price on them.

“Figure it out and show us?”

$10,000 a month

Best for

A team that can finish and roll out the work themselves, once the hard question is answered and the first working version exists in front of them.

How it runs

The senior read the $5,000 month buys, plus hands that prove it. A working session most weeks, async in between. The proof gets built between the calls, not in them. One partner leads the month; the other two are a question away.

What you get

The written read first, then the proof of concept: a harness wired to your real system, a prototype, the first primitives. Handed over with what your team needs to finish the job.

The work

  • Product discovery
  • Product design & prototyping
  • AI feature integration
  • and more

For scale: a month like this runs well under the fully loaded cost of one senior hire.

Talk through a retainer

“We need one thing built.”

A scoped project

Best when you need a thing built, not a standing relationship: work with clear edges and a finish line.

Fixed price

scoped together · priced before we start

Scope a project

Best for

  • A mess to diagnose
  • A prototype to prove
  • An MVP with a launch date

The moment it turns ongoing, it’s a retainer — and we’ll say so.

How it runs

A week to a couple of months in our process, with working sessions where they help.

What you get

The artifact you scoped, handed over with what your team needs to run it. The fee credits toward whatever comes next.

The work

  • Technical due diligence
  • UX audit
  • MVP & prototype builds
  • and more

“Come work inside our team.”

An embedded team

Best for a bigger org with more roadmap than hands, and for work that belongs inside your environment and your process. When the work can run from our side instead, that’s a retainer.

Billed hourly

20 to 30 hours a week · let’s talk

Talk through embedding

Best for

  • You know what needs building — the missing piece is capacity
  • Work that has to run in your environment
  • Open seats that are slow to fill

It’s how our largest clients work with us today.

How it runs

All three of us in your process — your tooling, your standups, your environment. We bill the hours as they happen; you only pay for the ones you use.

What you get

Shipped product from inside your own team, with senior product, design, and engineering judgment in the room while it happens.

The work

  • Full-stack product development
  • Design systems
  • Legacy modernization
  • and more

Don’t see the shape you’re looking for?

None of these are packages. Tell us where things stand: the budget, the mess, the half-formed idea. We’ll find the shape together.

Come talk to us

The work itself

17 services · 4 disciplines

What every engagement is made of.

Underneath every model is the same concrete work; the model sets how much of it you get and how it’s paid for. This is the whole toolbox, and every engagement pulls the mix that’s most useful for you. That’s what the first call is for.

  • AI strategy audit

    Strategy

    Where AI actually helps your product, and where it’s a distraction.

  • Platform assessment

    Strategy

    Senior eyes on your codebase, architecture, or product direction.

  • Technical due diligence

    Strategy

    The read an investor or acquirer needs before the deal closes.

  • AI enablement for teams

    Strategy

    Working sessions that get your team productive with AI tooling.

  • Product discovery

    Strategy

    Interviews and prototypes that turn a fuzzy idea into a build-ready plan.

  • Requirements & spec review

    Strategy

    An engineering-expert read of a spec before it goes to a build team.

  • Roadmap shaping

    Strategy

    What to build next, what to cut, and what order de-risks the bet.

  • UX audit

    Design

    Where users stall in your product’s real flows, and what to fix first.

  • Product design & prototyping

    Design

    Interfaces designed and tested in real code, not static mockups.

  • Design systems

    Design

    A component system your team can ship with, built into the product.

  • Full-stack product development

    Build

    Features designed, built, and launched end to end.

  • MVP & prototype builds

    Build

    A first version scoped to learn something, built fast.

  • AI feature integration

    Build

    LLM features with evals and guardrails, not just a chat box.

  • Legacy modernization

    Build

    Careful upgrades to the system you have, without stopping the roadmap.

  • Rescue engagements

    Build

    Taking over when a build went sideways: stabilize, then chart the way out.

  • Fractional CTO/CPO

    Leadership

    A senior seat at the table when a full-time hire doesn’t make sense yet.

  • Hiring support

    Leadership

    Role writing, screening, and interviews for the hires that outlast us.

From first call to first month

Whichever shape fits, getting started runs the same three steps.

  1. The call

    Thirty minutes with one of the three of us. You talk, we ask questions. No deck on either side.

  2. The proposal

    A one-page picture of the engagement: the shape, the cadence, the scope, and the price. Take it to whoever else needs convincing.

  3. The start

    Scoped projects usually kick off within two weeks. Retainers open with a three-month start, then run month to month.

Book a call

The questions we’d ask too

Who actually does the work?
The three of us. There’s no bench, and nothing gets handed to juniors. On a $5,000 or $10,000 retainer month, one partner leads with the other two a question away; on a $20,000 month, the engagement gets a dedicated slice of all three.
What happens when priorities change mid-month?
They will, and the retainer is built for it. The fee stays fixed while the queue reshapes around what matters now. No change orders. If what you need starts outgrowing the tier, we’ll say so plainly and reprice it together.
What if we just need a thing built, not a retainer?
Then it’s a scoped project — anything from a week of prototyping to a full MVP, with the price agreed before work starts. It’s also where we steer a mismatch: if the budget says $10,000 a month but the need says delivery, a scoped project serves you better than a stretched retainer.
Why are retainers fixed-price when embedded work is hourly?
Because retainer work happens on our side, a month is predictable enough to carry one flat number. Embedded puts us inside your workflow instead, where the pace isn’t ours to set, so we bill the hours as they happen and you only pay for the ones you use.
What does the three-month start commit us to?
Three months, then month to month with notice. It takes about that long for us to learn your product and for the value to show up in your roadmap. We’d rather lose a sale than sign you up for a month that can’t prove anything.

Wherever you’re stuck, start here.

Book 30 minutes and describe what’s going on. We’ll match it to a shape on the call. If there’s a budget in your head, say it and we’ll tell you what it buys — and if there isn’t, that’s what the call is for.

Book a callRather write first?