Keep learning
Growth leadership
How do you make all four engines work together instead of in isolation?

Document your ideal customer's role, goals, and challenges to tailor messaging and prioritise features that solve real problems they actually pay for.
.webp)
A buyer persona is a semi-fictional profile of your ideal customer. It includes their job title, company size, annual budget, pain points, goals, and how they make purchasing decisions. A SaaS company might have three personas: 'engineering manager', 'VP of operations', and 'CFO'. Each has different concerns, different decision-making criteria, and different language to persuade them.
Buyer personas matter because they align your entire go-to-market strategy. Marketing creates messages that resonate with each persona. Sales uses personas to tailor pitches. Product builds features personas care about. Without personas, you make generic products for generic people. With personas, you understand who you're actually trying to serve and what they actually care about.
The mistake most companies make is creating personas based on demographics alone ('mid-market director of marketing') without understanding their actual problems. A director of marketing at a fintech company has wildly different pressures than a director of marketing at a manufacturing company. Good personas are built on research: customer interviews, sales feedback, and behaviour data. They describe not just who people are but why they buy and what they're trying to achieve.
Without personas, marketing messages try to appeal to everyone and end up persuading no one. With personas, you can create targeted campaigns: one message for CFOs (focused on ROI and risk mitigation), another for engineers (focused on technical capability and integration), another for operations (focused on efficiency and scalability). This focus improves conversion.
Sales and marketing often disagree about who the 'real' decision-maker is. Personas settle this by mapping out all the decision-makers and influencers in a typical deal. It clarifies who marketing should target in initial campaigns and who sales needs to engage later in the cycle.
Product teams use personas to prioritise features. If 'VP of operations' is your most important persona and she cares deeply about mobile access, build mobile first. If 'engineering manager' cares most about API reliability, make API robustness a priority. Personas prevent building features no one asked for.
Talk to 10-15 customers across different segments. Ask about their role, challenges, goals, and how they evaluate solutions. Ask what their typical day looks like. Ask about their budget constraints. Record patterns in responses; people in the same role often share similar concerns.
Usually, you'll find 3-5 distinct personas based on job title and company size. A director at a 50-person startup has different needs than a director at 1,000-person enterprise. Create separate personas for each segment.
Personas should describe not just the person but how they buy. Does a 'VP of engineering' typically choose tools alone or with input from the team? Does budget come from operating expense or capital budget? Does purchasing need approval from procurement? These details shape your sales strategy.
Personas are only useful if your team uses them. Share in Slack, print them, put them in the sales playbook, reference them in strategy meetings. Refine them quarterly as you learn more. Outdated personas are worse than no personas.
Persona 1: 'PM Priya' (Project Manager). Role: Managing 5-10 projects simultaneously. Pain: Stakeholders asking for status updates every day. Goal: Single view of all projects and automatic status reporting. Budget: influences decision but doesn't approve. Persona 2: 'Engineer Eric' (Engineering Manager). Role: Managing team and projects. Pain: Context switching between tools breaks focus. Goal: Minimal tool ecosystem. Budget: Technical influencer, cares about API and integration. Persona 3: 'Finance Felix' (VP Finance). Role: Cost and capacity planning. Pain: No visibility into which projects are over budget. Goal: Financial analytics and capacity forecasting. Budget: approves purchases over £10K. Each persona got different messaging in campaigns.
A CRM vendor assumed 'sales director' was a monolithic role, but interviews revealed two distinct personas: 'quota-focused directors' and 'process-focused directors'. Quota-focused directors cared most about deal acceleration and forecasting accuracy. Process-focused directors cared about team enablement and best-practice adoption. The vendor had been positioning the product around forecasting (a quota concern) and missing sales directors who cared about process. They restructured messaging to speak to both, improving conversion by 35%.
A data analytics platform identified three personas: 'analyst Aaron' (wants flexibility), 'executive Eva' (wants dashboards), and 'manager Marcus' (wants simplicity). Quarterly roadmap planning used personas to allocate engineering: 40% of roadmap to improvements Aaron cared about (API, customisation), 30% to Eva's needs (preset reports, presentation mode), 30% to Marcus (templates, one-click setup). This allocation reflected customer revenue distribution, maximising value delivered to the personas that matter most.
How do you make all four engines work together instead of in isolation?

Build the dashboards and data pipelines that show your growth engines in one view so you can spot bottlenecks and make decisions in minutes, not meetings.

The wrong tools create friction. The right ones multiply your output without adding complexity. These are the tools I recommend for growth teams that move fast.
Analyse last cycle's results across all twelve metrics, identify the highest-leverage improvements, and set priorities that compound into the next period.
Pressure-test your strategy against market shifts, performance data, and team capacity so your direction stays relevant and ambitious.
Bill Aulet
Rating
Rating
Rating
Rating
Rating

Step by step approach to define customers, test value and design a go to market path that leads to repeatable revenue.
Neil Rackham
Rating
Rating
Rating
Rating
Rating

A clear walkthrough of Situation, Problem, Implication, Need payoff with examples that match complex deals.
David Hoffeld
Rating
Rating
Rating
Rating
Rating

Research backed techniques for discovery, framing and closing that marketers can support with better assets.
Eugene M. Schwartz
Rating
Rating
Rating
Rating
Rating

A field guide to message market fit. Use stages of awareness to pick angles, craft offers and brief ads that speak to real pains and jobs.
Not all customer feedback is equally valuable. Learn which segments of your customer base will give you the insights that actually change how you sell and who you should prioritise when time is limited.
Bad interviews produce polite answers that confirm what you already believe. Good interviews surface uncomfortable truths that change your strategy. The difference is in how you ask.
Win customers through direct sales conversations where reps guide prospects from discovery to close with personalised solutions and relationship building.
Store information in browsers to track user behaviour across visits and enable personalised experiences without requiring login for every interaction.
Prioritise tasks systematically by sorting them into urgent-important quadrants, focusing effort on high-impact activities.
Determine whether experiment results reflect real differences or random chance to avoid making expensive decisions based on noise instead of signal.
Unify customer data from every touchpoint to create complete profiles that power personalised experiences across marketing, sales, and product.
Plan how you'll reach customers and generate revenue by choosing channels, pricing, and sales models that match your product and market reality.
Set ambitious goals and measurable outcomes that cascade through your organisation, creating alignment and accountability for strategic priorities.
Deploy fast, low-cost experiments to discover scalable acquisition and retention tactics, learning through iteration rather than big bets.
Group customers by acquisition period to compare behaviour patterns and identify which acquisition channels and time periods produce the best long-term value.
Track predictable monthly subscription revenue to monitor short-term growth trends and make faster decisions than waiting for annual revenue reports.
Track predictable yearly revenue from subscriptions to measure business scale and growth trajectory in B2B SaaS and recurring revenue models.
Estimate the maximum revenue opportunity if you captured 100% market share to size your opportunity and prioritise which markets to enter first.
Turn satisfied customers into active promoters who systematically bring qualified prospects into your pipeline at near-zero acquisition cost.
Document your ideal customer's role, goals, and challenges to tailor messaging and prioritise features that solve real problems they actually pay for.
Measure the percentage of customers who stop paying to identify retention problems and calculate the true cost of growth in subscription businesses.
Calculate how many users you need in experiments to detect meaningful differences and avoid declaring winners prematurely based on insufficient data.
Organise customer and prospect information to track relationships, communication history, and next steps without losing context or duplicating effort.
Achieve the state where your product solves a genuine, urgent problem for a defined market that's willing to pay and actively pulling your solution in.
Track how fast your pipeline of ready-to-buy leads grows to forecast sales capacity needs and spot when lead quality or sales efficiency changes.
Store raw data from all business systems in one place to run analyses and build reports that combine information across marketing, sales, and product.