Blog
Notes from the loom.
How we build Warpyn, what 12,000 questions a day teach us, and guides for teams who want their numbers to explain themselves.
02
All posts
Everything we have written.
Engineering
7 min
240 sources, one spine: why everything hangs from the account ID
Every useful business question joins at least two tools. Here is how we pick the key they all hang from.
Guides
5 min
Thirty definitions that settle most arguments
Revenue, active, churned, expansion. Agree on thirty words and half your data disagreements disappear.
Product
6 min
What we learned answering 12,000 questions a day
The most common question is not about revenue. It is 'why did this number change?'
Security
8 min
Row-level permissions without a second data model
Answers should respect who can see what in the tools they came from. Here is how we do it without copying permissions by hand.
Product
4 min
Pulse: alerts that explain themselves
An alert that only says 'something changed' is a chore. Pulse sends the answer with it.
Engineering
9 min
How we made answers ten times faster
Median time to answer fell from 2.1 seconds to 0.4. Most of the gain came from not asking twice.
One email a fortnight. Only when we have something worth reading.
Engineering notes, guides and the changelog, in one short email.