Loading
Loading
Six steps, every project. The pipeline is what lets craft scale across very different briefs — a textbook, a remediation programme, an LLM rollout — without losing the thread.
98%
On-time delivery
1 wk
Discovery to signed brief
5 day
Sprint cycle
30 day
Post-launch care window
The same six phases every brief moves through — written down so nothing falls between the cracks.
01
Step 01
Listen first, scope second.
We start with a working call to understand the goal, the audience, the constraints, and the deadline. No deck, no theatre — just questions, written notes, and one direct answer at the end: yes, we can help, and here is what it looks like.
02
Step 02
Write it down. Sign it off.
Every project gets a written brief that names the deliverables, the success metric, the timeline, the named owners on both sides, and the budget. Nobody builds anything until both teams have signed off. This single step prevents almost every horror story you have heard about creative work.
03
Step 03
Two or three real directions.
We come back with two or three distinct directions — never three variations of the same idea. Each direction is fully thought through so the choice is real. You pick, we refine.
04
Step 04
Production with weekly demos.
Production runs in week-long sprints with a demo at the end of every sprint. Scope changes get logged, costed, and signed before they happen — never quietly absorbed. You see progress, you see decisions, and you never get surprised at the end.
05
Step 05
Ship, train, hand over.
Launch includes whatever the project needs: print files to the printer, ebook to retailers, app to the store, brand to the team. Plus training, documentation, and a written handover so the people who inherit the work can keep running it.
06
Step 06
Stay close after the launch.
Every project comes with 30 days of post-launch care: bug fixes, copy tweaks, retailer escalations, anything that surfaces in the first month. After that, we offer retainer or on-demand support — whichever fits.
The cadence you can plan a quarter around. Every project sprint runs on the same Monday-to-Friday rhythm.
Mon
Sprint kickoff
Plan the five-day scope and unblock anything sitting on your side.
Live check-in
Tue
Working day
Heads-down production on the named lead's queue.
Wed
Mid-sprint check
Quick walkthrough of what's shaping up, course-correct if needed.
Live check-in
Thu
Working day
Polish, edit, integrate, prep the demo build.
Fri
Sprint demo
Live walkthrough of the working artefacts. Written notes by EOD.
Live check-in
The behaviours we deliberately design the pipeline to prevent. Worth saying out loud.
Sales decks instead of working artefacts
Mystery scope creep absorbed quietly into the invoice
Email-only briefs with no signed scope
Black-box production with no demo until launch day
Shared inboxes you have to chase for a reply
Estimates that turn into bills 40% bigger at the end
Process is only as good as the principles underneath it. These four are non-negotiable.
01
Every project has a written brief and a written schedule. No project gets to the build phase on a verbal agreement.
02
Whatever stage the project is at, you see progress every week. Nothing disappears into a black box.
03
Every project has one named lead on our side. You always know who to email; we never hide behind a shared inbox.
04
If scope expands, we write it up and price it before we do the work. If it shrinks, we credit you. No silent invoicing.
Studio bench
The pipeline runs on whatever each practice needs — editorial software for publishing, OCR engines for digitalization, screen-readers for accessibility, model APIs for LLM consulting. No tool zealotry; we use what gets the work shipped.
Specific to how we run a project — for the questions that the global FAQ doesn't cover.
Every scope change gets a written change order — the new work, the new price, the new schedule, signed off before we touch it. No silent invoicing, and no quiet absorption that comes back as a bill at the end.
Your named decision-maker, our named project lead, and anyone they each want to bring. We run it on Zoom or Meet, 30 minutes, working artefacts on screen — not slides about working artefacts.
Stop whenever. We close out the current sprint, hand over what's built, and the brief stays on file. When you're ready to resume, the named lead picks it back up with full context.
The named lead stays on after launch for 30 days, fielding bug fixes, copy tweaks, retailer escalations, and small adjustments at no additional cost. After day 30 it's a retainer or on-demand work — whichever you prefer.
Yes, if you have one. We default to Linear for engineering work and Notion for editorial / design, but we'll join your Jira, Asana, or Monday workspace if that's where decisions live.
One senior on our team owns the project end to end — your only point of contact, signs off every deliverable, joins every demo. You never have to chase a shared inbox or wonder who's on what.