Three sizes. One builder.

A proven workflow, running on your stack.

We take a workflow we have already built and proven, install it on your stack, and hand it over running. No discovery phase, no custom work, no design cycle. That is what makes it the price it is, and it is the right choice when something we have already built is close to what you need.

If it turns out you need it fitted to how you actually work, that is a Standard build and we will say so before you buy rather than after.

You get the workflow running, a short runbook for operating it, and the managed monthly that keeps it running as the tools underneath it change.

STACK-NATIVE·FIXED PRICE·NO DISCOVERY·NO DECK·PROVEN WORKFLOW

Fitted to how you actually work.

The usual starting point, and the one to pick if you are not sure. We start with discovery: what the workflow really does, where it breaks, who touches it, and what the exceptions are that nobody wrote down. Then we build it, either by fitting a proven workflow to your operation or building the thing from scratch when nothing fits.

The difference from a Starter build is the discovery and the fitting. The difference from a Pro build is that this is one workflow done properly rather than a system spanning several tools and teams.

You get the system in production, a runbook your team can operate without us, a handoff session, and the managed monthly.

STACK-NATIVE·FIXED PRICE·DISCOVERY INCLUDED·NO DECK·THE DEFAULT

A system across tools and teams.

Bespoke, cross-system, and scoped per engagement. We own design, build, integration and handoff across the full surface: every input, every routing decision, every integration the system depends on, and every edge case the team needs handled.

This is the right shape when the work spans several tools and more than one team, and when the thing you are buying is an operating layer rather than a workflow.

Priced per engagement against scope and integration surface, and fixed before you sign. If you want that scope written down and priced before you commit to building it, that is what a Blueprint is for.

See the whole build specced before you commit.

For a larger build you may believe the approach works and still not be able to say what "it" is. A Blueprint is the paid answer to that: we spec the system, and you get the architecture, the sequence it gets built in, and a priced proposal you can take to a decision.

Credited in full against the build cost on contract signing, within 30 days. So the question it asks you is when to build, not whether to spend. If you walk, you keep the architecture and the proposal, which is what you paid for.

Most people do not need this. Pick a Standard build if you know what you want built, and a Blueprint if you are heading somewhere large and need it written down and priced first.

Every build runs on a managed monthly.

Every build runs on the managed monthly, because an unmaintained automation drifts and breaks. The connectors change, the models change, and the tools underneath your workflow ship breaking changes on their own schedule. The monthly is what keeps what we built for you running through all of that.

It is one flat number per account, set by how much we are running for you rather than by how many people use it. Adding people costs you nothing. Monthly starting at $395, and the exact number is quoted once the build scope is agreed, never before.

What it covers: we run it, we keep the system and its connectors current, and we fix drift on what we built. What it does not cover: new workflows, which are a fresh build at their own size rather than an unbounded support line.