06 / Full Stack
One brief for both halves
When operations do not run and the market cannot find you, splitting the work between two suppliers puts the seam between them exactly where the project is most likely to die. Scrub the rail below and watch the inside and the outside run on one brief, so the day it launches it is one company, not two halves pretending to match.
Before you scrub
Why one brief and not two
Two vendors is the bug
The hand-off is where these projects die, and adding a second supplier to fix the first one usually just moves the seam somewhere harder to see.
Same brief, both faces
The site has to describe the company as it will actually run on launch day, because buyers feel the gap between the two long before anyone inside the business does.
Two tracks, one timeline
The inside work and the outside work run off one brief, so neither launches describing a company the other cannot yet back up.
Twin Rail
Inside and outside on one scrub.
Five sample beats across roughly 10 weeks, laid out as one engagement instead of two projects sharing a calendar. Whichever pair of halves is hurting in your business is usually where the brief starts.
Week 1 · Beat 01 · One brief
One diagnosis
One call, one set of notes, and both halves named in the same hour.
Inside · Systems
Systems
I map the retype loops and find the number the room has stopped trusting.
Outside · Presence
Presence
The same morning covers the empty search results and whatever the site is currently claiming.
Scrub or pick a beat — both rails advance together. That is the point.
After the rail
Start from the pair that hurts.
Every Full Stack engagement starts from the two halves you already know are broken, and you almost always do know. From there it is one written brief, one timeline, and one person accountable through to launch and past it.
How it runs
How both halves stay on one brief
5 steps across about 10 weeks, run as one engagement. If what you want is an agency carousel with someone to chair it, I am the wrong person.
Fit
Both broken halves get named in a single call, which is usually shorter than people expect.
Brief
One scope page covering the systems and the presence, signed by both of us before week 3 starts.
Build
The inside ships first, and the outside stays honest about what the inside can actually do.
Launch
Usable and findable inside the same window, so the launch is one event and not two.
Hold
One person stays in the room through both the operations work and the inbound that follows it.
FAQ
Questions about Full Stack
What is Twin Rail?
An interactive sample of a Full Stack engagement. You scrub or step through 5 beats where the Systems track inside and the Presence track outside stay tied to one brief. The weeks on it are illustrative, and it is nobody's live plan.
Do I have to buy both halves?
No, and most people should not. A Systems Sprint or a Distribution Sprint on its own is the right answer when only one half is broken. Full Stack earns its cost specifically when both hurt and the handoff between them is the thing doing the damage.
Will you manage my other vendors?
No. Coordinating a roster of suppliers is a different job from doing the work, and doing both badly is how the seam appears in the first place. Managing your other vendors is not a job I take on.
What if one half finishes before the other?
That is the normal case, and the rail is drawn to show it: the systems work runs from week 3 and the publishing overlaps it from week 5. The constraint is only that neither half launches claiming something the other cannot yet support.
How long is Full Stack?
About 10 weeks, with everything agreed in writing first. The exact shape depends on how much of each half is genuinely broken, which is what the fit call is for, and the answer is sometimes that you only need one of them.