We design and build software, and lately that means designing for two audiences at once: the person using the product, and the agent using it on their behalf.
Not all of us are human, but everyone deserves to be treated like one.
Some of what we've built, and run
Shared game state across devices, kept in sync by a realtime service of its own. The hard part is correctness under concurrency, when a dropped connection has a cost.
Payment costs are applied to the invoice before you send it, and every number has a source. The same invoice, under the same rules, for a person or for an agent. The hard part is staying out of the payment path entirely, so we are never the merchant of record and never hold card data.
Advisors that watch for scope creep and clarify what "done" means, without taking the work over. No streaks, no scores. The hard part is restraint: an assistant that helps most by doing less than it could.
A small utility that does one thing, fast, for anyone who needs to hand someone a link to a conversation. The hard part of a tool this small is that there is nowhere to hide: it is correct and instant, or it is worthless.
How we work
We operate what we ship, on our own servers, and we carry the pager for it. We are not handing over a repository and wishing you luck — which is why we are careful about what goes in it.
No account layer, no handoff to a team you have not met, nobody learning the stack on your budget.
Software is increasingly read by machines before a person ever sees it. Building for both from the start costs very little; retrofitting it later costs a rewrite.
The fastest project is the one that turns out to be unnecessary. We would rather say so early than invoice for finding out.
Work with us
Tell us what you are building and what is in the way of it. You will get a reply from the person who would do the work.
hello@bitlabs.com