No client testimonial yet. I am not going to invent one.
You are considering a serious amount of money and the usual reassurance is not available. So here is everything else: builds you can test yourself right now, the standard my work has to pass, and the paperwork you would receive.
The position, stated once, plainly.
Nobody has finished a build and gone on record yet. Everything below is what stands in the meantime, and none of it requires you to trust me.
Use an anonymous quote.
A testimonial with no name attached is not evidence of anything. At this price it reads as invented, and it usually is.
Say "clients" while it is one.
Plural language before it is true is the cheapest lie on the internet and the easiest one to catch.
Show logos I have not earned.
No "as featured in", no tools I merely use displayed as if they endorsed me, no borrowed credibility of any kind.
Hand you things you can check.
Something to test, a standard to hold me to, and the paperwork you would receive. Those are stronger than a quote anyway, and they are true today.
The first kind of evidence: test it yourself.
Four builds are running. Not recordings of a demo environment, the actual thing, answering.
Send a message in and watch what comes back.
The front desk answers, asks the qualifying question, offers two real times and books one. Soma takes a single entry into four places. Som runs offline on a real phone. The operations screen holds status, owner and a dated next move.
A buyer who tests something trusts it more than a buyer who reads a quote about it.
The second kind: the standard my work has to pass.
Published in full on the method page, not summarised into a promise. Six checks, every build, before anything reaches a customer.
Six checks, and a launch that moves if one fails.
Almost nobody publishes the standard their own work must meet. Doing it means you can hold me to it, or hand it to whoever you hire instead of me.
The third kind: the paperwork you would receive.
Ask for any of these before you commit to anything. A provider who cannot produce them on request has not built them.
The scope of work
Line by line, per role, with what is included, what is not, and the acceptance criterion that decides whether each one is finished.
Commercial terms
Milestones, change orders priced before the work, ownership, termination, and what happens to your money if I walk away.
The responsibility split
One page saying who does what, so neither of us assumes the other is handling something.
The risk register
Including the risk you are too polite to raise: what happens if I disappear mid-build. In writing, with the mitigation beside it.
The weekly status report
What moved, what is next, what I am waiting on from you, and whether the date changed. Every Friday, including the quiet ones.
The data handling page
Where your data lives, what access I hold, what I keep, for how long, and what you can revoke at handover.
I run all of this on my own business first.
The site you are reading, the free tools on it, the capture app, the content system behind the notes, and the operations screen I work from. Built the same way, tested against the same six checks, living in accounts I own. If the method did not survive contact with a real business, it would have failed on mine before it reached yours.
Hospital systems, before any of this.
Front desk, human resources, building the forms the organisation ran on, performance improvement for a healthcare system, and helping hospital systems go live with Epic. This is the same work at a smaller scale, for businesses that never had access to it.
What gets published the day there is a result.
Written down now, so the standard is set before there is any incentive to lower it.
A name, or nothing.
The business named, the person named, their words unedited. If they would rather not be named, the result does not go up.
Numbers they gave me.
Not modelled, not estimated, not extrapolated from a sample of one. If the client did not say it, it does not appear.
Approved wording, in writing.
They read the exact sentences before publication and confirm them. That is already how the proof page works.
Asked at day thirty, not day one.
On launch day a client is relieved. A month in, they have a story with a number in it. The second one is worth ten of the first.
Three founding places exist at a reduced rate in exchange for exactly this: a named testimonial, once the build has been running.
Judge it on what you can check.
Test a build, read the standard, ask for the scope and the terms. If any of it does not hold up, you have lost nothing and you will know something useful about every provider you talk to next.