Designing a readiness assessment framework that maps where customers stand on the path to intelligent service delivery — informing product strategy, AI roadmap priorities, and the long-term vision for TOPdesk's platform.
My role: I designed the framework and the scoring model.
The Intelligent Front Door (IFD) is a strategic concept describing the shift from fragmented, channel-by-channel service delivery toward a single intelligent entry point that understands what users need and routes them to the right outcome with the least friction. I designed a comprehensive readiness framework that assesses how close each customer organisation is to achieving this vision.
The primary goal is to inform product strategy and the long-term AI roadmap — understanding which capabilities the customer base has today, where the gaps are, and what the platform needs to build (and in what order) to make intelligent service delivery a reality.
The framework measures six observable capabilities and assigns each customer an overall maturity stage using a weakest-link rule — the lowest-scoring capability constrains the entire front door. This approach reveals where organisations are truly blocked, not where they think they are, and helps prioritise product investment and roadmap sequencing.
The project synthesises findings from Gartner, Ivanti, HDI, SDI, and Forrester into a TOPdesk-specific scoring system that contextualises customer data against industry benchmarks.
The ITSM market is undergoing a fundamental shift. AI-enabled service delivery is moving from aspirational to essential, but most organisations are unprepared. Research reveals a critical insight: readiness — not product selection — determines outcomes.
Gartner projects $2B in wasted spend from organisations buying AI capabilities they are not ready to use. Without readiness assessment, investments fail. By 2027, 50% of service desk AI projects will be abandoned.
An evidence-based framework that tells organisations exactly what capabilities they need to build — and in what order — before investing in AI-enabled service delivery. Preventing overspend while accelerating readiness.
Each capability measures a distinct, observable aspect of front-door readiness. Together they form a complete picture of an organisation's ability to deliver intelligent service experiences.
How many ways can users reach you, and are they connected? Measures portal adoption, channel diversity, and intake distribution.
Can the system figure out what users need? Proxied from observable signals — form structure, categorisation patterns, and routing efficiency.
Once intent is understood, how many ways can it get resolved? Measures automation adoption, workflow maturity, and self-service depth.
Is there something behind the door? KB depth, deflection rates, content freshness, and knowledge utilisation patterns.
Does the system know who this user is? Integration depth, asset data richness, caller history utilisation, and relationship context.
How is the front door measured and improved? Feedback loops, measurement practices, and continuous improvement signals.
The framework's core principle: overall maturity = lowest individual capability score. An organisation scoring 4-4-4-2-4-4 is Stage 2, not Stage 3.7. This forces attention to the actual bottleneck rather than celebrating strengths while ignoring constraints. It mirrors how real service experiences work — a brilliant chatbot is useless if the knowledge base behind it is empty.
The framework is grounded in a synthesis of seven industry research sources — Gartner, Ivanti, HDI, SDI, Forrester, ScreenMeet and SmartDev — contextualised against TOPdesk's global customer base. The five below are the ones that directly calibrate the scoring; the remaining two informed the market picture rather than any threshold.
| Source | Key Insight | How It is Used |
|---|---|---|
| Gartner (2024–25) | 50% of service desk AI projects abandoned by 2027; $2B overspend from premature investment | Validates readiness-first approach; calibrates Stage 3–4 thresholds |
| Ivanti DEX 2025 | 36% would choose chatbot for IT (up 5pts/year); 89% report siloed data as blocker | Calibrates Channel Architecture scoring; identifies progression barriers |
| HDI 2024 | Only 11% use KB for >33% of tickets; knowledge remains primary bottleneck | Benchmarks Content & Knowledge thresholds against industry reality |
| SDI 2024 | <12% achieved self-service ROI; most orgs overestimate their maturity | Grounds Stage 3+ expectations; prevents inflated self-assessment |
| Forrester TEI 2025 | Quantified ROI of AI-enabled service delivery; cost-benefit thresholds | Informs what-if simulator parameters; validates investment scenarios |
The framework delivers insights through interactive dashboards that serve different stakeholder needs — from high-level strategic views for leadership to account-level drill-downs for customer-facing teams.
Analysed 7 major industry reports (Gartner, Ivanti, HDI, SDI, Forrester, ScreenMeet, SmartDev) to establish a grounded understanding of where the market stands and where it is heading. Synthesised findings into a coherent picture of readiness drivers and blockers.
Defined 6 measurable capabilities based on what differentiates mature service organisations from immature ones. Each capability maps to specific, observable platform behaviours rather than subjective assessments — ensuring the framework works at scale without surveys.
Discussed scoring thresholds with colleagues who know the accounts to check whether the model reflects reality. Ran sensitivity analysis to test how threshold changes affect stage distributions.
Built cross-cutting analyses: by region, product line, ARR tier, organisation size, and sector. Contextualised every internal metric against relevant industry benchmarks to answer "how do we compare?" not just "where are we?"
Built interactive simulators: "If KB adoption goes from X% to Y%, how many customers advance a stage?" Makes the framework explorable rather than static.
Prepared presentations and summaries for different audiences, translating the technical framework into accessible language.
Shows which capability is the actual bottleneck for the customer base — usually Content & Knowledge, not Channel Architecture — directly informing where to invest platform development effort.
Maps what percentage of customers are ready for specific AI features (chatbots, automated routing, proactive support) — guiding rollout sequencing and go/no-go decisions.
What-if simulators model the effect of platform improvements: "if we improve KB tooling and lift adoption, how many more customers become ready for guided experiences?"
Industry benchmarks provide realistic timelines — grounding the AI vision in where the market actually is, not where marketing says it should be.
Sector analysis shows that regulated industries face fundamentally different barriers — informing whether the roadmap needs segment-specific paths.
Account-level scoring supports targeted conversations about where a customer is and what would help them progress.
Channel mix analysis shows which customer segments are ready for chat-first experiences vs. still needing portal basics.
Shared framework and findings with stakeholders across the business, explaining the methodology and what the data shows.
Worked with the regional branches to get their account knowledge into one shared set of thresholds, so a Stage 3 in one branch means the same as a Stage 3 in another. That rollout is described on the AI Readiness page.
Built dashboards that people can use on their own rather than requesting ad-hoc analysis from me.
Synthesised 7 industry reports to ground the framework in published data rather than internal assumptions alone.
Industry analysis synthesis, maturity model design, measurement methodology, benchmarking.
Python, Pandas, Plotly, Streamlit, sensitivity analysis, what-if simulation, interactive dashboards.
Presenting findings to different audiences, translating technical methodology into plain language.
People initially wanted averages instead of weakest-link. But once they saw how it mirrors real experience (a broken link breaks the chain), it clicked.
"You are at Stage 2" did not prompt much discussion. "You are at Stage 2, and 80% of similar orgs are too — but the top 12% have moved to Stage 3" did. External context helps.
When people could model their own scenarios ("what if we get 60% on SSP?"), they engaged more deeply with the data than with static charts.
Measuring what customers do (not what they say) at scale produces signals without requiring survey participation or response bias.