BoardSnap is an iOS app that reads sales playbook whiteboards and turns ICP definitions, qualification criteria, stage gates, objection handling, and competitive positioning into a structured playbook document for the full sales team.
Sales playbooks are built by founders, heads of sales, or sales enablement teams who know what works. They're built in whiteboard sessions: here's the ICP, here's how we qualify, here are the stages and what's required to move between them, here's how we handle each objection, here's how we beat competitor X.
The problem is getting that knowledge into a document that new reps can actually use. Most sales playbooks are either too long (nobody reads them) or too vague (nobody can apply them). The whiteboard session produces the concrete, specific guidance — and that's what needs to be captured.
BoardSnap reads the whiteboard. The playbook document writes itself.
Company attributes (size, industry, tech stack), buyer persona (title, pain points, buying triggers), and disqualifiers (who is NOT a fit). Specific enough that a new rep can qualify a lead in two minutes.
Six to eight stages from first contact to closed/won. For each stage: what it is, what actions move a deal into it, and what the exit criteria are. Exit criteria are the most important part — write them explicitly.
MEDDIC, BANT, SPICED — or your own. Write the specific questions for each dimension. What does 'economic buyer identified' look like in practice for your specific deal? This specificity is what makes a playbook useful.
Top ten objections, each with a specific response and a next step. Write verbatim responses where possible — reps use exact language when it's available. 'Not in budget' is different from 'too expensive' — separate responses for each.
Main competitors with their strengths, weaknesses, and the specific phrases to use when a prospect mentions them. One section per competitor. Short and specific — not a long essay.
BoardSnap reads the ICP, stages, qualification framework, objection handling, and competitive positioning as a structured playbook document.
A sales playbook document: ICP definition with qualifiers and disqualifiers, stage-gate map with exit criteria, qualification framework with specific questions, objection/response library, and competitive positioning summaries. Action items cover any gaps in the playbook (missing objection responses, undefined stage gates). Ready to distribute to the sales team.
A series A startup formalizing their sales process for the first time. The founder's whiteboard session captured everything that had been in their head. BoardSnap's output became the onboarding document for the first two sales hires.
An established sales team refreshing their playbook after a product pivot. The board identified what stayed the same (ICP core, stage structure) and what changed (value messaging, competitive positioning). BoardSnap captured both the old and new versions in the same project.
Short enough to be read, specific enough to be useful. Most effective playbooks are five to fifteen pages — not a book. The whiteboard session naturally produces the density that works: concrete and specific, not comprehensive. BoardSnap captures that density without padding it.
The head of sales, one or two top performers, and one recently onboarded rep. The top performers know what works; the new rep knows what's confusing. The combination produces a playbook that's both accurate and usable.
Quarterly reviews for active teams. Trigger a refresh when win rates drop, when competitive landscape changes, or when a new product or market segment is added. BoardSnap projects accumulate playbook versions — track the evolution over time.
Yes. Role-play scenarios on a whiteboard — objection handling practice, discovery question drilling — produce real content when snapped. Capture the 'what worked' and 'what to try differently' from each training session into the project.
Snap the board, ship the action items in ten seconds.