Pricing
Published where it's a decision, scoped where it isn't.
You can see two prices on this page. The build isn't one of them.
That isn't evasion. The build gets priced against what the bottleneck costs you, and right now neither of us knows that number. We work it out on the call, in your figures, before I quote anything.
A dev shop would quote you hourly and the number would keep moving. An off-the-shelf tool bills monthly forever and still doesn't know how your company works. This is one fixed number, a working version first, and code you keep.
What you can decide today
Scoping call
Twenty minutes. We work out what the bottleneck is costing you. If it isn't worth building, I'll say so.
Free
Working prototype
Three weeks, running on your own documents. Credited in full toward the build.
If it isn't useful you stop there, and you've spent $3,500 finding that out in three weeks instead of in month five.
$3,500
The half dayOptional
Skip this if you can already name the bottleneck. Most people can. It's for teams who feel the drag and can't point to where it's coming from.
You leave with a written map: every bottleneck, what each costs now, what it costs at 30% more volume, and which to build, buy, or leave alone. Yours either way, including the ones where the answer is buy a tool and don't call me. Not credited toward a build, because unlike the prototype, none of the day's work ends up in the code.
$3,500
$4,500 on site
The build
How the build gets priced.
Not hourly, and not off a rate card. Three things set it, in order.
What it's costing you.
Worked out on the call, in your numbers. Most teams have never added it up.
The smallest fix that moves it.
Not everything you'd eventually want. The piece that shifts that number.
What you can approve now.
If the whole thing isn't in this year's budget, we build the part that pays for itself first.
You get the number at the prototype readout, after you've watched it run on your own data. That's the first point where I know what it takes and you know what it's worth. It's fixed from there.
The monthly
Starts at $600, sized with the build.
What you're buying is not having to run it.
Monitoring, backups, re-indexing as your documents change, and the updates that come with model and API changes. Someone also watches the number we agreed on, so you hear about a problem from a review instead of from a bad month.
It's set at the same readout as the build, so you see both numbers at once.
The terms
Twelve months, then month to month. Thirty days' notice either side. Sixty days before any price change, never during the first term. Thirty days to export if you leave. No cancellation fee.
Where the line is
New workflows, integrations or business rules are new work, quoted the way the build was. Holding the number is included. Setting a new one is a new round.
Model usage is billed to you by your AI provider, at cost, with nothing added by us. All prices plus tax where applicable.
Not on this page
Because you won't be paying it.
- No per-seat license, so the price doesn't grow when you hire.
- No annual license renewal. You own the code.
- No implementation partner billing separately.
- No minimum seat count.
Before you book
Two ways to know this isn't for you.
It's annoying, but it isn't growing.
If this process won't need another person the next time volume climbs 20 to 30%, buy a tool. I'll point you at one.
You need a number before discovery.
I can't give you one honestly. A price set before the problem is measured is a guess with a decimal point in it.
Questions
What buyers ask about the money.
Do you host our data?
We run it. You own it. Those are different things, and the agreement keeps them separate. Your data is yours from day one, not on final payment. You decide what goes in and how long it stays, we act on your instructions and nothing else, and you can export all of it at any time without asking. Your instance and your database are yours alone, never shared with another client. What we provide is the operating: monitoring, backups, updates and re-indexing, so you don't need an IT department to run it. That is what the monthly buys.
Whose account pays for the AI usage?
Yours, on your own account with the model provider. I set it up with you before launch, including the settings that keep your content out of training, and I show you what I configured. Two reasons it works this way. Your content is processed under your contract with them rather than mine, which is the answer your IT team wants. And you see what it actually costs, at cost, with nothing added by me. The prototype and the build run on my account, included in the price, so you don't need to set anything up to get started.
Start with the bottleneck, not the number.
Twenty minutes. Describe what's slow, and we'll work out together what it's costing you. If it isn't worth building, that's a useful answer too.