Engineering7 min read
A log is not an explanation
A complete log tells you everything the system did and nothing about why it did it. The gap between those two is where the hard afternoons go.
Maya Okonkwo
Co-founder & CTO
Writing
Notes on intake that sorts itself
What we have learned automating document and request intake — the extraction failures, the routing rules that aged badly, and the parts nobody warns you about.
Product
Designing guardrails that do not block the work
The failure mode of an approval gate is not that it lets bad actions through. It is that it gets switched off in week three because it asked about everything.
Daniel Reyes6 min read
Company
The audit trail is the product
Enterprise buyers are not asking whether the thing works. They are asking what happens in the room where someone has to explain what it did.
Inès Lefebvre5 min read
Engineering
What a vendor-agnostic core cost us, and why we paid it
Betting on one provider is a bet on their roadmap, their pricing and their uptime. We took the harder path and would take it again.
Daniel Reyes8 min read
Product
What we got wrong about onboarding
We spent a quarter making the first five minutes beautiful. The number that moved was in week two, and it was a documentation problem.
Maya Okonkwo5 min read
Security
Least privilege for identities that are not people
Your IAM model assumes a human on the other end who gets tired, goes home, and can be asked what they were thinking. None of that is true of a machine.
Inès Lefebvre6 min read