From your sent folder to a desk that answers.
About ten days from signature to a live desk. Here is every stage, what it asks of you, and what you own at the end. Nothing on this page is hand-waved; this is the actual delivery pipeline.
-
Kickoff and intake · days 0–2
On the sales call we lock two things: where your team currently asks you questions (email, Slack, drive-bys), and the five decisions you answered most recently. The desk then gets its own front door inside those same tools: a mail alias on your domain and a named channel in your existing Slack. Your team's one new habit is sending the question there instead of to you. Questions that still come straight to you can be forwarded into the desk with one click, so nothing is lost while the habit forms, and the weekly digest counts what routed around it so leakage stays visible.
Then you run the exports yourself, following exact click-paths: sent mail only from the last 90 days, call transcripts from your meeting tools, and the handful of Slack channels where your team asks you things. Read-only, from your own accounts, dropped into an install kit that runs on your infrastructure. You name anything to exclude up front, and a sensitive-pattern filter quarantines legal, payroll, and personnel threads before any mining happens. Budget 45 to 75 minutes of your time.
Why sent-only: your sent mail is where your answers live. Inbound mail is other people’s words. No transcripts? Three ten-minute recorded walkthroughs of recent decisions are the accepted floor, and the interview compensates for a thinner corpus.
-
Artifact mining drafts your codex · days 2–4
The pipeline pairs every question you were asked with the answer you gave, keeps only the decisions, and clusters them into candidate rules: when X happens, you consistently do Y. It also builds two things most owners have never seen about themselves: a contradiction ledger (the questions you answered differently on different days) and a voice profile (how you actually sound, so the desk’s drafts read like you from day one).
Every rule carries provenance: the specific email, chat message, or call it came from. A rule that cannot cite a real artifact is dropped automatically. Rules seen only once or twice are labeled as low-confidence drafts, never silently generalized.
This runs on an API key you create, on your own billing, inside the install kit. Your corpus never leaves your control.
-
The 90-minute interview · days 5–7
The one part of the pipeline that is a person, on purpose. Before the call, the pipeline turns the draft codex’s gaps into an interview guide: the contradictions to resolve, the rules with visible outcomes but unstated reasons, the categories where you answer out loud and leave no paper trail. Jeanette spends the 90 minutes exactly where the mining could not reach.
It opens with something most owners have never experienced: your own last 90 days of judgment, read back to you. The middle hour resolves the ambiguities, case by case, in your own words. The final section asks the question that shapes everything after: what must always reach you, no matter how good the desk gets? Those boundaries can only tighten the guardrails, never loosen them.
-
You review your codex · days 7–9
The interview transcript merges into the codex the same day. Then the review is yours, not ours, and that is deliberate: every rule, one screen at a time, Approve / Edit / Retire, from your phone if you like. Nothing becomes active without one of those clicks, and every click is an answer you will never have to give twice.
The desk cannot go live until you have reviewed at least 80% of the rules, and every single rule in pricing, client communication, and personnel.
-
The desk installs on accounts you own · days 9–10
One templated command deploys the desk: a mail alias on your domain, a Slack channel in your workspace, a small application on your own Cloudflare account (the free tier is enough), storing your codex in your own storage, making AI calls on your own key. Then a scripted smoke test, and a founder check where Jeanette personally sends a real question and reviews the draft for voice and correctness before anything reaches your team.
-
Four weeks of earned trust · then steady state
Week one, everything the desk drafts waits for your one-click approval. Week two, categories with a consistent record are proposed for greenlight, and you promote each one yourself on a 20-minute call with Jeanette. Week three, greenlit categories answer directly, each answer footnoted with the rule it came from so your team is a second safety net. Week four, your first full absorption report. Promotion is never automatic. Demotion always is.
What a standing answer actually looks like.
The codex is a structured book of rules, readable by the desk and by any human you hand it to. Every rule names its trigger, its scope, its exceptions, when it must escalate, and the real artifacts it was mined from. Here is one entry, in the format the pipeline produces. This is the template shape with illustrative values, not data from a client, because there are no clients yet.
id: DX-0042
category: pricing
title: "Rush-job surcharge"
trigger: "Client asks to compress a standard 3-week
deliverable to under 10 business days"
rule: >
Quote the standard price plus 25%. Never waive the
surcharge for new clients. May waive once per year for
a legacy client (>2 years), and only the owner decides
which client gets the waiver.
scope: "Applies to project work only, not retainers."
exceptions:
- "Nonprofit clients: surcharge is 15%, per owner's
2026-03-14 email to Dana."
escalate_when: "Client pushes back twice, or the ask is
under 5 business days."
confidence: confirmed
provenance:
- "sent-mail 2026-03-14 (thread: 'Hartford rush ask')"
- "slack #ops 2026-05-02"
- "interview transcript 00:41:20"
status: active
Notice three things. The rule is specific enough to act on. The exceptions are real, dated, and cited. And the escalate_when line means even this confirmed rule knows its own limits: the moment a case stops being routine, it comes back to the owner with a drafted recommendation.
Confidence labels drive the guardrails. A rule mined from one or two artifacts can never auto-answer. Only rules you affirmed in the interview, approved with a click, or wrote yourself are ever eligible, and only in categories you personally promoted.
Absorption rate: one number, counted in the open.
Every Friday, the “What Still Reached Your Desk” digest reports one metric:
absorption rate = questions resolved without you
────────────────────────────────
all desk-eligible questions that week
Resolved without you counts auto-answers in categories you greenlit, plus questions your team answered themselves from a codex citation. Desk-eligible counts everything that flowed through the desk, including questions that routed around it and were forwarded in, so leakage is visible instead of invisible.
Three rules are built into the arithmetic so the number cannot flatter itself:
- The raw counts are always shown. A 9-of-10 week and a 72-of-80 week are different stories, and the digest never hides the n. On a quiet week it reports plain counts instead of a misleading percentage.
- Reserved categories are excluded from the denominator. Personnel questions are never supposed to be absorbed. Counting them would punish the desk for escalating correctly, so they are not counted.
- Absorption is never reported without its error rate. The same digest lists every flagged misfire and every automatic demotion. A desk could look good by answering things it should not; this one cannot, because both numbers arrive in the same email.
Expected shape, stated plainly: near 0% in weeks one and two, by design, because everything is reviewed. It climbs as you greenlight categories. We do not quote a target percentage, because no pilot has produced one yet. The first real absorption numbers will be published when they exist.
You own everything. Deliberately.
Most software rents you an outcome. This install hands you the asset.
The codex is your IP
Your Decision Codex exports to plain, readable files at any time, from your own dashboard, no permission needed. It is the documented book of your business judgment, the asset that 85% of 8-figure agencies have built and most small firms never do (benchmark study).
The desk runs on your accounts
Your Cloudflare account, your mail alias, your Slack workspace, your API key, your billing. One configuration file holds it together, and you hold the file. Hand the whole thing to any developer, or to no one, and it keeps working.
Leaving is clean, by design
If we never speak again after the install, nothing breaks and nothing is held hostage. The weekly digest keeps arriving from your own infrastructure. If we disappear tomorrow, your answers don’t.
This mirrors how the founder has built client systems for years: independence designed in from the start, partnership continued by choice. The optional $300/month Desk Tending exists because judgment drifts, not because anything is locked.
It starts with a conversation about your last five decisions.
The 90-minute interview is the anchor of every install. Booking it is the first and only step.