The Fourteenth / method glyph
Loading the public record
OS-001 / How we work
The front page carries the short answer. This page carries the reasoning: the thesis behind 14th & Co., the method every engagement follows, and the delivery model that makes the work transferable instead of dependent.
01 / Why this exists
Between roughly 50 and 400 people, an operation crosses a line: the way work actually runs — policy, onboarding, decision rights, exceptions, escalation — stops fitting in anyone's head, but nobody has written it down yet. The company keeps operating on memory and proximity. It works until it doesn't: an audit, a departure, a new location, a volume spike.
The common responses buy capacity, not infrastructure. A senior title inherits the fog instead of clearing it. Contractors cover the gap while the knowledge stays temporary. A strategy deck names the work and leaves the team to execute it. All three leave the operating layer where it was: undocumented, unowned, and priced by the next emergency.
The alternative is to treat operations the way engineering treats systems: assess the risk, build the standard, write it down, and hand it over — so the operation survives the people who built it, including us.
Operating thesis
If the operation depends on a person remembering how it works, it is not infrastructure yet.
Every engagement, artifact, and standard 14th & Co. ships is a test of this one sentence.
02 / How every engagement runs
Stabilize → Standardize → Scale is not a slogan; it is the build order. Each phase produces a named artifact and ends on a condition, not a date.
One line, four crossings — Stabilize / Standardize / Scale / Transfer. The 14 is the method.
P-01
Stop the active bleeding.
Sort out what's actively at risk: compliance gaps, broken intake, payroll exceptions, decisions with no owner. The work nobody has had room to do gets a priority order.
Produces
The Infrastructure Read — a priced map of what's at risk and the order for fixing it.
Exit condition
Nothing on fire is unowned.
P-02
Document the working version.
Operating standards, playbooks, decision rights, escalation paths, review cadence. The version of the work that survives contact with a new hire.
Produces
The Operating Standard — the reference copy of how the work runs.
Exit condition
Two teams doing the same work do it the same way, verifiably.
P-03
Make it survive volume.
Readiness models, scorecards, meeting rhythms, and the org structure that lets the standard hold under growth instead of depending on the people who wrote it.
Produces
The Transfer System — manuals, templates, and rhythms your team operates without us.
Exit condition
The system holds under new volume, new hires, and our absence.
Transfer is not a fourth phase we sell separately. It is the exit criteria of the whole sequence: the engagement ends when your team runs the system without us.
03 / How we deliver
D-01
The person who scoped the work builds the work. You are never handed off to a team you didn't meet.
D-02
Nothing is priced until it has been read. The Infrastructure Read is free, arrives in 48 hours, and carries no pitch.
D-03
Engagements are priced by infrastructure scope with explicit boundaries and explicit ends. The meter is never running.
D-04
Automation carries the repeatable work — documentation, monitoring, pattern detection. Judgment stays human and named.
D-05
A small number of concurrent engagements, on purpose. Depth of build over breadth of book.
D-06
Every engagement is designed to make itself unnecessary. Transfer is not an upsell; it is the exit criteria.
Out of scope — so you don't waste a charter
If your charter lands on this list, the read says so directly — no pitch, and a pointer to where to go instead.
You own it. It stays.
Next step / 48 hour read
The charter walk takes a few minutes and starts the read: where the exposure sits, what gets built first, and what it costs.
Get your infrastructure read