Skip to content
128 changes: 128 additions & 0 deletions challenges/en/customer-experience.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
---
key: cx
order: 2
name: Customer Experience
tagline: Customers who stay and buy more
hero:
title:
- Customers who stay
- and buy more.
quote: We sign, then we lose track.
lead: "A large share of tomorrow's revenue already sits with today's customers. We build the organisation, processes, tools and metrics that secure it,"
highlight: from signature to renewal.
cta: Talk to an architect
bowtie:
activeStages:
- onboarding
- adoption
- expansion
caption: "After the signature: kick-off, value delivered, renewal and expansion."
symptoms:
title:
- Your customers leave
- and nobody saw it coming.
items:
- The handover from sales to delivery happens by email, and everyone asks the customer the same questions again.
- Renewals come to light a few weeks before the due date.
- Nobody knows which customers are at risk until they say so.
- Expansion opportunities depend on each account manager's instinct.
- Sales, support and account management do not share the same view of the customer.
audience:
- team: Customer Success
roles: Head of CS, CCO
benefit: A clear view of customer health and upcoming renewals.
- team: Customer Success
roles: CSMs, Account Managers
benefit: Fewer emergencies to handle, more meetings that prepare expansion.
- team: Leadership
roles: CEO, Managing Director
benefit: A rising NRR and growth that no longer relies on acquisition alone.
- team: Sales
roles: Sales teams
benefit: A clean handover after the signature, with no loss of information.
workstreams:
intro: Six workstreams, from signature to account growth.
items:
- category: Organisation
title: Who looks after which customer, and how
description: Portfolio segmentation, roles across account management, customer success and support, service levels by segment.
deliverable: Customer organisation model and coverage rules.
- category: Handover
step: 1
title: A handover with no loss of information
description: "What sales promised reaches delivery: handover record in the CRM, standard kick-off, onboarding milestones."
deliverable: Equipped handover and kick-off process.
- category: KPIs and steering
step: 3
title: Every customer's health, easy to read
description: Health score, risk signals, retention and revenue growth by segment, portfolio reviews.
deliverable: Customer dashboards and review rituals.
- category: Renewal
step: 4
title: Renewals anticipated, expansion managed
description: Due dates visible months ahead, renewal and expansion pipeline, account plans for key customers.
deliverable: A renewal and expansion pipeline in your CRM.
- category: Processes and tools
title: One shared view of the customer
description: "CRM, support and billing connected: every team sees the history, tickets, contracts and opportunities."
deliverable: A unified customer record and its automations.
- category: Enablement
title: Customer teams with the right tools
description: Follow-up, renewal and expansion playbooks, built into the teams' tools.
deliverable: Customer playbooks and an onboarding path for account managers.
aiBridge:
title: Weak signals come up before the customer leaves.
bullets:
- Tickets, emails and calls are read to detect a risk or an opportunity.
- Every account manager gets an account summary before their meeting.
- Account reviews take a few minutes to prepare.
demo:
channel: Account alert · Kestrel
agent: Customer Agent
time: "09:12"
opening:
kind: statement
text: "Churn risk detected. Health score: 72 → 54."
elements:
- type: status
label: Support
value: 3 critical tickets in 10 days
state: alert
- type: status
label: Usage
value: "-30% logins"
state: alert
- type: status
label: QBR call
value: Competitor mentioned twice
state: alert
- type: buttons
labels:
- Open the account
- Prepare the meeting
footer: Summary sent to Julie before her 14:00 meeting
method:
subtitle: From a portfolio analysis to recurring revenue you can steer.
steps:
- text: The Design Sprint analyses your portfolio, your churn and your renewals, and finds where revenue leaks.
- text: The squad builds the organisation, processes and metrics with your sales, delivery and support teams.
- text: Your teams steer the portfolio on the metrics, and renewals stop being a surprise.
tools:
- hubspot
- salesforce
- planhat
- zendesk
- vitally
note: "And the tools you already have: we start from your stack."
case:
headline: "[Client name]: [the shift in one sentence]."
summary: "[Context in two lines. What we built. What changed for leadership.]"
metrics:
- value: "[X]"
label: "[Renewal rate, before and after]"
- value: "[X]"
label: "[Share of revenue from existing customer growth]"
diagnostic:
question: What if your next growth already sits with your customers?
subtitle: In 30 minutes, a revenue architect reviews your customer base with you. You leave knowing where to start.
---
116 changes: 116 additions & 0 deletions challenges/en/revenue-ai.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,116 @@
---
key: ai
order: 6
name: Revenue AI
tagline: AI that works for your teams
hero:
title:
- Your teams and your AI agents,
- finally in the same system.
quote: Everyone uses ChatGPT, nobody sells better.
lead: "An AI agent does not know what a qualified opportunity is. Someone has to teach it. We pick the use cases that matter for your sales, we make reliable"
highlight: the data and processes they run on, and we measure what they bring in.
cta: Assess my AI maturity
bowtie:
activeStages:
- demand-generation
- discovery
- negotiation
- closing
- onboarding
- adoption
- expansion
caption: At every stage, AI captures information and returns it at the right time. As long as the stage is well defined.
symptoms:
title:
- Plenty of trials.
- Little effect on sales.
items:
- Every rep has their own AI tools, and nobody knows which ones.
- You paid for licences that half the team no longer opens.
- The AI pilot looked great in the demo, then stopped.
- Your customer data goes into tools nobody has approved.
- Nobody can say how much AI brought in this quarter.
audience:
- team: Leadership
roles: CEO, Executive team
benefit: An AI roadmap that delivers measurable results, not proofs of concept.
- team: Sales
roles: CRO, Sales Director
benefit: Teams that prepare, follow up and sell faster.
- team: Ops
roles: RevOps, Ops
benefit: AI use cases plugged into reliable, governed and maintained data.
- team: Field teams
roles: Reps and CSMs
benefit: Fewer admin tasks, more time with customers.
workstreams:
title: Six use cases, built on verified foundations.
intro: Each one is delivered in a Revenue AI Sprint.
items:
- category: Target
title: The right accounts, enriched and prioritised
description: Identifying the accounts that match your target, automatic enrichment, then prioritisation by buying signals. Your reps know who to call, and why.
deliverable: "A scoring agent plugged into the CRM: every morning, the list of accounts to call, enriched and ranked, with the signal behind each call."
note: "Prerequisite: an explicit ICP and a CRM that serves as the reference."
- category: Capture
title: Call notes fill in the CRM
description: Qualification, objections and next steps attached to the right deal, with no data entry.
deliverable: "A post-call agent connected to your phone system: summary, qualification fields and next step written to the deal, approved in one click."
note: "Prerequisite: defined sales stages and qualification fields."
- category: Prepare
title: Meeting prep in one minute
description: Account history, latest exchanges, likely stakes, questions to ask.
deliverable: "An automatic brief sent before every meeting in Slack or by email: account context, contacts, stakes and questions to ask."
note: "Prerequisite: a reliable account record and activity history."
- category: Steer
title: An assisted pipeline review
description: At-risk deals flagged before the meeting, with the reason for the risk.
deliverable: "A weekly alert in the team channel: at-risk deals, the reason for the risk and a prepared follow-up for each."
note: "Prerequisite: stage exit criteria and close dates that hold."
- category: Forecast
title: The forecast in plain language
description: Leaders ask their question in plain English and get the number, with its detail.
deliverable: "A forecasting assistant you can query in plain English, connected to the CRM: the number, its detail by deal and the change from last week."
note: "Prerequisite: a forecasting method and shared categories."
- category: Guide
title: The playbook in the rep's tool
description: The right resource at the right point in the cycle, with no digging through a drive.
deliverable: "A sales assistant plugged into your playbook: the right resource, standard objection or script pushed to the rep based on the deal stage."
note: "Prerequisite: an up-to-date playbook, stored in Notion or your knowledge base."
aiBridge:
title: AI speeds up a system that works. Anywhere else, it amplifies the mess.
bullets:
- An assistant plugged into a poorly filled CRM gives wrong answers with confidence.
- "That is why every sprint starts by checking the foundations: data, sales processes, tools."
- When they hold, we deploy. When they are missing, we tell you, and we start there.
method:
title: The Revenue AI Sprint
subtitle: Three weeks to move from trial to decision.
steps:
- title: Check the foundations
text: "Data, sales processes, tools: what is ready for AI and what is not."
- title: Prove it on a real case
text: A first use case plugged into your tools, used by a real team, measured.
- title: Decide what comes next
text: A roadmap costed in impact. If the foundations are not ready, we start there.
tools:
- hubspot
- salesforce
- claude
- notion
- modjo
- claap
note: Data in your CRM, intelligence with Claude, knowledge in Notion. Also deployable on the agent platform you already have.
case:
headline: Ocobo runs on AI every day, from meeting prep to sales coaching.
summary: "[Two lines on internal use, then a first client case from an engagement.]"
metrics:
- value: "[X]"
label: "[Time saved per rep]"
- value: "[X]"
label: "[Measured effect on pipeline]"
diagnostic:
question: Is your Revenue organisation ready for AI?
subtitle: In 30 minutes, a revenue architect assesses your teams' AI maturity with you. You leave knowing where to start.
---
120 changes: 120 additions & 0 deletions challenges/en/revenue-performance.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,120 @@
---
key: rp
order: 3
name: Revenue Performance
tagline: Revenue you can see coming
hero:
title:
- Revenue
- you can see coming.
quote: I find out how my quarter went at the end of the quarter.
lead: "Your board, your investors or your bank ask you for a forecast. Your teams give you a gut feeling. We build the system that turns"
highlight: your pipeline into reliable numbers, month after month.
cta: Talk to an architect
bowtie:
activeStages:
- discovery
- negotiation
- closing
- expansion
caption: "From first meeting to signature, then account expansion: everywhere your forecast takes shape."
symptoms:
title:
- Your numbers live in a few people's heads.
- Nowhere else.
items:
- Your forecast is rebuilt by hand in a spreadsheet at the end of every month.
- Pipeline stages mean something different to each rep.
- Big deals slip from one quarter to the next and nobody sees it coming.
- The CRM and finance give two different numbers for the same month.
- When a rep leaves, visibility on their accounts leaves with them.
audience:
- team: Leadership
roles: CEO, Managing Director
benefit: A number you can commit to in front of the board, with no end-of-quarter surprise.
- team: Finance
roles: CFO, Finance Director
benefit: A sales forecast aligned with budget and cash flow.
- team: Sales
roles: Sales Director, CRO
benefit: A readable pipeline, gaps spotted early, faster decisions.
- team: Sales
roles: Sales managers
benefit: Useful pipeline reviews, focused on the deals that matter.
workstreams:
intro: Four workstreams, prioritised from where you start.
items:
- category: Processes and tools
title: A pipeline that means the same thing to everyone
description: Sales stages defined by exit criteria, shared qualification, probability rules.
deliverable: Sales process documented and configured in your CRM.
- category: Data
title: Data you can rely on
description: Mandatory fields at the right time, clean-up, reconciliation between CRM and finance.
deliverable: A single data model and its quality rules.
- category: KPIs and steering
title: A forecast that builds itself
description: Forecast by category, rep commitment, forecast against actuals.
deliverable: Automated forecast, consolidated every week.
- category: Organisation
title: A steering ritual that holds
description: Weekly pipeline review, leadership dashboard, board or investor reporting.
deliverable: Dashboards and rituals run by your managers.
aiBridge:
title: Once the system is in place, AI makes it run faster.
bullets:
- Call notes update the CRM with no data entry.
- At-risk deals are flagged before the pipeline review.
- Leaders ask their question in plain English and get the number.
demo:
channel: "# leadership"
agent: Forecast Agent
time: "08:05"
opening:
kind: question
text: Where are we on the quarter?
elements:
- type: kpis
items:
- value: €1.24M
label: commit
- value: 82%
label: of target
- value: +6 pts
label: vs. last week
- type: progress
percent: 82
target: 100
- type: status
label: Brightlane · €180k
value: No activity for 14 days
state: alert
- type: status
label: Kestrel · €95k
value: Close date pushed back
state: alert
footer: Calculated from HubSpot, updated this morning
method:
subtitle: From diagnosis to numbers your teams deliver on their own.
steps:
- text: The Design Sprint measures the gap between your forecast and your actuals, and finds where it comes from.
- text: The squad delivers the priority workstreams in your CRM, with your sales managers and your finance leadership.
- text: Your teams run the rituals. We stay until the gap between forecast and actuals holds.
tools:
- hubspot
- salesforce
- modjo
- notion
note: "And the tools you already have: we start from your stack."
case:
headline: "[Client name]: [the shift in one sentence]."
summary: "[Context in two lines. What we built. What changed for the CEO.]"
metrics:
- value: "[X]"
label: "[Forecast against actuals gap, before and after]"
- value: "[X]"
label: "[Time saved on reporting]"
diagnostic:
question: What is the gap between your forecast and your actuals?
subtitle: In 30 minutes, a revenue architect measures it with you. You leave knowing where to start.
---
Loading
Loading