How a build actually goes
No discovery phase that bills for a month and produces a slide deck. We map the manual job, quote it fixed, build on a foundation that already works, and prove it against real cases before it touches a customer.
Map
We sit with the person who currently does the job by hand and write down every step, including the exceptions nobody documented.
Scope
You get a fixed-price proposal naming the exact catalogue solution, what we change, what it costs to run, and what it will not do.
Build
We adapt the proven open-source foundation rather than starting from a blank file, then wire in your numbers, wording and systems.
Prove
It runs in staging against real cases. You sign off on transcripts, not on a demo video.
Run
We monitor it, fix it, and change it when your business changes. You get a monthly report you can actually read.
What we insist on
These separate an automation you can run a business on from a demo that impressed someone once.
Your accounts, your data
The platform account is in your name from day one. You own the numbers, the message history and the billing relationship. Nothing switches off if you stop working with us.
Source control and a staging number
Every change is versioned and tested on a staging number before it reaches a customer. Rollback takes a minute.
Consent and opt-out at the core
Consent records, sender identification and automatic STOP handling are built in, not added after a complaint.
Proof, not demos
Sign-off happens on real transcripts from your own historical cases, not a recorded walkthrough.
Monitoring before launch
Alerting exists on day one. If something fails, we know before your customers tell you.
An exit that costs nothing
The foundation is open source and the repository is yours. Taking it in-house means a handover, not a negotiation.
Ready to map the first one?
Thirty minutes on the phone is usually enough to scope it.