audit revenuecroprise de postediagnosticrevenue operationsb2b

CRO Revenue Audit: The 30-Day Onboarding Method

Complete framework for auditing a revenue engine in the first 30 days as a new CRO: 8 pillars, 47 metrics, and a week-by-week audit calendar.

Charles-Alexandre Peretz21 min read

Co-founder of ACROSS INSIGHT, 15 years in Revenue Operations. Expert in B2B commercial performance diagnostics.

A CRO's revenue audit on taking up the role is the structured evaluation of the 8 pillars of the revenue engine (branding, acquisition, BDR, sales, CRM, RevOps, CSM, management) carried out during the first 30 days to produce a quantified diagnostic, identify critical breakdowns, and ground every decision in data rather than intuitions inherited from the previous role. It is the first step of the 100-day plan and the one that determines the quality of every step that follows: a CRO who skips the audit or rushes it builds their strategy on sand.

In the field, a recurring pattern emerges: CROs whose tenure lasts have almost always produced a structured written diagnostic by day 30, whereas those who leave quickly either skipped this step or delegated the audit to a team that lacked the perspective needed to connect the pillars to one another. The gap between the two trajectories shows up as early as week 5: the CRO who audited makes precise, well argued decisions, while the one who did not audit improvises and is constantly correcting course.

This article details the complete method: the 8 dimensions to cover, the 47 metrics to quantify, the maturity grid that turns observations into actionable findings, the week-by-week audit calendar, the format of the deliverable to hand to the CEO, the mistakes that invalidate a revenue audit, the comparison between an internal audit and an external audit, and the transition to quick wins from day 30 to day 60.

Key Takeaways

  • Mandatory scope: all 8 revenue pillars (branding, acquisition, BDR, sales, CRM, RevOps, CSM, management) must be covered. A partial audit produces a partial diagnostic and biased decisions.
  • Duration: 25 to 30 calendar days, including 15 to 20 days of interviews, with the rest spent analyzing data and writing the diagnostic.
  • Interview volume: between 25 and 40 individual interviews of 45 to 60 minutes with every revenue stakeholder, including 3 to 5 active customers.
  • Deliverable: a 10 to 15 page document structured around a quantified current state, major findings ranked by severity, and action priorities with estimated effort.
  • Quality criterion: a good audit produces at least 3 findings that no one in the organization had explicitly voiced before your arrival. If all your findings were already known, the audit lacks depth.
  • Average score observed: French B2B scale-ups between €10M and €100M ARR often score well below average in our diagnostics, with sharp gaps between pillars (acquisition is consistently the weakest pillar, management the strongest).
  • Main pitfall: confusing an audit with an inspection. The goal is not to hand out demerits, it is to understand why the organization works the way it does.

"Leaders who succeed in their transitions spend the early weeks learning, not acting. Those who skip this step make decisions based on incomplete information, then spend months fixing avoidable mistakes."

Michael Watkins, The First 90 Days (Harvard Business Review Press)

Why the Revenue Audit Is a CRO's First Act

A CRO joining a B2B scale-up between €10M and €100M ARR inherits a revenue engine built up over several years, often by accretion: a sales process set up by the first VP Sales, a CRM configured by a consultant who has since left, rituals imposed by a board that did not understand the metrics, and an oral culture that compensates for gaps in documentation. No dashboard captures this reality. No monthly reporting shows the interactions between pillars, the invisible dependencies, or the human workarounds that mask structural dysfunctions.

The Perception vs. Reality Gap

In our diagnostics, we systematically observe a gap between internal perception ("our CRM is well maintained," "our reps are good," "our pipeline is healthy") and measured reality. Teams overestimate their revenue maturity relative to the objective score calculated across the 8 pillars. This gap is all the more dangerous because it is invisible to a CRO who relies on what the incumbent team says. Branding and management are the pillars where overestimation is strongest, because they are the hardest to objectify without a structured grid.

Building a Common Language

The audit corrects this bias. It produces a common language, shared numbers, and a factual foundation on which to build the decisions of the following 70 days. A CRO who walks into the first 1:1 with the CEO with quantified findings immediately establishes credibility. A CRO who shows up with qualitative impressions positions themselves as a commentator, not a decision maker.

Audit vs. Informal Observation

The difference between a structured audit and informal observation comes down to three points: the audit is systematic (it covers all 8 pillars, not just the most visible ones), it is quantified (every finding rests on a metric), and it is documented (it produces a written deliverable). A CRO who spends 30 days "getting a feel for things" without a grid or a deliverable has not audited, they have wandered.

The 8 Pillars of a Complete Revenue Audit

A revenue audit covers the entire value chain, from first point of contact to renewal. Each pillar is assessed across 3 dimensions: documented processes, tools in place, and measured results. Our diagnostics use between 35 and 60 questions per pillar, grouped into categories weighted according to the business weight of each dimension.

Branding and Positioning

The CRO is not responsible for the brand, but is directly affected by its quality. A blurry positioning lengthens sales cycles, increases ghosting rates in prospecting, and forces reps to sell on price rather than value.

The audit checks message clarity, consistency between the website and the sales pitch, awareness within the target segment, and the team's ability to articulate differentiation in under 30 seconds. Questions to ask: do the top 5 reps describe the offer the same way? Is the pitch deck more than 6 months old? Can inbound prospects state what the company does before the first meeting?

In our diagnostics, branding is the pillar most often underrated by technical CROs, and yet it weighs directly on win rate: a blurry brand lengthens cycles, tips deals toward better-positioned competitors with an equivalent offer, and forces reps to sell on price.

Acquisition and Demand Generation

The audit maps every pipeline source: inbound, outbound, partners, events, paid, organic. For each source, it measures volume, conversion rate to qualified opportunity, cost per lead, and average cycle length.

The goal is not to judge marketing strategy but to understand where the pipeline comes from and which channels are structurally fragile or non-repeatable. A pipeline that depends on a single channel for more than 60% (often organic inbound or the founder's network) is a structural risk the audit must call out explicitly. Critical questions: what percentage of pipeline comes from sources the company controls? What is the 12-month trend for each channel? Is there a formalized SLA between marketing and sales?

BDR and Prospecting

The audit assesses the effectiveness of the prospecting engine: connect rate, qualified-meeting conversion rate, productivity per SDR, quality of the handover to sales, and consistency of outbound sequences. A qualified-meeting-to-contact-attempt ratio below 2% signals a targeting or messaging problem, not a volume problem.

Recurring patterns in our diagnostics: SDRs who spend more than 40% of their time on non-prospecting tasks (CRM admin, manual qualification, reporting), outbound sequences of more than 8 touches with no A/B testing, and an informal SDR-to-AE handover that loses context at every pass. Each pattern has a measurable cost in lost pipeline.

Sales and Closing

The core of the audit for a CRO. It covers the sales process (does it exist, is it followed, is it suited to the cycle), pipeline coverage, stage-by-stage conversion rate, sales cycle length by segment, win rate against identified competitors, average deal size, and performance dispersion across reps.

A gap of more than 3x between the top and bottom quartile of AEs signals failing coaching. Questions worth digging into: does the sales process in the CRM reflect the real process or a theoretical ideal? Are stage-to-stage exit criteria factual or self-reported? Is the forecast based on real probabilities or on historical averages that are never recalibrated?

In our diagnostics, Sales is the pillar with the widest gap between top and bottom performers: most sales engines rest on a minority of reps, and this imbalance stays invisible until it is quantified against real quota attainment. Once this finding is put in black and white, it changes the nature of the CRO's decisions.

CRM and Data Quality

A CRM is either a steering tool or a data graveyard, rarely something in between. The audit measures the completion rate of critical fields, the freshness of contact data, the consistency of pipeline stages with the real sales process, and the adoption rate among reps.

In most of the CRMs we audit, the completion rate of critical fields is too low to make a forecast reliable, which leaves any projection structurally fragile. The hidden cost of a poorly maintained CRM does not show up in the P&L, but it is paid for in decisions made on false data. Immediate warning signs: opportunities marked "in progress" with no activity in 90 days, contacts with no valid email, and custom fields created but never filled in.

RevOps and Steering

The audit assesses the existence and reliability of revenue reporting, forecast quality, data governance, the tech stack architecture, and the ability of the RevOps team (if one exists) to produce actionable insights.

A CRO who arrives with no RevOps team should treat that as a critical finding, not as a normal situation. In our diagnostics, companies with no dedicated RevOps function score notably worse than those that have one, at comparable size and maturity. Questions to ask: who owns data quality? How long does it take to produce the monthly reporting? Is the forecast an exercise in truth or in politics?

Customer Success and Retention

The audit measures trailing 12-month NRR, logo renewal rate, churn by segment, post-onboarding time-to-value, and the existence of an expansion playbook. An NRR below 100% means the revenue engine is leaking from the bottom, and no amount of acquisition will durably offset that structural leak.

Frequent patterns: no formalized customer health score, customer QBRs held only for top accounts, and upsell driven by reps (who lack usage context) rather than by CSMs (who have it). A CRO who ignores the CSM pillar in their audit gives up a growth lever that is often faster and cheaper than acquisition.

Management and Revenue Governance

The audit assesses the rituals in place (pipeline review, 1:1s, QBRs, executive review), the clarity of goals by role, the quality of sales coaching, and the alignment between the leadership team and the revenue function on priorities.

This is the pillar most often neglected and most correlated with the overall score in our diagnostics. Failing revenue governance shows up as meetings with no fixed agenda, decisions made in a small committee with no written record, and a CEO who gets pulled into operational matters because no one gives them the visibility they need. A CRO who does not diagnose management is diagnosing symptoms, not causes.

The 47 Metrics to Quantify by Day 30

A CRO with no numbers after 30 days is a consultant, not an executive. Here is the minimum grid to fill in, organized by pillar. Each metric should be documented with its source, its calculation date, and the corresponding industry benchmark when one exists.

PillarEssential MetricsSource
BrandingTarget awareness score, prospect NPS, pitch recall rate, website vs. pitch message consistencyInternal survey + interviews
AcquisitionLead volume by channel, MQL-to-SQL conversion rate, CAC by channel, 12-month trendCRM + marketing tools
BDRConnect rate, qualified meetings / SDR / month, cost per meeting, non-prospecting timeCRM + sequencing tool
SalesPipeline coverage, win rate, average cycle, ACV, quota attainment by AE, Q1/Q4 dispersionCRM
CRMCritical field completion rate, contact freshness, adoption rate, opportunities with no activity in 90 daysTechnical CRM audit
RevOps6-month forecast accuracy, number of active dashboards, stack costs, reporting production timeCRM + finance
CSM12M NRR, churn by segment, renewal rate, onboarding TTV, customer health scoreCRM + billing
ManagementRitual frequency, existence of a marketing-sales SLA, 1:1 completion rate, decision documentationDirect observation

Prioritizing Metrics by Urgency

Not all metrics carry the same weight. The essential revenue KPIs fall into three priority tiers. The first tier (to quantify in week 1-2) covers pipeline coverage, NRR, forecast accuracy, and quota attainment, because these are the four metrics that show whether the engine is holding up. The second tier (week 2-3) covers stage-by-stage conversion metrics, CAC, and sales cycle. The third tier (week 3-4) rounds out the picture with branding, BDR, and management metrics.

Building the Table Without a Benchmark

A table with no benchmark is a finding with no scale. For metrics where no industry benchmark is available, use the 6 to 12 month internal trend as the reference point. A stable metric is not necessarily good, and a declining metric is not necessarily bad, but the trend gives everyone an objective point of comparison.

Ou en est votre RevOps ?

Evaluez votre maturite sur les 8 piliers en 2 minutes. Score instantane, gratuit.

Faire le quiz gratuit →

The Maturity Grid: Turning Observations Into Findings

The classic mistake in a CRO audit is producing a list of problems with no hierarchy. A CEO who receives 40 findings of equal weight acts on none of them. The maturity grid solves this problem by ranking each observation on a 3-level scale.

LevelDefinitionScoreImplication
EstablishedThe process is documented, tooled, and produces measurable results70-100Maintain and optimize
Needs consolidationThe process exists but lacks rigor, tooling, or measurement50-69Structure within 90 days
Needs improvementThe process is absent, informal, or produces results below benchmark0-49Address as a priority

From Score to Actionable Finding

The overall score is not an end in itself. It is a prioritization tool: a pillar at 30/100 with a heavy weight on revenue (sales, acquisition) takes precedence over a pillar at 40/100 with a lighter weight (branding). In our diagnostics, the overall score of B2B scale-ups is dragged down by the weakest pillars, acquisition foremost, with sharp gaps from one pillar to the next. The Sales and Management pillars are consistently the most discriminating: a high score on these two pillars partially offsets weaknesses elsewhere.

Weighting by Business Impact

The maturity grid incorporates a weighting system that reflects the business impact of each pillar. A score of 40/100 in Sales (weight 8/10) is more critical than a score of 40/100 in Branding (weight 5/10). This weighting is not arbitrary: it reflects the business weight of each pillar within the revenue engine, from branding (the lightest weight) to sales and management (the heaviest weights).

The 25 to 40 Interviews: Who to See and in What Order

The revenue audit is first and foremost an exercise in listening. CRM data gives you the what, interviews give you the why. A CRO who only interviews their direct reports gets a filtered view. A CRO who also interviews individual contributors, support functions, and customers gets the truth.

IntervieweeNumberDurationWhat you're looking for
CEO190 minVision, frustrations, board constraints
CFO160 minUnit economics, budget, forecast vs. actual
Head of Marketing160 minPipeline sources, sales-marketing alignment
Sales managers2-360 minReal vs. theoretical process, coaching
Top 20% AEs3-545 minWhat actually works
Bottom 20% AEs2-345 minDay-to-day blockers
SDR/BDR3-545 minTarget quality, sequences, handover
CSM2-345 minChurn patterns, onboarding, expansion
RevOps1-260 minStack, data quality, forecast process
Product1-245 minRoadmap, field feedback, win/loss
Customers (top accounts)3-530 minExternal perception, pain points, reasons to stay

The Order of Interviews

Order matters. Start with the CEO and CFO to frame the constraints and understand the board's expectations. Move on to managers to understand the formal organization. Finish with individual contributors and customers to cross-check against the managerial version. Contradictions between hierarchical levels are the audit's most valuable findings: they reveal the dysfunctions no one puts into words.

The Interview Framework

Every interview follows the same structure: understand the role and scope, identify the top 3 obstacles to performance, ask "if you could change just one thing, what would it be," and note the contradictions between what different interviewees say. The last question of every interview should always be: "Is there a topic I haven't covered that you consider critical?" This open-ended question regularly produces the audit's most valuable insights.

Documenting Verbatims

Verbatims should be documented immediately after each interview, not at the end of the phase. A verbatim written down 3 days after the interview is a reconstructed memory, not reliable data. Recommended format: date, interviewee, 3 to 5 verbatim quotes, and 1 summary finding per interview.

The Deliverable Format: 10 to 15 Pages for the CEO

The written diagnostic is the CRO's first tangible deliverable. It is handed to the CEO between day 30 and day 35, and presented face to face, never sent by email without a discussion.

SectionContentLength
Executive summaryOverall score, 3 key messages (finding, opportunity, urgency)1-2 pages
Quantified current stateScore by pillar, key metrics, benchmark vs. market3-4 pages
Major findings5 to 7 findings ranked by severity, with evidence3-4 pages
Action priorities3 to 5 recommended initiatives for the following 90 days2-3 pages
AppendicesMetric details, interview list, sources1-2 pages

The Document vs. the Presentation

The document is not a PowerPoint presentation. It is a written, well-argued document, with complete sentences. A CEO who receives bullet points with no context cannot make a decision. A document structured in paragraphs forces the CRO to think their findings through in depth and allows the CEO to challenge them. CROs who produce a 40-slide deck dilute their message: the format constrains the thinking.

The Format of the Findings

Every finding follows a standard format: factual observation, data that supports it, estimated business impact, and connection to other findings. Isolated findings carry less weight than findings that reveal cross-cutting patterns. A finding that connects a weak CRM to forecast inaccuracy and sales manager frustration tells a coherent story the CEO can understand and prioritize.

The 5 Mistakes That Invalidate a Revenue Audit

Auditing Only Your Direct Scope

A CRO who audits only sales and pipeline misses the root causes. An underfed pipeline is often an acquisition problem. High churn is often an onboarding or forced-selling problem. An unreliable forecast is often a CRM governance problem. The audit must cover all 8 pillars, even those not under the CRO's direct responsibility.

Confusing Audit With Judgment

The audit is not a courtroom. A CRO who hands out bad grades to the incumbent team creates resistance and loses access to information. The goal is to understand, not to blame. Every dysfunction has a historical reason. The question is not "why is this done poorly" but "what constraints led to this situation."

Trusting the CRM Without Checking Data Quality

A pipeline showing 3x coverage in a CRM where 40% of opportunities have been dead for 6 months is worthless. The first action of a sales audit is to check the freshness and reliability of the data before calculating anything. In our diagnostics, the "real" pipeline (active opportunities with recent activity) is regularly well below the pipeline displayed in the CRM, once dead opportunities are stripped out. A CRO who bases their first findings on unclean data loses credibility at the very first readout meeting.

Producing an Audit With No Actionable Recommendations

A document that lists problems without proposing solutions is not a diagnostic, it is a complaint. Every finding must come with a recommendation that includes an estimated effort level (quick/medium/long), an expected impact (high/medium/low), and a suggested owner. The CEO does not just want to know what is wrong, they want to know what to do and in what order.

Keeping the Audit to Yourself

A diagnostic that stays in the CRO's drawer has no value. The audit should be shared with the CEO first, then with the leadership team in an adapted version, then with the relevant managers for their scope. Transparency about the diagnostic builds the CRO's credibility and creates the alignment needed to execute the recommendations. An unshared audit is an audit that never happened.

Internal Audit vs. External Audit: When to Bring in a Third Party

A CRO can run their own audit. It is even recommended during the first 30 days, because the audit process is also a process of discovery and relationship building. But certain situations warrant a complementary external audit.

DimensionInternal Audit (CRO)External Audit (Consultant/Firm)
ObjectivityLimited by role biasNeutral, no internal politics
BenchmarkBased on personal experienceBased on comparative data
RelationshipsBuilds trust with the teamNo long-term relationship
Technical depthStrong in their area of expertiseCovers the 8 pillars evenly
CostCRO time (already budgeted)€15K to €30K depending on scope
Leadership team credibilityPerceived as partisanPerceived as objective
ReproducibilityHard to reproduce 12 months laterStandardized methodology, tracks progress

Combining Both Approaches

In our diagnostics, we observe that CROs who combine a personal audit (interviews, field immersion) with a structured external diagnostic produce more robust recommendations and win buy-in from the CEO and board more easily. The internal audit brings on-the-ground understanding, the external audit brings the benchmark and the neutrality.

When an External Audit Is Essential

Three situations make an external audit nearly indispensable: when the CRO is the first person to hold the role (no predecessor to pass on context), when the board demands an independent diagnostic before approving a transformation budget, and when the company is planning a fundraise or an M&A deal within the next 12 months. In all three cases, a diagnostic signed by a third party carries political weight that an internal audit cannot match.

Revenue Audit vs. Financial Audit: Two Complementary Exercises

A revenue audit is not a financial audit. This confusion is common, especially when the CEO has a finance background.

DimensionFinancial AuditRevenue Audit
ObjectAccounts, cash flow, complianceSales engine, processes, capacity
Time framePast (last 12 months)Past + predictive (future capacity)
MetricsP&L, working capital, marginPipeline, conversion, NRR, CAC payback
Who does itCFO, external firmCRO, revenue consultant
DeliverableFinancial statements, compliance reportRevenue diagnostic, action roadmap
FrequencyAnnual or quarterlyAt every role transition + annually

The two audits complement each other. The financial audit says how much the company earns. The revenue audit says why it earns that amount and not twice as much, and what would need to change to get there.

Template: Week-by-Week Audit Grid

Here is a typical calendar for a 30-day revenue audit, ready to use as is by a CRO starting a new role. Each week has a clear objective and an interim deliverable.

WeekMain FocusInterviewsInterim Deliverable
W1Framing: CEO, CFO, board constraints, CRM access4-6 (CEO, CFO, leadership team)Framing brief (1 page): expectations, constraints, timeline
W2Managers and process: sales organization, rituals, pipeline8-10 (managers, RevOps)Org mapping + first CRM data extract
W3Field: AE, SDR, CSM, Product, customers10-15 (individual contributors + customers)Draft maturity grid (score by pillar)
W4Analysis and writing: cross-referencing data + interviews, findings3-5 (targeted follow-ups, checks)Complete diagnostic (10-15 pages)

Validation Checkpoints

At the end of each week, the CRO should be able to answer one key question. Week 1: "What are the 3 CEO expectations I need to address first?" Week 2: "What is the actual structure of the revenue engine versus the theoretical structure?" Week 3: "What are the 3 findings no one told me explicitly but the data confirms?" Week 4: "What is the optimal sequence of actions for the following 70 days?"

From Audit to Quick Wins: The Day 30 to Day 60 Transition

The audit is not an end point. It is the foundation for the next phase: identifying and executing quick wins. The transition between the two phases follows a simple logic.

Ranking Findings by Severity and Effort

Critical findings that require low effort become quick-win candidates. A critical finding that requires high effort becomes a structural initiative to be scoped in phase 3. The impact/effort matrix is the basic tool for this prioritization.

Validating With the CEO

The 3 to 5 selected quick wins must be validated by the CEO. A quick win not validated by the CEO is a political risk, not a win. The CEO needs to understand why each quick win was selected, what impact is expected, and how the result will be measured.

Assigning and Communicating

Every quick win needs a sponsor within the team and a success metric measurable in under 30 days. A quick win that is invisible to the organization has no effect on the CRO's credibility.

Classic Quick Wins

The classic quick wins that come out of a revenue audit are almost always the same: cleaning up ghost pipeline (immediate impact on forecast reliability), setting up a weekly pipeline review (impact on visibility), formalizing a marketing-sales SLA (impact on alignment), structuring CEO reporting (impact on trust), and formalized qualification of inbound leads (impact on conversion rate).

Further Resources

Sources Cited

  • Proprietary ACROSS INSIGHT data from our Revenue Health Score diagnostics conducted on B2B scale-ups between €10M and €100M ARR
  • Michael Watkins, The First 90 Days: Proven Strategies for Getting Up to Speed Faster and Smarter (Harvard Business Review Press, 2013)

Article written by Charles-Alexandre Peretz, co-founder of ACROSS INSIGHT, based on the analysis of our Revenue Health Score diagnostics conducted with B2B companies in hypergrowth. Last updated: April 16, 2026.

Questions fréquentes

Between 25 and 30 calendar days for a CRO starting a new role. The first 15 to 20 days are devoted to interviews (3 to 4 per day), the remaining 5 to 10 days to data analysis and writing the diagnostic. A CRO who tries to compress the audit into 2 weeks sacrifices either the number of interviews or the quality of the analysis. Both options produce an incomplete diagnostic.
No. A spreadsheet structured by pillar is enough for the first 30 days. What matters is the rigor of the evaluation grid, not the tool. That said, for a recurring audit or a multi-company benchmark, a dedicated tool such as a Revenue Health Score diagnostic brings standardization and comparability. The tool does not replace the method, it accelerates it.
This is the most common situation. The answer is to share interim findings as early as week 2: not a full diagnostic, but 2 to 3 factual observations that show the audit is progressing and producing value. A well-formulated interim finding buys time without compromising the quality of the final diagnostic. Example: "The displayed pipeline is €4.2M, but after cleaning out opportunities with no activity in the last 90 days, the real pipeline is €2.6M." This kind of factual finding reassures the CEO that the exercise is worth it.
Not in depth, but enough to identify dependencies. A CRO who discovers on day 60 that the product has a critical bug affecting churn missed something in their audit. One interview with the Head of Product and one with the CTO are enough to map the product risks that impact revenue. A revenue audit is not a product audit, but it needs to view the product through the lens of its commercial impact.
Resistance almost always comes from fear of being judged, not from a refusal to cooperate. The key is to frame the audit as an exercise in understanding ("I need to understand how things work before proposing anything") rather than as an evaluation ("I'm going to grade what's working and what isn't"). A CRO who asks open questions and visibly takes notes during interviews sends the right signal.
Yes, and it is even recommended once a year. A CRO who audits their own engine after 12 months in the role identifies the drift that habit makes invisible. The difficulty, obviously, is bias: people audit what they did not build more harshly than what they built themselves. This is exactly the case where a complementary external audit makes the most sense.
ROI is measured in decision quality, not in direct euros. A CRO who makes 5 strategic decisions based on a quantified audit has a better chance of getting it right than a CRO who makes the same decisions based on impressions. In our diagnostics, companies that implement at least 3 of the diagnostic's 5 priority recommendations see, on average, an 8 to 12 point improvement in their overall score within 6 months.
Yes, but face-to-face interviews remain superior for two reasons: body language provides information that Zoom does not capture, and informal conversations (before/after the interview, by the coffee machine) often produce insights that the structured interview does not reveal. If remote is unavoidable, plan for 20% more interviews to offset the loss of non-verbal information.

Move from intuition to certainty.

A complete diagnostic in 2 weeks. A 90-day action plan. Measurable results.

Schedule a call