Synthetic expert review
Synthetic expert review
The quotes and scores on this page are AI-generated, not statements from real customers or named individuals. As part of our feedback and improvement process, we prompt an AI model to adopt the perspective of industry-expert personas (IT leadership, service management, CMDB administration, security, ITIL consulting) and critique our documentation from an outside-in viewpoint. The "reviewers" below are simulated personas. This is a structured design-validation exercise, not a formal audit, certification, endorsement, or real-world deployment validation.
This page summarises structured review feedback generated during development using AI-based reviewer simulations.
Five reviewer perspectives were generated to represent different roles involved in service management and CMDB design, including IT leadership, service management, CMDB administration, security, and ITIL consulting.
Each review was generated independently, using the full documentation set as the only input, with no additional context or prompting beyond a standard evaluation brief.
The purpose of this process was to challenge the structure of the service models, identify gaps or unclear areas, and evaluate how the product would be perceived by different roles. The outputs below reflect these simulated perspectives.
This is not a formal audit, certification, endorsement, or real-world deployment validation. It is a structured design validation process used to refine the product before release.
The reviewer personas
These are AI-generated personas, not real people. Each row describes the profile the model was asked to adopt.
| Persona | Organisation profile | Experience |
|---|---|---|
| IT Director | 2,000-person company | Budget holder, evaluating build-vs-buy |
| IT Service Manager | Mid-size organisation, 40 IT staff | Runs the service desk, owns the tooling roadmap |
| CMDB Administrator | Assets power user | Two years of daily CMDB work, came in sceptical |
| Security and Compliance Lead | InfoSec background | ISO 27001 and SOC 2 audit experience |
| ITIL Consultant | Senior, independent | A dozen CMDB implementations across different organisations |
Each persona received the same brief: read the documentation, evaluate whether this product would be worth adopting, and score it honestly. Scores below are the model's own outputs in persona, not external benchmarks or measured results.
The IT Director persona: "I would install this week"
The IT Director persona evaluated LaunchPad as a proof-of-concept candidate. The question was simple: could this replace the weeks of internal design work that typically precede a CMDB rollout?
IT Director persona: "I would install Basic CMDB this week as a proof of concept with zero financial commitment."
What stood out was the low-risk entry point. Basic CMDB is free, deploys in minutes, and produces a working schema that the team can evaluate immediately. No procurement cycle, no vendor call, no consulting engagement required to see whether the product does what it claims.
The value proposition landed clearly: "LaunchPad replaces the weeks of CMDB schema design work that kills most JSM Assets implementations." Credibility scored 8 out of 10. Value proposition clarity scored 9 out of 10.
Where this persona pushed back: pricing was not visible in the documentation, and there was no obvious path from "I like this" to "here is what it costs." For a budget holder, that is a conversation stopper.
The IT Service Manager persona: "The documentation is a competitive advantage"
This persona evaluated LaunchPad through the lens of someone who would have to champion it internally, train a team on it, and live with the decision.
IT Service Manager persona: "Fix those gaps and this documentation would be a competitive advantage, not just a support resource."
Two things built trust quickly. First, the What LaunchPad does and does not do page. Being upfront about limitations, rather than burying them, signalled that the product was built by practitioners who understand how IT teams actually evaluate tools. Second, the governance playbooks. Having review cadences, ownership patterns, and data quality guidance built into every schema told the reviewer that this was not just a deployment tool with no aftercare.
Clarity scored 9 out of 10. Trustworthiness scored 8 out of 10.
The gaps: this persona wanted a "zero to first schema in 30 minutes" quickstart guide, and flagged that some governance content was heavier than a mid-market team would need on day one.
The CMDB Administrator persona: scepticism lowered
This persona represented the toughest audience: someone who builds and maintains CMDB schemas daily, who has seen tools promise structure and deliver chaos, and who would arrive expecting the usual consultant-grade handwaving.
CMDB Administrator persona: "The documentation reads like it was written by someone who has actually run a CMDB, not someone who read about it in a consultant's slide deck."
What earned credibility was specificity. The schemas ship with real attribute configurations, sensible reference types, and documented rationale for design decisions. The common mistakes page was called out as evidence of genuine operational experience: you do not write about those failure modes unless you have lived through them.
Technical accuracy scored 8 out of 10. Practical usefulness scored 8 out of 10.
Where this persona wanted more: advanced AQL patterns (nested traversals, performance tips for large schemas), automation rule builder walkthroughs with screenshots, and API documentation for integration builders. Power users will extend these schemas, and the documentation needs to support that trajectory.
The Security and Compliance persona: a clear framing for the CISO
This persona assessed LaunchPad through the lens of audit readiness, data classification, and whether the schemas would support compliance frameworks without extensive rework.
Security and Compliance persona: "LaunchPad gives you 70% of the data model for 10% of the cost and implementation time."
The Cybersecurity schema and the compliance-related attributes across other schemas were evaluated against ISO 27001 and SOC 2 requirements. The reviewer concluded that the schemas provide a strong foundation for compliance mapping, though they noted that the documentation itself does not include a vendor security page, data processing details, or explicit Forge security architecture information.
Security coverage scored 7 out of 10. Compliance readiness scored 7 out of 10.
The recommendation was conditional but positive: this persona would present LaunchPad to a CISO with specific framing around what the schemas provide out of the box versus what the organisation would need to layer on top.
The ITIL Consultant persona: "Buy this and hire me for three months instead of six"
This persona brought the broadest frame of reference: a dozen CMDB implementations, each with its own set of design debates, stakeholder negotiations, and schema rewrites. The evaluation was whether LaunchPad could genuinely compress the early phases of a CMDB programme.
ITIL Consultant persona: "Buy LaunchPad and hire me for three months instead of six. They would get a better outcome in less time for less money. That is not something I say about most products in this space."
The schemas were evaluated against ITIL 4 configuration management practices. The assessment: structurally sound, with sensible defaults that reflect how mature IT organisations actually operate. The maturity model content was praised for being honest about the journey rather than pretending that deploying a schema is the same as achieving configuration management maturity.
The common mistakes page was singled out as "battle-scarred experience," the kind of guidance that only comes from having watched real implementations fail.
ITSM rigour scored 8 out of 10. Practical value scored 9 out of 10. Documentation quality scored 9 out of 10.
Where this persona pushed back: maturity model timelines (how long does Level 1 to Level 2 actually take?), and a migration guide for teams replacing a failed first CMDB attempt. Both are common scenarios that the documentation does not yet address.
Summary of scores
Scores are AI-generated outputs in persona, not external benchmarks.
| Dimension | IT Director | IT Service Manager | CMDB Administrator | Security Lead | ITIL Consultant |
|---|---|---|---|---|---|
| Credibility | 8/10 | 8/10 | 8/10 | 6/10 | 8/10 |
| Clarity | 9/10 | 9/10 | 9/10 | ||
| Practical value | 8/10 | 9/10 | |||
| Technical depth | 7/10 | 7/10 | 8/10 | ||
| Schema quality | 8/10 |
Empty cells indicate dimensions that the persona did not score, not low marks.
What the personas agreed on
Across all five perspectives, three themes came up consistently:
-
The writing is authentic. Every persona commented on the practitioner voice. The documentation reads like it was written by someone who has done this work, not someone describing it from a distance.
-
The "does and does not do" honesty builds trust. Being explicit about limitations is unusual for product documentation. Multiple perspectives cited it as the moment their evaluation shifted from cautious to engaged.
-
The entry point is low-risk. Basic CMDB as a free, zero-commitment starting point removes the procurement friction that stalls most CMDB initiatives before they begin.
What they wanted next
The perspectives also converged on gaps:
- Pricing visibility. Every persona that indicated purchase intent also noted pricing was not visible.
- A quickstart guide. A single walkthrough from install to first linked ticket, under 30 minutes.
- Advanced content for power users. AQL cookbook, automation walkthroughs, API reference.
- Vendor security documentation. Data processing, Forge architecture, audit-relevant details.
- Customer stories. Even one or two informal case studies would close the remaining credibility gap.
This feedback is actively shaping the documentation roadmap. If you are reading this and have deployed a LaunchPad schema in production, we would like to hear your story.
Round 2 reviews (April 2026)
A second round of reviewer simulations ran in April 2026, with rotated personas to surface different angles. Five new perspectives were generated: Head of ITSM and Platform Operations at a 5,000-person SaaS enterprise; Enterprise Architect in a regulated industry (tier-1 bank); Senior SRE and Platform Engineer at a cloud-native scale-up; a newly hired JSM Administrator with a 90-day CMDB mandate; and an independent ITIL 4 and ISO 20000 consultant with more than 15 years of implementations.
Each persona received the same brief as Round 1. Read the documentation end-to-end with no prior context, evaluate whether LaunchPad would be worth adopting, and score honestly. The purpose is the same too. This is not a formal audit, certification, or endorsement. It is a structured design validation process used to keep refining the product between releases.
The Head of ITSM persona: "practitioner-authored, but opaque on pricing"
This persona evaluated LaunchPad from the procurement seat of a 5,000-person SaaS business. The question was whether this could replace custom consulting work and get a schema deployed fast enough to justify the budget line.
Head of ITSM persona: "Practitioner-authored, governance-rigorous CMDB-in-a-box for Atlassian that demonstrates mature operational thinking, but pricing opacity, incomplete documentation, and missing production-readiness guidance present material risks for enterprise deployment."
The positives landed quickly. The schemas are thoughtful across business, application, and infrastructure layers, the governance playbooks contain operational detail rather than aspirational language, and the Forge-native deployment model addresses the vendor-risk reflex that procurement teams apply to any new Atlassian app.
Where the persona pushed back: no pricing anywhere in the documentation, no published support SLA, incomplete screenshots in installation pages, and no production-readiness framework for teams planning a multi-team rollout. Credibility scored 8 out of 10. Enterprise readiness scored 6 out of 10. Schema quality scored 8 out of 10.
The Enterprise Architect persona: schema-sound, vendor-risk-opaque
This persona read the documentation with TOGAF, ISO 27001, SOC 2, and DORA responsibilities in the background. The focus was whether the schemas can carry compliance weight, and whether the vendor story is specific enough for a regulated-industry procurement review.
Enterprise Architect persona: "LaunchPad creates working Assets structure in minutes, but governance, data residency transparency, and compliance control mapping require enterprise scrutiny before production deployment."
The compliance coverage in the Enterprise IT CMDB governance playbook was rated the strongest single page. Explicit mapping to SOC 2, ISO 27001, PCI-DSS, and HIPAA, with AQL audit queries and retention policies that are actually retention policies, not documentation ornaments. The three-tier ownership model and the federation principle in best practices were both cited as evidence of Configuration Management System thinking rather than single-database thinking.
The gaps were specific. Forge tenancy isolation, encryption-at-rest guarantees, and data residency commitments are not documented. DORA ICT risk requirements, mandatory for EU-regulated financial entities from 2025, are not addressed. Integration architecture for ServiceNow, Tanium, Qualys, and CMDB federation is conceptual rather than prescriptive. Vendor transparency scored 3.5 out of 10. Compliance coverage scored 6.5 out of 10. Governance rigour scored 7.5 out of 10.
The SRE and Platform Engineer persona: good for ITSM, thin for cloud-native extensibility
This persona brought a cloud-native scale-up frame: Kubernetes, GitOps, on-call automation expectations, and a strong prior that any CMDB not integrated into the deployment pipeline becomes shelfware within six months.
SRE and Platform Engineer persona: "LaunchPad creates the structure that CMDB operations depend on, turning weeks of design debate into minutes of template deployment, but the hard work of keeping it accurate, connected, and operationally useful remains entirely yours."
The Cloud-Native Infrastructure schema was rated well-modelled for modern Kubernetes estates, with correct object types (Cluster, Namespace, Deployment, Container Registry, Service Mesh) and governance that acknowledges drift. The change-management linkage between incidents, changes, and CI status updates was highlighted as the core operational win. Responders can query AQL to find affected services without flipping between CMDB and wiki tabs.
The ceiling showed up on extensibility. The Assets REST API is referenced but not documented for external consumers. There is no Forge SDK guide, no webhook patterns, no event-driven sync examples for ArgoCD or Flux, and no Terraform-parity story for schema-as-code shops. AQL is treated procedurally rather than with a formal cookbook. Operational utility scored 7 out of 10. API extensibility scored 5 out of 10. Cloud-native fit scored 7 out of 10.
The new JSM Admin persona: can ship in 90 days, if screenshots land
This persona represented the person actually doing the rollout. Six months into their JSM role, mid-market organisation, 90-day mandate, competent but not expert.
New JSM Admin persona: "I can go from zero to a working, queryable schema in under an hour with concrete step-by-step instructions, but I'll hit walls fast on troubleshooting if something doesn't match what the screenshots promised to show."
Pacing landed well. The decision tree in "Which schema should I choose?" works for a first-time reader, Basic CMDB and Service Catalogue quickstarts include realistic starter data with time estimates, and rollback and safety are explicit enough to build confidence before the first deployment.
The walls came in waves. Screenshot placeholders on installation and first-launch pages will break trust the moment the live UI differs from the text description. The gated operate section creates a day-8 cliff when a new administrator needs ownership and incident-linkage guidance. There is no scaled-population guide for the day a stakeholder asks how to load 500 servers instead of 20. And AQL examples beyond basic filters are missing just when they would be most useful. Usability scored 8 out of 10. Troubleshooting coverage scored 6 out of 10. Completeness scored 5 out of 10.
The ITIL consultant persona: "genuine awareness of why CMDBs fail"
This persona brought a 15-year frame of reference across a dozen CMDB implementations, deep familiarity with ITIL 4 and ISO 20000, and a prior that most CMDB projects fail for governance reasons rather than tooling reasons.
ITIL Consultant persona: "Most CMDB projects fail not because the tooling is bad, but because the scope was wrong, the data went stale, and nobody could explain what the CMDB was actually for, and this product shows deep awareness of exactly those failure modes."
The maturity model was rated the strongest single artefact. Four levels, honest about where teams actually sit (mostly level 1 to 2), no aspiration inflation toward level 5. The common mistakes page was cited as evidence that the authors have watched implementations collapse, and the federation principle in best practices maps to the ITIL 4 Configuration Management System concept rather than treating the CMDB as a single database.
The gaps were practice-level rather than content-level. Problem Management is barely covered relative to Change Enablement. SLA Management exists as a schema, but the feedback loop back into incident prioritisation is not narrated. There is no worked Change Advisory Board example, no Cost or Service Financial Management guidance, and no Knowledge Management linkage to a Known Error Database. A ServiceNow migration runbook would close a gap that affects roughly a third of prospects. ITIL 4 alignment scored 7 out of 10. Governance rigour scored 8 out of 10. Maturity realism scored 9 out of 10. Documentation quality scored 9 out of 10.
Summary of Round 2 scores
Scores are AI-generated outputs in persona, not external benchmarks.
| Dimension | ITSM Head | Enterprise Arch | SRE | New Admin | ITIL Consultant |
|---|---|---|---|---|---|
| Credibility | 8/10 | ||||
| Clarity | 7/10 | 8/10 | 9/10 | ||
| Technical depth | 6/10 | 7/10 | 7/10 | ||
| Enterprise readiness | 6/10 | 6.5/10 | |||
| Schema quality | 8/10 | 8/10 | 8/10 | ||
| Governance rigour | 7.5/10 | 8/10 | |||
| Vendor transparency | 3.5/10 | ||||
| API extensibility | 5/10 | ||||
| Cloud-native fit | 7/10 | ||||
| Usability | 8/10 | ||||
| Completeness | 5/10 | ||||
| ITIL 4 alignment | 7/10 | ||||
| Maturity realism | 9/10 |
Empty cells indicate dimensions the persona did not score. The aggregate across reported dimensions is about 7.3 out of 10.
What Round 2 confirmed
All five perspectives, reading the documentation without anchoring on Round 1, independently cited the same three things:
- The writing is authentic. Practitioner voice, not consultant-grade deck language. Every review used some variant of "this reads like someone who has done the work".
- The "does and does not do" page builds trust. Multiple perspectives cited the scope boundaries page as the moment their evaluation shifted from cautious to engaged, and the "common mistakes" page as evidence that the authors have lived through real implementations.
- The schemas are opinionated in proportion to problem. The decision tree in "Which schema should I choose?" matches the ITIL 4 principle of adopting practices to context, not to organisation size.
What Round 1 asked for, and Round 2 reaffirmed
Round 1 (March 2026) and Round 2 (April 2026) converged on the same blockers. Remediation is now prioritised:
- Pricing and commercial terms. Procurement-blocker for the ITSM Head. Still not on the site.
- Vendor security and Forge architecture documentation. Round 1 asked for it. Round 2 added the regulated-industry dimension (DORA mapping, DPA transparency, tenancy isolation, residency).
- A 30-minute quickstart. Still missing. The new-admin persona reached this need earliest and called it the difference between a confident pilot and a stalled one.
- Advanced content for power users. AQL cookbook, API reference, Forge SDK guide, automation walkthroughs. Both the SRE and the new-admin personas flagged it.
- Production-readiness checklist. Scaling limits, capacity planning, multi-team federation patterns. Blocking for any rollout above a single team.
- Customer stories. Still missing. Even one or two case studies would close the remaining credibility gap.
New themes in Round 2
- Regulated-industry compliance specificity. Beyond general SOC 2 and ISO 27001, the Enterprise Architect persona called for explicit DORA ICT risk mapping, audit-log immutability SLAs, and a data classification policy.
- Cloud-native extensibility ceiling. Well-modelled for Kubernetes environments, but thin on GitOps and event-driven sync, Terraform-style schema-as-code, and Backstage, Port, or Cortex adjacency.
- Day-8 cliff for new admins. A fresh administrator can get through day 1 on public content, then hits a wall on day 8 when gated operate pages cover ownership and incident linkage. Two conceptual pages (how requests flow through services, understanding object types) have now moved to the public tier as a partial remediation. The broader fix is a public post-deployment bridge for first-week orientation.
- Closed-loop ITIL 4 practices. SLA Management, Problem Management, and Cost Management each exist in isolation, but the feedback loops between them (SLA breach feeding incident prioritisation, problem records aggregating incident patterns, cost data supporting service financial management) are not wired or narrated.
What this means for the roadmap
Round 1 and Round 2 findings are consolidated in the published Roadmap. Commitments landing this quarter include a published pricing page, a vendor security and Forge architecture page, the AQL cookbook, a production-readiness checklist, and the post-deployment bridge. Longer-lead work includes integration playbooks (ServiceNow, Tanium, Qualys, AWS Config, Azure Resource Graph), an API reference, customer stories, DORA-specific compliance mapping, and a ServiceNow to Assets migration runbook.
Interactive visualisation (schema explorer, decision-tree chooser, live topology, AQL playground) is on the roadmap to bring this content to life. Docusaurus remains the home of the written documentation.
Round 3 is planned for Q3 2026 once the Q2 commitments land.
This remains a structured design validation process, not a formal audit, certification, or customer endorsement. It exists to keep the product honest between releases.