Who we are
and what we're building.

We care how it reads and how it looks, down to the words on a page and the shape of a migration. When something is not right we fix it rather than file it. Taste is most of what a small team has to offer, so we spend it carefully.

We would rather sit inside someone's actual workflow than read a requirements document about it. At our size every customer conversation reaches the people writing the code, usually the same week. When something breaks for you, that is what we are doing that day.

Two people set each other's standard. We show each other the version we are slightly embarrassed by, early, because the alternative is polishing alone and calling it progress. Most of the good work here started as somebody else's half-finished idea.

We build for where this is going, not only for where it is. Models, prices and providers will keep moving, so we would rather design for the change we can already see coming than optimise for the arrangement that happens to hold today.