You shouldn't need a call to find out whether you can afford us.
Fixed scope, fixed price, quoted before we start and unchanged afterward. We don't bill hourly and we don't send change orders for things we should have caught in scoping.
What things cost
Full operations build
Several sources joined into one operational view, with role-based access, alerts and reporting on top. Scoped and quoted individually.
90 days of fixes
Milestone billing
Two or three builds
Systems that share plumbing, usually intake, follow-up and tracking. Cheaper than buying them one at a time, because the connectors only get built once.
60 days of fixes
30 / 30 / 40
One build
One job taken over end to end, made for your systems and your formats. The usual way in, and the fastest thing to prove.
30 days of fixes
30 / 30 / 40
Two of us, three builds at a time. That's the whole company, which is why you always talk to the person writing your system, and why we sometimes can't start when you'd like. We'll give you the real date rather than the one you want to hear.
Ways to pay less
Combine builds, or let us tell your story. Discounts stack.
Bundle builds
Builds that share plumbing cost less together. The second build is 20% off and the third is 30% off, because the connectors only get built once.
Be a case study
Take 10% off any project if we can publish your company name, the problem and the results on our site once it's live. You approve every word before it goes up.
Come back later
Add another build within six months of going live and it still gets bundle pricing, as if you'd bought them together.
What actually moves the number
Not hours. Four things, and you can usually guess where you sit on each of them before we ever speak.
How messy the input is
The single biggest driver. Reading a web form is not the same job as reading forty dealers' PDFs, photographs of handwritten sheets, and forwarded email threads. The same agent can be a two-week build or a four-week one depending on nothing but this.
How many systems it touches
Every system it reads from or writes to is another connector, another set of edge cases and another thing that can change underneath us. The first two are included in every build.
Whether anything lacks an API
A legacy ERP, a portal that only works through a login, or a system whose only output is an email. All workable, all slower, and we price that honestly instead of discovering it in week three.
How much judgment is involved
Moving a field from one place to another is cheap. Deciding what to reorder, netting what's already inbound and applying each vendor's real lead time is not. The second one is where the money actually is.
What's included
| One build | Two or three | Full build | |
|---|---|---|---|
| Free audit and written plan | Yes | Yes | Yes |
| Data sources connected | 1–2 | 2–4 | 4–8 |
| Writes back to your systems | Yes | Yes | Yes |
| Human approval step | Always | Always | Always |
| Written acceptance criteria | Yes | Yes | Yes |
| Role-based views | No | No | Up to 4 |
| Alerts and thresholds you control | Basic | Yes | Full rules engine |
| Works on a phone | Where it matters | Yes | Yes |
| Team training | 1 hour | 2 hours | Half day |
| Documentation at handover | Yes | Yes | Yes |
| Post-delivery fixes | 30 days | 60 days | 90 days |
| Monthly support plan | Optional | Optional | Optional |
| You own the code and the data | Yes | Yes | Yes |
Running costs are yours, and they're small. Everything runs in your accounts under your billing: the automation platform, the model usage, the database, the hosting, the texting. Together that's typically $40 to $180 a month for a two or three build system. You get an estimate with a ceiling in writing before anything gets built, and we cap model spend on day one so a runaway process can never turn into a surprise bill. Because it's all in your name, you're never locked to us to keep it running.
After the fix period: the support plan
Systems connect to other people's software, and that software changes. The support plan keeps yours running when it does.
Support plan
- We monitor it and fix breakages, even when the cause is on someone else's end: a vendor changes their API, a login expires, a supplier changes their PDF layout
- Up to 2 hours a month of small changes, like a new field, a new report or a new rule
- Reply within one business day, and your fixes go to the front of the line
- A monthly check-in on what ran, what it caught and what to improve
- We watch model and API spend so there are no surprise bills
Without a plan
- If something we built doesn't work as agreed during the fix period, we fix it free, plan or no plan
- After that, if something breaks because another tool changed, we fix it at $150 an hour in 30-minute blocks, and tell you the estimate before we start
- Scheduled around plan clients, usually within three business days
- Everything is documented and runs in your accounts, so any developer can work on it
Payment, and how you get out
Two of us and a fixed price only works if both sides know exactly where they stand. So here it is.
30 at kickoff
Paid after the free audit, once you've seen the written plan and the fixed number. It books the calendar and starts the access setup.
30 at the proof checkpoint
End of week one, when your own real data is visibly moving through the system. If it isn't, you stop here and owe nothing further.
40 at go-live
Released when the acceptance criteria written into the scope are met. Not when we say it's done, and not when it feels done.
The week-one guarantee. If your real data isn't flowing through the system by the end of the first week, you walk, owe nothing beyond the kickoff payment, and keep the map and everything built so far. What "working" means is written into the scope before anyone starts, in terms you can test, so it's never a matter of opinion. Fair both ways: once the system meets what we agreed, the balance is due.
What the weeks look like
A single build. Larger projects follow the same shape over more weeks. You see working software in week one, not a status update.
Fifteen-minute call
What you sell, where, and which part of the week eats the most hours. If we're not a fit we say so here.
The audit, free
About forty-five minutes with you and whoever actually does the work. You get a written plan, a recommended first build and a fixed number, and you keep the plan either way.
Connect and prove
We wire up the data sources and show you your own real data flowing through by Friday. This is the checkpoint, and the week you decide whether to keep going.
Build the logic
It starts doing the job on real inputs, with you reviewing every output before anything gets sent or written. You tell us where it's wrong and we tune it.
Go live and train
Approval steps set to your comfort level, your team trained, documentation handed over. Then you watch it for a week before you trust it, which is correct.
30 days of fixes
Anything behaving wrong, we fix at no cost. Not new features. The thing we agreed on, working the way we said it would.
The questions we actually get asked
How does this price against what it's worth to me?
What if it doesn't work?
Will it send something embarrassing to my customers?
Do I need to replace my ERP or my job software?
What do you need access to?
My data is messy. Is that a problem?
Can I get a discount?
Who actually does the work?
What happens after the fix period ends?
What happens if you disappear?
Get a real number
The estimator gives you a range in two minutes. The free audit turns it into a fixed figure that doesn't move afterward.
hello@charidan.com