The 90-Day Transformation Playbook

01Why 90 Days? The Science of Transformation Windows

02Pre-Engagement: The Readiness Assessment (Days –14 to 0)

• Founder Alignment Check — If co-founders disagree on the company's direction, no operating system will help. We conduct separate 60-minute interviews with each founder, asking identical questions about vision, priorities, and non-negotiables. If there's more than 30% divergence on strategic priorities, we facilitate an alignment session before proceeding. This session alone has saved three companies from post-transformation collapse.
• Financial Runway Verification — Transformation requires attention, and attention requires runway. If a company has less than 6 months of runway, the transformation competes with fundraising for founder time — and fundraising always wins. We require a minimum of 9 months of runway to begin, or a signed term sheet for imminent funding.
• Team Stability Assessment — If more than 20% of the team has turned over in the last 90 days, or if a critical leadership hire is imminent, we delay. Installing systems on a team that's about to change is waste. We need the people who will own the systems to be present during installation.
• Data Access & Infrastructure — We need access to financial data (P&L, cash flow, unit economics), product analytics (usage data, cohort analysis), sales data (CRM, pipeline), and HR data (org chart, compensation, tenure). If this data doesn't exist or can't be assembled within two weeks, the diagnostic phase will be spent gathering data instead of analysing it — cutting its effectiveness by half.
• Executive Sponsorship Commitment — The CEO or primary founder must commit to 8–10 hours per week during Phase 1 and Phase 2, dropping to 4–5 hours during Phase 3 and 4. This is non-negotiable. We've never seen a successful transformation without active executive participation. Delegating the transformation to a COO or Chief of Staff without CEO involvement produces systems that the CEO later overrides.

03Phase 1: The Diagnostic (Days 1–15)

04Diagnostic Area 1: Revenue Architecture Audit

• Lead Source Analysis — Where are your last 100 customers actually coming from? Not what your attribution model says — what's really happening. We interview recent customers to understand their actual decision journey. In 70% of our engagements, the founder's belief about their primary lead source is wrong. The real source is usually some combination of founder network, word-of-mouth, and one channel that works but hasn't been intentionally invested in.
• Pipeline Velocity Mapping — We measure the time between every stage transition in your pipeline: lead to qualified, qualified to demo, demo to proposal, proposal to close, close to onboard. For each transition, we identify: the median time, the variance, the conversion rate, and the primary reasons deals stall or die. This map reveals where your revenue engine is leaking.
• Win/Loss Analysis — We review your last 20 closed-won and 20 closed-lost deals. For each, we document: initial source, qualification criteria met, buying committee involved, objections raised, competitive alternatives considered, and the decisive factor. Patterns emerge quickly — and they're almost never what the sales team reports in pipeline reviews.
• Pricing & Packaging Examination — Is your pricing aligned with the value your customers receive? We analyse your pricing against three benchmarks: cost-to-serve (are you profitable per customer?), willingness-to-pay (are you leaving money on the table?), and competitive positioning (are you priced where your value proposition says you should be?). In 40% of engagements, we find a pricing adjustment that increases revenue 15–25% without affecting close rates.
• Revenue Concentration Risk — What percentage of your revenue comes from your top 3 customers? Top 10? If any single customer represents more than 15% of revenue, that's a strategic risk that needs addressing before you scale. We map concentration by customer, by segment, by channel, and by product line.
• Renewal & Expansion Analysis — For subscription businesses: what's your gross renewal rate, net revenue retention, and expansion rate by cohort? We decompose each metric by customer segment, onboarding quality, usage depth, and support interaction volume. This analysis often reveals that retention is not a customer success problem — it's an onboarding problem that manifests 6 months later.

05Diagnostic Area 2: Organisational Clarity Assessment

• Decision Rights Mapping — For every major recurring decision (pricing changes, feature prioritisation, hiring, budget allocation, customer escalations), we map: who actually makes the decision, who thinks they make the decision, who has veto power, and how long it takes. The gap between 'who should decide' and 'who actually decides' is the single biggest predictor of organisational dysfunction.
• Invisible Bottleneck Identification — Every startup has 3–5 people whose plates are so full they've become single points of failure. They're usually not in leadership — they're senior ICs or team leads who've accumulated responsibilities because they're reliable. We identify them by mapping task dependencies and communication patterns. Resolving these bottlenecks typically frees 20–30% of organisational capacity.
• Information Flow Analysis — How does critical information move through the company? We trace five types of information: customer feedback, product decisions, financial updates, competitive intelligence, and strategic priorities. For each, we document: where it originates, how it's transmitted, who receives it, and how long the transmission takes. Most startups have information latency of 5–10 business days for critical updates — meaning the team is always operating on stale data.
• Meeting Audit — We catalogue every recurring meeting: purpose, attendees, duration, frequency, and output. The median startup at this stage spends 35% of its collective time in meetings. Of that, roughly 40% is low-value: status updates that could be async, decision meetings where no decisions are made, or alignment meetings where attendees don't need to be aligned. This audit typically identifies 10–15 hours per week of recoverable time across the team.
• Role Clarity Index — For each role, we assess: Does the person know their top 3 priorities? Does their manager agree? Does their output match? We score role clarity on a 1–5 scale across the team. Companies below 3.0 average are in 'organisational fog' — people are busy but not productive because they're working on the wrong things.

06Diagnostic Area 3: Financial Health & Unit Economics

• True Customer Acquisition Cost (CAC) — Not just marketing spend ÷ new customers. True CAC includes: marketing spend, sales salaries (allocated by time spent on new vs. existing), founder time (valued at their opportunity cost), tooling costs for sales and marketing, and onboarding costs for new customers. When we include founder time, CAC is typically 2–3× higher than the reported figure.
• Lifetime Value (LTV) by Cohort — LTV calculated not as a blended average, but decomposed by acquisition cohort, customer segment, plan tier, and acquisition channel. This decomposition almost always reveals that 20–30% of customers have negative unit economics — they cost more to acquire and serve than they'll ever pay. The blended average masks this because the best customers subsidise the worst.
• Gross Margin by Product Line — Revenue minus cost of goods sold (hosting, third-party services, support time, implementation effort) for each product or service line. We allocate support and implementation costs based on actual time tracking, not estimates. Most companies discover at least one product line with margins 15–20 points lower than they assumed.
• Burn Rate Scenario Analysis — Three scenarios: current trajectory, 20% growth acceleration, and 20% growth deceleration. For each, we model runway, cash position at key milestones, and the fundraising timeline implications. This isn't financial modelling for the sake of it — it's building the financial guardrails that inform every operational decision in the transformation.
• Working Capital & Cash Conversion — How long does it take to convert a signed contract into cash in the bank? We map the complete cash conversion cycle: sales cycle + contract execution + onboarding + first invoice + payment terms + collection time. For B2B companies, this cycle is typically 90–180 days — meaning 3–6 months of revenue is always 'in transit.' Understanding this cycle is essential for cash flow planning.
• Departmental Cost Allocation — Where is the money actually going? We allocate all costs to four categories: Revenue Generation (sales, marketing), Revenue Delivery (engineering, product, customer success), Revenue Support (operations, finance, HR), and Overhead (office, insurance, legal). The typical healthy ratio is 40/35/15/10. Significant deviations indicate structural misallocation.

07Diagnostic Area 4: Process & Tooling Inventory

• Tool Stack Audit — Every tool in the company's tech stack, documented with: purpose, primary users, monthly cost, integration status (connected to other tools vs. standalone), data quality (is the data in this tool reliable and current?), and utilisation rate (percentage of licensed seats actively used). We typically identify 20–30% cost savings from tool consolidation alone.
• Process Documentation Assessment — What processes exist in documented form vs. tribal knowledge? We categorise every critical process as: Documented & Current, Documented & Outdated, Undocumented but Consistent, or Undocumented & Inconsistent. The last category is where operational risk lives — these are the processes that break when the person who 'just knows how to do it' goes on holiday or leaves the company.
• Data Flow Mapping — How does data move between systems? We trace five critical data flows: lead-to-customer data, financial transaction data, product usage data, customer support data, and HR/people data. For each flow, we identify: manual handoff points (where a human copies data from one system to another), data quality gaps (where information is lost or corrupted in transit), and automation opportunities.
• Automation Readiness Assessment — Which manual processes could be automated with existing tools, and which require new tooling? We prioritise automation opportunities by: time saved per week, error reduction potential, and implementation complexity. The top 3–5 automation opportunities typically free 15–25 hours per week of team time.
• Security & Compliance Check — Who has access to what? We audit access controls, data handling practices, and compliance readiness. This isn't our primary focus, but it's part of the operational baseline — and we've caught critical security gaps (admin credentials shared via Slack, customer data in unencrypted spreadsheets) in 30% of engagements.

08Diagnostic Area 5: Culture & Velocity Diagnostic

• Decision Latency Measurement — We track 10 representative decisions from the previous 30 days: when was the problem identified, when was information gathered, when were options presented, when was a decision made, and when was it communicated. The median decision latency tells us how fast the company can act. Best-in-class startups at this stage make most operational decisions in 24–48 hours. The median in our dataset is 5–7 business days.
• Feedback Loop Frequency — How often does customer feedback reach the product team? How often does sales feedback influence marketing? How often does engineering performance data inform hiring? We map the frequency and quality of every cross-functional feedback loop. Companies with weekly feedback loops iterate 3× faster than those with monthly loops.
• Psychological Safety Assessment — Can team members raise problems without fear of blame? We measure this through structured interviews and anonymous surveys, looking for specific indicators: are post-mortems blame-free? Do junior team members speak up in meetings? Are failed experiments discussed openly? Low psychological safety is the silent killer of startup velocity — people who fear blame hide problems until they're crises.
• Accountability Culture — The opposite end from psychological safety, and equally important: does the team hold each other accountable for commitments? We look for: are deadlines treated as real or aspirational? Do people follow up on action items from meetings? Is there a clear consequence for consistent under-delivery? The healthiest cultures have both high safety (it's OK to fail) and high accountability (it's not OK to not try).
• Energy & Sustainability — Is the team's current pace sustainable? We assess through burnout indicators: average working hours, weekend work frequency, vacation days used, and self-reported energy levels. A team running at 110% intensity during a transformation will crash. We need to know the baseline so we can calibrate the transformation's intensity appropriately.

09The Diagnostic Scorecard: Synthesis & Prioritisation

10Phase 2: The Architecture (Days 16–40)

11System 1: The Operating Rhythm

• Daily Standup (15 min, team-level) — Not a status update. Each person answers one question: 'What is the one thing I will complete today that moves my primary metric?' This creates focus and public commitment. If a standup takes more than 15 minutes, the team is too large (split it) or the format is wrong (cut status updates; they belong in async tools).
• Weekly Operating Review (60 min, leadership) — The most important meeting in the company. Structure: 10 min on Health Metrics (any alerts?), 20 min on Lever Metrics (what moved, why, what action?), 15 min on cross-functional blockers (anything one team needs from another), 15 min on decisions (items that need resolution this week). Every decision is documented with: decision made, owner, deadline, and communication plan.
• Weekly Team Retrospective (30 min, team-level) — What worked this week? What didn't? What will we change? The retrospective is the primary mechanism for continuous improvement at the team level. Without it, the same problems recur weekly and the team develops learned helplessness. The retrospective must be psychologically safe — no blame, no justification, just observation and adjustment.
• Monthly Business Review (90 min, leadership + board observers) — Outcome Metrics deep-dive: MRR decomposition, unit economics update, team health dashboard, and strategic priority assessment. The first 30 minutes are metrics; the next 30 are root-cause analysis of the 2–3 biggest changes; the final 30 are strategic decisions for the next 30 days.
• Quarterly Strategic Planning (Half-day, leadership) — Step back from execution. Reassess: Are we pursuing the right market? The right customers? The right product strategy? Quarterly planning produces 3–5 company-level objectives for the next 90 days, each with an owner, key results, and resource allocation. We use a modified OKR framework that emphasises 'bets' (high-uncertainty, high-upside initiatives) alongside 'commitments' (predictable, essential work).
• Annual Strategy Offsite (2 days, leadership + key stakeholders) — Not a retreat. A structured strategy session covering: market landscape reassessment, competitive positioning update, 12-month financial model, organisational design for the next stage, and 3–5 'big bets' for the year. We provide facilitation guides and pre-work templates for each session.

12System 2: The KPI Architecture

13System 3: The Revenue Engine Blueprint

• Stage 1: Awareness & Attraction — How do prospects discover you? We map every active channel (content, paid, referral, outbound, partnerships), the audience each reaches, the messaging used, and the mechanism that moves a prospect from 'aware' to 'interested.' For each channel, we define: investment level, expected volume, time to impact, and the leading metrics we'll monitor.
• Stage 2: Qualification & Conversion — How do interested prospects become qualified opportunities? We design the qualification criteria (ICP fit + buying intent signals), the scoring model, and the handoff protocol from marketing to sales. We define the exact moment a Marketing Qualified Lead becomes a Sales Qualified Lead, the SLA for sales follow-up, and the escalation path if SLAs are breached.
• Stage 3: Sales & Close — How do qualified opportunities become customers? We map the sales stages, define exit criteria for each, design the proposal/negotiation framework, and establish forecasting methodology. For founder-led sales companies, we design the transition plan to a dedicated sales function — including the role profile, interview process, and first-90-days plan for the first sales hire.
• Stage 4: Onboarding & Activation — How do new customers reach their first value milestone? We design the onboarding sequence: day-by-day touchpoints for the first 14 days, the definition of 'activated' (the specific action that correlates with long-term retention), and the intervention protocol if activation stalls. Companies that improve activation rate by 10% typically see a 25–30% improvement in 12-month retention.
• Stage 5: Retention, Expansion & Advocacy — How do you keep customers, grow their spend, and turn them into referral sources? We design the health scoring system, expansion trigger map, QBR (Quarterly Business Review) framework, and referral programme. This stage is where the revenue engine becomes self-reinforcing — each successful customer reduces the cost of acquiring the next one.

14System 4: The Talent Operating System

• Role Architecture — Every role has a Role Card: primary output (not activities), 3–5 key metrics they influence, decision rights (what they can decide without approval), and growth path (what mastery looks like at this role, and what the next role is). Role Cards replace traditional job descriptions and are updated quarterly. They're the foundation of performance conversations, hiring criteria, and compensation decisions.
• Hiring Engine — A repeatable, data-driven hiring process: sourcing strategy by role type, structured interview protocols (identical questions for all candidates in the same role), evaluation scorecards that force interviewers to rate specific dimensions rather than give holistic 'gut' assessments, and a calibration meeting format that reduces individual bias. We also design the candidate experience — because how you hire signals how you operate.
• Performance & Development System — A lightweight system that replaces the annual review with continuous feedback. Monthly 1:1s between every manager and report, using a structured format: What's your proudest output this month? What's your biggest learning? What do you need from me? Quarterly development conversations focused on skill gaps relative to the Role Card. Semi-annual compensation reviews tied to output and market benchmarks.
• Compensation Framework — A transparent compensation structure with defined bands for each role level, clear criteria for advancement between bands, and an equity allocation framework that's consistent across the company. We design the framework to be competitive enough to attract top talent and fair enough to retain it — while being sustainable for a startup's cash constraints.
• Onboarding System — A structured 90-day onboarding programme (detailed in the Hiring Decision Matrix resource): Week 1 immersion, Weeks 2–4 guided contribution, Weeks 5–8 independent ownership, Weeks 9–12 full integration. Each phase has specific milestones, check-in protocols, and success criteria. This system reduces time-to-productivity by 40% and early attrition by 50%.

15Phase 3: The Build (Days 41–70)

• Tool Configuration & Integration — We set up or reconfigure your CRM, project management, analytics, and communication tools to match the new operating system. This includes data migration, automation setup (we typically install 10–20 automated workflows using tools like Zapier, Make, or native integrations), and integration testing between systems. The goal: zero manual data entry for any metric that appears in the KPI architecture.
• Process Installation & Coached Cycles — Every new process gets run at least twice with our team present. The first cycle is co-facilitated (we run it, your team participates). The second cycle is observed (your team runs it, we watch and give feedback). We document friction points after each cycle and adjust the process before the third cycle, which the team runs independently.
• Team Training & Enablement — Role-specific training sessions for every new process. Not generic workshops — contextualised sessions using your actual data, your actual customers, your actual challenges. Each session includes: the 'why' (what problem this process solves), the 'how' (step-by-step walkthrough), the 'what if' (common edge cases and how to handle them), and the 'who' (escalation paths when the process doesn't cover a situation).
• Dashboard & Reporting Build — We build the dashboards and reports that make the KPI architecture visible. Three dashboards: the Daily Pulse (Tier 1 Health Metrics, automated, always-on), the Weekly Review Board (Tier 2 Lever Metrics with trend lines and owner attribution), and the Monthly Business Review Deck (Tier 3 Outcome Metrics with decomposition and commentary). We use your existing analytics tools where possible and introduce new ones only when the existing stack can't support the requirement.
• Feedback Loop Installation — The meta-system that keeps everything else improving. Weekly team retrospectives, monthly process reviews (is this process still serving its purpose?), and quarterly system audits (are the four systems still aligned with each other and with the company's current needs?). The feedback loops are the most important installation — they're what makes the operating system self-improving rather than static.

16Phase 4: The Stabilisation (Days 71–90)

• Adoption Monitoring Dashboard — A meta-dashboard that tracks process adherence for every installed system. Which meetings are being held on time? Which metrics are being updated? Where are people reverting to old habits? Each gap gets a targeted intervention — not a lecture, but a conversation about what's making the new process harder than the old one.
• Performance Benchmarking — We re-run the Diagnostic Scorecard at Day 80, comparing against the Day 1 baseline. Typical improvements across our last 30 engagements: 40–60% increase in decision speed, 25–35% improvement in forecast accuracy, 50% reduction in 'firefighting' time, 30% decrease in total meeting time, and 20–40% improvement in role clarity scores.
• Edge Case Documentation — Every operating system hits scenarios it wasn't designed for. An unusual customer situation. A team member leaving mid-sprint. A board request that doesn't fit the reporting framework. We document each edge case, design a solution collaboratively with the team, and update the process documentation. By Day 90, the playbooks should cover 95% of situations the team encounters.
• Handoff & Independence Plan — The final deliverable: a comprehensive handoff document that includes the complete operating system documentation (with all edge case updates), process owner contact list, escalation protocols, and a 6-month evolution roadmap. The roadmap specifies: which processes to review and when, which metrics to recalibrate as the company grows, and which systems will need significant upgrades at specific headcount thresholds.
• Post-Engagement Support Structure — We offer optional 30/60/90-day check-ins after the engagement ends. These are 90-minute sessions focused on: what's working, what's drifted, and what needs to evolve. Most clients use 1–2 check-ins; some use all three. The goal is to prevent the common 'decay curve' where new systems slowly revert to old habits without external reinforcement.

17What Changes After 90 Days: Measured Results

18Common Failure Modes (And How We Prevent Them)

• Failure Mode 1: Executive Lip Service — The CEO agrees to the transformation but doesn't participate. They delegate it to a COO or Chief of Staff, attend the kickoff, and then vanish into fundraising or product work. The team reads this as a signal: the transformation isn't a priority. Prevention: The pre-engagement CEO commitment contract, with specific weekly time allocations and explicit consequences for non-participation.
• Failure Mode 2: Trying to Fix Everything — The diagnostic reveals 15 problems. The team tries to address all 15 simultaneously. Nothing gets fixed properly. Prevention: The Priority Matrix forces ranking. We address 5–7 issues in Phase 2, sequence them, and explicitly defer the rest to the 6-month evolution roadmap.
• Failure Mode 3: Over-Engineering for Current Scale — Designing systems appropriate for a 200-person company when you have 25 people. The systems are technically excellent but operationally burdensome. Prevention: The 'minimum viable system' principle — design for current scale plus one growth stage, not for your ultimate ambition.
• Failure Mode 4: Installation Without Buy-In — Processes are installed because the consultant designed them, not because the team believes in them. Adoption is compliant but unenthusiastic. Prevention: Collaborative architecture in Phase 2 — the team co-designs every system, understands the 'why' behind every decision, and has veto power over approaches that don't match their working style.
• Failure Mode 5: Metric Worship — The KPI architecture becomes an end in itself. The team spends more time measuring than doing. Prevention: The 15-metric cap and the weekly 'action ratio' — we track what percentage of metric reviews produce an action. Below 30% means the metrics aren't driving decisions and need recalibration.
• Failure Mode 6: Abandoning the Rhythm — The operating rhythm is maintained for 4–6 weeks, then meetings start getting cancelled, agendas get ignored, and the company reverts to ad-hoc management. Prevention: The stabilisation phase explicitly monitors cadence adherence, and the 6-month roadmap includes 'rhythm audit' checkpoints.
• Failure Mode 7: Single Point of Failure — The transformation is owned by one person (usually the COO or the engagement lead). When that person is unavailable, the systems stall. Prevention: Every system has a primary owner and a documented backup. The handoff document includes 'bus factor' analysis for every process.

19Appendix A: Templates & Tools Included

20Appendix B: Case Snapshots

21A Final Note on Intellectual Honesty