1. Discovery question block
Use this to determine whether the client needs a CMS, owner mode, operator dashboard, workflow map, or a simpler low-code lane.
- What part of the system breaks most often right now?
- Who needs to edit it after launch?
- Do they want control, simplicity, or speed most?
- What are they paying for today that they do not understand?
2. Stack recommendation matrix
A reusable framework for recommending Google, WordPress, Firebase, hybrid, low-code, or nonprofit-operations stacks.
- Best-fit platform
- Fallback platform
- Control vs complexity
- Maintenance and lock-in notes
3. Owner editing model grid
Use this when the client does not know whether they need WordPress editing, dashboard editing, Owner View, or support-only editing.
- CMS editing for heavy editorial owners
- Owner View for visual/text instructions on the real page
- Dashboard editing for structured asset control
- Support-only when change safety matters more than autonomy
4. Workflow map template
A repeatable map for intake, production, publishing, editing, support, and recovery.
- Where leads enter
- How work is staged
- How updates are approved
- How post-launch requests are captured
5. Recap delivery template
This is the structure for what the client should leave with after the session.
- Recommended stack
- Backup stack
- Why this order makes sense
- What to build now, next, and later
6. Objection handling set
Reusable responses for price, platform hesitation, lock-in fear, and “why not just use one tool?” questions.
- Price reframed as avoided rebuild cost
- Platform choice reframed as workflow fit
- Lock-in reduced through fallback planning
- Hybrid explained as a practical compromise
7. Conversion path map
This block ties the consult into the actual revenue ladder.
- 3-page shell
- 5-page shell
- Owner View service
- Workflow support or custom buildout
8. Competitor contrast
A reusable comparison that explains why this lane is stronger than generic web consulting or agency discovery calls.
- Not just advice
- Not just one ecosystem opinion
- Not just qualification for a build
- It teaches the machine and the build order
9. Nonprofit / mission adaptation
Use this when the operator is a case manager, nonprofit founder, housing program, or other mission-driven service lane.
- Role-safe dashboards
- Case intake and follow-through
- Support and visibility lanes
- Operational simplicity for thin teams
10. Follow-up email structure
A repeatable follow-up that confirms what was understood and what the next paid move should be.
- What we decided
- What we ruled out
- What to build first
- The clean next service lane
11. Five recommended mixes
Use these as reusable one-pagers during or after the consultation instead of rebuilding your recommendation logic from scratch.
- Starter operator mix
- Founder with limited time
- Content-heavy brand
- Premium site buyer
- Mission or compliance-sensitive buyer
12. Active Codee versions
These are now separate recommendation modes you can prescribe, not just names in a guide.
- Codee Sprint
- Codee Owner
- Codee Editorial
- Codee Operator
- Codee Architect