A studio in two halves, joined by one visible seam

Split the work. Ship the whole.

SPLIT/FORM runs in two modes. FORM argues about what to make. SPLIT writes what ships. The seam between them is where most products quietly die — so we keep it visible, measurable, and moving as you scroll.

Move the seam
Scroll — the seam follows the chapters
← → nudge it from the keyboard
Controls sit in the bar under the footer
It is decorative: the page reads fully at rest.

Two halves that refuse to agree politely.

01 / Manifesto

Left of the seam — FORM

Design that leaves a paper trail.

We argue about the first screen for a week, in the open, with everyone reading the thread.
Every decision keeps a written trace: what we chose, what we rejected, and why.
If it cannot be drawn simply, it is not understood yet — so we keep drawing.

Right of the seam — SPLIT

Engineering that keeps the receipts.

We turn that week of argument into a shipped slice by Friday, tests included.
Every trace becomes a test: the reason a thing exists is the reason it stays.
If it cannot be measured in production, it is still an opinion — so we instrument it.

The seam is not a handoff. It is the same room, with the lights on both sides.

Illustrative engagements, written the way we would write them.

02 / Work

Example · Illustrative — fictional case studies

Example · Illustrative

Fieldnote

A field-survey tool for environmental researchers who work offline for days. We rebuilt the capture flow around one question: what happens when signal returns?

Illustrative 11 weeks to first public release

Illustrative 3 → 1 screens to log a sample

Example · Illustrative

Ledgerhouse

A cooperative bank's internal approvals board. We replaced a 14-step wizard with a single reviewable ledger, and wrote the audit trail as a first-class surface.

Illustrative 42% fewer escalations in pilot

Illustrative 9 days from spec to staging

Example · Illustrative

Northline Transit

A route-planning console for a regional bus network. Dispatchers could not see consequence; we made every change show its downstream effect before it commits.

Illustrative 2.4× faster incident replan

Illustrative 0 mandatory training sessions

All figures and diagrams above are illustrative. They show how we write outcomes, not client results.

What each half actually does.

03 / Capabilities

Research & framing

Two weeks with the people who will use it, the people who will pay for it, and the person who will maintain it at 2am. We leave with a written problem, not a mood board.

Interface systems

Component libraries with an opinion: constrained type scale, one accent, documented states, and a rule for when to break the rule.

Front-end engineering

Semantic HTML first, then only the JavaScript the interaction earns. Performance budgets are set before the first pixel, not after the audit.

Platform & delivery

CI, environments, observability, and a rollback you have rehearsed. We hand over a system your team can run without us in the room.

Four chapters. The seam parks in a new place for each.

04 / Process

Frame

We write the problem in one page, in plain sentences, and read it out loud with the people who own the outcome. If the room disagrees, we are not done framing.

Cut

We remove the half of the scope that would have taken twice as long and delivered half the value. The cut list is part of the deliverable, not an internal note.

Build

Design and engineering work in the same branch, on the same screen, against the same acceptance list. No handoff document, no lost translation.

Prove

We ship to a small audience, measure what we said we would measure, and write down what surprised us — including the things we got wrong.

Bring us the part that keeps slipping.

05 / Contact

Tell us what is stuck between design and engineering. We reply within two working days with a straight answer about whether we are the right studio for it.

hello@splitform.studio

Studio hours 09:00–18:00 UTC
Remote-first · quarterly in-person weeks
New engagements from Q3