Services

Four ways we can help.

We keep engagements small, senior-led and time-boxed. Whether you need a full application built, a CLI that doesn't embarrass your team, or a second opinion on a decision you're stuck on — here's what that looks like.

01 / 04

Web applications

3–6 month engagements

We build long-lived business applications in Go and TypeScript — the kind of systems that outlive roadmaps, migrations, and the people who originally scoped them.

→
Architecture & data modelDocumented, reviewable, and paired with the trade-offs we considered.
→
Production-grade codebaseTyped end to end, tested at the seams, deployable from day one.
→
Ops runbookDashboards, alerts, and the exact queries to run when something breaks at 3am.
→
Clean handoverTwo weeks of pairing with your team so the knowledge doesn't leave with us.
Discuss this service →
02 / 04

Developer tooling

4–10 week engagements

Internal CLIs, build pipelines, and platform glue that your engineers actually enjoy using. Tools are a force multiplier — they deserve as much craft as the product they support.

→
Needs assessmentA day of pairing with the team that will live with this thing. No tool designed at a distance.
→
Single-binary CLI or serviceCross-platform, signed, distributed via the channel your team already uses.
→
Docs that get readExamples first, reference second. Written by the person who wrote the code.
Discuss this service →
03 / 04

Open source packages

Ongoing, funded by the studio

We extract the genuinely reusable parts of client work into open source packages and maintain them in public. Our clients get a better codebase; the ecosystem gets a battle-tested library.

→
12 maintained packagesAcross Go and TypeScript — collectively downloaded 2.4M times a month.
→
Semver we meanBreaking changes are rare, announced, and accompanied by a migration guide.
→
Sponsorship tierFor companies whose business depends on a package staying healthy.
Discuss this service →
04 / 04

Technical advisory

1–4 week engagements

Architecture reviews, hiring calibration, and second opinions. We come in, spend focused time with your team, and leave a written deliverable you can act on.

→
Architecture reviewA written report with findings, trade-offs and prioritised recommendations.
→
Hiring calibrationWe run your technical interview loop once, then rewrite it based on what we saw.
→
Second-opinion deep-diveOn a specific decision your team is stuck on. Fixed fee, two-week timebox.
Discuss this service →
How we work

Fixed-fee, written briefs, zero surprises.

01

Discovery

Two weeks, fixed fee. A written brief, architecture sketch, and honest go/no-go.

02

Kickoff

We embed. Shared Slack, shared repo, daily progress notes. No status meetings.

03

Build

Weekly demo, open repo, continuous deploy to a staging environment your team can break.

04

Handover

Two weeks of pairing, a recorded walkthrough, and a 90-day bug-fix warranty.

Selected work

A few things we've shipped recently.

dashboard mock
Web application2025

Vellum Health — billing pipeline

Rebuilt a claims pipeline in Go. Six weeks from first commit to production cutover.

6weeks
99.98%first-pass
−62%manual work
CLI screenshot
Developer tooling2025

Cartograph — deploy CLI

A single-binary CLI that replaced eleven legacy scripts and onboarded every new hire in a day.

11→1scripts
<50mscold start
1.2kuses/wk
migration log
Infrastructure2024

Lumen Data — Postgres migration

Zero-downtime migration of a 4TB Postgres instance to RDS — and a toolchain the team still uses.

0sdowntime
3×faster
MIToss tool
report excerpt
Advisory2025

Ataraxia — advisory

Two-week architecture review. Found the bottleneck; proposed three fixes; they shipped the cheapest one.

2weeks
3×throughput
1report
FAQ

Questions we get often.

Do you work with equity instead of cash?

No. We run as a services business — fixed fee, fixed scope, fixed timeline. If your project needs equity financing, it probably needs a co-founder more than it needs an agency.

Can you work with our existing team?

Yes — most of our engagements are embedded. We review code, attend planning, and leave behind a team that understands the new code as well as we do.

Will you sign our MSA?

Usually, yes. We have a short studio MSA we prefer, but we're happy to negotiate. We won't sign anything that bans open-sourcing non-proprietary components.

Do you offer retainers?

Rarely. Retainers select for sitting around; we'd rather ship a thing, leave, and come back when there's a new thing.

Where are you based?

Distributed across Europe and the Middle East. We run on overlapping 09–14 UTC core hours and will travel for kickoff if it helps.

Booking Q3 2026

Ready to talk specifics?

Send us a brief →