Overview

When the proposal-router skill drafts a proposal, it lands in Drive and posts to #elevaite-team. Before that proposal goes to a prospect, one of us reviews it against this checklist. The goal is a 5-minute pass that catches the failure modes a routine is most likely to make — not a deep rewrite.

Before You Start

Access to Google Drive where proposal is stored
Access to Slack #elevaite-team channel
Discovery call transcript or notes for reference
Current pricing rates (FAIO = $9,500/3-mo or $8,500/12-mo as of 2026-04-25)
Prospect's website for company name verification

Steps

Review discovery accuracy: verify company name spelling (legal name, check their website if unsure), industry specificity, employee count, stakeholder names/titles, and primary pain point in their language
Check tier match defensibility: confirm recommended tier matches manual judgment, pricing matches current rates, and total cost math is correct
Validate industry-specific customization: ensure case study reference matches their industry, phase examples feel relevant to their work, and compliance/regulatory mentions are present if relevant
Review voice and brand: check for no em dashes in copy, contractions used appropriately, no forced reframes or copywriter tricks, and no inside-baseball jargon
Verify Day-90 walk-away clause for FAIO tier and above: confirm clause is present and visible with non-defensive language
Final send readiness check: confirm recipient email and cc's, create specific subject line, write first line referencing discovery call, include clear next step, and set Drive link permissions correctly
If spotting pattern issues across 2+ proposals, update the proposal-router skill configuration and log changes in decisions folder

Quality Check

Each section took approximately 60 seconds or less (except final send readiness at 45 seconds)
No section required more than 5 minutes of editing (if so, flag fundamental routine issue)
All checklist items verified for the specific proposal
Proposal ready to send without further edits

Common Issues

Wrong tier matching: Routine likely missed a qualifier - note which one in Slack thread to update matching logic
Generic industry references: Update Step 5 customization map in proposal-router skill
Repeated failure modes: Don't just fix individual proposal - update the routine at skills/proposal-router/SKILL.md
Em dashes in copy: Replace with periods, parentheses, or commas for natural voice

Proposal Review Before Send