A customer-led workflow

Quarterly Planning

Turn customer and team insights into OKRs and roadmap priorities. Plan your quarter based on data, not opinions or whoever spoke loudest in the last meeting.

Customer evidence

Rappi
“Citations in reports are critical for us. They build trust and prove accuracy — when leadership sees top citations, it reinforces credibility.”
Juan CanalHead of Product, RappiRead their story

Make the decision with the evidence in reach.

Ask a specific question of your company context. Inspect the accounts and source material behind the answer before using it in a report or a team decision.

BuildBetter interface supporting Quarterly Planning
Product example. Inspect findings alongside their customer and source context.

Put it to work.

01

Quarter-in-Review Aggregation

Pull all Q1 conversations—customer calls, internal meetings, all-hands recordings, strategy sessions, support data—into a single collection and query it as one unified dataset.

02

Strategic Theme Identification

Ask Chat to surface the top 3–5 strategic themes from your Q1 data. It clusters mentions by frequency, finds patterns across teams, and shows you the leading indicators hiding in your conversations.

03

Data-Backed OKR Generation

Once themes are identified, ask Chat to suggest OKRs for Q2 with measurable key results grounded in customer data. Replace "we think customers want X" with "78 customers mentioned X in Q1."

04

Roadmap Prioritization Matrix

For each candidate roadmap item, Chat can tell you: how many customers mentioned it, what they said, revenue impact, and urgency signals. Data replaces debate.

05

Planning Document Generation

Generate a formatted quarterly planning doc with one click: Q1 retrospective, customer insights, strategic themes, proposed OKRs, and roadmap recommendations—ready to share with your team.

06

Team Alignment Without Debate

Share the planning doc before your planning session. Everyone sees the same customer data. Alignment happens faster because priorities are grounded in evidence, not opinion.

A practical place to start.

Phase 1 — Aggregate Q1 Data
  1. Create a Q1 Review Collection

    Gather all Q1 conversations into one collection: customer calls, internal team meetings, all-hands recordings, strategy sessions, and support ticket data.

  2. Ask strategic diagnostic questions

    Query Chat: "What are the top customer problems from Q1?" / "What did we commit to but didn't ship?" / "What internal blockers came up repeatedly?" / "What market opportunities did customers mention?"

Phase 2 — Find Strategic Themes
  1. Identify Q2 strategic themes

    Query Chat: "Based on all Q1 data, what are the top 3–5 strategic themes that should guide Q2?" You'll get themes ranked by mention frequency with supporting evidence.

  2. Generate OKR recommendations

    Query Chat: "Based on these themes, suggest OKRs for Q2 with measurable key results." Creates data-backed OKRs instead of best guesses.

Phase 3 — Build the Q2 Roadmap
  1. Prioritize with customer impact data

    Query Chat: "For each potential roadmap item, tell me: customer mention count, revenue impact signals, and urgency." This creates a prioritization matrix based on real data.

  2. Generate the planning document

    Click Generate → Generate Document → "Quarterly Planning." Creates a formatted doc with Q1 retrospective, customer insights, strategic themes, proposed OKRs, and roadmap recommendations.

Phase 4 — Team Alignment
  1. Share the planning doc before the meeting

    Distribute the generated doc 24 hours before your planning session. Everyone comes in with the same customer data already visible.

  2. Run a focused alignment session

    With shared data as the foundation, debate is replaced by decisions. Use the session to finalize OKRs and assign owners rather than arguing priorities.

  3. Set up Q2 tracking collections

    Create Q2 collections to track progress. Configure weekly auto-reports so you can monitor whether Q2 conversations are validating or challenging your OKRs in real time.

Keep the workflow useful
  • Start aggregating your Q1 collection two weeks before planning—don't try to do it all in the last two days
  • Ask Chat for strategic themes before forming any opinions yourself—let the data lead, then apply your judgment
  • Include internal team meetings in your Q1 collection, not just customer calls—blockers and commitments matter
  • Generate the planning doc and share it async before your planning session so the meeting is about decisions, not discovery
  • Compare Q2 themes to Q1 themes to identify whether you're making progress on the same problems or new ones are emerging

Keep exploring.

Ready to plan your next quarter with data, not opinions?

Bring a real question. We’ll walk through the context and the next step together.

Book a demo