Tag: Notion

Conference Starter Pack
Conference Starter Pack

$97

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Score where you are still the bottleneck. Install 1-3-1 so the next problem comes back as a recommendation. Walk the 5 Ds as a what-if-tomorrow check. Buy Now is the packaged bundle: three Notion tools plus the matching Claude skills, so you are not assembling the starter pack from blank pages.

The grab-and-go pack from the Restoration Leadership Toolkit. Three of the most-used tools, bundled. For restoration owners who just heard the doer-to-leader message and want something they can run this week, not a 12-week program on day one.

What’s in the pack

Conference pack: start with the bottleneck assessment.
1. 1-3-1 Delegation Worksheet
2. Owner Bottleneck Self-Assessment
3. 5 Ds Succession Risk Checklist
The matching skills from the Leadership AI plugin: delegation-1-3-1, owner-bottleneck-assessment, succession-5ds-checklist.

Run them in this order. The bottleneck names the constraint. 1-3-1 is the first habit. The 5 Ds is the exposure you do not want to discover the hard way.

1. Owner Bottleneck Self-Assessment

Find out where your company still depends on you. An owner bottleneck exists when growth, decision speed, and consistency are limited by your personal involvement in day-to-day decisions. You become both the most important and the most constraining person in the business.

Check the box for each statement that is true today. Count the checks in each section, then total them. Range is 0-25. Be honest. The value is in the truth.
1. Decisions only you make. Estimate / pricing approvals over a set dollar amount. Hiring and firing. Vendor choices. Which jobs you take. Refunds, credits, concessions.
2. Interruptions by department. Production calls daily. Office pulls you into billing or scheduling. Sales checks pricing before quoting. Techs call from job sites. Customer complaints land on you.
3. Recurring questions. The same operational questions every week. People wait for you. “Ask the owner” is the default. You re-explain the same processes. Things stall when you are unavailable.
4. Tasks that should be delegated. Estimates you could hand off. Scheduling / dispatch. Collections / AR. Ordering equipment. Work others could produce.
5. Areas with no backup. No one else can run production. Only you hold key carrier relationships. Only you see the full financial picture. No written SOPs for the things you do. If you are gone a week, something breaks.
Bands: 0-6 Mild (tighten the remaining gaps). 7-13 Moderate (you are the bottleneck in one or two areas; fix the worst one first). 14-19 Heavy (the business runs through you; start delegating now, deliberately). 20-25 Severe (you ARE the business; this is the #1 risk to growth and to an exit).

Write your top 3 to delegate first. For one full week after you score, log every interrupt for a decision. Sort into Delegate now / Delegate after training / Keep (truly owner-only). The department with the most checks is this quarter’s target. Install 1-3-1 there first.

2. 1-3-1 Delegation Worksheet

1-3-1 worksheet — force recommendations on the floor.

The old way (escalation): “Hey boss, the dehu on the Maple St job died. What do you want me to do?” You just took back the problem, the thinking, and the decision. That is three jobs.

The 1-3-1 way (delegation): “The dehu on Maple St died. Here are three options I looked at, here is the cost of each, and here is what I would do. Just need your yes.” You own one job: the decision.
- 1. One issue. The decision that is actually needed, in one or two sentences. Not the whole story. The fork in the road.
- 3. Three real options. Each with pros, cons, and a rough cost or effort. “Do nothing” can be one when it is honest. Stuck at two? Push for a third. Even “do nothing and revisit Friday” or “escalate to the carrier.”
- 1. One recommendation. The option they would pick if it were their call, and why in one line.
- A default. What they will do if they do not hear back by a deadline, so the job does not stall waiting on you.
Explain the rule once, out loud. Pin the format where decisions get made (truck, office, group chat). When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait. Run at least five real conversations. Approve the recommendation whenever it is reasonable. Resist solving it yourself, even when you are faster. Note who takes to it quickly. That is a signal for a future-manager pick.

The first few 1-3-1s will be lopsided. Three fake options, or a recommendation with no reasoning. Coach it. Do not grade it. Phase done when at least one person is bringing 1-3-1s without being reminded.

Worksheet fields if you are copying it: prepared by, date, job / account, urgency (Today / This week / No rush); the issue; three options (what it is, two pros, two cons, rough cost); the recommendation and what they need from you; the default deadline; owner sign-off (Approved as recommended / Approved with changes / Chose a different option / Let’s talk).

Owner gut-check before you sign: could this person have made this call without me? If yes, tell them so, and next time push it all the way down.

3. 5 Ds Succession Risk Checklist

5 Ds succession risk — decide what leaves with you.

Succession is not a retirement problem. It is a what-if-tomorrow problem. Check a box only if it is true and current today. Not “mostly.” Not “we talked about it once.” A box you want to be true is still a blank box. Half-true protections fail exactly when the D hits.
1. Death. Current signed will that names the business. Funded buy-sell if there are partners. Key-person life payable to the company. A second check-signer on file at the bank. Someone who can legally bind the company. Passwords in a recoverable place. A named person who can run production 30+ days. Spouse / heirs know who to call.
2. Divorce. Separate vs marital property actually confirmed, not guessed. Prenup, postnup, or buy-sell provision. Books not commingled. A valuation method in writing. Operating cash structured so a personal dispute cannot freeze payroll.
3. Disease. Someone has actually run production on a vacation test. Backup estimator. Payroll / AP / AR without your hands. Carrier relationships that will not collapse if you are unreachable. Disability and business-overhead coverage. A one-page interim chain-of-command with dollar thresholds.
4. Drugs / dependency. Dual approval over a dollar threshold. A second set of eyes on the books. No single point of failure, including you. A trusted advisor allowed to tell you the truth. Key roles documented and cross-covered.
5. Departure / disaster. Tribal knowledge written down. Relationships not owned by one person. Off-site backups you have test-restored. A continuity plan for your own shop. Backup vendor / equipment list.
Count the blanks. Published bands on the scored sheet: 0-6 resilient; 7-15 moderate; 16-27 high; 28+ you are the company. Pick the three blank boxes that would hurt most if the D hit tomorrow. Name an owner and a date. Re-run it every year, and after any life or business change. This is an awareness tool, not legal, financial, or insurance advice. Use it to walk into the attorney, agent, and CPA prepared.

What to do after the three

Take the top-3 bottleneck list into a 90-day doer-to-leader plan (Weeks 1-2 are this assessment). After 1-3-1 sticks, write decision rights so people stop defaulting to you out of habit. The 5 Ds blanks that are also “no backup” boxes on the bottleneck assessment are the same exposure. Name them once.

If you want the next layer after this pack: Leadership Readiness Kit (checklist, scorecard, planner, 1-3-1) or Owner Freedom Kit (audit, bench, 90-day, 5 Ds, 1-3-1).

If you want the packaged pack

You can run the three tools from the outline above. Buy Now is the bundle delivered by email after checkout: the three Notion pages (duplicate each so the master stays clean), plus the matching skills if you want the interviews walked. Same Square button at the top of this page.

Coaching and operational tools only. Not legal, financial, insurance, or HR advice.
Related on Tygart Media: leadership OS · owner freedom kit.
August 13, 2026
Complete Restoration Operating System (Notion + AI)
Complete Restoration Operating System (Notion + AI)

$597

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Build the six Notion databases. Write the 17 SOPs. Hang the 12 KPIs. Talk your own Claude through intake, equipment, claims, and Friday numbers. Buy Now is the packaged flagship: the Notion workspace you duplicate, plus the 8-skill plugin zip, so you are not wiring the system of record and the AI from a blank page.

This is the Notion + AI operating system for a restoration shop. Notion is the system of record. The plugin is the expert you talk to. Outputs from each skill are formatted to paste into the matching Notion tool.

What it is

Complete restoration OS — Notion tools + AI skills on one bench.

Two halves that are meant to run together.

Notion half. Six plug-and-play tools plus an IICRC protocol lookup. Job tracking, equipment, claims, SOPs, KPIs, crew onboarding. Duplicate them into one workspace page named something like Operations. One sidebar section, whole business.

AI half. An 8-skill Claude plugin. A setup skill runs a five-minute interview, writes a company-profile.md, and every other skill reads it. SOPs, KPI targets, claims drafts, and onboarding plans come out in your voice.

You need a free Notion account and any Claude that supports Skills / Plugins. If you can chat with Claude and run a /command, you are good.

The six Notion tools
1. Restoration Job Tracker Pro. Every job from first notice of loss to final invoice, with live margin. This is the hub. Everything else hangs off jobs.
2. Equipment Inventory & Deployment Tracker. Where every air mover and dehu is, and what each one is earning. Asset IDs, daily rates, current deployments.
3. Insurance Claims Command Center. Claims, adjusters, documentation, supplements, and aging balances in one place.
4. Restoration Company SOP Library (17 SOPs). The core procedures, written down. Status starts as Template. Flip to Adopted when you approve each one.
5. Restoration Business KPI Dashboard. The 12 numbers that move profit. Friday 15 to update. One summary row on the first business day of the month.
6. Crew Onboarding & Training Tracker. Roster, certifications with expiration dates, equipment sign-offs. Next hire, duplicate the checklist set.
Plus IICRC Protocol Lookup. Ask “what does S500 say about Category 3 water?” and get a plain-English pointer plus PPE. It is a lookup assistant, not a substitute for the published standard. Defer to current IICRC text, local codes, and your certified judgment.

The 17 SOPs to write (or adopt)

If you are building this yourself, start a table with SOP #, title, category, owner role, linked standard, and status (Draft / In Review / Active / Needs Update). The kit’s 17 are:
1. SOP-01 Water Damage: Initial Inspection & Scoping
2. SOP-02 Water Extraction & Category Determination
3. SOP-03 Structural Drying & Daily Monitoring / Psychrometry
4. SOP-04 Antimicrobial Application
5. SOP-05 Mold Remediation: Containment Setup
6. SOP-06 Mold Remediation: Removal & Clearance
7. SOP-07 Fire & Smoke: Soot Assessment & Cleaning
8. SOP-08 Contents Pack-Out & Inventory
9. SOP-09 Equipment Setup, Tracking & Retrieval
10. SOP-10 PPE & Job-Site Safety
11. SOP-11 Customer Communication & Daily Updates
12. SOP-12 Photo Documentation & Moisture Logging
13. SOP-13 Estimate Writing & Xactimate Scoping
14. SOP-14 Insurance Adjuster Coordination & Supplements
15. SOP-15 Job Completion, Walkthrough & Certificate of Satisfaction
16. SOP-16 Invoicing & Collections
17. SOP-17 New Job Intake / FNOL Handling
Do not customize all 17 today. Adopt the water set first. The rest within the month. Swap in your company name, your equipment, your local disposal rules.

The 12 KPIs

Build a dashboard with KPI, category, definition, frequency, owner, target, this month, last month, trend. The kit tracks these twelve:
- Revenue (Financial, monthly)
- Gross Margin % (Financial, monthly, target ≥ 45%)
- Net Profit % (Financial, monthly, target ≥ 12%)
- Days Sales Outstanding / AR Aging (Financial, monthly, target ≤ 45 days)
- Average Job Size (Financial, monthly)
- Lead-to-Job Conversion % (Sales, weekly, target ≥ 35%)
- Jobs Sold (Sales, weekly)
- Average Days to Dry (Production, weekly, target ≤ 3.5 days)
- Labor Efficiency % (Operations, weekly, target ≥ 70%)
- Equipment Utilization % (Operations, weekly, target ≥ 60%)
- Rework / Callback % (Customer, monthly, target ≤ 3%)
- Customer Satisfaction / NPS (Customer, monthly, target ≥ 70)
Those targets are the kit’s starting case file, not gospel. Mix of mitigation vs reconstruction will shift them. The habit is the product: fifteen minutes every Friday updating statuses.

How to hang it yourself

Set them up in this order. Each one feeds the next.
1. Job Tracker (30-45 min). Add 2-3 active jobs. Real jobs, not test data. Log today’s moisture readings.
2. Equipment Tracker (30-45 min). Every dehu, air mover, scrubber, and meter, with asset IDs. Set actual daily rates. Log where everything is deployed right now.
3. Claims Command Center (20-30 min). Add adjusters first. Then a claim record for every active claim. Log outstanding supplements and unpaid balances.
4. SOP Library (20 min now, ongoing after). Read, customize, flip Status to Adopted as you approve.
5. Crew Tracker (20 min). Roster, certs, equipment sign-offs.
6. KPI Dashboard (15 min, then 15 min every Friday). Enter this month’s jobs and leads, including the ones you lost.
7. IICRC skill (5 min). Install, then ask something real: “Cat 2 toilet overflow into a carpeted hallway. What’s the protocol?”
If a template ships with rows marked (Sample), keep them while you learn. Delete them once your real data is flowing.

How the system runs day to day

Day to day: open the tool, paste facts, review, file.
- Morning: Job Tracker board. What’s active, what needs a monitoring visit.
- On every truck roll: equipment deployments updated; moisture readings logged to the job.
- When the adjuster calls: Claims Command Center open. Every supplement, authorization, and dollar in front of you.
- New hire starts: Crew Tracker checklist; SOP reading list; sign-offs gate the equipment.
- Friday: the Friday 15 in the KPI ledger.
- Month end: one KPI summary row. Review utilization before buying equipment.
This does not replace JobNimbus, Encircle, or Xactimate. Those are job management, documenting, and estimating. This is the ops layer most shops never finish.

The 8 AI skills

Eight AI skills hang next to the SOPs and KPIs.
1. restoration-setup. “Set up the kit.” Guided interview. First run. The concierge.
2. job-intake-assistant. “We just got a water call.” New-loss intake, water Cat/Class, scope plus safety, a paste-ready job summary.
3. equipment-advisor. “How many air movers for this room?” Sizing, placement, monitoring plan.
4. sop-generator. “Write an SOP for mold containment.” Any of the 17, or a new one, in your voice.
5. claims-assistant. “Draft a follow-up to the adjuster.” Emails, supplement justifications, aging-claims chase.
6. kpi-coach. “Here are my numbers this month.” The 12 KPIs computed and trended. Biggest leak named, with fixes.
7. crew-onboarding-builder. “Onboard a new tech.” Week-1 / 30 / 60 / 90 plus an IICRC certification roadmap.
8. iicrc-protocol-lookup. “What does S500 say about Cat 3 water?” Plain-English pointer plus PPE.
Install the plugin yourself

Option A (recommended). Save the restoration-kit folder. In Claude run:
```
/plugin marketplace add /path/to/restoration-kit
/plugin install restoration-kit@profit-detective
/restoration-kit:restoration-setup
```
Option B. Copy each folder inside skills/ into ~/.claude/skills/. On Windows that is C:Users.claudeskills. Then say “run restoration setup.”

Keep company-profile.md in the folder you work in. Every skill reads it.

If you want the packaged system

You can rebuild this from the outline above. Buy Now is the flagship delivered by email after checkout: Notion duplicate links for the six tools plus IICRC lookup, the plugin zip (eight skills and the README), and the setup sequence so you drop it in and run. Same Square button at the top of this page.

This is an operational system only. Not legal, insurance, or licensing advice.

Related restoration products

The AI half of this system is the Restoration Operations Kit — Claude Edition. For the leadership side, see the Restoration Leadership Toolkit — Claude Edition. Software comparisons that pair with the Claims and Job Tracker tools: Albi vs DASH and Xactimate integrations. Lead-gen context lives in Google Ads for Restoration.
Related on Tygart Media: Starlink on a water job · S500 in the van · local SEO for restoration.
August 13, 2026
Accountability Conversation Planner
Accountability Conversation Planner

$39

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Plan a hard conversation before you have it, so it stays about the work, not the person. Buy Now is the packaged Notion planner you duplicate for each talk, so you are not rebuilding the six prompts from a blank doc.

Tool #4 of the Restoration Leadership Toolkit. Use this when an employee, manager, or family member in the business keeps missing the mark and you have been avoiding the talk. Ten minutes of prep keeps the conversation calm, specific, and fixable.

Most restoration owners handle performance problems the same way. They tolerate underperformance for too long. They address it once, informally, in a conversation that does not result in change. They tolerate it some more. Then they either fire the person abruptly, often in response to a specific incident rather than the pattern, or they keep tolerating it because replacing people is painful. Neither outcome serves the business. The people who are performing well watch this and conclude that performance does not matter here.

How to use it

Accountability conversations — six prompts, one script.
1. Duplicate a page so the blank stays clean for next time.
2. Work through prompts 1 through 6 in order. Be specific. Vague prep makes for an emotional conversation.
3. Draft your opening line and close from the script outline, then set a follow-up date.
4. Keep your notes factual. This is a planning doc, not a personnel record. Log formal actions where your policies require.
Fill the situation first: who this conversation is with; their role / relationship to the business; the date you plan to have it; where (private, not on the job site, not by text).

You cannot hold someone accountable for expectations you have not communicated clearly. If the standard was never spelled out, that is on you to own in the room, and to fix going forward. Accountability without support is just pressure.

The six prompts

Six prompts that keep the talk specific.

1. What is the actual issue?

One or two sentences. The pattern, not a single bad day. Name the business impact: missed deadline, blown margin, safety, crew morale, a client complaint. Strip out the frustration and the personality read.

Accountability is forward-looking: what went wrong, what is the standard, how do we close the gap? Blame is backward-looking and personal. Stay on the first one.

2. What specific behavior needs to change?

An observable action someone could see on a camera. “Calls in after the crew is already on site,” not “doesn’t care.” If you cannot point to the behavior, you are not ready to have the talk yet.

“Do good work” is not an expectation. “Complete moisture documentation within 2 hours of equipment placement, using the standard form, with readings at all points on the moisture map” is an expectation. The more specific the expectation, the more possible accountability becomes.

3. What have I already allowed or tolerated?

Be honest. Where did I let this slide, stay quiet, or fix it myself instead of addressing it? Naming your part keeps the conversation fair and stops it from sounding like an ambush.

The most powerful signal in any shop is what the leader does, not what the leader says. If you have been the one quietly finishing their job file, they learned the standard was optional.

4. What expectation needs to be clarified?

State the standard plainly, the way you would want it repeated back. “On site by 7:00, truck stocked the night before.” If this was never spelled out, own that in the room.

For each role you eventually need written performance standards: output (what they produce), behavior (how they show up), and development (what they are working to improve). Share them at hire and review them at every performance discussion. The planner is the prep for one talk. The standards are what make the next talk shorter.

5. What consequence or support is needed?

Both sides. What changes if the behavior continues (the consequence) AND what you will provide to help them succeed (training, a checklist, a ride-along, clearer priorities).

If doing good work and doing poor work produce the same outcome, the same pay, the same treatment, the same opportunities, there is no accountability mechanism. Consequences must exist and must be applied consistently. That cuts both ways: recognition for excellent work, and a real next step when the standard is missed.

6. What does success look like in 30 days?

Concrete and measurable, so you both know if it worked. “Zero late starts for four weeks.” “Job files closed within 48 hours.” This becomes the check-in agenda on the follow-up date.

The longer the gap between a performance miss and the feedback, the weaker the feedback becomes. Address it in the moment or as soon as you can. Then put the 30-day target on a calendar so the talk is not a one-off.

Conversation script outline

Five beats. Keep it calm and short. Say your piece, then listen. Fill the blanks from your answers above.
- Open (set the tone): “I want to talk through [issue] because I think you can do this well and I have not been clear. This is not about [personality].”
- Name the issue + behavior (1 and 2): “What I am seeing is [behavior]. The impact on the business is [impact].”
- Own my part (3): “I have let this go without saying anything, and that is on me. Clarifying now.”
- State the expectation + support (4 and 5): “Going forward the standard is [standard]. To help, I will [support]. If it keeps happening, [consequence].”
- Confirm the 30-day target + listen (6): “In 30 days, success looks like [target]. What is your take. What would help, and is any of this off?”
Write their response under the script. Do not argue it in the room. Listen, then come back to the standard and the 30-day target.

Follow-up

Follow-up is the accountability — write the next check-in.
- Follow-up check-in date
- What I will look at on that date (from Prompt 6)
- Outcome: On track / Needs another conversation / Resolved
This planner is Weeks 9-10 of the 90-Day Doer-to-Leader Transition Plan: hold one real accountability conversation this phase, and have your developing manager run the huddle at least once while you sit in. A weekly 15-minute huddle with a fixed agenda (numbers, jobs at risk, who needs what) is the rhythm that makes the hard talk less of a surprise.

A prompt you can give your own Claude if you want it walked: walk me through these six prompts for this specific situation and hand back a finished script and 30-day follow-up, in our company’s voice.

If you want the packaged planner

You can run the six prompts on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) for each conversation so the master stays clean. The situation block, the six prompts, the script outline, and the follow-up are already laid out. Same Square button at the top of this page.

Pairs with the Leadership Readiness Checklist (does accountability live below you, or are you the only enforcer) and the 90-Day plan. Matching Claude skill: accountability-planner. Coaching and operational tool only. Not legal or HR advice. This is a planning doc, not a personnel record.
Related: Restoration Leadership Toolkit — Claude Edition. Also 1-3-1 Delegation Worksheet.
August 13, 2026
90-Day Doer-to-Leader Transition Plan
90-Day Doer-to-Leader Transition Plan

$199

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Run six two-week phases. By Week 12 the business runs a notch less on you and a notch more on your people. Buy Now is the packaged Notion plan you duplicate and date, so you are not assembling the 12-week spine from blank pages.

The capstone of the Restoration Leadership Toolkit. This turns the doer-to-leader message into a plan you actually run. Work it top to bottom. Do not skip ahead. Each phase sets up the next. You cannot clarify decision rights (Weeks 5-6) until you know your bottlenecks (Weeks 1-2).

How to use this plan

90-day arc: bottlenecks first, then rhythm.
- Duplicate a page and rename it “90-Day Plan – {start date}.”
- Block 30-45 minutes every Friday to work the current phase and check boxes.
- Start by running the Owner Bottleneck Self-Assessment and the Owner Dependency Audit. Their results feed Weeks 1-2 directly.
- Fill the three setup lines before Week 1.
Write these three lines now:
- My #1 reason to step back (what I would do with the time)
- The one person I am betting on as my first real manager
- Start date / target Week-12 date
Weeks 1-2. Identify your bottlenecks

Goal: get brutally honest about where the company still runs through you. You cannot delegate what you have not named.
1. Run the Owner Bottleneck Self-Assessment and write down your top 3 bottleneck areas.
2. Run the Owner Dependency Audit. List every decision or task that only you can do today.
3. For one full week, log every time someone interrupts you for a decision. A tally on your phone is fine.
4. Sort that list into three buckets: Delegate now / Delegate after training / Keep (truly owner-only).
5. Circle the top 3 bottlenecks that cost you the most time or money. These are your 90-day targets.
6. Tell your team what you are doing and why: “I am working a 90-day plan to push decisions down. Expect me to hand more back to you.”
Phase 1 done when you have a written top-3 bottleneck list and your team knows the shift is coming. The audit rates Low / Med / High across nine areas (sales, production, finance, customer-issue resolution, hiring, vendor relationships, estimating / project management, emergency response, decision rights). Low = 1, Med = 2, High = 3. Total is 9-27.

Weeks 3-4. Install 1-3-1 conversations

Weeks 3–4: install 1-3-1 conversations.

Goal: stop being the answer key. Train the team to bring one issue, three options, and one recommendation, so you coach instead of solve.
1. Explain the 1-3-1 rule to the team: bring 1 issue, 3 options, 1 recommendation. Not just the problem.
2. Print or pin the 1-3-1 format where decisions get made (truck, office, group chat).
3. When someone brings you a raw problem, ask: “What are your three options, and which do you recommend?” Then wait.
4. Run at least 5 real 1-3-1 conversations this phase and approve their recommendation whenever it is reasonable.
5. Resist solving it yourself, even when you are faster. Let them carry it. This is the hard part.
6. Note who takes to it quickly. That is a signal for your future-manager pick in Weeks 7-8.
Phase 2 done when at least one person is bringing you 1-3-1s without being reminded. One issue, three real options (pros, cons, rough cost), one recommendation, and a default if they do not hear back by a deadline.

Weeks 5-6. Clarify decision rights

Goal: write down who decides what, and up to what dollar amount, so people stop defaulting to you out of habit.
1. List the 10-15 recurring decisions your team faces (refunds, equipment, scheduling, scope changes, hiring, pricing exceptions).
2. For each, write a dollar or scope threshold people can decide under without asking you.
3. For each, name who owns it when you are not in the room.
4. Capture it in one simple Decision Rights list (a shared doc or a section on the plan page).
5. Walk the team through it and tell them: “Under this line, you do not need me. Decide and tell me after.”
6. Pick one decision you currently own and hand it off completely this phase. Do not take it back.
Phase 3 done when there is a written decision-rights list and at least one decision has fully left your plate. Starter rows live on the Owner Dependency Audit if you need them.

Weeks 7-8. Develop one manager

Weeks 7–8: develop one manager on real work.

Goal: go deep on ONE person. A single real manager beats five people you are “keeping an eye on.”
1. Choose one person to invest in as your first real manager. Use the Middle Manager Evaluation Scorecard if you are torn.
2. Have a direct conversation: “I want to grow you into running X. Here is what that looks like.”
3. Hand them one area to own end-to-end (a crew, a job type, scheduling, QC). Outcome, not task.
4. Set a weekly 30-minute 1-on-1 with them and protect it like a paying job.
5. Name the 1-2 skills they most need to build and how you will help (ride-along, training, a stretch job).
6. Let them make a real decision this phase and coach the outcome instead of grading it.
Open a bench list while you do this. One row per key function: role, current owner, candidate, backup depth, skill gaps, one observable 90-day action, delegation plan, check-in rhythm, status. A blank candidate is itself a finding. Phase 4 done when one person owns one area end-to-end and has a standing 1-on-1 with you.

Weeks 9-10. Create an accountability rhythm

Goal: replace you-chasing-everyone with a repeatable cadence that surfaces problems early, without you in the middle of every thread.
1. Stand up a weekly 15-minute team huddle with a fixed agenda: numbers, jobs at risk, who needs what.
2. Pick the 3-5 numbers the team reviews every week (jobs in WIP, days-to-dry, AR, callbacks, leads).
3. Decide who owns each number and reports it. Not you.
4. Use the Accountability Conversation Planner to prep any hard conversation so it stays about the work, not the person.
5. Hold one real accountability conversation this phase using that structure.
6. Have your Week 7-8 manager run the huddle at least once while you sit in and observe.
Phase 5 done when the weekly huddle runs on schedule and someone other than you can run it. About the work, not the person.

Weeks 11-12. Review, adjust, and repeat

Goal: measure what changed, lock in the wins, and set the next 90 days. This is not the end. It is the first turn of the flywheel.
1. Re-run the Owner Bottleneck Self-Assessment and compare to your Week 1 score.
2. Take a planned half-day fully off and note what broke or escalated to you. That is your next bottleneck.
3. List what got delegated successfully vs what bounced back to you, and why it bounced.
4. Give your developing manager direct feedback on the quarter and agree on next-quarter goals.
5. Update your Decision Rights list and raise one threshold now that the team has proven itself.
6. Pick next quarter’s top bottleneck and start a fresh 90-day cycle (duplicate the page again).
Phase 6 done when you have re-scored, taken real time off, and named the next quarter’s target.

Success looks like

By the end of 90 days, a healthy transition looks like:
- You can take a full day off without the business stalling or your phone melting.
- Your team brings you 1-3-1 recommendations, not raw problems to solve.
- There is a written decision-rights list, and people decide under the line without asking.
- One person owns one area end-to-end and has a standing 1-on-1 with you.
- A weekly huddle runs on cadence, and someone other than you can run it.
- Your re-scored bottleneck number is lower than it was in Week 1.
- You have already named next quarter’s target, because doer-to-leader is a flywheel, not a finish line.
Not every box will be checked, and that is fine. Progress on the top-3 bottlenecks matters more than a perfect scorecard. Run it, adjust, repeat.

While you are in it, run the 5 Ds as a what-if-tomorrow check. Pick the three blank boxes that would hurt most if the D hit tomorrow.

If you want the packaged plan

You can run the six phases from the outline above. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) and rename it with the start date so the master stays clean. The setup lines, the phase checkboxes, and the success list are already laid out. Same Square button at the top of this page.

The other four tools in the Owner Freedom Kit feed this spine: Owner Dependency Audit, Restoration Leadership Bench Builder, 5 Ds Succession Risk Checklist, 1-3-1 Delegation Worksheet. Matching Claude skill: doer-to-leader-90-day. Coaching and operational tool only. Not legal or HR advice.
Related: Restoration Leadership Toolkit — Claude Edition. Also Owner Bottleneck Self-Assessment.
August 13, 2026
5 Ds Succession Risk Checklist
5 Ds Succession Risk Checklist

$29

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Stress-test the company against Death, Divorce, Disease, Drugs/dependency, and Departure/Disaster. Check a box only if it is true and current today. Buy Now is the packaged Notion checklist with the scored sheet and mitigation notes, so you are not rebuilding the 5 Ds from a blank doc.

Succession is not a retirement problem. It is a what-if-tomorrow problem. The blank boxes are your exposure. Honesty rule: a box you want to be true is still a blank box. Half-true protections fail exactly when the D hits.

How to run it

Run the 5 Ds as a risk checklist — not a slogan.
1. Walk each of the 5 Ds. Check a box only if it is true and current today. Not “mostly.” Not “we talked about it once.”
2. Read the mitigation note under each D. That is the concrete fix for the boxes you left blank.
3. Count the blanks. Find your band. Pick your top 3 shore-ups. Name an owner and a date.
4. Re-run it every year, and immediately after any life or business change: a new partner, a marriage or divorce, a major new account, an acquisition, or a health scare.
1. Death. If you died tomorrow

If you were gone permanently, could the business survive the week, pay people, and not get sold for scraps?
- There is a current, signed will and the business is named in it.
- There is a buy-sell agreement (if there are partners) defining who buys your share, at what price, and how it is funded.
- Key-person life insurance exists on you, payable to the company, sized to cover payroll plus obligations while it stabilizes.
- At least one other person can sign checks (signatory on file at the bank, not just “knows the login”).
- Someone other than you can legally bind the company (contracts, AOBs, subcontracts). Documented authority, not assumed.
- Your spouse / heirs know who to call and where the documents live.
- Passwords, accounts, and licenses are in a recoverable place a trusted person can reach.
- A named person can run production and keep jobs moving for 30+ days without you.
Mitigation. Get a buy-sell drafted by an attorney and fund it with life insurance. An unfunded buy-sell is a wish, not a plan. Add a second check-signer and a documented officer who can bind the company. Put credentials in a password manager with an emergency-access contact. Write a one-page “if I am gone” sheet. Tell your spouse where it is.

2. Divorce. If your marriage ended

A divorce can put your ownership stake, your cash, and your focus in play. A contested split can starve a cash-hungry shop.
- You know whether the business is separate vs marital/community property in your state. Confirmed, not guessed.
- There is a prenup, postnup, or buy-sell provision that addresses ownership in a divorce.
- The business is not commingled with personal finances (clean books, separate accounts, documented owner pay).
- A current, defensible valuation (or a method to set one) exists.
- Your spouse’s role and any claim (employee, owner-on-paper, guarantor) is documented.
- Operating cash and credit lines are structured so a personal dispute cannot freeze payroll.
Mitigation. Talk to a business attorney about a postnuptial or a buy-sell clause that fixes ownership treatment now, while things are calm. Clean up commingling. Establish a valuation method in writing. Calm is the only time you can do it.

3. Disease. If you were medically out for 30-90 days

Not death. A heart attack, a serious diagnosis, a bad accident. You are alive but out. Does the company idle or run?
- Someone can run daily production and dispatch without you for 30, 60, 90 days. Named, and they have actually done it (vacation test).
- Estimates still get written and approved if you are the estimator. A backup exists.
- Payroll, AP, and AR keep running without your hands on them.
- Carrier / TPA relationships will not collapse if you are unreachable. Someone else has the relationships and portal access.
- You carry disability income insurance so household income does not depend on you working.
- Business overhead expense (BOE) insurance or a cash reserve can cover fixed costs while you recover.
- A simple interim chain-of-command is written down, with dollar/decision thresholds.
Mitigation. Run a real “two weeks off” test this quarter and watch what breaks. Cross-train a backup estimator. Look at disability and Business Overhead Expense coverage. Write a one-page interim chain-of-command with decision thresholds.

4. Drugs / dependency. If you (or a key person) became unreliable

The uncomfortable one. Substance issues, gambling, burnout, a mental-health crisis. Yours or a key person’s. The risk is a slow decline, not a clean exit.
- No single person (including you) is a single point of failure whose impairment would quietly sink the company.
- Financial controls exist (dual approval over a threshold, reconciliations, a second set of eyes on the books).
- A trusted advisor or peer would tell you the truth if your performance was slipping, and has standing to.
- Key roles have documented duties and cross-coverage.
- There is an employee assistance path / clear policy for getting a valued person help without an instant, messy termination.
- If a key person had to be removed fast, you could. Access and knowledge are not locked solely in their head.
Mitigation. Dual approval over a dollar threshold, monthly reconciliations, a second set of eyes on the books. Document and cross-train so no one person can sink a function. Put a real advisor in your corner who is allowed to tell you the truth. Have a humane path to help and the access to act fast if you must.

5. Departure / disaster. If a key person walked, or the building burned

Two faces of the same risk: a critical person quits, or a fire/flood/storm/cyber event takes out your office, fleet, data, or a major account overnight.
- Production runs if your best PM or lead tech quits Friday. Their knowledge is documented, not tribal.
- Key customer and carrier relationships are not owned by one person who could walk and take the book with them.
- A non-solicit / non-compete / confidentiality agreement is in place where appropriate and enforceable in your state.
- Critical SOPs, pricing, and account knowledge are written down. Losing one person does not erase how the work gets done.
- Data is backed up off-site (estimating files, photos, accounting, contacts) and you have actually tested a restore.
- You have a business continuity / disaster plan for your own office or fleet. You restore others. Are you covered?
- Business-interruption insurance would replace income if you could not operate for weeks.
- A backup vendor/equipment plan exists so one lost truck, warehouse, or sub does not stall live jobs.
Mitigation. Document tribal knowledge. Spread customer and carrier relationships across more than one person. Put reasonable non-solicit/confidentiality agreements in place (attorney confirms enforceability in your state). For disaster: off-site backups you have test-restored, a written continuity plan for your own shop, business-interruption coverage, and a backup equipment/vendor list.

Overall exposure rating

Overall exposure rating after all five Ds.

Count your blank boxes across all 5 Ds. The packaged checklist scores 45 boxes. Find your band:
- 0-6 Low / Resilient. The business could survive a major shock to you. Maintain it. Review annually and after any big change.
- 7-15 Moderate. You would survive a short absence but a permanent loss would hurt. Close the highest-stakes gaps (Death + Disease) first.
- 16-27 High. A 30-day absence would seriously disrupt the company. A permanent loss could end it. Treat this as a current-quarter priority.
- 28+ Critical / You are the company. If something happened to you tomorrow, the business likely does not survive intact. Start the top-3 shore-ups this week.
Write three lines: blank-box total, exposure band, and which D scored worst.

Top 3 shore-ups

Top 3 shore-ups — write the next actions.

Pick the three blank boxes that would hurt most if the D hit tomorrow. Be specific. Name an owner. Set a date.

Most shore-ups need one of these professionals: a business / estate attorney (buy-sell, will, non-competes, postnup); an insurance agent (key-person life, disability, BOE, business-interruption); a CPA / financial advisor (valuation, financial controls, continuity reserve).

This is an awareness and planning tool, not legal, financial, or insurance advice. Use it to find your gaps and to walk into the attorney, agent, and CPA prepared.

If you want the packaged checklist

You can run the five lists on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) so the master stays clean. The boxes, the mitigation notes, the score table, and the top-3 shore-ups are already laid out. Same Square button at the top of this page.

Pairs with the Owner Dependency Audit (what breaks if you vanish 30 days) and the Restoration Leadership Bench Builder (who can run production when a D hits). Matching Claude skill: succession-5ds-checklist.
Related: Restoration Leadership Toolkit — Claude Edition. Also 90-Day Doer-to-Leader Transition Plan.
August 13, 2026
1-3-1 Delegation Worksheet
1-3-1 Delegation Worksheet

$19

Delivered by email after checkout.

Buy Now →

Secure checkout via Square — all major cards accepted
You can copy this method and do it yourself. Teach the team to bring one issue, three options, and one recommendation instead of a raw problem. Buy Now is the packaged Notion worksheet you duplicate for every decision they hand up, so you are not rebuilding the form from a blank doc.

Tool 1 of the Restoration Leadership Toolkit. The line is: stop bringing me problems. Start bringing me decisions. The 1-3-1 method trains your people to think like owners. You keep one job: approve, tweak, or redirect.

The old way vs the 1-3-1 way

Old way vs 1-3-1 way.

The old way (escalation): “Hey boss, the dehu on the Maple St job died. What do you want me to do?” You just took back the problem, the thinking, and the decision. That is three jobs.

The 1-3-1 way (delegation): “The dehu on Maple St died. Here are three options I looked at, here is the cost of each, and here is what I would do. Just need your yes.” You own one job: the decision.

The rule

The 1-3-1 rule.
- 1. One issue. State the decision that is actually needed, in one or two sentences. Not the whole story. The fork in the road.
- 3. Three real options. Three things you could actually do. Each with pros, cons, and a rough cost or effort. “Do nothing” can be one of the three when it is honest.
- 1. One recommendation. The option they would pick if it were their call, and why in one line.
- A default. What they will do on their own if they do not hear back by a deadline, so the job does not stall waiting on you.
Stuck at two options? Push for a third. Even “do nothing and revisit Friday” or “escalate to the carrier.” A real third option is where the good thinking usually hides.

How to install it

How to install 1-3-1 on the team.
1. Explain the rule to the team once, out loud. Pin the format where decisions get made: truck, office, group chat.
2. When someone brings a raw problem, ask: “What are your three options, and which do you recommend?” Then wait.
3. Run at least five real 1-3-1 conversations before you decide it “isn’t working.” Approve the recommendation whenever it is reasonable.
4. Resist solving it yourself, even when you are faster. Let them carry it. That is the hard part.
5. Note who takes to it quickly. That is a signal for your future-manager pick.
The first few times, the 1-3-1s will be lopsided. Three fake options, or a recommendation with no reasoning. Coach it. Do not grade it. The goal is a team that brings you thinking, not just questions. Phase done when at least one person is bringing 1-3-1s without being reminded.

The worksheet (copy this)

Duplicate a page or print a half-sheet for every decision that gets handed up. Fill it in this order.

Who and when
- Prepared by
- Date
- Job / account (if any)
- How urgent: Today / This week / No rush
1. The issue / decision needed

One or two sentences. What decision are we actually making? Why does it need a decision now? Then one more line: what happens if we do nothing / decide nothing?

3. The three options

For each option write four lines:
- What it is
- Pros (two bullets)
- Cons (two bullets)
- Rough cost / effort
1. My recommendation

I recommend Option __. Why (one or two lines). What I need from you: a yes / a budget approval / a different call / a quick conversation.

What I will do if I do not hear back
- If I do not hear back by: (date / time)
- I will go ahead and: (the default)
- Owner is OK with me proceeding this way unless they say otherwise
Owner decision / sign-off
- Approved as recommended / Approved with changes / Chose a different option / Let’s talk
- If changed, what
- Any conditions or budget cap
- Owner name and date
Owner gut-check before you sign

Could this person have made this call without me? If yes, tell them so, and next time push it all the way down to them. That is how the bottleneck clears.

This worksheet is Weeks 3-4 of the 90-Day Doer-to-Leader Transition Plan. After it sticks, write decision rights (who decides what, up to what dollar amount) so people stop defaulting to you out of habit. Hand off one decision completely and do not take it back.

A prompt you can give your own Claude if you want it walked: convert this escalated question into one issue, three options with pros/cons/cost, one recommendation, and a default if I do not answer by a deadline.

If you want the packaged worksheet

You can run 1-3-1 on a legal pad. Buy Now is the Notion page delivered by email after checkout. Duplicate it (··· → Duplicate) for every decision so the master stays clean. The fields, the option tables, the default, and the sign-off are already laid out. Same Square button at the top of this page.

Pairs with the 90-Day Doer-to-Leader Transition Plan (Weeks 3-4) and the Owner Dependency Audit when you are ready to map who should decide. Matching Claude skill: delegation-1-3-1. Coaching aid, not legal or HR advice.
Related: Restoration Leadership Toolkit — Claude Edition. Also Owner Bottleneck Self-Assessment.
August 13, 2026
I Actually Used Claude Fable 5 Before the Government Pu (2026)

Three days. That’s how long Claude Fable 5 existed in the wild before the US government killed it.

On Monday, June 9, Anthropic launched Fable 5 and Mythos 5. On Thursday, June 12, Commerce Secretary Howard Lutnick issued an export control directive ordering Anthropic to suspend access for any foreign national. Since Anthropic can’t verify nationality in real time, they shut it down for everyone. Globally. Immediately. The stated reason was a narrow jailbreak vulnerability — one Anthropic says exists in other publicly deployed models too.

I’m not writing this to debate export controls. I’m writing this because I spent those three days running Fable 5 in production — not benchmarking it, not kicking the tires, actually building with it — and I have something most people writing about this don’t have: receipts.

Day One: The Model Dropped and I Put It to Work

Day one — the model dropped and I put it to work.

Fable 5 launched June 9. By that afternoon, I had it running a Batch 8 sprint across my Tygart Media site — refreshing 10 pages of Claude content that needed updating. Fable 5 updated comparison tables, corrected model names across the lineup, added FAQPage schema, injected internal links, and expanded word counts. Post 4787 went from 750 words to 1,602. Post 9821 went from 1,782 to 2,543. Five posts refreshed with full SEO treatment — schema, FAQs, RankMath meta, silo links — in a single session.

That same day, I had Fable 5 write a complete guide to itself. Not a press release rewrite — a 2,100-word article with an interactive cost calculator, a model picker tool, and a section called “How We Actually Use Each Model” that mapped my real production workflows to each tier: Haiku for the daily 25-post SEO sweeps, Sonnet for desk articles, Opus for deep refreshes, Fable for portfolio-wide audits and strategy. The draft landed in Notion with scoped CSS and JS, ready to paste into WordPress as a single Custom HTML block.

Day Two: Fable 5 Ran My Entire SEO Audit

Day two — Fable 5 ran the SEO audit.

June 10. I ran a full SEO audit of tygartmedia.com through Fable 5. It identified that Fable 5 itself was the top content gap — a model launched 24 hours ago with zero dedicated coverage and peak search intent. So it wrote the article to fill its own gap. It drafted the piece, tagged the slug, assigned the category, and queued internal links to five existing posts.

That same day, Fable 5 wrote and published “The Signal: AI Just Split Into Two Lanes” — a 1,400-word field notes piece that wove together Fable 5’s launch, OpenAI’s S-1, Chrome WebMCP, and the emerging thesis that AI was splitting into a product lane and an infrastructure lane. The article went through the full pipeline: SEO optimization, AEO with 8 FAQ Q&As, GEO entity enrichment, Article + FAQPage schema, taxonomy assignment, internal linking, quality gate — then published via REST API. It even created the LinkedIn draft in Metricool and scheduled it for 2:30 PM Pacific.

That article exists right now at tygartmedia.com. I didn’t write it. Fable 5 did, with me directing the strategy and approving the output. The quality bar was real journalism, not AI slop.

Day Three: Building the Infrastructure Layer

June 11. While the Fable 5 Complete Guide sat in Notion waiting for a featured image, I was using Fable 5 to build the systems that would keep my content operation running. I had it update the Claude Intelligence Desk — my Notion page that serves as the authoritative source of truth for every Claude model name, API string, and price across my entire content operation. Every article gets verified against that desk before publishing. Fable 5 updated it with its own pricing: $10 input, $50 output per million tokens.

I also had Fable 5 design my Pricing Freshness Engine — a WordPress mu-plugin that shadow-checks Anthropic’s live pricing against what’s displayed on my site. The engine had been running in shadow mode since June 2, catching drift before it reaches readers. Fable 5 added itself to the canonical pricing store.

Meanwhile, my 6 scheduled email agent tasks — morning triage, midday check, afternoon wrap, newsletter extraction, weekly prep, and weekly self-audit — were running on the same Claude infrastructure, handling my inbox while I focused on building. The whole system runs on my Max plan. No extra API charges.

What Fable 5 Actually Felt Like

Here’s what the benchmarks don’t tell you: Fable 5 understood intent, not just instructions.

When I told it to run a page refresh, it didn’t just update the text — it checked model names against my Intelligence Desk, verified pricing against live documentation, added schema markup, expanded FAQs, injected internal links, and updated the dateline. It treated each task as a system, not a checklist.

When I asked it to write the Complete Guide, it included a section about how we actually use each model tier in production — because it knew from context that an article about Claude models on a site that runs on Claude models should demonstrate firsthand expertise, not just recite specs. It even built interactive JavaScript widgets inline — a cost calculator and a model picker — without being asked, because it understood the article needed to be useful, not just informative.

The gap between Fable 5 and what came before it was the largest single-model jump I’ve experienced since I started building on Claude in 2024.

What Most Commentators Are Missing

What most commentators are missing.

Most people writing about the shutdown never used Fable 5. They’re debating precedent, policy, the implications for AI regulation. All valid. But the conversation is incomplete without understanding what was actually deployed.

This is the first time the US government has aimed export controls at a deployed commercial AI model rather than at chips or hardware. That’s unprecedented. Anthropic complied but publicly disagreed, calling it a likely misunderstanding based on a narrow jailbreak that exists in other models too.

Every other Claude model — Opus, Sonnet, Haiku — remains fully available and unaffected.

What I Lost

Here’s what the government took from me specifically:

My Fable 5 Complete Guide is sitting in Notion, ready to publish, with the proxy fix queued. The pricing pages need Fable 5 rows added. The Freshness Engine needs Fable 5 in its canonical store. The WordPress proxy’s ALLOWED_DOMAINS needs a one-line gcloud update. All of it was queued up. All of it was dependent on a model that no longer exists.

The infrastructure I built this week — the Intelligence Desk, the Pricing Freshness Engine, the content pipeline that ran “The Signal” from draft to published with schema and social scheduling in a single session — all of that still works with Opus and Sonnet. But the ceiling is lower. The tasks that Fable 5 handled in one pass will take two or three with the models that remain.

What Happens Now

Anthropic says this isn’t permanent. They’re working to restore access.

For people like me who build businesses on top of these tools, the uncertainty is the real cost. Three days is long enough to build production workflows, deploy infrastructure, and write articles that reference a model’s existence — and short enough that all of it gets yanked before you can publish.

But I’m not pulling back. This week confirmed the trajectory. AI at this level isn’t a nice-to-have — it’s the infrastructure of how modern knowledge work gets done. Whether it’s Fable 5 or whatever comes after it, this capability exists now. You can’t un-ring that bell.

I know because I rang it. For three days, I built real things with a model the government decided the world shouldn’t have. And the work is still there in my Notion, waiting.

Will Tygart is the founder of Tygart Media, where he builds AI-native content operations across a portfolio of WordPress sites. He has been building production workflows on Claude since 2024. His Claude Intelligence Desk, Pricing Freshness Engine, and content pipeline systems were all built or upgraded using Claude Fable 5 during its three-day window.

Related on Tygart Media: Fable 5 complete guide · Claude Fable 5 · how to use Claude.

June 13, 2026

Notion MCP Setup with Claude: Complete Config + the Errors Nobody Documents

Last verified: June 2026.

There are two ways to connect Notion to Claude over the Model Context Protocol (MCP), and almost every tutorial only covers one of them. Worse, none of them tell you why the connection succeeds but Claude still says it cannot find any of your pages. This guide covers both paths – the hosted OAuth connector and the self-hosted token route – with the exact config, the scopes that matter, the rate limit you will hit, and the specific error strings that show up when something is wrong. It is written from actually running this, not from reading the docs.

Which Notion MCP should you use: hosted or self-hosted?

Flow from app/IDE through MCP to servers and data APIs — Hosted vs self-hosted Notion MCP.

Short answer: use the hosted MCP at https://mcp.notion.com/mcp for almost everything. It uses OAuth, so you never handle a token, and it respects your existing Notion permissions automatically. Use the self-hosted npm server with an internal integration token only when you need headless, unattended automation (a cron job, a server with no human to click “Allow”), because the hosted server requires an interactive OAuth approval that a background process cannot complete.

Factor	Hosted (mcp.notion.com)	Self-hosted (npm + token)
Auth	OAuth (interactive)	Internal integration token (ntn_)
Permissions	Inherits your full Notion access	Only pages you explicitly share
Setup time	~2 minutes	~10 minutes
Headless / cron	No (needs a human to approve)	Yes
Best for	Claude Desktop, Claude Code, daily use	Servers, scripts, multi-user backends

How do I connect Notion to Claude using the hosted MCP?

Five-step path: account, API keys, billing, usage, workspaces — Connect Notion to Claude via hosted MCP.

This is the fast path. No token, no npm.

Claude Desktop / Claude.ai: Open Settings > Connectors, click Add custom connector (or pick Notion if it appears in the directory), and paste the URL https://mcp.notion.com/mcp. A Notion OAuth window opens. Approve it, choose which workspace and which top-level pages the connector may see, and you are done. The scope you pick in that OAuth screen is the whole ballgame – see the gotcha below.

Claude Code (CLI): one command.

claude mcp add --transport http notion https://mcp.notion.com/mcp

Then run /mcp inside Claude Code to trigger the OAuth login. After approving, verify it is live:

claude mcp list

You should see notion with a connected status. If it shows failed or needs auth, run /mcp again and complete the browser flow – the CLI cannot proceed past OAuth on its own.

How do I set up the self-hosted Notion MCP with an integration token?

Use this when you need automation that runs without a human. Three steps: create the integration, get the token, then wire it into your MCP config.

1. Create the integration and copy the token

Go to https://www.notion.so/my-integrations and click New integration. You must be a Workspace Owner – if the button is greyed out, that is why.
Name it, select the workspace, and choose Internal integration type.
On the integration’s settings page, set Capabilities: Read content, plus Update/Insert content if you want Claude to write. If you only grant Read, every write attempt fails with a permission error later – this is a common self-inflicted wound.
Click Show, then copy the Internal Integration Token. New tokens start with ntn_ (older ones start with secret_ and still work). Treat it like a password.

2. Add it to your MCP config

For Claude Desktop, edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/; Windows: %APPDATA%\Claude\). Add:

{
  "mcpServers": {
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "ntn_your_token_here"
      }
    }
  }
}

Restart Claude Desktop completely (quit, do not just close the window). On Windows, if npx is not found, use the full path to npx.cmd or run via cmd /c – the config does not inherit your shell PATH.

3. The step everyone forgets: share the pages

An internal integration starts with access to nothing. Creating it and pasting the token is not enough. For every page or database you want Claude to touch, open it in Notion, click the … menu (top right), choose Connections (or Add connections), and select your integration. Access is inherited by child pages, so sharing a top-level page covers its whole subtree. Skip this and Claude will connect cleanly and then truthfully report that it cannot see any content.

What are the most common Notion MCP errors and how do I fix them?

Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key — Common Notion MCP errors and fixes.

These are the failure messages you will actually see, and what each one means.

“Could not find page” / Claude returns zero results from a workspace that clearly has pages

Cause, in order of likelihood: (1) you did not share the page with the integration (self-hosted), or you scoped the OAuth grant too narrowly (hosted); (2) the page is in a different workspace than the one the integration is tied to. Fix: re-check the Connections menu on the specific page, or re-run the OAuth flow and widen the page selection. An integration token is bound to one workspace – it cannot see another.

API token is invalid (HTTP 401 unauthorized)

The token is wrong, was regenerated, or has a stray space/newline from copy-paste. Re-copy it with the Show button, paste it into the env block with no surrounding whitespace, and restart the client. If you rotated the token in Notion, the old one dies immediately – update every config that used it.

Validation error / “body failed validation” (HTTP 400)

Claude tried to write a property type that does not match the database schema – for example sending plain text into a Select, or a malformed date. This is not a connection problem. Tell Claude the exact property names and types, or ask it to fetch the database schema first before writing.

“Rate limited” / HTTP 429

Notion enforces roughly 3 requests per second per integration (averaged, with short bursts tolerated). Bulk operations – “update 200 rows,” “scan every page” – blow straight through this. The fix is pacing, not a bigger plan: have Claude batch in small groups and add a short delay between calls. If you are scripting around the MCP, honor the Retry-After header on a 429 instead of hammering.

spawn npx ENOENT (server will not start, self-hosted)

Node/npx is not on the PATH the client sees. Install Node, then point command at the absolute path to npx (or npx.cmd on Windows). This is the number-one self-hosted startup failure.

MCP server shows “failed” in claude mcp list right after adding it

For the hosted server this almost always means OAuth was never completed – run /mcp and approve in the browser. For the self-hosted server it means the process crashed on launch; run the npx command manually in a terminal to see the real stack trace.

What can Claude actually do with Notion once connected?

With read + write capabilities granted, Claude can search your workspace, read pages and databases, create pages, append blocks, and update properties on existing rows. Practical things that work well: “summarize this Notion doc,” “create a row in my tasks database with these fields,” “find every page mentioning X and list the links,” “turn this conversation into a meeting-notes page.” Things that get awkward: very large pages (the response can get truncated – verify the write actually landed by fetching it back), and bulk edits that trip the rate limit. A reliable habit is to treat Notion as the source of truth and have Claude verify by re-fetching after any write, because timeouts on big pages can commit silently and still return a malformed response.

Security notes from running this in production

Scope the OAuth grant tightly. The hosted connector inherits whatever you approve. If you only need one project area, share only that top-level page, not the whole workspace.
Never hardcode the token in a file you might commit. Keep ntn_ tokens in an env var or your OS secret store, and reference them from config. If a token leaks, revoke it in my-integrations immediately – revocation is instant.
Grant the minimum capability. If Claude only needs to read, do not enable insert/update. You can always widen it later.
Audit which integrations have access to sensitive databases periodically; the Connections menu on each page shows the current list.

If you are wiring up several connectors at once, the mechanics generalize – see our broader Claude MCP setup guide for the config patterns that apply across servers, and the AI operator’s stack for how Notion fits alongside the other tools day to day. If your reason for connecting Notion is to get your own content cited by AI systems, the structure of the pages matters as much as the wiring – see how AI engines cite content.

FAQ

Do I need a paid Notion plan to use the MCP?

No. The API and integrations work on free Notion workspaces. You do need to be a Workspace Owner to create an internal integration.

Why does Claude say it connected but can’t find my pages?

Almost always the page-sharing step. A self-hosted integration has access to nothing until you add it via the page’s Connections menu. For the hosted connector, you scoped the OAuth approval too narrowly – re-run it and select more pages.

What is the Notion API rate limit?

About 3 requests per second per integration, averaged over time with small bursts allowed. Exceeding it returns HTTP 429. Pace bulk operations and respect the Retry-After header.

What does the ntn_ prefix mean on my token?

It is the current internal integration token format. Tokens created today start with ntn_; older secret_ tokens still function and do not need to be replaced.

Can the hosted Notion MCP run in a headless cron job?

No. The hosted server requires interactive OAuth approval, which an unattended process cannot complete. Use the self-hosted npm server with an ntn_ token for headless automation.

How do I let Claude write to Notion, not just read?

Enable Update content and Insert content under the integration’s Capabilities (self-hosted), or approve write scope during OAuth (hosted). Read-only is the default and will reject every write with a permission error.

Where do I put the Notion MCP config for Claude Desktop?

In claude_desktop_config.json – ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows. Add a notion entry under mcpServers and fully restart the app.

Can one integration access two workspaces?

No. An internal integration is bound to the single workspace it was created in. For a second workspace, create a second integration (or a second OAuth grant on the hosted connector).

Related reading from operators who run AI tooling daily: Claude Code vs Cursor, Claude Code vs Codex, and Claude in Chrome for LinkedIn automation.

Frequently Asked Questions

What is the Notion MCP server for Claude?

The Notion MCP server is a connector that lets Claude read, search, and interact with your Notion workspace through the Model Context Protocol. With it connected, you can ask Claude to find pages, summarize databases, draft content into Notion, or retrieve information — all without copying and pasting anything manually.

What is the difference between the Notion OAuth connector and the self-hosted token route?

The OAuth connector (available in Claude Desktop’s built-in integrations) is the fastest path — authorize once and Claude gets read access to pages you share with the integration. The self-hosted route uses a Notion Internal Integration token in your claude_desktop_config.json, giving you more control over scopes and works in Claude Code environments where OAuth connectors aren’t available.

Why does Claude say it can’t find my Notion pages after connecting?

The most common reason is that you haven’t shared the specific pages or databases with your Notion integration. Notion’s permission model requires explicit page-level grants — a successful connection does not automatically give access to all your content. Go to the page in Notion, click the three-dot menu, choose ‘Add connections’, and select your integration.

What scopes does the Notion MCP integration need?

For read operations: Read content and Read user information. For write operations: Update content and Insert content. Avoid requesting more scopes than you need — the minimum set reduces the blast radius if a token is ever compromised. Set scopes when creating your Notion Internal Integration at notion.so/my-integrations.

Does the Notion MCP integration work with Claude Code?

Yes. Add it via ‘claude mcp add notion npx @notionhq/notion-mcp-server’ and set your NOTION_API_KEY as an environment variable. Claude Code picks it up on the next session. The self-hosted token route works in both Claude Desktop and Claude Code; the OAuth connector is currently Desktop-only.

What rate limits does the Notion API have?

Notion’s API enforces a rate limit of 3 requests per second per integration. For typical conversational use this is invisible, but if you ask Claude to crawl a large database or process many pages in sequence, you may see 429 errors. The fix is to add a short sleep between bulk operations or use Notion’s pagination to fetch in smaller batches.

📖 Related Claude Guides

June 3, 2026

How to Connect Any Tool to Claude with MCP: Complete Setup Guide

Last verified: June 2026

MCP (Model Context Protocol) is how you give Claude hands. Out of the box Claude can talk; with an MCP server connected, it can read your files, query a database, hit an API, or drive a browser. This guide covers the two places you actually wire servers up: the claude_desktop_config.json file for the Claude Desktop app, and the claude mcp add command for Claude Code (the terminal/IDE tool). It ends with the troubleshooting section the official docs skip: path problems, JSON syntax traps, servers that silently never load, and the Windows quirks that cost people an afternoon.

Everything below is checked against the current Claude Code MCP docs and tested commands. If you want the wider picture of how MCP fits into a working setup, see the AI operator’s stack.

What is MCP and what is an MCP server?

MCP transport options at a glance

Transport	Use case	Config location	Works with
stdio	Local tools, CLIs, scripts	claude_desktop_config.json or `claude mcp add`	Claude Desktop, Claude Code
SSE (HTTP)	Remote servers, cloud services	URL in config	Claude Desktop, Claude Code
Streamable HTTP	Production remote MCP	URL in config	Claude Desktop, Claude Code

MCP is an open standard for connecting AI models to external tools and data. An MCP server is a small program that exposes a set of tools (functions Claude can call) over that protocol. Claude is the client; the server is the thing that actually does the work, like reading a Postgres table or creating a GitHub issue.

There are two transport types you will deal with in practice:

stdio (local): the server runs as a process on your machine. Claude talks to it over standard input/output. Best for filesystem access, local databases, and custom scripts. This is what most “install this MCP server” instructions mean.
HTTP (remote): the server lives on the internet at a URL. Best for cloud services (Notion, Sentry, Stripe, GitHub). Often uses OAuth. SSE is the older remote transport and is now deprecated; use HTTP for new remote servers.

The same server can usually be added to both Claude Desktop and Claude Code. The mechanics differ: Desktop uses a JSON file you edit by hand, Claude Code gives you a CLI that writes the config for you.

How do I add an MCP server to Claude Desktop?

Claude Desktop reads a single JSON file. You edit it, fully quit the app, and reopen. There is no in-app “add server” button for custom servers as of June 2026, so the file is the source of truth.

Where is claude_desktop_config.json?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json (paste that into the File Explorer address bar; it expands to C:\Users\YOU\AppData\Roaming\Claude\)

The fastest way to open it: in Claude Desktop go to Settings > Developer > Edit Config. That button creates the file if it does not exist and opens the folder. If the file is brand new it may be empty or just {}.

The config file structure

Everything lives under a top-level mcpServers object. Each key is a name you choose; each value describes how to launch the server. Here is a complete, working file with a local filesystem server and a remote Notion server:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "C:\\Users\\YOU\\Documents"
      ]
    },
    "notion": {
      "command": "npx",
      "args": ["-y", "@notionhq/notion-mcp-server"],
      "env": {
        "NOTION_TOKEN": "secret_your_token_here"
      }
    }
  }
}

Three fields do all the work:

command the executable to run (npx, node, python, uvx, or an absolute path to a binary).
args an array of arguments. Each flag and value is its own array element. "--port 8080" as a single string will not work; use "--port", "8080".
env an object of environment variables (API keys, tokens). Optional.

After saving, completely quit Claude Desktop (on Windows, right-click the system tray icon and choose Quit; closing the window is not enough) and reopen it. You should see a tools/connector indicator in the chat input. For a full Notion walkthrough including the token, see connecting Notion to Claude with MCP.

How do I add an MCP server to Claude Code (CLI)?

Side-by-side cards defining what Claude Code is and is not — Add an MCP server to Claude Code CLI.

Claude Code does not make you hand-edit JSON. The claude mcp command manages servers for you and writes to the right file. This is the part people get wrong most often, so here is the exact, verified syntax.

claude mcp add

The general form for a local (stdio) server is:

claude mcp add [options] <name> -- <command> [args...]

The -- is load-bearing. Everything before it is for Claude Code; everything after it is the command that launches your server. Real examples:

# Local filesystem server
claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ~/Documents

# Local server with an environment variable
claude mcp add --env AIRTABLE_API_KEY=YOUR_KEY airtable -- npx -y airtable-mcp-server

# Remote HTTP server
claude mcp add --transport http notion https://mcp.notion.com/mcp

# Remote HTTP server with an auth header
claude mcp add --transport http github https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer YOUR_PAT"

Option ordering matters. All flags (--transport, --env, --scope, --header) must come before the server name. Put a flag after the name and you will get a confusing parse error or the flag will be passed to your server instead of to Claude Code.

Scopes: local, project, user

The --scope flag decides where the config is written and who sees it:

local (the default) loads only in the current project, private to you. Stored in ~/.claude.json keyed by the project path.
project loads in the current project and is shared with your team. Stored in a .mcp.json file at the project root that you commit to git.
user loads across all your projects, private to you. Also stored in ~/.claude.json.

# Available across all your projects
claude mcp add --scope user --transport http sentry https://mcp.sentry.dev/mcp

# Shared with your team via .mcp.json in the repo
claude mcp add --scope project filesystem -- npx -y @modelcontextprotocol/server-filesystem .

When the same server name exists at multiple scopes, local wins over project, which wins over user. The whole entry from the winning scope is used; fields are not merged.

claude mcp list, get, and remove

# List every configured server and its connection status
claude mcp list

# Show the full config for one server
claude mcp get github

# Remove a server
claude mcp remove github

claude mcp list is your first diagnostic. It shows each server as connected, pending, or failed. Project-scoped servers from a .mcp.json you have not approved yet show as Pending approval until you run claude interactively and accept them.

Other useful commands

# Add from a raw JSON blob (handy when copying from a server's README)
claude mcp add-json weather '{"type":"stdio","command":"npx","args":["-y","weather-mcp"]}'

# Import everything you already set up in Claude Desktop (macOS / WSL)
claude mcp add-from-claude-desktop

Inside a running Claude Code session, type /mcp to see live server status, tool counts, and to trigger OAuth login for remote servers that need it.

Troubleshooting: the errors the docs skip

Most MCP failures are not exotic. They are paths, quoting, and the app not restarting. Work this list top to bottom.

Server not loading / no tools appear

Did you actually restart? Claude Desktop only reads the config at launch. Fully quit (tray icon > Quit on Windows, Cmd+Q on macOS) and reopen. In Claude Code, run claude mcp list to see the real status instead of guessing.
Is the command on PATH? The single most common stdio failure is npx, node, python, or uvx not being found by the app. GUI apps often have a narrower PATH than your terminal. Fix it by using an absolute path. Find it with which npx (macOS/Linux) or where npx (Windows), then put that full path in command.
Read the logs. Claude Desktop writes per-server logs. macOS: ~/Library/Logs/Claude/. Windows: %APPDATA%\Claude\logs\. Look for mcp-server-NAME.log. The actual error (missing module, bad token, wrong path) is almost always sitting right there.

spawn ENOENT or “command not found”

This means the OS could not find the executable named in command. It is a PATH problem, not a Claude problem. Use the absolute path (see above). On Windows specifically, see the npx note below.

JSON syntax errors (the silent killer)

If claude_desktop_config.json has a single syntax error, Claude Desktop loads zero servers and usually says nothing. The usual culprits:

Trailing commas. JSON forbids a comma after the last item in an object or array. "args": ["a", "b",] is invalid.
Smart quotes. If you edited the file in a word processor, curly quotes (the slanted kind) break the parser. Use a code editor and straight quotes only.
Unescaped Windows backslashes. In JSON, \ is an escape character, so every backslash in a Windows path must be doubled: C:\\Users\\YOU\\Documents. A single backslash silently corrupts the string.

Paste the whole file into any JSON validator before restarting. Thirty seconds there saves an hour of staring.

Claude Code: flag passed to the wrong place

If claude mcp add behaves strangely, you almost certainly put a flag after the server name or forgot the --. Reread the order: claude mcp add [flags] NAME -- COMMAND ARGS. The -- separates Claude Code’s flags from your server’s command.

Windows quirks

npx needs a wrapper in some setups. If a bare "command": "npx" fails on Windows, launch it through cmd: "command": "cmd" with "args": ["/c", "npx", "-y", "the-server-package"]. This resolves a class of “npx works in my terminal but not in Claude” failures.
Use the right config root. It is %APPDATA%\Claude\ (which is AppData\Roaming), not AppData\Local. Mixing these up means you are editing a file the app never reads.
Git Bash mangles paths. If you run commands through Git Bash, it can rewrite paths like /c/Users or absolute paths inside arguments. Prefer PowerShell or cmd for claude mcp add, or pass paths exactly as Windows expects them.
WSL is a separate world. A server installed inside WSL is not visible to a Windows-native Claude Desktop, and vice versa. Keep both on the same side.

Remote server returns 401 / 403

The server needs authentication. In Claude Code, run /mcp and complete the OAuth flow in your browser. If you hardcoded an Authorization header and it is rejected, the token is wrong for that endpoint; remove the header and let OAuth handle it instead.

Frequently asked questions

What is an MCP server in one sentence?

A small program that exposes tools (functions like read-file or query-database) to Claude over the Model Context Protocol, so Claude can take real actions instead of only producing text.

What is the difference between Claude Desktop and Claude Code for MCP?

Claude Desktop is the chat app and you configure servers by hand-editing claude_desktop_config.json, then restarting. Claude Code is the terminal/IDE tool and you configure servers with the claude mcp add command, which writes the config for you.

Where is the Claude Desktop config file?

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. Windows: %APPDATA%\Claude\claude_desktop_config.json. The quickest way to open it is Settings > Developer > Edit Config inside the app.

Why is my MCP server not showing up?

In order of likelihood: you did not fully restart the app, the command is not on the app’s PATH (use an absolute path), or there is a JSON syntax error such as a trailing comma, a smart quote, or an unescaped Windows backslash. Check the per-server log in the Claude logs folder for the exact error.

What does the double dash do in claude mcp add?

The -- separates Claude Code’s own flags from the command that launches your server. Flags like --transport and --env go before it; the actual launch command (npx -y some-server) goes after it.

What is the default scope for claude mcp add?

local. The server loads only in the current project and stays private to you. Use --scope user to make it available in every project, or --scope project to share it with your team via a committed .mcp.json.

Is SSE or HTTP the right transport for remote servers?

HTTP. SSE still works but is deprecated. Use --transport http for any new remote server unless its documentation specifically requires SSE.

How do I remove an MCP server?

In Claude Code, run claude mcp remove NAME. In Claude Desktop, delete that server’s entry from the mcpServers object in claude_desktop_config.json and restart the app.

Where to go next

Once your servers connect cleanly, the leverage comes from using them well. For how this fits a daily workflow, read the AI operator’s stack; if you are choosing between coding environments, see Claude Code vs Cursor. And if you want a concrete first server to wire up, the Notion MCP setup is a clean, high-value place to start.

Frequently Asked Questions

What is MCP and why does it matter for Claude?

MCP (Model Context Protocol) is an open standard that lets Claude connect to external tools, databases, APIs, and services. Without MCP, Claude can only work with text in the conversation window. With an MCP server connected, Claude can read your files, query a live database, hit an API, or control a browser — turning it from a chat interface into an autonomous agent.

How do I add an MCP server to Claude Desktop?

Edit the claude_desktop_config.json file (found at ~/Library/Application Support/Claude/ on Mac, %APPDATA%/Claude/ on Windows). Add your server under the ‘mcpServers’ key with a ‘command’, ‘args’, and optional ‘env’ block. Save the file and restart Claude Desktop. The server appears in Claude’s tool list if it loaded correctly.

How do I add an MCP server to Claude Code?

Run ‘claude mcp add [args…]’ from your terminal. For a remote SSE server use ‘claude mcp add –transport sse ‘. List configured servers with ‘claude mcp list’. Servers added this way are scoped to your user profile unless you use the –project flag.

Why does my MCP server connect but Claude can’t see my data?

The most common cause is scope or permission gaps. For Notion, verify your integration has been granted access to the specific pages/databases — the connection succeeds even without page access. For file servers, check that the path in your config resolves correctly from the shell Claude launches (not your interactive shell). For OAuth servers, re-authorize and confirm token scopes.

What is the difference between stdio and SSE MCP transports?

stdio runs the MCP server as a local subprocess — Claude launches the command you specify and communicates over stdin/stdout. This is used for local tools and CLIs. SSE (Server-Sent Events) connects to a remote HTTP server. Use stdio for local tools like filesystem access or database clients; use SSE or Streamable HTTP for cloud services or shared team servers.

Which MCP servers should I start with?

The highest-value first connections are: filesystem (read/write your local files), a database client for your primary DB, and a service you interact with daily (Notion, Slack, GitHub, Linear). The Notion MCP server is a clean first project — see the dedicated setup guide on this site for the exact config and common errors.

📖 Related Claude Guides

June 3, 2026

The AI Operator’s Stack: How One Person Runs a Multi-Brand Content Machine

Last verified: June 2026.

Most “AI stack” articles hand you a list of tools. This one is about the wiring between them, because that is where the leverage lives. After running a multi-brand content operation end to end – research, writing, publishing, and distribution to a couple dozen destinations – one lesson keeps repeating: the tools are commodities, and the connective tissue is the moat. Here is the whole machine, and how the pieces talk to each other.

One machine, four jobs

One machine, four jobs.

The stack has four jobs: capture an idea, produce the content, remember everything, and distribute it where both people and AI engines will find it. Miss any one and the system stalls.

1. Intelligence and intake

The front door is an “AI as PR team” intake: you drop a raw thought, a link, or a voice memo, and the model turns it into the right shapes – an outline, a short post, a full brief. A lightweight signal scraper watches a professional network for the language practitioners actually use and feeds those angles back as prompts, so the writing starts from how people really talk instead of a blank page.

2. Production

Claude is the reasoning engine. A content pipeline turns a brief into a structured article; an image model generates the visuals; and a set of “beat desks” – small scheduled agents, each owning one topic – research, draft, quality-gate, and self-publish to WordPress through its REST API. Every desk has a freshness gate: if there is nothing genuinely new and sourceable, it skips the run rather than manufacture filler. A clean skip is a successful run.

3. Record and state

Notion is the control plane – the registries, the per-desk specs, the run logs, the system of record. The governing principle is load-bearing: the model is not the runtime. Claude supplies judgment; durable execution lives on schedulers and cloud jobs; Notion holds the state. Separate those three and the machine keeps running whether or not anyone is watching it.

4. Distribution and grounding

This is the layer most stacks forget, and the one that compounds. Publishing to your own site is half the job; the other half is getting that content into the indexes search engines and AI assistants actually read. Two moves do the heavy lifting. First, IndexNow pings the Bing index the moment anything changes – that is how new and updated content gets grounded fast instead of waiting on a crawl. Second, a social scheduler fans a tailored post out to a professional network – a personal profile plus company pages – drafted first for human approval, never blasted.

Here is the part worth internalizing: that professional network matters far more than its follower count suggests, because it is one of the most-cited domains in AI answers. Since it flows into the same index that feeds AI grounding, every post is also a citation asset. You are not chasing likes – you are seeding the corpus that AI engines quote back to the next person who asks.

The loop that compounds

The loop that compounds.

The layers are not a straight line; they form a loop. A researched social post is a compressed seed. Crack it open into a full article cluster – a core piece, audience-specific variants, an FAQ, schema, internal links – publish those, then queue the new URLs back to the scheduler as future posts. Social feeds the site; the site feeds social; both feed the grounding layer. Content you already made becomes the raw material for what you make next.

Why every layer optimizes for citation

Why every layer optimizes for citation.

AI engines do not cite broad overviews. They cite operational specifics, head-to-head comparisons, and fresh, dated facts. So the whole stack is tuned for that: specific over general, “this versus that” where it genuinely helps a reader decide, and same-day freshness on anything that changes. The pages that earn the most citations are the least glamorous – the exact limits, the real configuration, the honest comparison – because those are the answers nobody else keeps current.

The honest edges

This is maintained, not magic. Long-form articles on a professional network have no public API, so that step is a manual paste – and it happens to be the most citation-valuable format, which means the highest-value action is also the least automatable one. Auth tokens expire and quietly break distribution until someone notices. Account IDs drift, so you verify live before any bulk action. The wiring is powerful precisely because keeping it wired is real work.

Related on Tygart Media: Cursor command center · fleet bots · Notion second brain.

Frequently asked questions

Do you need to be a developer to run this?

No, but you need to be comfortable wiring tools together – connecting an API, editing a config file, reading a log. The reasoning model closes much of that gap, but the operator still has to understand how the pieces connect.

Why optimize for Bing and not just Google?

Because the AI assistants people increasingly ask their questions to are grounded substantially on the Bing index. Winning that index is how you get cited in AI answers – a different and faster game than ranking on a traditional results page.

Is the social distribution automated?

The drafting is. Publishing is draft-first: the system stages every post for a human to approve before it goes live. Automation writes; a person decides.

What is the single highest-leverage piece?

The connective tissue – the model-context wiring that lets the brain reach your tools, and the distribution wiring that pushes finished content into the indexes AI reads. Start there. See our guide to connecting any tool to Claude with MCP and how AI engines actually cite content.

June 3, 2026

Tag: Notion

Conference Starter Pack

What’s in the pack

1. Owner Bottleneck Self-Assessment

2. 1-3-1 Delegation Worksheet

3. 5 Ds Succession Risk Checklist

What to do after the three

If you want the packaged pack

Complete Restoration Operating System (Notion + AI)

What it is

The six Notion tools

The 17 SOPs to write (or adopt)

The 12 KPIs

How to hang it yourself

How the system runs day to day

The 8 AI skills

Install the plugin yourself

If you want the packaged system

Related restoration products

Accountability Conversation Planner

How to use it

The six prompts

1. What is the actual issue?

2. What specific behavior needs to change?

3. What have I already allowed or tolerated?

4. What expectation needs to be clarified?

5. What consequence or support is needed?

6. What does success look like in 30 days?

Conversation script outline

Follow-up

If you want the packaged planner

90-Day Doer-to-Leader Transition Plan

How to use this plan

Weeks 1-2. Identify your bottlenecks

Weeks 3-4. Install 1-3-1 conversations

Weeks 5-6. Clarify decision rights

Weeks 7-8. Develop one manager

Weeks 9-10. Create an accountability rhythm

Weeks 11-12. Review, adjust, and repeat

Success looks like

If you want the packaged plan

5 Ds Succession Risk Checklist

How to run it

1. Death. If you died tomorrow

2. Divorce. If your marriage ended

3. Disease. If you were medically out for 30-90 days

4. Drugs / dependency. If you (or a key person) became unreliable

5. Departure / disaster. If a key person walked, or the building burned

Overall exposure rating

Top 3 shore-ups

If you want the packaged checklist

1-3-1 Delegation Worksheet

The old way vs the 1-3-1 way

The rule

How to install it

The worksheet (copy this)

Who and when

1. The issue / decision needed

3. The three options

1. My recommendation

What I will do if I do not hear back

Owner decision / sign-off

Owner gut-check before you sign

If you want the packaged worksheet

Day One: The Model Dropped and I Put It to Work

Day Two: Fable 5 Ran My Entire SEO Audit

Day Three: Building the Infrastructure Layer

What Fable 5 Actually Felt Like

What Most Commentators Are Missing

What I Lost

What Happens Now