Most Email CRM setups fail because teams configure features before defining daily operating habits. A seven-day onboarding plan avoids that trap. This guide gives founders a practical Email CRM setup week, with one focused task per day to build labels, routing, ownership, and review cadence without overwhelm.
Day 1: define your stage language
Pick six stages and write one-line definitions for each.
This creates the shared vocabulary your team needs before touching settings.
Stage language is the foundation of everything else. If two people on your team apply the label stage/active to different kinds of conversations, every review, every report, and every handoff is unreliable. Spend Day 1 entirely on getting the definitions right and shared — do not touch Email settings until this document exists.
Your six stages and their working definitions:
New: First contact established, no substantive exchange yet. Timer starts — first response due within agreed SLA.
Active: Ongoing exchange underway. Next action is clearly defined and dated. We are the primary driver.
Waiting: We sent the last substantive message. Awaiting their reply. Follow-up trigger is scheduled.
Committed: They have confirmed intent to proceed in writing or by voice. Moving toward execution.
Closed Won: Revenue recognized or contract signed. Thread archived after a brief close-out note.
Closed Lost: No viable path forward. One-line loss reason recorded before archiving.
Write these definitions in a shared Google Doc. This document becomes your pipeline handbook — link to it in your team wiki or onboarding materials. Review and update it quarterly as your sales motion evolves.
Day 2: set up labels and views
Create stage labels and source labels. Build a clean active view that only shows work requiring action.
Avoid adding advanced labels on day two. Keep it operational.
In Email, go to Settings → Labels → Create new label. Create each stage label with the stage/ prefix. Assign colors systematically: warm colors (orange or amber) for stages requiring your action today, neutral colors (grey or blue) for passive waiting states, green for committed and closed-won.
Create source labels next: source/inbound, source/referral, source/outbound, source/expansion (for existing customer upsell). These labels do not drive daily prioritization — they drive weekly source analysis.
Then configure your inbox view. In Email's inbox settings (gear icon → Inbox), create up to five starred sections. Configure your first section to show starred emails, your second to show stage/new and stage/active threads. This puts your highest-priority work at the top of your inbox without requiring you to open label views separately.
Test the setup by applying each label to a test thread and confirming it appears in the right inbox section.
Day 3: configure intent routing filters
Add filters for inbound forms, referrals, and key lead sources. Route these to stage/new.
At the same time, suppress low-value notification clutter.
Day 3 is filter configuration day. Go to Settings → Filters and Blocked Addresses → Create a new filter.
Priority filters to build today:
Filter 1: From [your-form-notification-address] → Apply stage/new, source/inbound, skip spam. This auto-tags every contact form submission.
Filter 2: Subject contains "intro" OR "introduction" → Apply stage/new, source/referral. Catches most warm intros.
Filter 3: From [list of newsletter platform domains] → Skip inbox, apply newsletters. Clears subscription noise from your daily triage.
After creating each filter, apply it to existing messages by selecting "Also apply to matching conversations." This retroactive application immediately clears noise from your inbox that arrived before the filters were configured.
Verify each filter is working by checking whether recent messages that should be labeled actually received the correct labels.
Day 4: define response and follow-up rules
Set practical SLA bands and response status definitions:
- Acknowledged: you have read the message and confirmed receipt
- Answered: you provided the substantive reply the message required
- Advanced: you moved the deal forward — next stage, booked meeting, sent proposal
Tie every active thread to a due date using Email snooze.
Day 4 is about converting your stage definitions into operational timing commitments. For each stage, define the maximum acceptable response time:
stage/new→ first response within the agreed hot-inbound SLA (typically one hour for high-intent leads, same day for standard inbound)stage/active→ next action completed within the agreed timeframe (typically same day or next business day)stage/waiting→ follow-up sent within five business days of the last message if no reply
Write these timing commitments into your pipeline handbook next to the stage definitions.
Practice using Email snooze with intention: open five active threads, write a brief next-action annotation in each ("Next: send pricing deck by Thursday / Owner: me"), and snooze each thread to the appropriate date. This builds the snoze-with-context habit that keeps your pipeline moving without requiring external tools.
Day 5: standardize templates and close-outs
Create basic templates for acknowledgment, next-step asks, and polite close-outs.
This reduces response variance and protects quality under load.
Email Templates (formerly Canned Responses) let you save reusable message drafts. Enable them in Settings → Advanced → Templates. Then build your minimum template library.
Template 1: Initial acknowledgment Use when you receive an inquiry but cannot respond fully immediately. Brief, warm, and specific: "Thanks for reaching out — I've seen your message and will follow up with [specific thing] by [specific date]."
Template 2: Next-step ask Use at the end of a discovery conversation to confirm alignment and book the next step: "Great to connect — based on what we discussed, the right next step is [specific action]. Here are [two times that work] for a follow-up call. Does either work for you?"
Template 3: Proposal delivery Use when sending a proposal or pricing: "Attached is the proposal we discussed. Key points: [three bullets]. Happy to walk through any questions — let me know."
Template 4: Polite close-out Use after your follow-up sequence ends without a response: "Since I haven't heard back, I don't want to keep pinging you unnecessarily. If the timing isn't right, I'll leave the door open for whenever you're ready. No hard feelings either way."
Keep templates short and personalizable. The first line should always be customized — templates that read like form letters reduce conversion.
Day 6: run a mini pipeline review
Test your process with a twenty-minute practice review:
- Open every stage label and review each thread — make one decision per thread in thirty seconds
- Check for missing owners and next actions — any thread without both needs immediate remediation
- Identify stale threads older than seven days — make a close-lost decision or set an immediate follow-up
Fix gaps immediately while setup context is fresh.
The mini review on Day 6 is diagnostic: you are testing whether the system you built in Days 1-5 is working as intended. Common Day 6 findings:
- Several high-intent threads from last week did not receive the
stage/newlabel — your form notification filter is misconfigured - Multiple active threads have no next action annotation — the snoze-with-context habit from Day 4 did not stick
- Three threads that should be closed-lost are still labeled active — close-out discipline needs reinforcement
Each finding is a system gap to fix immediately, while you still have setup context fresh in your mind. After Day 6, you know exactly what is and is not working.
Day 7: lock weekly cadence
Schedule a recurring weekly review block and document your process in one page.
Sustained review is what turns setup into a real operating system.
On Day 7, create two calendar events: a twenty-five minute recurring event every Friday at 4pm (or Monday at 9am) labeled "Email pipeline review," and a fifteen-minute recurring event at the same frequency labeled "Tracking update" — this is when you update your stage counts in the tracking spreadsheet.
Then write a one-page process document. It should cover: your six stage definitions, your response SLA bands, your template library location, your filter list (with what each filter does), and your weekly review checklist. This document is what a co-founder, new hire, or assistant needs to run the pipeline in your absence.
The one-page process document also serves as a forcing function for clarity. If you cannot describe your pipeline process in one page, the process is not yet clear enough to be reliably executed by anyone other than you.
Conclusion
An email CRM onboarding week works when each day focuses on one behavior-changing improvement and ends with clear process ownership. Keep the setup simple, then improve based on real friction from live pipeline flow. For the full framework, read The Complete Email CRM Guide for Founders. Continue with Email CRM Checklist for Early-Stage Startups and From Inbox Chaos to Organized Pipeline. Get started with Kaname when scale demands unified inbox context.