Where to start

Start with one thing.

You have one problem you can name. A system you own does not reach what the business actually needs, and you want that built — without hiring a product team first, and without buying a roadmap to find out what to build.

What month one delivers

The first month goes to the outcome you named.

The plan

What gets built, in what order, with a duration and total-cost estimate. Those numbers are stated at day 30, by people who have been working inside your systems, rather than guessed at in a sales call.

The first working piece

The thinnest end-to-end slice of the thing you named, running in your own environment, where you can use it and judge it.

The decision

What happens next, decided with the plan and the working piece both in front of you.

After month one

One relationship. The price follows how much is going on.
  • The build carries onMonth two works the plan, on the same subscription at the same Build price. There is nothing to re-sign and no second contract to negotiate.
  • Then Care, once it is liveSoftware is never done. Once the thing we built is running in production, the subscription can dial down to Care: monitoring and alerting, dependency and vendor-API updates, business-hours incident triage, and small fixes inside a bounded monthly allowance. Care is quoted per system.
  • And back up for the next thingWhen there is a next thing worth building, a build month comes back on at the Build price. Work larger than the Care allowance is that, rather than an overage or a change order.

A Care month runs to a lighter standard than a build month and says so: alert-driven rather than calendar-driven, inside business hours, with one written note each month. It attaches to a system we shipped to production, so it is never a way in, and it is not a support desk — your team keeps the support queue.

What it costs, and what you are committing to

Starting with one thing does not change the price or the paperwork. This is the Build subscription, entered by a company with one outcome to build instead of a standing queue.
Build
$10k per monthSomeone on your side keeps priorities clear and answers questions.
Term
A 90-day initial term, then month to month.Long enough to plan a quarter, ship against it, and see whether it worked.

First 30 days

Something real in 30 days.

Build and Guided start differently. Both aim for one agreed milestone you can see and judge by day 30.

Build

We start with the first priority from the queue you already have.

Guided

We use the first part of the 30 days to find and shape the highest-leverage first move.

By day 30

The agreed milestone is working and can be judged against the pass test in your SOW.

If we miss the agreed milestone for reasons within our control, choose ten business days at no charge or end the engagement with your first month refunded and nothing further owed.