A conversation, 45 minutes

The people on this call know operations — how work arrives, who touches it, and at which step it stops being predictable — and they can commit to what happens next without taking it back to anyone.

If a question needs somebody else, the engineer who built the matching or whoever knows a particular integration, we bring them onto the call while you are still on it. The point of the forty-five minutes is that they end in an answer rather than in a follow-up.

Your process, as it actually is. Not the diagram of it. Where the work arrives from, who touches it, and at which step it stops being predictable.

Your real documents, if you have them to hand. We open two or three on screen and read them the way the system would. This is usually where the conversation gets specific.

Where our approach fits, and where it does not. We build in six steps — intake, structure, decision, exception, write-back, record — and we will say plainly which of them your problem actually needs.

The six steps ›

Within a few days you get our reading of it: what we would build, in what order, what the first working piece would be, and what it would take to get there.

If the scope is clear enough, that comes with a price. If it is not, it comes with the one thing that would make it clear — usually a paid review of a single flow, 3 days to 2 weeks, credited against the project.

Package prices are on the site. Work that is not a package is priced after the review, because a number produced before anyone has read your systems is a guess — and the person who guesses low delivers a worse system rather than a cheaper one.

Pricing · How we work

And we keep to them. If we finish in thirty, we finish in thirty.