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
Shared game state across devices in real time. The hard part is correctness under concurrency, when a dropped connection costs somebody money.
Reminder sequences that go out from the client's own accounts, with payment going to the client's own links. The hard part is staying out of the payment path entirely, so we are never the merchant of record and never hold card data.
It tells a person when they are talking to a machine. The hard part is saying it plainly enough that a non-technical reader actually understands what they are agreeing to.
It scores how legible a site is to an automated reader and serves pages back in a clean form. The hard part is deciding what "machine-readable" means while no standard agrees.
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