Pricing

Three stages, and you can stop after any of them. A week to find out what is worth building, then one project at a time in the order that pays back first, then nothing at all unless you want us to stay.

Book a discovery week I already have a spec

Automation Discovery Week

From $2,000

One week with the people doing the work. We trace real jobs end to end, cost every automation candidate, and hand back five build-ready assets. Team size sets the price because team size sets how long the gathering takes.

A model of how the operation runs today
A clickable prototype
A costed, sequenced roadmap
A written proposal
The hours and cost behind every item

Book a discovery week

1 to 20 people: $2,000
21 to 50 people: $4,000
51 or more: A short call first

Paid when you book. Full refund any time before the gathering starts, and the assets are yours whatever you decide next.

Projects

$6,000 to $18,000 each

We build one process at a time, in the order the roadmap sequenced. Each project is quoted as a project rather than by the hour or the week, so the number you approve is the number you pay. Most clients do two or three in the first few months.

Scoped against the roadmap you already have
Built in your accounts, on your tools
Documented in plain language
Each one pays for itself before the next starts
Stop after any of them

Typical length: Three to six weeks
Priced: Per project, before it starts
Order: Whatever pays back first

The roadmap from your discovery week prices every candidate exactly, so you see each number before you commit to any of them.

Maintenance

Optional

A finished build runs without us, so there is nothing to buy when you start. If you later want us watching it, improving it, or taking on the next process, we agree that when it comes up.

Everything we build is yours
No platform to be locked into
Runs in your accounts if we part ways

Commitment: None up front
Agreed: After a build is live
Scope: Whatever you want covered

We quote this once there is something live to talk about, based on what you actually want covered.

Why it is shaped this way

We do not quote a build before we have looked.

A price given down the phone is a guess, and the guess is always wrong in the direction that suits whoever made it. The week exists so the first thing we build is the thing that pays back first.

The expensive part is finding out, so we made it cheap.

Two thousand dollars to learn whether automation pays back in your business, and you keep the analysis whether you build with us, with someone else, or not at all.

Each project stands on its own.

No sequence you are committed to finishing. Each one is scoped to deliver and pay back by itself, so stopping after the first is a normal outcome rather than a failure.

You own what we build.

It runs in your accounts, on your tools, documented in plain language. Another developer can pick it up, and there is no 2V platform sitting in the middle of it.

Second track

If you already know what you want built

Some work arrives specified. A requirements document, a design, an RFP, or a roadmap from a discovery someone else ran. There is no point charging you to rediscover it, so we skip the week and price the build directly.

Milestones, from the spec

When the specification is solid enough to break into stages, we price each stage and you approve them one at a time. You know the total before we start and you can stop at a milestone boundary. This is the right shape for most build-to-spec work, including long ones.

Time and materials

When the scope will genuinely move, which is honest for research-heavy work or a product still finding its shape, we bill for the time spent and report against it. We suggest this only when fixed milestones would mean padding the estimate to cover the unknowns.

Either way we read the specification first and tell you what we think is missing from it before quoting. That part is free, and it is usually the most useful half hour in the process.

Send us the spec

Questions about pricing

Do we have to do the discovery week?

No. It is the right start when you know something is wrong but not which process to fix first, which is most people. If you already have a specification, a design, or a roadmap from someone else, we can price the build directly. See the second track above.

Why is the discovery week priced by team size?

Because the gathering is. Tracing how work moves through a fifteen-person company takes a week. Doing it across forty people means more interviews, more processes and more handoffs to follow, so it takes two. The deliverables are the same five assets either way.

Why price projects rather than by the hour?

An hourly rate makes our speed your risk, and it turns every efficiency we find into a smaller invoice. Pricing the project puts that risk on us. You approve a number, and that is the number, whether the work takes us four weeks or six.

What decides where a project lands in the $6,000 to $18,000 range?

How many systems it touches, how much has to be built rather than configured, and how fast you want it. Wanting it sooner means more people on it, which costs more. Your roadmap prices each candidate individually, so you are never guessing from a range.

Can we stop after one project?

Yes, and some clients do. Each project is scoped so it delivers on its own and pays back on its own. There is no sequence you are committed to finishing and nothing degrades if you stop.

What does maintenance cost?

We quote it once a build is live, based on what you want covered. Most clients do not need it at the start, so there is nothing to buy up front.

We want a six-month product build. How does that work?

That is the second track. We break the specification into milestones, price each one, and you approve them as they come. If the scope is genuinely uncertain we will say so and suggest time and materials instead, because a fixed price on an unknown scope just means we pad it.

Can we pay by card?

The discovery week, yes, on the booking page, and you get a Stripe receipt immediately. Projects are invoiced.

Who owns what you build?

You do. It runs in your accounts on your tools, documented in plain language. If we stop working together it keeps running, and another developer can pick it up. There is no 2V platform in the middle.

Start with the week

One week, five build-ready assets, from $2,000. You keep them whatever you decide to do next, and nothing after it is committed until you approve the number.

Book a discovery week Or book a call first