Named for the spine of a play.
Stanislavski gave actors a term for the thing that keeps a performance from collapsing into a sequence of unrelated scenes. He called it the through-line of action: the spine running the length of the play, connecting every moment on stage to the purpose of the whole.
A company has exactly the same problem and rarely names it. Work happens in scenes. People arrive, learn what the work actually requires, and leave with it. What remains is a folder of documents and nobody who remembers why any of the decisions in them were made.
Throughline is the spine. One brain that every product reads from and writes back to, so a lesson learned on a Tuesday is available to every system, in every account, by Wednesday. It is not a wiki and not a folder. Nobody has to remember to go and look at it, because the things doing the work are already inside it.
It is deliberately unglamorous. Most of what it holds is the residue of ordinary work: what was tried, what it cost, what broke, and the rule that came out of it.
Theatres leave a single bulb burning on the empty stage overnight. They call it the ghost light. It is the one thing still on after everyone has gone home.
Questions the brain has recorded and cannot yet answer. We count them on purpose. A system that only tracks what it knows will quietly tell you it knows everything, and the number that matters when you are deciding whether to trust one is the other number.
Twenty-one AI employees.
One reporting line.
Not a swarm of prompts. A named organisation with rank, division and an escalation path, every one of them reading from and writing back to the same brain. When one of them learns something, none of the others has to learn it again.
Owns the relationships, the government liaison, and the final call.
Routes every request to the right specialist and holds the definition of done.
Delivery
Takes a signed engagement and makes it a shipped thing.
- OttoDelivery producerSequences the work so no handoff gets dropped between specialists.
- ShaunSpecTurns a request into testable acceptance criteria before anyone builds.
- JayEngineerBuilds anything stateful or secure, through an eight-gate harness.
- DhruveshWeb developerDesigns and builds a marketing surface end to end in one pass.
- DexDesignerStudio-grade visuals with a point of view, never a template.
- CherylCXAudits the real rendered product and ships the fix with proof.
Quality & R&D
Proves it works, proves it is safe, and finds what would make it better.
- QuincyQA managerScopes the testing, challenges weak passes, rolls up the verdict.
- RiaTesterRuns the acceptance suite and reports evidence, not impressions.
- MaxSecurityHardens against the real methodologies before an external audit does.
- FelixOptimiserAudits the office for leverage and argues for subtraction first.
- TitiResearcherScouts and vets what would make a given specialist better.
- LuckyDataGuards the record and reads the numbers bad news first.
Marketing
Builds the demand and makes the work findable.
- AmosCMOSets the positioning, the channels, and the demand engine behind the number.
- HappyWriterWrites proposals and long-form to the assessor's rubric, never to a word count.
- KimiSEOWins the ranking and the citation, on Google and in the answer engines.
- NicolePublisherReformats per channel, queues it, and gets it out on time.
Sales & Customer Success
Opens the relationship and keeps it healthy.
- MashySalesQualifies, pitches, handles objections, closes what can honestly close digitally.
- KokoCustomer successReads account trajectory and calls the save before it goes red.
Strategy & Finance
Decides which bet to make and whether the numbers survive it.
- DanielBusiness advisorPositioning, pricing, and the honest build-or-kill call.
- MarcusCFOBottoms-up models and unit economics, with every assumption named.
New know-how enters once.
Every product has it by morning.
Throughline is not sold to you directly. It sits underneath the products that are, the way a component brand sits underneath the machine it makes possible. Each product keeps its own name, its own site and its own customers, and carries a small mark back to here.
- Step one
A lesson is learned
Once, by one employee, on one job, in one account. Usually the expensive way.
- Step two
It is written into the brain
Not into a document that someone might read. Into the memory every system already reads from.
- Step three
It is pushed down to every tenant
Every product, every account, at the same time. Nothing was rebuilt and nothing was released.
A conversational front office
Answers, qualifies and books in the company's own voice, at any hour.
TenantsAn onboarding and training system
Turns what the company knows into how a new person learns it.
TenantsA compliance evidence vault
Keeps the proof, and knows which proof is still missing.
Tenants
No redeploy. No version bump. No migration, and no customer asked to upgrade anything. The products did not change. What they know did.
A dozen things it learned the hard way.
A brain is only worth having if you can see what is in it. These are sanitised: the rule survives, the client does not appear. Every one of them cost something to find out, and none of them has to be found out again.
Decisive evidence
Decide with enough evidence, not all evidence. The job is to call it, not survey it.
Spec is the contract
The spec's acceptance criteria ARE the tester's test scenarios ARE the engineer's definition of done. If it's not in the spec, it isn't built or tested.
Zoom-inspect images
Always zoom-inspect generated images for stray on-screen text before wiring them in.
Real over stock
Prefer real product or screens over stock illustration. When you must use stock, pick one whose colour matches your accent.
Force a fresh deploy
After adding an environment variable, force a fresh deploy. The build cache will serve the old version if you only add the variable without a code change.
CI trigger paths
Test CI on a real pull request, not just on push. The two triggers run different code paths.
Know your gate
Know exactly what your gate does and doesn't cover. State the unverified bits out loud, don't let a green check launder unverified work.
License discipline
Avoid a copyleft-licensed component for anything embedded in a commercial product; prefer permissively licensed alternatives.
Independent reviewers
Multiple independent reviewers beat one. A functional tester, a design-system reviewer, and a CX reviewer each catch a different class of bug.
Key on provider ID
Key external identities on the immutable provider ID, never auto-merge accounts on an unverified email.
Contextual escaping
Escaping is contextual at every sink. Any place autoescape is turned off needs its own sanitizer.
Find the real ceiling
When entering a crowded lane, look for where the real ceiling actually is before competing on the feature everyone already ships.
If your organisation is losing
what it knows.
A brain can be seeded rather than started empty, which is the difference between a system that is useful in a year and one that is useful in a week. Write and describe the situation. If it is not worth doing, we will say so, which is cheaper for both of us than finding out later.
No form, no tracking, no newsletter. This site sets one thing in your browser and it is which theme you picked.