Your job
Decide what Vela AI actually does at launch — and what it doesn't. Your job is to define the scope, protect the timeline, and make sure Sales can demo something compelling.
👥 You are a team of 2
Divide and conquer: one person focuses on feature prioritisation and the timeline, the other on demo strategy and beta plan. Align before presenting.
What you need to deliver
This is guidance to help structure your thinking — not a strict checklist. Focus on what matters most for a realistic plan.
1. What are the 3–4 launch features?
From the full product vision, what ships at launch? Prioritise ruthlessly.
2. What are we NOT building for launch?
Be explicit about what is cut and why. This is as important as what you include.
3. What does the demo look like?
Walk through what Sales will show on a call. What is the sequence? What is the "wow" moment?
4. Who are the beta users and when?
How many users test before launch? From where? What feedback do you need?
5. What is the 8-week build timeline?
High-level: what happens each week? When is feature freeze? When is beta?
Your constraints
- Feature freeze at Week 3 — nothing new enters the roadmap after that
- Engineering team has 4 people for this product
- Must integrate with Salesforce and HubSpot at launch (non-negotiable)
- Demo must be ready by Week 6 for Sales to start calling prospects
Who to talk to
- Sales: What do reps need to see in a demo to close deals?
- Marketing: What is the product hook — the one thing that makes people sign up?
- Operations: What does a Salesforce/HubSpot integration realistically take?
- Enablement: How complex is the product to learn? What training will reps need?
Watch out for
- Building too many features — a focused product beats a bloated one
- No clear "wow" moment in the demo
- Promising integrations or features that 4 engineers can't ship in 8 weeks
- Not involving Sales in defining the demo — they're the ones using it
You have 60 minutes. Go talk to other teams now.