Give every new tech a structured path from day one — and never lose track of who is certified.
Who This Is For
Who the crew onboarding tracker is for.
Built for restoration owners who are growing their crew but onboarding is chaotic, certifications are tracked in someone’s head, and no one is sure who is cleared to run what equipment.
The Problem
The crew onboarding problem.
Restoration technician turnover is real. When you hire someone new, the first 90 days determine whether they stay. Chaotic onboarding — no clear expectations, no structured training, no visibility into their progress — accelerates the exit. Meanwhile, certification lapses create liability. Knowing who holds WRT, who is overdue for renewal, and who is cleared to operate specific equipment should not require asking around.
What You Get
What you get with the crew onboarding tracker.
New hire checklist: day 1, week 1, and month 1 milestones with owner sign-off
Certification tracker: WRT, ASD, FSRT, AMRT, CCT, and any custom certs you add
IICRC course progress log: completion dates and renewal reminders built in
Training module library: add your own procedures, videos, and field guides
Equipment sign-off tracker: who is cleared to operate what, with sign-off date
Performance notes log for structured 30/60/90 day reviews
Restoration Crew Onboarding & Training Tracker
$19
Delivered to your inbox within 24 hours — no shipping, no waiting
Secure checkout via Square — all major cards accepted
Frequently Asked Questions
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive a download link for the ZIP file and/or Notion duplicate link immediately.
Do I need any special software?
A free Notion account is required. No other software needed.
Can I customize this for my specific business?
Yes — that is the point. Everything is built to be edited. Swap in your company name, add your specific workflows, remove anything that does not apply. It is a starting point, not a locked template.
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
Know your numbers. Run your business on data instead of gut feel.
Who This Is For
Who the restoration KPI dashboard is for.
Built for restoration owners who are making decisions from memory and instinct because they have no clean view of what is actually happening in their business.
The Problem
The KPI visibility problem.
Most restoration owners can tell you roughly how many jobs they have going. They cannot tell you their average job cycle time, their close rate by lead source, which equipment categories are underutilized, or whether this month is actually better than last year. Running a business without this data is not a strategy — it is luck management. The owners who grow intentionally know their numbers.
What You Get
What you get with the KPI dashboard.
Revenue tracker: monthly totals by job type and lead source
Job count and average job value trending over time
Cycle time tracking: from FNOL to final invoice, average and by job type
Lead source attribution: where are your best jobs actually coming from
Equipment utilization rate by asset category
Crew productivity metrics
Weekly and monthly summary views — one glance, full picture
Restoration Business KPI Dashboard
$29
Delivered to your inbox within 24 hours — no shipping, no waiting
Secure checkout via Square — all major cards accepted
Frequently Asked Questions
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive a download link for the ZIP file and/or Notion duplicate link immediately.
Do I need any special software?
A free Notion account is required. No other software needed.
Can I customize this for my specific business?
Yes — that is the point. Everything is built to be edited. Swap in your company name, add your specific workflows, remove anything that does not apply. It is a starting point, not a locked template.
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
Every procedure your crew needs, documented and accessible — not a PDF that lives in a drawer.
Who This Is For
Who the SOP library is for.
Built for restoration owners who know their company needs documented procedures but have never had time to build them.
The Problem
The SOP coverage problem.
Most restoration companies run on institutional knowledge — what the senior tech knows, what the owner remembers, what got passed down verbally on the first job. That works until the senior tech leaves, or a new hire does something wrong, or an adjuster asks for your remediation protocol documentation. Every serious restoration company needs written procedures. Almost none of them have them.
Secure checkout via Square — all major cards accepted
Frequently Asked Questions
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive a download link for the ZIP file and/or Notion duplicate link immediately.
Do I need any special software?
A free Notion account is required. No other software needed.
Can I customize this for my specific business?
Yes — that is the point. Everything is built to be edited. Swap in your company name, add your specific workflows, remove anything that does not apply. It is a starting point, not a locked template.
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
Track every claim, supplement, authorization, and payment — nothing falls through the cracks.
Who This Is For
Who the insurance claims command center is for.
Built for restoration contractors who spend hours chasing adjusters, re-sending supplement requests, and discovering unpaid claims at month end.
The Problem
The claims coordination problem.
Insurance work is where restoration companies make their money — and lose it. A missed supplement, a forgotten authorization, an unanswered depreciation dispute. These are not small errors. Most restoration contractors are managing claims across spreadsheets, sticky notes, and email threads, hoping nothing slips. Something always slips.
What You Get
What you get with the claims command center.
Claims database: every active and closed claim with full status from FNOL to final payment
Supplement log: every request, every response, every pending item tracked
Authorization tracker: what has been approved, what is pending, what was denied and needs appeal
Payment reconciliation: expected vs. received, outstanding balance visible at a glance
Adjuster directory: contacts linked directly to their claims
Communication templates: pre-written supplement requests and depreciation dispute language
Restoration Insurance Claims Command Center
$29
Delivered to your inbox within 24 hours — no shipping, no waiting
Secure checkout via Square — all major cards accepted
Frequently Asked Questions
How is this delivered?
Within 24 hours of purchase via email from will@tygartmedia.com. You will receive a download link for the ZIP file and/or Notion duplicate link immediately.
Do I need any special software?
A free Notion account is required. No other software needed.
Can I customize this for my specific business?
Yes — that is the point. Everything is built to be edited. Swap in your company name, add your specific workflows, remove anything that does not apply. It is a starting point, not a locked template.
Is there a refund policy?
Because this is a digital product, all sales are final. If you have a problem with your purchase, email will@tygartmedia.com and we will sort it out.
By Will Tygart• Long-form Position
• Practitioner-grade
If your WordPress site goes down tomorrow, what happens to your content?
For most operations, the answer is: it’s gone until the site comes back, and if it comes back wrong, there’s a recovery process that takes hours and may not be complete. The content lives in WordPress because WordPress is the system — not just the distribution point, but the source of truth.
This is tool-first design. And it’s fragile in ways that only become visible when something breaks.
The behavior-first alternative separates the functions that WordPress conflates. Writing and storing content is one behavior. Publishing and distributing it is another. They require different things from a tool: storage requires permanence, searchability, and accessibility regardless of publishing status; distribution requires web performance, SEO infrastructure, and public availability. WordPress is genuinely excellent at distribution. It was never designed to be a durable content storage layer.
The practical implementation: every piece of content in a behavior-first operation goes to Notion first, WordPress second. The Notion page is the permanent record. The WordPress post is the published output. If the WordPress site goes down, the content is not at risk. If you need to migrate hosts, rebuild the site, or switch platforms, the content travels with you. If the WAF blocks your publisher, you mark the Notion entry “Pending WP Push” and execute when the path is clear — nothing is lost.
What This Looks Like in Practice
Notion as a storage layer for WordPress — how it looks in practice.
The write → store → distribute pipeline has three distinct stages, each with a clear tool responsibility:
Write: Claude generates the article, optimized for SEO/AEO/GEO, with schema markup and internal linking. This happens in conversation, in a batch pipeline, or via a Cloud Run service.
Store: The article lands in Notion — in a content tracker database with properties for status, target keyword, WP post URL, and a claude_delta metadata block at the top of each page. This is the permanent record. It’s searchable, linkable, and accessible to any future Claude session without reconstructing context.
Distribute: The article publishes to WordPress via REST API. The WordPress post ID and URL get written back to the Notion record. The content now exists in two places — one for humans and future AI sessions (Notion), one for search engines and web visitors (WordPress).
The Secondary Benefit: Portable Content
The secondary benefit: portable content you can re-use.
The deeper value of this architecture isn’t failure resilience — it’s portability. Content stored in Notion can be published to any destination: WordPress, a different CMS, an email campaign, a PDF, a social post. The content is decoupled from its distribution channel. When you need to repurpose an article as a lead magnet, extract a section for a social post, or adapt it for a different site, it’s all in one place in a structured format that Claude can read and reformat in seconds.
This is what “content as knowledge” looks like operationally. Not a metaphor — a literal architecture where content is stored as knowledge first and distributed as content second.
The tool that makes this possible (Notion) costs nothing for a solo operator. The behavior that makes it valuable — writing to storage before distribution — costs nothing but the discipline to do it consistently. Build the system around that behavior and the tool choice becomes almost irrelevant.
Frequently Asked Questions
Does this mean we need to maintain content in two places?
You’re maintaining it in one place (Notion) and publishing it to a second (WordPress). The WordPress post is generated from the Notion record, not maintained separately. Updates go to Notion first; the WordPress post gets updated via API. There’s no manual sync required.
What if our team doesn’t use Notion?
The behavior (store before distribute) can be implemented with any persistent storage layer — Google Docs, Airtable, a Git repository. Notion is recommended because it supports relational databases, Claude MCP integration, and structured metadata that makes the content retrievable and reusable. But the behavior is the requirement; the tool is the implementation detail.
How does this handle content updates and revisions?
Revisions happen in Notion. The updated Notion content is pushed to WordPress via API, overwriting the previous version. The Notion page serves as the revision history — Notion’s native version history tracks changes at the page level without any additional configuration.
Who this is for: The person building your knowledge and relationship tracking system — your office manager, a tech-savvy ops person, or a consultant helping you get organized. This brief builds a Notion-based Second Brain layer that sits on top of your existing CRM to capture the relational intelligence that your job management software never will. No coding required. Full setup takes 3–4 hours. The strategy this supports is in Your CRM Is Not a Lead Database.
What a Second Brain Does That Your CRM Doesn’t
What a second brain does that your CRM doesn’t.
Your job management software (ServiceTitan, Jobber, or similar) is built to track transactions: jobs, invoices, and technician assignments. It is exceptional at this. What it cannot do is capture the relational layer — who referred whom, who replied to your hiring email, which adjuster said they’d keep you in mind for the next CAT event, which homeowner’s reply mentioned their neighbor’s flooded basement.
This is the intelligence that determines whether your CRM becomes a community. It lives in email threads, in the notes field of your phone contacts, in your memory after a golf round with an adjuster. It disappears when your office manager leaves, when you switch phone carriers, when the thread buries itself under 400 new emails.
The Notion Second Brain captures this layer systematically. It’s not a replacement for your CRM. It’s a relationship intelligence layer that your CRM was never designed to hold.
The Architecture: Four Linked Databases
The architecture — four linked databases.
The system uses four Notion databases connected by relations. Notion’s free tier supports all of this — you do not need a paid plan for the initial build. If you add more than five members, you’ll need to upgrade to the Plus plan ($10/user/month).
Database 1: Contacts
Your master contact registry. Every person in your network gets a record here. This does not replace your CRM contact list — it supplements it with relationship context that belongs in a knowledge management tool, not a job management tool.
Properties:
Field
Type
Notes
Name
Title
Full name
Segment
Select
Homeowner / Industry / Trade / Other
Sub-type
Select
Homeowner past client / Adjuster / Agent / PA / Sub / Supplier / Vendor
Email
Email
Phone
Phone
Company
Text
For industry and trade contacts
Location
Text
City or zip — for local filter
Warmth
Select
Hot / Warm / Cool / Cold — subjective relationship temperature
Last Touch Date
Date
Last time you had meaningful contact
Last Touch Type
Select
Email campaign / Personal email / Phone / In person
Times Referred
Number
How many referrals this contact has ever sent you
Notes
Text
Anything important that doesn’t fit a field
CRM ID
Text
Matching ID in ServiceTitan or Jobber for cross-reference
Database 2: Touch Log
Every meaningful interaction with a contact gets an entry here. Campaign sends, personal replies, phone calls, in-person conversations. This is how you build a timeline of every relationship in your network.
Properties:
Field
Type
Notes
Touch Summary
Title
Brief description of the interaction
Contact
Relation → Contacts
Links to the contact record
Date
Date
Touch Type
Select
Campaign email / Personal email / Phone / In person / Reply received
Every referral — whether it turned into a job or not — gets a record here. This is where you track the ROI of the community strategy over time.
Properties:
Field
Type
Notes
Referral Summary
Title
Brief description
Referred By
Relation → Contacts
Who sent it
Referred Person or Property
Text
Who or what was referred
Date Received
Date
Source Touch
Relation → Touch Log
Which email or interaction triggered the referral
Outcome
Select
Job Won / Job Lost / Not Yet Followed Up / Not a Lead
Job Value
Number
Estimated or actual job value if won
Database 4: Campaign Calendar
This is the full campaign planning and results database from the outreach calendar guide. It lives here in the Second Brain so that every campaign is linked to the contacts and touches it generates.
Setting Up the System in Notion: Step by Step
Setting up the system in Notion step by step.
Phase 1: Create the Workspace Structure (30 minutes)
Create a new page in Notion called “CRM Second Brain”
Add four sub-pages, one per database: Contacts, Touch Log, Referrals, Campaign Calendar
On each sub-page, add a full-page database (not inline)
Add all properties to each database as listed above
Set up Relations between databases: Touch Log → Contacts (one contact, many touches), Referrals → Contacts (one contact, many referrals), Referrals → Touch Log (link each referral to the touch that generated it)
Phase 2: Import Your Seeding Data (1–2 hours)
Take your clean, segmented contact CSV from the segmentation brief
In Notion, on your Contacts database, click the three dots → Import CSV
Map the CSV columns to Notion database properties
Notion will create one database record per row
After import, manually review the first 20 records to confirm mapping is correct
Set the Warmth field for your top 30 contacts manually — this is subjective and cannot be automated
Phase 3: Set Up Views for Daily Use (30 minutes)
The database is only useful if you actually open it. Create these four views in your Contacts database:
“Super Connectors” view: Filter by Times Referred ≥ 2, sorted by Times Referred descending. This shows you your highest-value network contacts at a glance.
“Gone Cold” view: Filter by Last Touch Date is before 6 months ago AND Warmth is Warm or Hot. These are relationships that need attention.
“Follow Up Today” view: Filter from Touch Log — Follow Up Needed = true AND Follow Up Date = today. Surfaces what needs action today.
“Homeowners — Local” view: Filter by Segment = Homeowner AND Location contains [your city/zip]. Your residential community at a glance.
Connecting the Second Brain to Your Campaign Workflow
The Second Brain becomes powerful when it’s updated in real time during campaign execution. Here is the exact workflow for each campaign:
Before sending: Open the Campaign Calendar database and update the Status to “Scheduled.” Verify that the target audience count in your email platform matches your Contacts database filtered view for that segment.
Within 48 hours of sending: Log the campaign as a single batch entry in the Touch Log: Touch Type = “Campaign email”, Direction = Outbound, Date = send date. This creates the event anchor for all replies that follow.
For every reply received: Add a Touch Log entry: Touch Type = “Reply received”, Direction = Inbound, link to the Contact record, set Signal based on content (Referral Generated, Lead Mentioned, or Positive). If a follow-up is needed, check Follow Up Needed and set Follow Up Date.
For every referral: Add a Referrals database entry immediately. Link to the Contact who sent it and to the Touch Log entry that triggered it. Set Outcome to “Not Yet Followed Up” until the lead is worked.
After 12 months of this workflow, your Super Connectors view will show you exactly which five to ten people in your network are responsible for the majority of inbound referrals. These are the people to take to coffee, to thank personally, to invite to events. The system surfaces what intuition alone cannot track at scale.
Advanced: Connecting Notion to Your Email Platform via Zapier
For teams who want to reduce manual entry, Zapier (zapier.com) can automate the Touch Log entry step. This requires a Zapier account (free tier allows five automated workflows) and basic Zapier setup familiarity.
The automation: When a contact replies to a Mailchimp campaign → Zapier creates a Touch Log entry in Notion with the reply details, linked to the Contact record by email address.
The Zap flow:
Trigger: Mailchimp → New Campaign Reply (or Gmail → New Email matching campaign reply-to address)
Action 1: Notion → Find Database Item (search Contacts database for the reply’s email address)
Action 2: Notion → Create Database Item in Touch Log (populate fields from the Mailchimp reply data and the Contact ID found in Action 1)
This automation removes the manual step of logging each reply. It does not remove the step of reviewing replies and adding qualitative Signal and Notes — that still requires human judgment.
Zapier setup documentation: zapier.com/apps/mailchimp/integrations/notion and zapier.com/apps/gmail/integrations/notion.
Notion Pricing for This Use Case
Scenario
Plan Needed
Cost
Solo owner managing the database alone
Free
$0/month
Owner + office manager (2 users)
Free (up to 5 collaborators on free plan)
$0/month
Owner + office manager + 3 others
Free (up to 5 still covered)
$0/month
6 or more users
Plus plan
$10/user/month
For most restoration companies running this system, the free tier is sufficient indefinitely. The system described here does not require Notion AI, advanced automations, or enterprise features.
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
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
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
Create account at mailchimp.com. Select Essentials plan. Enter billing info.
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.
Go to Audience → Manage Audience → Import Contacts. Upload each CSV file separately, assigning a tag during each import: “Homeowner”, “Industry”, “Trade”.
Map CSV columns to Mailchimp fields: First Name → FNAME, Last Name → LNAME, Email → EMAIL, Job Type → JOB_TYPE, Segment → SEGMENT.
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
Create account at brevo.com. Select Starter plan ($9/month).
Go to Contacts → Lists → Create a List. Create three lists: “Homeowners”, “Industry Contacts”, “Trade Contacts”.
Go to Contacts → Import Contacts. Upload each CSV, assign to the corresponding list.
Map fields: First Name → FIRSTNAME, Last Name → LASTNAME, Email → EMAIL. Create custom attributes for JOB_TYPE if needed.
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
In Mailchimp, go to Account → Settings → Domains → Add and Verify Domain
Enter your company domain (e.g., yourcompany.com)
Mailchimp will provide you with specific DNS records to add: a CNAME record for DKIM and a TXT record for verification
Log into your domain registrar and add these records exactly as shown. Allow 24–48 hours for DNS propagation.
Return to Mailchimp and click “Authenticate Domain” once DNS has propagated. A green checkmark confirms success.
Brevo Domain Authentication
Go to Settings → Senders & IP → Domains → Add a Domain
Enter your domain and follow the same process — Brevo provides specific DNS records for SPF and DKIM
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
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
Go to Campaigns → Create Campaign → Email
Select “Plain Text” as the campaign type (not the drag-and-drop builder)
Write your email copy in the plain text field
Use Mailchimp merge tags for personalization: *|FNAME|* for first name, *|JOB_TYPE|* for the custom job type field
Example: “Hi *|FNAME|*, It’s [Owner Name] from [Company]. We worked with you on your *|JOB_TYPE|* job a while back…”
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
Go to Campaigns → Email Campaigns → Create an Email Campaign
Choose “Plain Text” from the template selection
Use Brevo’s personalization tokens: {{ contact.FIRSTNAME }}, {{ contact.JOB_TYPE }}
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
Open each draft campaign
In the Campaign Builder, go to the Schedule step
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.
For your first campaign (no historical data), use Tuesday or Wednesday at 9:30am local time as a default
Brevo Scheduling
In the campaign builder, select “Schedule” on the final step
Set date, time, and timezone
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)
Go to notion.com and create a free account
Create a new page called “CRM Touch Calendar”
Add a database (table view) with the following properties:
Add all six planned campaigns for the year as rows in the database
Set the Status to “Planned” for all. Update to “Draft Ready”, “Scheduled”, and “Sent” as you progress
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 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
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:
March or April: One operational ask (hiring or vendor). Three segments. Uses the templates from the other guides in this series.
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
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:
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
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.
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
Why vendor asks work 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
The vendor ask taxonomy.
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:
Vendor Name — the business or person being referred
Trade/Service Type — what they do
Referred By — which contact in your database made the referral (linked to your contact database)
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
Using Claude to write vendor ask emails.
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.
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
What the Notion OS 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
How the starter is priced and scoped.
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.
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.
