01 · ForgeBuilt on Atlassian ForgeNative to your Jira instance
02 · PrivacyZero data exportNothing leaves your tenant
03 · ScopeNo consulting requiredSelf-service, immediate use
04 · Library13 service modelsProduction-ready structures
Why structure matters
Jira works technically. It fails organisationally.
Without structure, everything above JSM is a workaround. These are the symptoms we hear every week.
↻
Tickets bounce between teams
No service-to-team mapping means every request is a guessing game. Structure fixes routing.
?
Ownership lives on Slack
Service ownership exists in people's heads, not in the system. Structure makes it explicit.
✕
SLA reporting is impossible
Services are not tied to agreements. You cannot report on what you have not structured.
⊘
Impact analysis is guesswork
Nothing is connected. When a server goes down, nobody knows what depends on it.
◷
Onboarding takes weeks
New hires cannot understand dependencies because they are not documented.
⎗
Reports need spreadsheets
Manual exports and pivot tables every month because the data is not structured.
What you get
From ad-hoc configuration to a working service model.
Every deployment moves you from the left column to the right. Additive, reversible, ready to use.
Before
Disconnected asset lists and ad-hoc object types.
→
After
Service structure in place
Object types, attributes, and relationships installed and visible in JSM Assets.
Before
Asking around on Slack to find the owner.
→
After
Ownership is explicit
Named owners on record for every service, linked to teams and agreements.
Before
Tickets bouncing until someone claims them.
→
After
Routing works
Service-to-team mapping built into the structure from day one.
Before
Manual exports and spreadsheet assembly every month.
→
After
Reporting becomes possible
Structured data ready for reporting. No more monthly data archaeology.
How it works
Three steps. No workshops.
STEP 01 · SCAN
Understand your environment
LaunchPad analyses your Jira instance and shows how requests, fields, and structure behave in practice. Not assumptions. Actual usage.
STEP 02 · DEPLOY
Install a working structure
Choose a proven service model and install it in minutes. Ownership, routing, and relationships are defined from day one.
STEP 03 · OPERATE
Improve over time
Identify gaps, simplify complexity, and evolve your setup based on real patterns — not guesswork.
What's in the box
Everything the app ships with, at a glance.
✓
Pre-built service models
13 production-ready Assets schemas covering the common shapes of a working service desk.
✓
Ownership and routing structure
Teams, roles, and service-to-team mapping baked into every schema. No retrofitting.
✓
Environment analysis
Scans your Jira instance, surfaces gaps, recommends a matching service model.
✓
Request flow integration
Connects request types to Assets fields so tickets carry the context they need.
✓
Safe, additive deployment
Deploys alongside your existing data. Never modifies existing schemas. Rolls back cleanly.
✓
Native Forge architecture
Runs inside your Atlassian tenant. No external services. Nothing leaves your site.
Service model library
Thirteen production-ready service models.
From a lightweight starter to a comprehensive enterprise structure. Each includes object types, attributes, and relationships.
Starter
Basic CMDB
Servers and applications mapped to people. The minimum viable CMDB structure for service accountability.
Operational
Core Schema
People, teams, applications, and vendors with ownership mapped across your organisation.
Operational
Standard CMDB
Servers, databases, applications, and network devices with ownership, location, and dependency mapping.
Operational
Service Catalogue
Service categories, SLAs, support teams, and knowledge articles mapped to business services.
Operational
Priority Matrix
Impact and urgency mapped to priority levels with clear escalation paths.
Operational
SLA Management
SLA policies, escalation rules, and tracking structures mapped to services and support tiers.
Advanced
Cloud-Native Infrastructure
Kubernetes clusters, containers, serverless functions, and managed services with clear team ownership.
Advanced
Cybersecurity Asset Inventory
Security assets, vulnerabilities, controls, and compliance requirements with clear ownership.
Advanced
Software Asset Management
Licences, entitlements, installations, and compliance positions tracked per publisher. Audit-ready from deployment.
Enterprise
Enterprise IT CMDB
Infrastructure, applications, services, compliance, and multi-cloud operations unified in a single schema.
Enterprise
Vendor Management
Vendors, contracts, risk assessments, and performance tracked against SLAs.
Enterprise
Workforce Management
Employees, contractors, skills, certifications, and equipment tracked with department ownership.
Enterprise
Documentation Management
Page ownership, review cadences, validation status, and capability claims tracked with release readiness.
13production-ready service models, covering the full spectrum from minimum-viable CMDB to enterprise-scale service management. Free for up to 10 users.
Schema Extensions
Extend your model when you need more.
Purpose-built schema extensions for use cases that go beyond the starter set. Delivered as importable structures. You deploy them. No consultancy attached.
Catalogue coming post-launch
Specialised domain schemas
Extensions for verticals and use cases that need more than the core service model.
Catalogue coming post-launch
Custom extension work
Scoped, fixed-price work when your use case sits outside the catalogue.
Catalogue coming post-launch
Reusable, not bespoke
Designed as products — import, use, own. Not one-off deliverables.
Schema Extensions catalogue and pricing will be published post-launch. Custom extension work is available on request today.
Beyond the app
For when you're ready to go further.
Playbooks · Q3 2026
Run it properly.
Operational IP for teams scaling beyond initial deployment. Governance, AQL patterns, migration guidance, maturity models.
// A separate offering. Not required to use LaunchPad.
Advisory · Available now
Short, bounded input when you need it.
Schema reviews, scoped workshops, office-hours Q&A, post-deployment health checks. Hours to days, never months.
// We provide structure and direction. We don't run your service desk.
From practitioners
What people running JSM actually say.
“
We'd been putting off the Assets build for eight months. LaunchPad got us from empty to running in an afternoon.
