The studio
Work we're hired for, and work we publish ourselves
Filed by the studio · engineering & product
“Ship the boring infrastructure before the flashy feature.”
We take client briefs and we ship our own products. Client work pays for testing, monitoring, and documentation. We run those habits on our own products first, on our own users, before they show up on someone else's roadmap.
What holds up under a client's traffic goes into how we build for ourselves. Shortcuts we wouldn't give a client don't last on our own on-call either.
Fewer decks, more running code. After launch we stay on the plumbing.
Practice
Product engineering
Surfaces
Web · mobile · cloud
Engagement
Project or retainer
Work
Client software & our own products
What we build
Client workClient work covers the full stack of a platform. Most engagements touch more than one of these.
- Web & mobile apps
- Browser and native interfaces, built to a client's brand and shipped to their users.
- APIs & integrations
- Services, webhooks, and the third-party connections that have to keep working.
- Cloud infrastructure
- Environments, pipelines, and the account and access hygiene underneath them, built so a client can run it without us.
- Data plumbing & operational tooling
- Migrations, jobs, admin panels, dashboards. The tooling that keeps a platform operable after launch.
- AI processes & integration
- Models wired into the systems a company already runs: workflows, tools, and the joins between them.
How we work
4 stagesListen & scope
Workshops and audits to find the shape of the problem before we write it as code.
Design & architect
Systems, interfaces and data models, sketched and argued over before we start building.
Build & ship
Iterative delivery in pieces small enough to review properly and reverse if one of them is wrong.
Operate & support
Monitoring, on-call, and the slow accumulation of fixes after launch.
Our own products
The shopAlongside client work, we design, build and run a small shop of our own SaaS. No names on this page. The products started as software we needed, and stay small enough that we still answer the support email.
Client work has deadlines and users who aren't us. Our own products have renewals, edge cases, and the 3am page, because we live with them.
- Scope
- We keep a small shelf, and we still run what we ship.
- Dogfooded
- We run our own products first. If something breaks, we get the page.
- Funded by the practice
- Client work pays the bills, so the shop answers to users.
Get in touch
One inboxGot a brief, a platform that needs work, or an AI process to stand up? Write to us. There's no form.
hello@bnc.rocks