Tag: Notion

  • Email Automation Setup for Restoration CRM Outreach: Technical Implementation Guide

    Email Automation Setup for Restoration CRM Outreach: Technical Implementation Guide

    Who this is for: The person setting up your email system — your office manager, your IT contact, or a freelance marketing person you’ve brought in. This brief assumes basic comfort with web-based software (setting up accounts, uploading files, clicking through settings). No coding required. The strategy behind this system is in Your CRM Is Not a Lead Database and the full 12-month calendar is in The 12-Month CRM Touch Calendar.


    What We’re Building

    A four-to-six email annual touch sequence for three audience segments (homeowners, industry contacts, trade contacts), running through a standard email marketing platform, triggered on a predetermined calendar, and tracked in a simple Notion or spreadsheet log.

    The system requires no custom development. It uses off-the-shelf software that any non-technical person can configure in an afternoon. Total ongoing maintenance time after setup: approximately one hour per campaign, four to six times per year.


    Platform Selection: Mailchimp vs. Brevo for Restoration Companies

    Both platforms are appropriate for this use case. Choose based on your database size and send frequency:

    Choose Mailchimp if: Your database is under 1,500 contacts, you want the most widely documented platform (easiest to find help online), and you’re comfortable paying $13–$30/month. Mailchimp’s Essentials plan is sufficient — you do not need Standard or Premium for this use case.

    Choose Brevo if: Your database is over 1,500 contacts, you only send 4–6 times per year and want to avoid paying for contacts you rarely email, or you want built-in transactional email for other automations. Brevo’s Starter plan is $9/month with no contact storage limits — you pay based on emails sent, not contacts stored. For a 2,000-contact database sending 6 campaigns per year, Brevo costs significantly less than Mailchimp.

    The setup instructions below cover both platforms in parallel. Follow the path that matches your platform choice.


    Step 1: Account Setup and List Import

    Complete the database segmentation build from the CRM segmentation technical brief before starting this step. You should have three clean CSV files: Homeowners, Industry, and Trade.

    Mailchimp Setup

    1. Create account at mailchimp.com. Select Essentials plan. Enter billing info.
    2. Go to Audience → Manage Audience → Add a Field. Add two custom merge fields: JOB_TYPE (text) and SEGMENT (text). These allow personalization tokens in email copy.
    3. Go to Audience → Manage Audience → Import Contacts. Upload each CSV file separately, assigning a tag during each import: “Homeowner”, “Industry”, “Trade”.
    4. Map CSV columns to Mailchimp fields: First Name → FNAME, Last Name → LNAME, Email → EMAIL, Job Type → JOB_TYPE, Segment → SEGMENT.
    5. After import, verify contact counts match your spreadsheet totals. A mismatch usually means invalid email format in some rows — check the import error log.

    Brevo Setup

    1. Create account at brevo.com. Select Starter plan ($9/month).
    2. Go to Contacts → Lists → Create a List. Create three lists: “Homeowners”, “Industry Contacts”, “Trade Contacts”.
    3. Go to Contacts → Import Contacts. Upload each CSV, assign to the corresponding list.
    4. Map fields: First Name → FIRSTNAME, Last Name → LASTNAME, Email → EMAIL. Create custom attributes for JOB_TYPE if needed.
    5. Verify counts after import.

    Step 2: Sender Domain Authentication (Critical for Deliverability)

    This is the step most people skip and then wonder why their emails land in spam. Both Mailchimp and Brevo require domain authentication to ensure your emails are delivered to inboxes rather than spam folders. This step requires access to your domain’s DNS settings (usually managed through your domain registrar — GoDaddy, Namecheap, Google Domains, or similar).

    What Authentication Does

    SPF, DKIM, and DMARC records tell receiving mail servers that your email marketing platform is authorized to send email on behalf of your domain. Without them, major providers (Gmail, Outlook, Yahoo) increasingly route your emails to spam or refuse delivery entirely.

    Mailchimp Domain Authentication

    1. In Mailchimp, go to Account → Settings → Domains → Add and Verify Domain
    2. Enter your company domain (e.g., yourcompany.com)
    3. Mailchimp will provide you with specific DNS records to add: a CNAME record for DKIM and a TXT record for verification
    4. Log into your domain registrar and add these records exactly as shown. Allow 24–48 hours for DNS propagation.
    5. Return to Mailchimp and click “Authenticate Domain” once DNS has propagated. A green checkmark confirms success.

    Brevo Domain Authentication

    1. Go to Settings → Senders & IP → Domains → Add a Domain
    2. Enter your domain and follow the same process — Brevo provides specific DNS records for SPF and DKIM
    3. Add records at your domain registrar. Verify in Brevo after propagation.

    If your company uses a shared hosting email (e.g., yourbusiness@gmail.com rather than yourbusiness@yourcompany.com), you cannot authenticate a shared domain. In this case, create a free Google Workspace account at $6/month to get a branded email address before proceeding. Sending from info@yourcompany.com vs. yourcompany@gmail.com meaningfully affects both deliverability and perceived professionalism.


    Step 3: Build the Campaign Templates

    For the CRM community touch strategy, plain text emails outperform designed HTML templates. Research on warm, relationship-based email consistently shows that recipients perceive plain text as more personal and authentic. The goal is an email that looks like it came from a person, not a marketing department.

    Mailchimp Plain Text Campaign

    1. Go to Campaigns → Create Campaign → Email
    2. Select “Plain Text” as the campaign type (not the drag-and-drop builder)
    3. Write your email copy in the plain text field
    4. Use Mailchimp merge tags for personalization: *|FNAME|* for first name, *|JOB_TYPE|* for the custom job type field
    5. Example: “Hi *|FNAME|*, It’s [Owner Name] from [Company]. We worked with you on your *|JOB_TYPE|* job a while back…”
    6. Set up subject line, preview text, from name (use owner’s first name, e.g., “Mike from Acme Restoration”), and from email address (owner’s direct email preferred over info@ for homeowner segment)

    Brevo Plain Text Campaign

    1. Go to Campaigns → Email Campaigns → Create an Email Campaign
    2. Choose “Plain Text” from the template selection
    3. Use Brevo’s personalization tokens: {{ contact.FIRSTNAME }}, {{ contact.JOB_TYPE }}
    4. Configure sender name and address as above

    Build all six campaigns for the year in draft mode before publishing any of them. Label each draft clearly: “Q1-2026-Homeowners-Hiring”, “Q2-2026-Homeowners-Storm-Prep”, etc. This allows you to see the full year’s campaign lineup at once and catch any overlap or redundancy before it goes out.


    Step 4: Schedule the Campaign Calendar

    Mailchimp Scheduling

    1. Open each draft campaign
    2. In the Campaign Builder, go to the Schedule step
    3. Select “Schedule” and set the date and time. Use the send time optimization feature if available on your plan — it will automatically send to each contact at the time they’re most likely to open based on historical behavior.
    4. For your first campaign (no historical data), use Tuesday or Wednesday at 9:30am local time as a default

    Brevo Scheduling

    1. In the campaign builder, select “Schedule” on the final step
    2. Set date, time, and timezone
    3. Brevo’s Send Time Optimization is available on paid plans and functions similarly to Mailchimp’s

    Schedule all three segment versions of each campaign within the same 2-hour window on the same day — homeowners first, then industry, then trade — staggered by 30 minutes. This prevents simultaneous reply volume from overwhelming a single inbox.


    Step 5: Build the Results Tracking System in Notion

    Both platforms provide analytics (open rate, click rate, unsubscribes) automatically. The tracking that neither platform does is the qualitative signal — replies, referrals, leads mentioned, and relationship warmth indicators. That layer goes in Notion.

    Setting Up Notion (Free Tier)

    1. Go to notion.com and create a free account
    2. Create a new page called “CRM Touch Calendar”
    3. Add a database (table view) with the following properties:
    Property Type
    Campaign Name Title
    Send Date Date
    Segment Select (Homeowners / Industry / Trade / All)
    Touch Type Select (Operational Ask / Educational / Milestone / Seasonal)
    Platform Select (Mailchimp / Brevo / CRM)
    Status Select (Planned / Draft Ready / Scheduled / Sent)
    Open Rate Number (percent)
    Reply Count Number
    Referrals Generated Number
    Leads Mentioned Number
    Notes Text (for qualitative observations)
    1. Add all six planned campaigns for the year as rows in the database
    2. Set the Status to “Planned” for all. Update to “Draft Ready”, “Scheduled”, and “Sent” as you progress
    3. After each campaign sends, log the open rate from your email platform and manually count and log reply count, referrals, and lead mentions from your email inbox

    The Notion database becomes your campaign intelligence layer. After two or three years of data, you’ll have clear evidence of which touch types generate the highest referral rates, which segments are most engaged, and which subject lines perform best for your specific audience.


    Step 6: Set Up Reply Management

    For the homeowner and industry segments, replies to hiring emails and vendor asks often include lead mentions (“actually, our neighbor just had water get in last week”). These need to route to whoever handles incoming leads immediately, not sit in an inbox until someone reviews the campaign results.

    The simplest solution: create a dedicated email address (campaigns@yourcompany.com or outreach@yourcompany.com) as the reply-to address for all campaigns. Set up a simple email rule that forwards any reply mentioning keywords like “water”, “damage”, “claim”, “flooded”, “burst”, or “insurance” to your main dispatch email address.

    In Gmail, set this up under Settings → Filters and Blocked Addresses → Create a new filter. In Outlook, use Rules → Create a New Rule. Set the trigger to “subject or body contains” and the action to “forward to [dispatch email]”. This catches the accidental leads without requiring manual review of every reply.


    Cost Summary

    Item One-Time Monthly Annual
    Mailchimp Essentials (500 contacts) $0 $13 $156
    Mailchimp Essentials (1,000 contacts) $0 $20 $240
    Brevo Starter (unlimited contacts) $0 $9 $108
    Google Workspace (if needed for branded email) $0 $6 $72
    Notion free tier $0 $0 $0
    Email validation (one-time list clean) $5–$15 $0 $0

    Total annual cost for a fully operational system: $108–$312 depending on platform choice and contact volume. This covers 4–6 campaigns per year to a warm, segmented local database of up to 2,000 contacts.


  • The 12-Month CRM Touch Calendar for Restoration Companies

    The 12-Month CRM Touch Calendar for Restoration Companies

    The hiring email works. The vendor ask works. The educational resource works. The problem is that none of them happen consistently unless they’re on a calendar with an owner, a template, and a send date.

    This article is the hub of the entire CRM Community Framework — the piece that turns a good idea into a running system. Everything in the strategy described in Your CRM Is Not a Lead Database lives or dies by whether it gets scheduled.

    What follows is a full 12-month outreach calendar for a restoration company, built around legitimate business triggers. Every touch has a reason that isn’t “we want to sell you something.” Every touch reinforces that your company is active, professional, and thinks of its network as more than a lead source.


    The Architecture: Four Touch Types Across Twelve Months

    A sustainable touch cadence has four types of emails distributed across the year. Too many of one type and it starts to feel like a newsletter you never asked for. The right mix keeps the relationship varied, human, and genuinely useful.

    Type 1: Operational Ask (2x per year)

    A real business need: hiring, vendor search, supplier sourcing. These are your highest-engagement emails because recipients can actually help you with something concrete. They feel useful to the sender. Covered in detail in the hiring email guide and the vendor ask guide.

    Type 2: Educational Resource (2x per year)

    A genuinely useful piece of content — a seasonal maintenance checklist, a guide to what to do in the first 24 hours after a pipe burst, a “what your insurance actually covers” plain-language explainer. No CTA beyond “thought you’d find this useful.” The goal is to be the trusted expert in their inbox, not the company asking for something.

    Type 3: Company Milestone or Update (1x per year)

    An anniversary, a new certification, a new service area, an award or recognition. Framed around what it means for the people in your network — not as a press release. “We just hit five years and I wanted to thank the people who’ve trusted us with their homes and their claims.” This is the most relationship-dense email of the year and the one most restoration companies never send.

    Type 4: Seasonal Safety or Storm Alert (1x per year)

    Before major storm season, freeze season, or wildfire season depending on your geography, a brief heads-up email positions you as the local expert who thinks about their community’s safety. No pitch. Just: “Freeze season is coming — here are three things to check in your home before temps drop.” A link to a longer blog post if they want more detail. Short, local, relevant.


    The 12-Month Calendar Template

    Adapt the timing based on your region and business cycle. The example below assumes a general U.S. market with standard restoration seasonality (storms in spring/summer, freeze in winter). Adjust as needed.

    January: Seasonal Safety Email

    Type: Type 4 — Seasonal Safety
    Audience: Full database
    Trigger: Winter freeze season
    Content: “Three things to check before a hard freeze” — pipes, outdoor faucets, HVAC filters, sump pump. Link to a full blog post if you have one. 150 words max.
    Why it works: January is a low-activity month for most homeowners. A helpful, non-promotional email from a company they already trust is genuinely welcome.

    March: Hiring Email (if applicable) OR Vendor Ask

    Type: Type 1 — Operational Ask
    Audience: Three segments (homeowners, industry, trade)
    Trigger: Spring hiring cycle begins, or sourcing subs for storm season
    Content: Use the templates from the hiring or vendor guides. If you’re not hiring, a specialty sub search ahead of storm season is always relevant in Q1/Q2.
    Why it works: Spring is when most restoration companies start ramping for busy season — hiring and vendor sourcing at this time is authentic and expected.

    May or June: Educational Resource

    Type: Type 2 — Educational Resource
    Audience: Homeowners only
    Trigger: Pre-storm season
    Content: “Your storm prep checklist for [your region]” — gutters, roof, trees near the house, emergency kit, insurance policy review. One page. No CTA other than “save this somewhere useful.”
    Why it works: This email will be forwarded. Homeowners share safety resources with neighbors and family. It’s one of the highest organic-reach emails you’ll send all year.

    August or September: Company Milestone Email

    Type: Type 3 — Company Update
    Audience: Full database
    Trigger: Company anniversary, new certification (IICRC, RIA), new service area, or team growth milestone
    Content: Short, personal note from the owner. Thank the people who’ve been part of the journey. Mention what’s new. No ask. Just appreciation.
    Why it works: Late summer is a natural “back to business” moment. A warm, human email from a company you’ve worked with is a pleasant interruption in a busy inbox.

    October or November: Hiring OR Vendor Ask (second round)

    Type: Type 1 — Operational Ask
    Audience: Three segments
    Trigger: Pre-winter hiring, or sourcing vendors for year-end projects
    Content: Second operational ask of the year. If you hired in March, this is a different position or a referral partner ask. Vary the type so it doesn’t feel like a pattern.
    Why it works: Fall is another natural hiring window. And year-end is when restoration companies start planning vendor relationships for the coming season.

    December: Educational Resource (Optional)

    Type: Type 2 — Educational Resource
    Audience: Homeowners
    Trigger: Holiday season, travel, and winter property risks
    Content: “What to check before you leave for the holidays” — water shutoff, thermostat settings, emergency contacts. Optional — if you already sent a freeze checklist in January, this may feel redundant. Only send if the content is genuinely different and useful.
    Why it works: December holiday homeowner emails have strong open rates because they’re immediately relevant to something the homeowner is actively thinking about.


    The Minimum Viable Calendar: If You Do Nothing Else

    If the full six-touch calendar feels like too much to start, here is the two-email annual minimum that will still meaningfully move the needle:

    1. March or April: One operational ask (hiring or vendor). Three segments. Uses the templates from the other guides in this series.
    2. June or July: One educational resource (storm prep checklist). Homeowners only. No CTA.

    Two emails per year to a warm local database of 400–800 contacts will reach more people with a higher quality impression than $2,000 spent on Facebook ads to a cold audience. The bar is genuinely that low — because almost nobody in the restoration industry is doing this at all.


    The Technical Setup: Building the Calendar in Notion

    The Notion free tier (available at notion.com — free for individuals and small teams) is sufficient for this system. You need one database with the following properties:

    Property Type Purpose
    Email Name Title What this touch is called
    Send Date Date Scheduled send date
    Touch Type Select Operational Ask / Educational / Milestone / Seasonal Safety
    Audience Select Full Database / Homeowners / Industry / Trade
    Platform Select Mailchimp / Brevo / CRM / Direct
    Status Select Planned / Draft Ready / Scheduled / Sent
    Template Link URL Link to the draft in Mailchimp or the Notion doc with the copy
    Results Text Open rate, replies received, referrals generated

    Create a calendar view of this database filtered to the current month. Every Monday, glance at it. If something is sending in the next two weeks and isn’t in “Draft Ready” status, that’s your action item for the week.

    Set the following Notion reminders on each row: 14 days before send date (“write/review draft”), 3 days before send date (“schedule in email platform”), 1 day after send date (“log results”).


    Connecting the Calendar to Your Email Platform

    For Mailchimp Users

    Build a campaign for each email in advance using Mailchimp’s campaign drafts feature. Give each draft a name that matches the Notion database row (e.g., “March 2026 — Hiring Email — Homeowners”). When the draft is ready, link it in the Template Link field of your Notion row. Schedule it in Mailchimp 3 days before your intended send date so you have time to make last-minute adjustments. After sending, pull the open rate and reply count from Mailchimp’s Reports tab and log them in the Results field in Notion.

    For Brevo Users

    Brevo’s Campaigns section works the same way — drafts can be built in advance and scheduled. Brevo’s analytics are straightforward: open rate, click rate, unsubscribes. Log these in Notion after each send.

    For CRM-Native Email (Jobber or ServiceTitan)

    Neither platform has robust campaign scheduling, so the process is more manual. Build the email copy in Notion, then on the scheduled send date, copy it into your CRM’s email function and send manually. Log results in Notion immediately after.


    Using Claude to Maintain the Calendar Year Over Year

    After your first year running this system, you’ll have a Notion database with six email records, each containing the copy, the results, and the audience. In year two, you don’t start from scratch — you improve what worked and adjust what didn’t.

    Here’s a prompt you can use at the start of each year to refresh your calendar with Claude:

    “I run a restoration company in [city] and I send 4–6 emails per year to my CRM database to stay top of mind. Here are the emails I sent last year and their results: [paste Notion export]. Based on these results and the current time of year ([month]), help me plan this year’s calendar. Suggest which touch types to repeat, which to update, and any new ones that might be relevant given [any business changes — new service area, new certifications, team growth, etc.]. Keep the total to 4–6 sends.”

    This is the compound interest of the system — each year’s data makes next year’s calendar smarter and more targeted.


    The Results You Should Expect

    Realistic benchmarks for a warm local restoration CRM database of 300–800 contacts:

    • Open rate: 30–45% for operational asks and seasonal safety emails; 25–35% for educational resources; 40–55% for the company milestone email (people open personal notes)
    • Reply rate: 2–8% on operational asks (higher for the hiring email in our experience); under 1% on educational content (they read, they don’t reply)
    • Referral rate: 0.5–2% per operational ask email (so 2–16 referrals per campaign for a 800-contact list)
    • Lead mentions in replies: Expect 1–4 per operational ask campaign from homeowners who mention a neighbor or family member who “just had something happen”

    These numbers are modest. The cumulative effect across 4–6 touches per year is not. A company that consistently runs this system for three years has touched every warm contact in their database 12–18 times with relevant, human, non-salesy content. That is a referral pipeline that no Google Ads campaign can build.


    Frequently Asked Questions

    How do I know if I’m emailing too much?

    Watch your unsubscribe rate. For a warm local database, a healthy unsubscribe rate is under 1% per campaign. If you’re consistently seeing 2–3%+ unsubscribes, reduce frequency or audit whether your content is genuinely useful vs. promotional.

    Should every touch include an offer or discount?

    No. This is the most important rule of the system. The moment your CRM emails start offering 10% off water damage mitigation, you’ve converted them from relationship touches into promotional emails. Your contacts will start treating them as such — lower open rates, more unsubscribes, zero referrals. Keep the strategy clean: no promotions, no CTAs, no discounts. Just presence.

    What if we miss a planned send date?

    Send it anyway, or skip it and move to the next one. A late educational resource is still useful. A late hiring email is no longer authentic if you’ve already filled the position. Use your judgment — the goal is consistency over perfection, and six emails per year gives you enough margin that a missed one doesn’t break the system.

    Can we automate any of this?

    The scheduling and platform side can be automated — Mailchimp sequences can be set to send automatically on a schedule. The content should not be fully automated. Each touch should have a human review before it goes out, especially the operational asks and the milestone email. The value of this system comes from its authenticity. Automation can help with logistics; it cannot replace judgment.


  • The Vendor Ask Email: How Restoration Companies Turn Operational Needs Into Community Touchpoints

    The Vendor Ask Email: How Restoration Companies Turn Operational Needs Into Community Touchpoints

    You need a reliable drywall sub. Or a specialty cleaning supplier. Or a caterer for your company appreciation event. Or an electrician you can confidently refer to homeowners after the remediation is done.

    These are real operational needs that every restoration company has constantly. Most owners solve them the hard way — Google searches, calls to other contractors, trial-and-error with vendors they find cold. What almost nobody does is the obvious thing: ask the 600 people in their database who already know and trust their company.

    This guide covers the vendor and supplier outreach strategy — the second major touchpoint in what we call the CRM Community Framework. You don’t need a new hire to execute this. You need one email, one segment, and 30 minutes.


    Why This Works When Cold Outreach Doesn’t

    When you post a vendor search on a trade forum or send a cold email to a supplier you found online, you’re a stranger. The vendor has no context for who you are, what volume you do, or whether you pay on time. The relationship starts at zero.

    When you email your CRM database with a vendor ask, every person receiving that email has a prior relationship with your company. Past homeowner clients know you did good work and were professional. Insurance adjusters have worked claims with you. Subcontractors know how you run a job. These are warm introductions waiting to happen — you just have to ask for them.

    And here’s the secondary benefit that most owners miss: even the contacts who don’t know a vendor are being reminded that your company is active, growing, and doing interesting projects. A vendor ask email signals operational health. Companies that are struggling don’t post on social media or send emails about sourcing suppliers for interesting projects. It is passive brand maintenance disguised as a practical business email.


    The Vendor Ask Taxonomy: What’s Worth Sending

    Not every operational need warrants a database email. The test is simple: would a genuinely good referral from someone in my network be more valuable than what I’d find cold? If yes, send it. Here are the categories that consistently pass that test:

    Specialty Subcontractors

    Drywall, painting, flooring, HVAC, electrical, plumbing. Any trade you regularly need for rebuild phases but don’t always have on contract. Your past clients include property managers, contractors, and homeowners who’ve renovated — they know tradespeople. Your adjusters know everyone in the local restoration and construction ecosystem. This is your highest-yield vendor ask category.

    Specialty Suppliers

    A new product line you’re adding (e.g., antimicrobial coatings, specialty cleaning agents), equipment suppliers you haven’t worked with, or a specific vendor for a material type you don’t use regularly. Your trade contacts and vendor network are the right audience for this one.

    Service Vendors for Your Own Business

    Catering for a company event. A photographer for updated headshots or job site documentation. A branded merchandise vendor for uniforms or promotional items. A commercial cleaning company for your shop or vehicles. These asks go to your full database — homeowners and industry contacts alike. They’re genuinely human asks that anyone could help with.

    Referral Partners for Post-Job Services

    The restoration job is done. Now the homeowner needs a good contractor for reconstruction, a HVAC tech for the system you flagged, or a structural engineer to sign off on something. Building a trusted referral list for these services is valuable for your clients and your reputation. Email your database: “We’re looking for a structural engineer we can confidently recommend to clients in the [market] area. If you know someone exceptional, I’d love an introduction.”


    The Email Copy: Vendor Ask Templates

    Same rules as the hiring email: short, plain text, personal tone, no sales pitch. The vendor ask should feel like a text message from a professional, not a procurement RFP.

    Template A: Specialty Sub Search (Full Database, Local Filter)

    Subject line: Looking for a great [trade] sub in [city/region] — know anyone?

    Hi [First Name],

    Quick ask — we’re working on a larger project coming up and are looking for a reliable [drywall / flooring / painting / electrical] subcontractor in the [city] area. Someone who does quality work and communicates well.

    If you know anyone in the trades who fits that description, I’d love a quick introduction. Just reply here with their name and contact info and I’ll take it from there.

    Thanks in advance, and hope you’re doing well.

    [Your Name]
    [Company Name]
    [Phone]


    Template B: Referral Partner Ask (Full Database)

    Subject line: Building our referral network — do you know a great [contractor type]?

    Hi [First Name],

    One thing we try to do well is connect our clients with trusted professionals for the work that comes after our part is done. We’re currently building out our referral list for [reconstruction contractors / structural engineers / HVAC techs / general contractors] in the [region] area.

    If you’ve worked with someone exceptional and would trust a personal recommendation, I’d genuinely appreciate the introduction. We’re not looking for a business arrangement — just trying to build a list of people we’d feel confident referring to our clients.

    Reply any time. And as always, if you ever need anything from us, don’t hesitate.

    [Your Name]
    [Company Name]


    Template C: Event Vendor or Business Service (Warm Contacts, Full Database)

    Subject line: Random ask — do you know a good [caterer / photographer / printer]?

    Hi [First Name],

    Totally different kind of email from me — we’re putting together a company appreciation event this spring and I’m looking for a caterer in the [city] area who does great work for smaller groups. Anything in the 30–50 person range.

    If you have a go-to recommendation, I’d love to hear it. Reply here and I’ll reach out directly.

    Hope things are good on your end.

    [Your Name]


    The Technical Setup: Same Infrastructure, Different List

    If you’ve already built the three-segment email setup from the hiring email guide, you’re 80% done. The vendor ask uses the same list infrastructure. The only question is which segments receive which version:

    • Specialty sub search: Send to all three segments. Homeowners know tradespeople. Adjusters know the construction ecosystem. Trade contacts know it best of all.
    • Referral partner ask: Send to homeowners and industry contacts. Trade contacts already know your referral landscape.
    • Event vendor / business service: Send to your full database. This is a fully human ask that anyone could help with.

    One tactical addition for vendor asks vs. hiring emails: consider adding one line at the bottom that invites the vendor themselves to reach out if the ask describes their own business. “If this describes you or your company, feel free to reply directly.” This occasionally turns a referral request into a direct vendor relationship.


    Building This Into a System: The Notion Vendor Tracker

    The vendor ask email generates two kinds of value: immediate referrals and long-term intelligence about who in your network knows whom. To capture both, build a simple tracker in Notion (free tier works fine for this).

    Your Notion Vendor Tracker needs four database properties:

    1. Vendor Name — the business or person being referred
    2. Trade/Service Type — what they do
    3. Referred By — which contact in your database made the referral (linked to your contact database)
    4. Status — Contacted / Vetted / Active Vendor / Not a Fit

    Every reply to a vendor ask email gets a row in this database. After 12 months of running this strategy quarterly, you’ll have a vendor intelligence layer that no competitor can replicate — because it came from your specific network, not a cold search.

    The Referred By column is especially valuable. Over time, you’ll see which contacts in your database are the most connected and most likely to generate useful introductions. These are your super-connectors. They deserve extra attention in your community touch cadence.


    Using Claude to Write Vendor Ask Emails for Any Scenario

    The templates above cover the most common scenarios. For anything else, here are four prompts you can paste directly into Claude at claude.ai:

    For a specialty sub search:

    “Write a short, plain-text email from a restoration company owner to their past client database. We’re looking for a reliable [trade type] subcontractor in [city/region] for an upcoming project. The tone should be warm and direct — like a personal note, not a business solicitation. Ask if they know anyone who does quality work in this trade. Keep it under 100 words. Sign it from [owner name] at [company name].”

    For a referral partner ask:

    “Write a short email from a restoration company owner to insurance adjusters and past clients. We’re building a referral list of trusted [contractor type / engineer type] for post-restoration work, and we’re asking our network for recommendations. We’re not offering a referral fee — just trying to build a list of people we’d feel comfortable referring our clients to. Keep it under 120 words, conversational tone.”

    For an event vendor ask:

    “Write a casual, friendly email from a business owner to their contact list asking for a recommendation for a [caterer / event space / photographer] for a small company event of about [number] people in [city]. It should feel like texting a friend, not a business email. Under 80 words.”

    For customizing to your market:

    “I run a restoration company in [city] that handles residential water, fire, and mold jobs. My typical CRM contact is a homeowner who had a claim 1–3 years ago, or an insurance adjuster I’ve worked with on claims. Write a vendor ask email to this audience for [specific need]. Match the tone of this example from our company: [paste an example email you’ve written].”


    Frequently Asked Questions

    How is a vendor ask email different from spam?

    The key difference is relationship context. You’re emailing people who have a prior relationship with your company — they’ve worked with you, used your services, or referred you business. A genuine operational ask to a warm contact is fundamentally different from unsolicited commercial email. The contacts who don’t want to hear from you will unsubscribe; the contacts who are engaged will stay and, often, reply.

    What if the vendor ask generates more replies than we can handle?

    This is a good problem to have, and it’s unlikely. A typical vendor ask to a 500-contact list generates 5–20 replies. Log each one in your Notion tracker, respond within 24 hours, and prioritize follow-up by referral quality. If volume becomes a real issue, add a line to the email: “If you have a recommendation, please reply by [date] so I can review all suggestions together.”

    Should we offer to reciprocate referrals?

    Yes, naturally, but don’t make it transactional in the email. A line like “We’re always happy to refer business your way as well” is appropriate in the trade contacts version. In the homeowner version, keep it purely human — you’re not negotiating a referral exchange with someone who had a water loss two years ago.

    What’s the difference between this and a referral fee program?

    A referral fee program creates a financial incentive structure. This strategy creates a community touchpoint. The distinction matters because the motivation for helping you is different — people who respond to this email are doing it because they like you and want to be helpful, not because they’re chasing a check. That’s a different kind of relationship and a stronger one long-term.


  • Notion OS Starter — Single-Database Command Center Setup for $299

    Notion OS Starter — Single-Database Command Center Setup for $299

    What Is the Notion OS Starter?
    A single master database in your Notion workspace that handles task triage, project tracking, and client records simultaneously — with multiple views (board, table, calendar) configured for how you actually work. Not the full 6-database Second Brain architecture. The right starting point if you’re not yet running multi-client operations at scale.

    The full Second Brain is built for operators managing 10+ clients, 5+ projects simultaneously, and an AI-native workflow. Not everyone needs that on day one.

    The Notion OS Starter is the foundation — one well-built database with the right properties, the right views, and the right structure to grow into. It handles everything a solo operator or small team needs without the complexity of a 6-database architecture they’ll spend two weeks understanding before they use it.

    What the Starter Includes

    • Master operations database — Single database with properties for task type, project, client, status, priority, due date, and owner
    • 5 configured views — Today’s tasks, by project, by client, weekly calendar, and full table
    • 3 SOP pages — How to add a task, how to start a new project, how to onboard a client — written for your specific workflow
    • Inbox page — Capture page for unprocessed tasks and ideas before they get categorized
    • Dashboard — Linked view summary showing active projects, overdue tasks, and upcoming deadlines
    • Upgrade path document — When and how to graduate to the full 6-database Second Brain (so you know what you’re growing into)

    Pricing

    Package Includes Price
    Solo Setup for 1 person, up to 5 active projects $299
    Small Team Setup for 2–5 people with shared views and ownership assignments $499
    Solo + AI Solo setup + claude_delta metadata on key pages for AI session context $599

    Get Your Notion Workspace Built Right

    Tell us how many people will use it, how many active projects you’re juggling, and what’s currently falling through the cracks. We’ll scope the right package.

    will@tygartmedia.com

    Email only. No commitment to reply. Turnaround quoted within 1 business day.

    Frequently Asked Questions

    What Notion plan do I need?

    The Solo package works on Notion Free. The Small Team package requires Notion Plus or Team plan for shared workspace access and permission management.

    How is this different from a Notion template?

    Templates are generic starting points that require significant customization to fit your actual workflow. This is a custom build — we configure properties, views, and structure around your specific clients, projects, and working style before handoff.

    Can I upgrade to the full Second Brain later?

    Yes — and it’s designed for that. The master database becomes one of the six databases in the full architecture. Clients who start with the Starter get upgrade pricing on the full Second Brain setup.


    Last updated: April 2026

  • Notion Second Brain Setup for Agency Owners and AI-Native Operators

    Notion Second Brain Setup for Agency Owners and AI-Native Operators

    What Is a Notion Second Brain Setup?
    A Notion Second Brain is a structured personal knowledge operating system — not a template dump, but a living architecture that captures decisions, organizes projects, tracks clients, and gives you (and your AI) persistent operational context. Built right, it becomes the intelligence layer between your brain and your tools.

    Most Notion setups look impressive for three weeks and collapse by month two. The problem isn’t Notion — it’s that generic templates aren’t built around how you actually work.

    We built our own from scratch. It runs a multi-client agency, integrates directly with Claude AI, maintains operational memory across sessions, and has been stress-tested across content operations at scale. We’ve now productized it so you don’t have to rebuild what we already broke and fixed.

    Who This Is For

    Agency owners, fractional executives, solo operators, and founders who are drowning in browser tabs, scattered notes, and tools that don’t talk to each other. If you’re running more than 3 clients or 5 active projects and your “system” is a mix of sticky notes, Slack threads, and half-finished Notion pages — this is for you.

    What the 6-Database Command Center Architecture Delivers

    • Command Center Hub — One master dashboard linking every active project, client, and initiative with live status
    • Client & Project Database — Structured client records, deliverable tracking, and project timelines in one view
    • Content Pipeline — Brief-to-publish workflow with status stages, site assignment, and AI output staging
    • Knowledge Lab — Permanent storage for research, SOPs, skill documentation, and reference material
    • Operations Ledger — Decision log, session history, and change records so nothing gets lost
    • Task Triage Board — Priority-ranked action queue pulling from every database in the system

    The claude_delta Standard (What Makes This Different)

    Every page in this system includes a claude_delta v1.0 metadata block — a structured JSON header that gives Claude AI immediate operational context when you paste a page into a session. No re-explaining. No re-briefing. Claude reads the block and knows what it’s looking at.

    This is not something you’ll find in an Etsy template. It’s the result of running a real AI-native agency operation and discovering what actually breaks when your context window expires.

    What We Deliver

    Item Included
    Full 6-database architecture setup in your Notion workspace
    claude_delta metadata standard applied to all key pages
    Claude AI integration guide (how to use your Second Brain in sessions)
    3 custom views per database (board, table, calendar)
    SOP templates for your top 5 recurring workflows
    1-hour architecture walkthrough call
    30-day async support for questions and adjustments

    What You Get vs. DIY vs. Generic Agency

    Tygart Media Setup DIY (YouTube tutorials) Generic Notion Consultant
    Built around AI-native workflows
    claude_delta AI context standard
    Multi-client agency architecture Sometimes
    Ongoing async support Extra cost
    Proven under real operational load Unknown Unknown

    Ready to Stop Rebuilding Your System Every 90 Days?

    Send a note describing your current setup (or lack of one) and what you’re trying to manage. We’ll tell you if this is the right fit.

    will@tygartmedia.com

    Email only. No sales call required. No commitment to reply.

    Frequently Asked Questions

    Do I need to already use Notion?

    You need a Notion account (free works for setup, Team plan recommended for ongoing use). No prior Notion experience required — we build it around your workflows, not the other way around.

    How long does setup take?

    The architecture is built within 5 business days. The walkthrough call is scheduled in week two. Adjustments and SOP templates are completed within 30 days.

    What if I already have a Notion setup I’ve been using?

    We can audit your existing structure and either retrofit the 6-database architecture into it or rebuild cleanly. We’ll recommend one or the other after reviewing your current setup.

    Is this just a template I download?

    No. This is a custom build in your workspace. We configure databases, relations, views, formulas, and the claude_delta metadata standard to match your actual operation — clients, projects, workflows, and all.

    What industries is this built for?

    Originally built for a content and SEO agency. The architecture works for any service business running multiple clients, projects, or revenue streams simultaneously. Consultants, fractional CMOs, boutique agencies, and solo operators with complex operations are the best fit.

    Does this work with Claude, ChatGPT, or other AI tools?

    The claude_delta standard was designed for Claude. The architecture works with any AI tool — the metadata blocks and structured content make any LLM more effective when you paste pages into sessions. Claude integration is deepest out of the box.

    Last updated: April 2026

  • Notion for the Restoration Industry: Building Content Operations That Drive Local Authority

    Notion for the Restoration Industry: Building Content Operations That Drive Local Authority

    The Agency Playbook
    TYGART MEDIA · PRACTITIONER SERIES
    Will Tygart
    · Senior Advisory
    · Operator-grade intelligence

    The restoration industry has a content problem that most operators don’t recognize as a content problem. The work is technical, the market is local, the competition is intense, and the buying decision is urgent — someone’s basement is flooding or their ceiling has water damage and they need a contractor now. Traditional marketing advice — build a brand, nurture a relationship, post on social media — doesn’t map well to an industry where the customer need is immediate and the decision window is short.

    What does work: topical authority built through genuinely useful content, local SEO that answers the specific questions people ask when damage happens, and a content operation that can produce and maintain that content at scale. This is what we’ve built for restoration industry clients, and Notion is the operational backbone that makes it manageable.

    What does a Notion content operation look like for the restoration industry? A restoration industry content operation in Notion tracks content across specific damage types — water, fire, mold, asbestos, storm — and service geographies, with keyword research integrated into the content pipeline and a publishing workflow that routes content through optimization, schema injection, and WordPress publication. The operation is built for volume and specificity, not general brand content.

    Why the Restoration Industry Is a Good Content Market

    Restoration is a strong content market for several reasons. The questions people ask when damage occurs are specific and consistent: how much does water damage restoration cost, how long does mold remediation take, what does fire damage smell like after a week. These questions have real search volume and low competition from authoritative content — most restoration company websites are thin on useful information.

    The industry also has strong local search intent. Someone searching for water damage restoration is almost always searching for someone local. Content that combines topical authority — demonstrating genuine expertise in the damage type — with local specificity performs well in this environment.

    Finally, the industry is fragmented. Most restoration companies are regional or local operators without the resources to build and maintain a serious content operation. That gap creates opportunity for content-forward operators to establish authority that larger, less content-focused competitors can’t easily replicate.

    How the Content Architecture Works

    The content architecture for restoration clients follows a hub-and-spoke structure. Hub pages cover the primary service categories at the depth required for topical authority — comprehensive guides to water damage restoration, mold remediation, fire damage recovery. Spoke pages cover specific questions, cost breakdowns, process explanations, local variations, and comparison topics that radiate from each hub.

    In Notion, this architecture is tracked in the Content Pipeline database with content type tags distinguishing hub pages from spoke content. The hub pages are the long-term SEO assets; the spoke content generates ongoing traffic from specific long-tail queries and builds the internal link structure that supports the hubs.

    The keyword research layer — what topics need coverage, what questions are being asked in the target geography, what the competition looks like for each keyword — feeds directly into the Content Pipeline as briefs. Each brief becomes a content record that moves through the standard status sequence before it reaches WordPress.

    The Local Intelligence Layer

    Generic restoration content — “water damage restoration: everything you need to know” — competes with national franchise content from large chains and major insurance resources. It’s hard to win that competition for a regional operator.

    Local intelligence changes the equation. Content that reflects genuine knowledge of a specific market — the most common cause of water damage in the local housing stock, the local insurance carriers and their specific claim processes, the geographic factors that affect mold growth in the region — differentiates from generic content in a way that matters to both search engines and local readers.

    Capturing and maintaining that local intelligence is a knowledge management problem. In Notion, it lives in the client’s Knowledge Lab records — market-specific reference documents that inform every piece of content written for that client and that Claude reads before starting any content session for that site.

    The B2B Network as Distribution

    Content production is half the equation. Distribution matters — who sees the content and whether it reaches the decision-makers and referral sources who drive restoration business.

    A B2B industry network built around a shared activity — golf, in one model we’ve seen work well — can be a powerful distribution channel for restoration industry relationships. Insurance adjusters, property managers, contractors, and restoration company owners all participate in an industry where relationships drive referrals. A network format that builds those relationships efficiently creates a distribution layer that pure content can’t replicate.

    The content operation and the network operation reinforce each other. The content builds the credibility and visibility that makes the network meaningful. The network provides the relationships and industry intelligence that make the content genuinely informed rather than generic. Neither works as well without the other.

    What Makes Restoration Content Different

    Restoration content has specific requirements that distinguish it from general service business content. The subject matter is emotionally charged — people are dealing with damaged homes and possessions, often under insurance and contractor pressure. The content needs to be factually precise — cost ranges, process timelines, and technical specifications that are wrong will be called out quickly by industry readers. And the local dimension is non-negotiable — a guide to water damage restoration that doesn’t reflect local contractor pricing, local building codes, or local insurance market realities is less useful than one that does.

    Meeting these requirements at scale — across multiple clients, multiple damage types, multiple geographies — is what makes Notion’s pipeline architecture valuable for restoration content operations. The knowledge layer stores the local intelligence. The pipeline tracks the content. The quality gate ensures nothing publishes with claims that can’t be supported.

    Working in the restoration industry?

    We build content operations for restoration companies — the topical authority architecture, the local intelligence layer, and the publishing pipeline that makes it run at scale.

    Tygart Media has deep experience in restoration industry content. We know what works, what the keywords are, and what differentiates in a fragmented local market.

    See what we build →

    Frequently Asked Questions

    What content topics work best for restoration companies?

    Cost guides perform consistently well — people want to know what water damage restoration costs, what mold remediation costs, what fire damage cleanup costs. Process explanations — what happens during restoration, how long it takes, what to expect — also perform well because they reduce anxiety during a stressful situation. Local content that reflects knowledge of the specific market outperforms generic content for the same topics at the local search level.

    How much content does a restoration company need to build topical authority?

    For a regional restoration company targeting a metro area, meaningful topical authority typically requires fifty to one hundred published articles covering the primary damage types, the key cost and process questions, and local variations. That’s a six-to-twelve month content build at reasonable publishing velocity. The content compounds over time — articles published in month one are still generating traffic in month twelve and beyond.

    How do you handle the local specificity requirement across multiple restoration clients in different markets?

    Each client’s market-specific intelligence lives in their Knowledge Lab records in Notion — a set of reference documents covering local pricing, local contractors, local insurance market conditions, and geographic factors specific to their service area. Claude reads these records before starting any content session for that client. The records are the mechanism that makes content locally specific without requiring the writer to have personal knowledge of every market.

  • How to Set Up Notion So Claude Remembers Everything

    How to Set Up Notion So Claude Remembers Everything

    Last refreshed: May 15, 2026

    Update — May 15, 2026: On May 13, 2026, Notion shipped the Notion Developer Platform (version 3.5), with Claude as a launch partner. The platform adds Workers, database sync, an External Agents API, and a Notion CLI. The patterns described in this article still work, but there is now a native, sanctioned alternative for some of what previously required custom MCP wiring or third-party automation. For the full breakdown of what changed and what it means for the Notion + Claude stack, see Notion Developer Platform Launch (May 13, 2026). For the underlying operating philosophy, see The Three-Legged Stack.

    Claude AI · Fitted Claude

    Claude doesn’t remember anything between sessions by default. Every conversation starts from zero. For casual use, that’s fine. For an operator running a complex business across multiple clients, projects, and entities, that reset is a real problem — and the solution is architectural, not a workaround.

    Here’s how to set up Notion so Claude has the context it needs at the start of every session, without you manually rebuilding it every time.

    How do you set up Notion so Claude remembers everything? You don’t make Claude remember — you make the relevant context retrievable. A Claude-ready Notion setup has three components: a metadata standard that makes key pages machine-readable, a master index Claude fetches at session start to know what exists, and a session logging practice that captures what was decided so the next session can pick up where the last one ended. Together these create functional persistence without relying on Claude’s native memory.

    What “Remembering” Actually Means

    It’s worth being precise about what we’re solving for. Claude’s context window — the information it has access to during a session — is large. The problem is that it resets between sessions. Information from Monday’s session isn’t available in Tuesday’s session unless it’s either in the system prompt or retrieved during the new session.

    The goal isn’t to give Claude a persistent memory in the biological sense. The goal is to ensure that any context Claude would need to operate effectively in a new session is stored somewhere Claude can retrieve it, and that Claude knows to retrieve it before starting work.

    That’s a knowledge management problem, not an AI problem. Solve the knowledge management problem and the memory problem resolves itself.

    Step 1: The Metadata Standard

    Every key Notion page needs a brief structured metadata block at the top — before any human-readable content. The metadata block makes the page machine-readable: Claude can read the summary and understand the page’s purpose and key constraints without reading the full content.

    The minimum viable metadata block for each page includes: what type of document this is (SOP, reference, project brief, decision log), its current status (active, evergreen, draft), a two-to-three sentence plain-language summary of what the page contains and when to use it, and a resume instruction — the single most important thing to know before acting on this page’s content.

    With this block in place, Claude can orient itself to any page in seconds. Without it, Claude has to read the full page to understand whether it’s relevant — which is slow and impractical at scale.

    Step 2: The Master Index

    The master index is a single Notion page that lists every key knowledge page in the workspace: its title, Notion page ID, type, status, and one-line summary. Claude fetches this page at the start of any session that involves the knowledge base.

    The index answers the question Claude needs answered before it can retrieve anything: what exists and where is it? Without the index, Claude would need to search for relevant pages by keyword — imprecise and dependent on the page having the right words. With the index, Claude can scan the full list of what exists and identify exactly which pages are relevant to the current task.

    Keep the index current. Add a row whenever a significant new page is created. Archive rows when pages are deprecated. The index is only useful if it accurately represents what’s in the knowledge base.

    Step 3: Session Logging

    The session log is the practice that creates true continuity across sessions. At the end of any significant working session, a brief log entry captures what was decided, what was done, and what the next step is. That log entry lives in the Knowledge Lab as a dated record.

    The next session starts by reading the most recent session log for the relevant project or client. Claude picks up with full awareness of what the previous session decided and where the work stands — not because it remembered, but because the information was captured and is retrievable.

    Session logs don’t need to be long. Three to five sentences covering the key decisions and the next step is sufficient. The goal is continuity, not comprehensive documentation. A session log that takes two minutes to write saves ten minutes of context reconstruction at the start of the next session.

    The Start-of-Session Protocol

    With the metadata standard, master index, and session logging in place, every session starts the same way: “Read the Claude Context Index and the most recent session log for [project/client], then let’s work on [task].”

    Claude fetches the index, identifies the relevant pages, fetches those pages and reads their metadata blocks, reads the most recent session log, and begins work with genuine operational context. The context transfer that used to require ten minutes of manual explanation happens in under a minute of automated retrieval.

    This protocol works because the setup work was done upfront. The metadata blocks were written. The index was created and maintained. The session logs were captured. The session start protocol is fast because the knowledge management discipline that makes it fast was already in place.

    What This Doesn’t Replace

    This architecture doesn’t replace judgment about what’s worth capturing. Not every session produces information worth logging. Not every Notion page needs a metadata block. The discipline of the system is knowing what deserves to be in the knowledge base and what doesn’t — and being honest about the maintenance overhead that every addition creates.

    A knowledge base that captures everything becomes a knowledge base that surfaces nothing useful. The curation decision — what goes in, what stays out — is as important as the architecture that stores it.

    Want this set up correctly?

    We configure the Notion + Claude memory architecture — the metadata standard, the Context Index, the session logging practice, and the start-of-session protocol — as a done-for-you implementation.

    Tygart Media runs this system in daily operation. We know what makes it work and what breaks it.

    See what we build →

    Frequently Asked Questions

    Does Claude have a memory feature that makes this unnecessary?

    Claude has a memory system in claude.ai that captures information from conversations and surfaces it in future sessions. This is useful for personal context — preferences, background, recurring topics. For operational context in a business setting — current project status, client-specific constraints, recent decisions — the Notion-based architecture described here is more reliable, more comprehensive, and more controllable. The two approaches complement each other rather than competing.

    How often should session logs be written?

    For sessions that produce significant decisions, complete meaningful work, or advance a project to a new stage — write a log entry. For sessions that are purely exploratory or produce nothing durable — skip it. The rule of thumb: if the next session on this topic would benefit from knowing what happened in this session, write the log. If not, don’t. Logging every session creates overhead without value; logging selectively keeps the knowledge base signal-dense.

    What’s the difference between a session log and a Notion page?

    A session log is a dated record of what happened in a specific working session — decisions made, work completed, next steps identified. A Notion knowledge page is a durable reference document — an SOP, an architecture decision, a client reference — that’s meant to be read and used repeatedly. Session logs are ephemeral and time-stamped. Knowledge pages are evergreen and maintained. Both are in the Knowledge Lab database, distinguished by the Type property.

    Can this setup work for a team, not just a solo operator?

    Yes, with additional structure. The metadata standard and master index work the same for a team. Session logging becomes more important with multiple people working on the same projects — the log creates a shared record of what was decided so team members don’t reconstruct it for each other. The additional requirement for a team is clarity about who owns the knowledge base maintenance — who updates the index, who reviews pages for currency, who writes the session logs. Without that ownership, the system degrades quickly in a team setting.

  • Notion Command Center Daily Operating Rhythm: Our Exact Playbook

    Notion Command Center Daily Operating Rhythm: Our Exact Playbook

    The Agency Playbook
    TYGART MEDIA · PRACTITIONER SERIES
    Will Tygart
    · Senior Advisory
    · Operator-grade intelligence

    A daily operating rhythm is the difference between a Notion system you use and one you maintain out of obligation. The architecture can be perfect — six databases, clean relations, filtered views for every operational question — and still fail if there’s no structured daily interaction that keeps it current and useful.

    This is our exact playbook. Not a template, not a philosophy — the specific sequence we run every working day to keep a multi-client, multi-entity operation on track from a single Notion workspace.

    What is a Notion Command Center daily operating rhythm? A daily operating rhythm for a Notion Command Center is a structured sequence of interactions with the workspace that keeps it current and actionable — a morning triage that clears the inbox and sets priorities, an end-of-day close that captures completions and pushes deferrals, and a weekly review that repairs drift and resets for the next week. The rhythm is what transforms a database architecture into a living operating system.

    Morning Triage: 10–15 Minutes

    The morning triage has one goal: leave it knowing exactly what the top three priorities are for the day and with the inbox at zero.

    Step 1: Zero the inbox. Open William’s HQ and go to the inbox view — all tasks without a priority or entity assigned. Every untagged item gets a priority (P1–P4), a status (Next Up or a specific date), and an entity tag. Nothing stays in the inbox. Items that don’t warrant a task get deleted.

    Step 2: Read the P1 and P2 list. These are the only tasks that own today’s calendar. Read the list. Mentally commit to the top three. If the P1 list has more than five items, something is mislabeled — P1 means real consequences today, not “this would be good to do.”

    Step 3: Check the content queue. Filter the Content Pipeline for anything publishing in the next 48 hours that isn’t in Scheduled status. Anything publishing tomorrow that’s still in Draft or Optimized is a P1. Fix it before anything else.

    Step 4: Check blocked tasks. Any task in Blocked status needs a decision or a message now. Blocked tasks that age without action create downstream problems that compound. Clear them or escalate them — don’t leave them blocked.

    Total time: ten to fifteen minutes. The output is not a plan — it’s a commitment to three specific things, with everything else deprioritized explicitly rather than just ignored.

    Working Sessions: No Rhythm, Just Work

    Between morning triage and end-of-day close, there’s no prescribed rhythm. The triage gave you your three priorities. Work on them. The system doesn’t need to be consulted again until something changes — a new task arrives, a content piece needs to move to the next stage, a decision gets made that should be logged.

    The one active habit during working sessions: when you create something that belongs in the system — a new contact, a new content piece, a completed task — log it immediately. The temptation to batch-log at the end of the day creates a gap where things get missed. The cost of logging in real time is thirty seconds per item. The cost of not logging is an inaccurate system that can’t be trusted.

    End-of-Day Close: 5 Minutes

    Step 1: Mark done tasks complete. Any task completed today gets its status updated to Done. This takes thirty seconds and keeps the active task view clean.

    Step 2: Push or reprioritize uncompleted tasks. Anything you intended to do but didn’t — update the due date or move it down in priority. Don’t leave tasks with today’s due date sitting undone without a decision about when they’ll happen.

    Step 3: Check tomorrow’s content queue. Anything publishing tomorrow that needs a final pass? If yes, that’s the first thing tomorrow morning. If no, close out.

    Step 4: Log anything significant created today. New contacts, new content pieces, new decisions — anything that belongs in the system but was created during the day without being logged. The end-of-day close is the catch for anything that wasn’t logged in real time.

    Total time: five minutes. The output is a clean system — no stale due dates, no ambiguous task statuses, no undocumented decisions.

    Weekly Review: 30 Minutes, Sunday Evening

    The weekly review is the repair mechanism. It catches what the daily rhythm misses and resets the system before the next week begins.

    Revenue check: Any deal stuck in the same pipeline stage as last week with no activity? Any proposal sent more than five days ago without a follow-up?

    Content check: Next week’s content queue — fully populated and scheduled? Any articles published this week without internal links? Any content pipeline records that have been in the same status for more than seven days?

    Task check: Archive all Done tasks older than 14 days. Any P3/P4 tasks that should be killed rather than deferred again? Any P2 leverage tasks being continuously pushed — a warning sign that the leverage isn’t actually happening?

    Relationship check: Any CRM contacts who should have heard from you this week and didn’t?

    System health check: Any automation that failed silently? Any SOP that was used this week that turned out to be outdated? Any knowledge that was generated this week that should be documented?

    Total time: thirty minutes. The output is a reset system — clean task database, current content queue, up-to-date relationship log, healthy knowledge base.

    Monthly Entity Reviews: 10 Minutes Each

    Once a month, open each business entity’s Focus Room and run a quick scan. For each entity, one key question: is this entity’s operation healthy? Are the right things happening, is nothing falling through the cracks, does the content or relationship pipeline need attention?

    The monthly review catches drift that’s too slow for the weekly rhythm to notice — a client relationship that’s been slightly neglected for six weeks, a content vertical that’s been deprioritized without a conscious decision, a system health issue that’s been accumulating quietly.

    Ten minutes per entity. The output is either confirmation that the entity is on track or a set of tasks to address the drift before it becomes a problem.

    Want this system set up for your operation?

    We build Notion Command Centers and the operating rhythms that make them work — the architecture, the views, and the daily practice that keeps a complex operation on track.

    Tygart Media runs this exact rhythm daily. We know what makes the difference between a Notion system that works and one that gets abandoned.

    See what we build →

    Frequently Asked Questions

    What if the morning triage takes longer than 15 minutes?

    It means the inbox accumulated too much since the last triage. The first few times you run the rhythm after setting up a new system, triage will take longer while you establish the habit of keeping the inbox clear in real time. Once the habit is established, fifteen minutes is consistently sufficient. If triage regularly exceeds twenty minutes, the inbox discipline needs attention — too many items are accumulating without being processed during the day.

    How do you handle urgent items that arrive mid-day?

    Anything genuinely urgent — P1 level — gets addressed immediately and logged in the system as it’s resolved. Anything that feels urgent but can wait goes into the inbox for the next triage. The discipline of not treating every incoming item as immediately actionable is one of the harder habits to establish, and one of the most valuable. Most things that feel urgent at arrival are P2 or P3 by the time they’re calmly evaluated.

    Is the weekly review actually necessary if the daily rhythm is working?

    Yes. The daily rhythm catches individual task and content issues. The weekly review catches patterns — a client relationship drifting, a pipeline stage backing up, an automation failing silently. These patterns are invisible in daily operation because each day’s view is too narrow. The weekly review is the only moment when the full operation is visible at once, which is when patterns become apparent.



  • Notion + GCP: Running an AI-Native Business on Google Cloud and Notion

    Notion + GCP: Running an AI-Native Business on Google Cloud and Notion

    Last refreshed: May 15, 2026

    Claude AI · Fitted Claude

    Running an AI-native business in 2026 means making a decision about infrastructure that most operators don’t realize they’re making. You can run AI operations reactively — open Claude, do the work, close the session, repeat — or you can build an infrastructure layer that makes every session faster, more consistent, and more capable than the last.

    We chose the second path. The stack is Google Cloud Platform for compute and data infrastructure, Notion for operational knowledge, and Claude as the AI intelligence layer. Here’s what that combination looks like in practice and why each piece is there.

    What does it mean to run an AI-native business on GCP and Notion? An AI-native business on GCP and Notion uses Google Cloud Platform for infrastructure — compute, storage, data, and AI APIs — and Notion as the operational knowledge layer, with Claude connecting the two as the intelligence and orchestration layer. Content publishing, image generation, knowledge retrieval, and operational logging all run through this stack. The business is not just using AI tools; it’s built on AI infrastructure.

    Why GCP

    Google Cloud Platform provides three things that matter for an AI-native content operation: scalable compute via Cloud Run, AI APIs via Vertex AI, and data infrastructure via BigQuery. All three integrate cleanly with each other and with external services through standard APIs.

    Cloud Run handles the services that need to run continuously or on demand without managing servers: the WordPress publishing proxy that routes content to client sites, the image generation service that produces and injects featured images, the knowledge sync service that keeps BigQuery current with Notion changes. These services run when triggered and cost nothing when idle — the right economics for an operation that doesn’t need 24/7 uptime but does need reliable on-demand availability.

    Vertex AI provides access to Google’s image generation models for featured image production, with costs that scale predictably with usage. For an operation producing hundreds of featured images per month across client sites, the per-image cost at scale is significantly lower than commercial image generation alternatives.

    BigQuery provides the data layer described in the persistent memory architecture: the operational ledger, the embedded knowledge chunks, the publishing history. SQL queries against BigQuery return results in seconds for datasets that would be unwieldy in Notion.

    Why Notion

    Notion is the human-readable operational layer — the place where knowledge lives in a form that both people and Claude can navigate. The GCP infrastructure handles compute and data. Notion handles knowledge and workflow. The division of responsibility is clean: GCP for machine-scale operations, Notion for human-scale understanding.

    The Notion Command Center — six interconnected databases covering tasks, content, revenue, relationships, knowledge, and the daily dashboard — is the operational OS for the business. Every piece of work that matters is tracked here. Every procedure that repeats is documented here. Every decision that shouldn’t be made twice is logged here.

    The Notion MCP integration is what makes Claude a genuine participant in that system rather than an external tool. Claude reads the Notion knowledge base, writes new records, updates status, and logs session outputs — all directly, without requiring a manual transfer step between Claude and Notion.

    Where Claude Sits in the Stack

    Claude is the intelligence and orchestration layer. It doesn’t replace the GCP infrastructure or the Notion knowledge base — it uses them. A content production session starts with Claude reading the relevant Notion context, proceeds with Claude drafting and optimizing content, and ends with Claude publishing to WordPress via the GCP proxy and logging the output to both Notion and BigQuery.

    The session is not just Claude doing a task and returning a result. It’s Claude operating within a system that provides it with context going in and captures its outputs coming out. The infrastructure is what makes that possible at scale.

    What This Stack Enables

    The combination of GCP infrastructure and Notion knowledge unlocks operational capabilities that neither provides alone. Content can be generated, optimized, image-enriched, and published to multiple WordPress sites in a single Claude session — because the GCP services handle the technical distribution and the Notion context provides the client-specific constraints that govern each site. Knowledge produced in one session is immediately available in the next — because BigQuery captures it and Notion stores the human-readable version. The operation runs at a scale that one person couldn’t manage manually — because the infrastructure handles the mechanical work while Claude handles the intelligence work.

    What This Stack Costs

    The honest cost picture: GCP infrastructure at our operating scale runs modest monthly costs, primarily driven by Cloud Run service invocations and Vertex AI image generation. Notion Plus for one member is around ten dollars per month. Claude API usage for content operations varies with session volume. The total monthly infrastructure cost for the stack is a small fraction of what equivalent human labor would cost for the same output volume — which is the point of building infrastructure rather than hiring for scale.

    Interested in building this infrastructure?

    The GCP + Notion + Claude stack is advanced infrastructure. We consult on the architecture and can help design the right version for your operation’s scale and requirements.

    Tygart Media built and runs this stack live. We know what the implementation actually requires and where the complexity is.

    See what we build →

    Frequently Asked Questions

    Do you need GCP to run an AI-native content operation?

    No — GCP is one infrastructure option among several. The core stack (Claude + Notion) works without any cloud infrastructure for smaller operations. GCP becomes valuable when you need reliable service infrastructure for publishing automation, image generation at scale, or data infrastructure for persistent memory. Operators starting out don’t need GCP; operators scaling up often find it the right addition.

    How does Claude connect to GCP services?

    Claude connects to GCP services through standard REST APIs and the MCP (Model Context Protocol) integration layer. Cloud Run services expose HTTP endpoints that Claude calls during sessions. BigQuery is queried via the BigQuery API. Vertex AI image generation is called via the Vertex AI REST API. Claude orchestrates these calls as part of a session workflow — fetching context, generating content, calling publishing APIs, logging results.

    Is this architecture HIPAA or SOC 2 compliant?

    GCP offers HIPAA-eligible services and SOC 2 certification. A “fortress architecture” — content operations running entirely within a GCP Virtual Private Cloud with appropriate data handling controls — can be configured to meet healthcare and enterprise compliance requirements. This is an advanced implementation beyond the standard stack described here, but it’s achievable within the GCP environment for organizations with those requirements.

  • How We Use BigQuery + Notion as a Persistent AI Memory Layer

    How We Use BigQuery + Notion as a Persistent AI Memory Layer

    Last refreshed: May 15, 2026

    Claude AI · Fitted Claude

    The hardest problem in running an AI-native operation is not the AI — it’s the memory. Claude’s context window is large but finite. It resets between sessions. Every conversation starts from zero unless you engineer something that prevents it.

    For a solo operator running a complex business across multiple clients and entities, that reset is a real operational problem. The solution we built combines Notion as the human-readable knowledge layer with BigQuery as the machine-readable operational history — a persistent memory infrastructure that means Claude never truly starts from scratch.

    Here’s how the architecture works and why each layer exists.

    What is a BigQuery + Notion AI memory layer? A BigQuery and Notion AI memory layer is a two-tier persistent knowledge infrastructure where Notion stores human-readable operational knowledge — SOPs, decisions, project context — and BigQuery stores machine-readable operational history — publishing records, session logs, embedded knowledge chunks — that Claude can query during a live session. Together they provide Claude with both the institutional knowledge of the operation and the operational history of what has been done.

    Why Two Layers

    Notion and BigQuery solve different parts of the memory problem.

    Notion is optimized for human-readable, structured documents. An SOP in Notion is readable by a person and fetchable by Claude. But Notion isn’t a database in the traditional sense — it doesn’t support the kind of programmatic queries that make large-scale operational history navigable. Searching five hundred knowledge pages for a specific historical data point is slow and imprecise in Notion.

    BigQuery is optimized for exactly that: large-scale structured data that needs to be queried programmatically. Operational history — every piece of content published, every session’s decisions, every architectural change — lives in BigQuery as structured records that can be queried precisely and quickly. But BigQuery records aren’t human-readable documents. They’re rows in tables, useful for lookup and retrieval but not for the kind of contextual understanding that Notion pages provide.

    Together they cover the full memory requirement: Notion for what the operation knows and how things are done, BigQuery for what the operation has done and when.

    The Notion Layer: Structured Knowledge

    The Notion knowledge layer is the Knowledge Lab database — SOPs, architecture decisions, client references, project briefs, and session logs. Every page carries the claude_delta metadata block that makes it machine-readable: page type, status, summary, entities, dependencies, and a resume instruction.

    The Claude Context Index — a master registry page listing every key knowledge page with its ID, type, status, and one-line summary — is the entry point. At the start of any session touching the knowledge base, Claude fetches the index and identifies the relevant pages for the current task. The index-then-fetch pattern keeps context loading fast and targeted.

    What the Notion layer provides: the institutional knowledge of how the operation works, what has been decided, and what the constraints are for any given client or project. This is the layer that makes Claude operate consistently across sessions — not by remembering the previous session, but by reading the same underlying knowledge base that governed it.

    The BigQuery Layer: Operational History

    The BigQuery operations ledger is a dataset in Google Cloud that holds the operational history of the business: every content piece published with its metadata, every significant session’s decisions and outputs, every architectural change to the systems, and — most importantly — the embedded knowledge chunks that enable semantic search across the entire knowledge base.

    The knowledge pages from Notion are chunked into segments and embedded using a text embedding model. Those embedded chunks live in BigQuery alongside their source page IDs and metadata. When a session needs to find relevant knowledge that isn’t covered by the Context Index, a semantic search against the embedded chunks surfaces the right pages without requiring a manual search.

    What the BigQuery layer provides: operational history that’s too large and too structured for Notion pages, semantic search across the full knowledge base, and a machine-readable record of everything that has been done — which pieces of content exist, what was changed, what decisions were made and when.

    How Sessions Use Both Layers

    A typical session that requires deep operational context follows a pattern. Claude reads the Claude Context Index from Notion and identifies relevant knowledge pages. It fetches those pages and reads their metadata blocks. For operational history — “what has been published for this client in the last thirty days?” — it queries the BigQuery ledger directly. For knowledge gaps not covered by the index, it runs a semantic search against the embedded chunks.

    The result is a session that starts with genuine institutional context rather than a blank slate. Claude knows how the operation works, what the relevant constraints are, and what has happened recently — not because it remembers the previous session, but because all of that information is accessible in structured, retrievable form.

    The Maintenance Requirement

    Persistent memory infrastructure requires persistent maintenance. The Notion knowledge layer stays current through the regular SOP review cycle and the practice of documenting decisions as they’re made. The BigQuery layer stays current through automated sync processes that push new content records and session logs as they’re created.

    The sync isn’t fully automated in a set-and-forget sense — it requires periodic verification that records are being captured correctly and that the embedding model is processing new chunks accurately. But the maintenance overhead is modest: a few minutes of verification per week, and occasional manual intervention when a sync process fails silently.

    The system degrades if the maintenance lapses. A knowledge base that’s three months stale is worse than no knowledge base — it provides false confidence that Claude has current context when it doesn’t. The maintenance discipline is as important as the architecture.

    Interested in building this for your operation?

    The Notion + BigQuery memory architecture is advanced infrastructure. We build and configure it for operations that are ready for it — not as a first Notion project, but as the next layer on top of a working system.

    Tygart Media runs this infrastructure live. We know what the build and maintenance actually requires.

    See what we build →

    Frequently Asked Questions

    Why use BigQuery instead of just storing everything in Notion?

    Notion is optimized for human-readable structured documents, not for large-scale programmatic data queries. Storing thousands of operational history records — content publishing logs, session outputs, embedded knowledge chunks — in Notion creates performance problems and makes precise programmatic queries slow. BigQuery handles that scale trivially and supports the SQL queries and vector similarity searches that make the operational history actually useful. Notion and BigQuery do different things well; the architecture uses each for what it’s good at.

    Is this architecture accessible to non-engineers?

    The Notion layer is. The BigQuery layer requires comfort with Google Cloud infrastructure, SQL, and API integration. Building and maintaining the BigQuery ledger is an engineering task. For operators without that background, the Notion layer alone — the Knowledge Lab, the claude_delta metadata standard, the Context Index — provides significant value and is fully accessible without engineering support. The BigQuery layer is the advanced extension, not the foundation.

    What does “semantic search over embedded knowledge chunks” mean in practice?

    When knowledge pages are embedded, each page (or section of a page) is converted into a numerical vector that represents its meaning. Semantic search finds pages with vectors close to the query vector — pages that are conceptually similar to what you’re looking for, even if they don’t use the same words. In practice this means Claude can find relevant knowledge pages by describing what it needs rather than knowing the exact title or keyword. It’s significantly more reliable than keyword search for knowledge retrieval across a large, varied knowledge base.