We are two years old and we are telling you that on purpose
Most about pages of companies our size are written to sound like companies four times our size. This one is not, because the thing we are actually selling — that a named person will answer when reconciliation breaks on the last Friday of the month — stops being true at four times our size.
Three things we decided early and have not revisited
Each of these costs us something measurable. That is how you can tell they are real commitments rather than values-page furniture.
First
The person who answers should be able to fix it
Support tiers exist to protect engineering time, and they work — at the cost of putting a translator between the problem and the person who can solve it. We have not hired a tier one, and the cost of that is real: our response times are slower than a scripted queue. We think the trade is worth it and we would rather say so than quietly rank badly on a metric we chose not to optimise.
- Every engineer does one support day a fortnight
- Median first reply: 4 hours, business days only
- No chatbot, no deflection funnel, no ticket deflection target
Second
A finance tool should be boring on purpose
We ship on Tuesdays and we ship small. Nobody wants their reconciliation software to have a redesign the week of close, so the interface has moved very little in two years and most of the work has gone under it. This is the least exciting thing about the company and it is the reason customers stay.
- No breaking API change since launch
- Release notes published before the release, not after
- Month-end freeze: nothing ships between the 28th and the 3rd
Third
We would rather lose the deal than win it by implying
We are not SOC 2 Type II yet. We are Type I, the audit window for Type II closes in March, and every enterprise deal we have lost this year we lost on that line. The alternative was to write "SOC 2 compliant" and let the reader assume, which is what most of this market does, and which would have made the sentence you are reading impossible to write.
- Type I today, Type II expected Q2
- Sub-processor list published, with change notice
- Security questionnaire answered in full before a call, not after
“They were eighteen months old and pre-Type-II when we signed, which my CFO hated. What sold it was that their founder answered the security questionnaire herself, in full, including the three rows where the answer was no.”
- From first call to signed
- 6 days
- From first call to signed
- Questions answered "no"
- 3
- Questions answered "no"
Trusted by support teams at
- Meridian
- Coastline Health
- Fieldstone
The roles open right now
Three of them, which is what a company of nineteen people can absorb in a quarter. If the list is empty by the time you read this, the speculative address below is read by a person.
Engineering2 openings
Nothing that fits? We read every speculative application — hiring@acme.example.
…which is why the migration queues behind the reporting job rather than failing outright. The lock is held for as long as the report runs, and on a large table that can be several minutes.
The safe version is to set a lock timeout and accept that the migration may need a second pass, rather than letting it wait indefinitely and block every write behind it.
About Page 02
The founder’s letter instead of the evidence wall: a byline and a dateline, for a company whose best asset is still conviction rather than a six-year record — and it ends on the job board, because /team is linked from job posts more often than from sales decks.