Mountain View Events
Owner, venue coordinator, and two sales assistants
Generated from setupyour-workshop-products
AI adoption readiness demo
This is the workshop pre-work product: score the team's readiness, name the honest next step, identify gaps, and keep risky customer-system actions out of scope until there is a separate approved build.
4.05/5
customize_first
Customize the workshop pre-work before booking so the exercises use real examples.
Ready signals.
- Audience is clear.
- Workflow candidates are specific enough to practice on.
- Human approval culture is strong.
- Team has time to practice.
Fix before rollout.
- Approved facts need a customer-safe source before AI drafts answers.
- Tool access and data boundaries need to be clarified.
Generated readiness report
Pre-work with boundaries.
The report names next step, readiness gaps, action plan, non-goals, and customer-system boundaries.
# AI Adoption Readiness: Mountain View Events Operator: Jim Audience: Owner, venue coordinator, and two sales assistants ## Readiness score - 4.05/5 - customize_first ## Recommended next step - Customize the workshop pre-work before booking so the exercises use real examples. ## Strengths - Audience is clear. - Workflow candidates are specific enough to practice on. - Human approval culture is strong. - Team has time to practice. ## Gaps - Approved facts need a customer-safe source before AI drafts answers. - Tool access and data boundaries need to be clarified. ## Current tools - Gmail, Google Calendar, Squarespace, Google Drive ## Desired outcomes - Know whether to start with training, an Opportunity Map, or an agent build - Give the team a safe first AI habit - Name one follow-up build candidate without pretending integrations are already wired ## Risk boundaries - pricing exceptions - legal questions - refunds - booking holds ## Action plan - Jim: Create a one-page approved-facts sheet for the first training examples. Proof: Approved facts separate policies, prices, availability, and exceptions. - Mountain View Events: Pick two real team tasks to use during the workshop. Proof: Examples include inputs, desired output, reviewer, and stop conditions. - Jim: Confirm whether the follow-up should be workshop, Opportunity Map, or first build. Proof: Recommendation names the next paid step and the non-goals. ## Non-goals - No autonomous external sending from this readiness report. - No CRM, calendar, email, booking, payment, or website integration is included. - No customer-system write access, credential handling, or private transcript storage. ## Pricing anchor - Adoption readiness can be sold as workshop pre-work or included in an Opportunity Map.