Pricing
A price you can put in a budget. Not a discovery call.
Three ways we price, pilots, pods and product licences. Tell us the workflow you want fixed and you get a scoped range in two business days, with the assumptions written down.
How we quote
We quote against a measured outcome, hours saved, errors removed, cycle time cut, and we write the assumptions next to the number so you can argue with them.
business days to a range
workflow to start
code in your accounts
Engagement models
Pick the shape first. The number follows.
Most operators start with a pilot, move to a pod once the number moves, and licence a product where we already built one.
Fixed scope
Proof pilot
One workflow, one measurable number, a working system on your data at the end of it.
3 to 5 weeks
- Single workflow in production
- Baseline and after measurement
- Your stack, your data, no sandbox
Monthly
Forward deployed pod
Engineers sitting with your operators, shipping into the live operation every week.
Rolling, 3 month minimum
- 2 to 4 engineers plus a lead
- Weekly release into production
- Runbooks and handover as you go
Licence
Platform and product
Our shipped products, e-signature, construction management, IoT gateways, priced against what you sign, build or monitor.
Annual
- Seat or usage based
- Implementation quoted separately
- Support and SLA included
Ranges are typical starting points for US engagements. Regional teams in Canada, Lithuania and India change the blend, and the quote.
What moves the number
Four things, and none of them are logos.
How messy the data is
Clean warehouse tables price differently than 40 years of PDFs, scans and tribal knowledge. We look before we quote.
How many systems it touches
One ERP is a line item. An ERP, a WMS, a telematics feed and a paper process on the floor is an integration plan.
Who has to trust the output
An internal assistant and a system that signs off on a shipment carry different evidence, audit and review costs.
How fast you need it live
A twelve week runway is cheaper than a six week one. Compression costs people, and we price it honestly.
In every price
- Discovery on site or on a call with the people who do the work
- A written scope with the number, the assumptions and what is out
- Source code and infrastructure in your accounts from day one
- Weekly demo, weekly release, no invisible months
- Runbook, handover and training before we step back
Quoted separately
- Licences you buy directly, cloud spend, third party model usage
- Change requests that move the measured outcome, quoted before we start them
- Hardware, field devices and shipping on IoT builds
What the money bought
Numbers from operations we have already priced.
Packing list build time on a live factory floor, from 4.5 hours to 25 minutes.
Mismatch complaints after the first pilot shipped into production.
Weeks from kickoff to the first release running in a customer account.
Request pricing
Send the workflow. Get the range.
The more you tell us about the systems and the people involved, the tighter the number comes back. Product research, competitive evaluation or scope planning all count as a good reason to ask.
Do you publish a rate card?
We publish the shape, not a single hourly number. Pods are priced by team size and duration, pilots by scope, products by seat or volume. Tell us the workflow and you get a range the same week.
Can we start small?
Most engagements start as one pilot on one workflow. If the number does not move, you stop there and you keep the code.
Who owns what we build?
You do. Repositories, infrastructure and models live in your accounts. There is no platform lock and no per-seat toll on your own workflow.
How fast can you give a number?
Two business days for a range, about a week for a written scope once we have seen the systems involved.
Rather talk it through before you ask for a number?
Thirty minutes with an engineer who has shipped this kind of system, no slides.