Let's Talk Solutions presents
LaunchPad installs the structured Assets layer underneath your service desk, so tickets route correctly, ownership exists, and reporting becomes operational from day one.
Most teams stand up Jira Service Management, get requests flowing, and never finish the layer underneath. Data goes into free-text fields instead of structured objects. It works well enough to limp along, until you try to do any of these five things.
Source: Gartner
Source: Gartner
Source: IP Fabric
You cannot aggregate by attributes that do not exist as data.
Rules need predicates. Predicates need fields. Fields need a schema.
Tickets cannot route to a team or service that was never modelled.
If no object owns the service, nobody owns the outcome.
Anything that reads your data, from automation rules to Rovo, has nothing structured to work with. The newest example of the same gap.
LaunchPad installs a typed Assets layer underneath your service desk. Same five labels, opposite outcome. Reporting works on data that exists, automation rules find the fields they need, routing lands somewhere real, ownership has an object that holds it, and anything downstream reads structure instead of free text.
Aggregate by typed attributes that exist as data, not by free-text strings to interpret.
Rules read predicates that resolve. The fields exist. The schema holds them.
Service, owner, and support team are objects. Tickets route to a real destination.
Every service has an owner object. The escalation path is a query, not folk knowledge.
A structured layer anything downstream can read. The newest example of the same gap, closed.
One platform, three implementation phases. Each capability shows its in-app label in parentheses once, so there is no post-install confusion.
Environment Analysis · Discovery (Scan Your Environment in the app)
Read-only scan of your service desks, request types, fields, and workflows. Environment Analysis recommends the service models that fit your setup, with transparent match scores and reasoning.
Service Models · Structure (Install from the app)
Deploy a curated service model additively, with its full object structure, relationships, and ownership patterns. Review the impact before anything lands.
Request Flow Analysis · Operational Adoption (Request Field Analyser in the app)
Scans request types for free-text fields and duplicated values that should be Assets objects. Generates the exact configuration recipe you apply yourself.
LaunchPad installs additively, so structure lands alongside what you already run. The library covers the common ITSM areas: CMDB foundations, service catalogue, software asset management, vendors, cybersecurity, workforce, documentation, and enterprise IT. These are not blank templates. They are opinionated, ITIL-aligned schemas built from real enterprise work, each mapped to named ITIL practices. The Service Catalogue model, for example, ships eight object types, including Business Service, Service Owner, Support Team, and Service Level. Install one, review it, adapt it, extend it.
Swipe to see the full library
Installing a schema is half the job. Getting data in is the other half, and it is where most Assets rollouts stall. The Workbook Engine (Import and Export in the app) generates a guided Excel workbook for any installed schema, one sheet per object type, with reference fields included. You fill it in, or paste in data you have already exported. On upload, LaunchPad checks every value against your live schema through the Assets API before anything is written. If an attribute is a date and the cell holds an IP address, that value fails validation rather than importing data the schema cannot hold. The validation is LaunchPad’s own logic running against the schema you actually installed, not a generic CSV passthrough, so what lands matches the structure you built.
See how the Workbook Engine worksWhat lands matches the schema
LaunchPad reads your configuration and adds structure alongside what you already have. It does not merge, repair, or overwrite existing objects. When it creates a structured field, it creates a new field. It never alters your existing free-text field, and it never adds anything to your request forms on its own. Your existing fields and all their history stay exactly as they are, so you can move at your own pace and pre-populate history before you switch anything over. It runs on Atlassian Forge inside your own tenant, and no customer data leaves your instance.
In a live Jira Service Management scan, LaunchPad analysed 2 service desks, 4 projects, 50 request types, 123 custom fields, and 272 request-type field references in around 8 seconds.
The scan recommended Workforce Management, Core, Basic CMDB, and Enterprise IT CMDB as high-fit starting models. It also highlighted where employee and organisational data was being captured through repeated free-text fields, such as employee ID, department, location, and email address.
That is the real gap most teams sit on: Jira has the fields, but the structure is missing.
Founder
LaunchPad comes from 15 years of hands-on ITSM and Atlassian work, including large-scale service management environments where Jira, Assets, ownership, routing, and reporting needed to work in practice.
The 13 models are based on patterns seen repeatedly across real service operations. They are not abstract templates. They are practical starting structures designed to help teams move faster, reduce rework, and make Jira Service Management easier to operate from day one.
Not affiliated with or endorsed by Atlassian.
The LaunchPad app is a single tier: from USD $4.53 per user per month, billed through the Atlassian Marketplace. Optional support and custom Rovo agent work are separate. No tier maze, no hidden add-ons to unlock the core product.
Environment Analysis, Service Models, the Workbook Engine, and Request Flow Analysis, in one Forge-native app installed from the Atlassian Marketplace.
Expert LaunchPad walkthroughs, licensed governance playbooks, partner-led delivery for larger rollouts, and custom Rovo agent work for teams that want an agent reasoning over their actual records, not just explaining structure.
See support and servicesLaunchPad is built and supported by Let’s Talk Solutions (LTS), a UK Atlassian specialist. The app is the product. Support and services are optional.
Your automation rules, reports, routing, and any AI you point at your data are only as good as the structure underneath them. On a thin or free-text layer there is nothing solid for them to work with. LaunchPad gives you that layer. Everything downstream gets better because the foundation is there, not because LaunchPad does the downstream work for you.
A Rovo capability that will advise on your Assets structure: explaining schemas and relationships, guiding population order, and suggesting AQL. It runs on Rovo, so it will work on sites where Rovo is active, and Rovo is included in paid Atlassian Cloud plans. On the way, not in the app yet.
Schema extension and alignment: it will merge object types, align structures across schemas, and model additively onto what you already have. In development, arriving in the same release.
No live demo of either coming capability until it is in the shipping build. Instance-level answers that name a real owner or query records are the custom agent service, which lives in optional support.
If you are moving from ServiceNow to Jira Assets, LaunchPad gives you a structured place to land: a model to map into, the Workbook Engine to populate with your exported data, and structured fields ready for you to connect to your requests. You export from ServiceNow, you populate the workbook, LaunchPad checks every value against the schema and imports. There is no connector, and nothing in the data move is automated: you control the export and the mapping, LaunchPad gives you the structured destination and validates what you bring.
Install LaunchPad from the Atlassian Marketplace, and the read-only scan is the first thing it runs, or book a walkthrough with LTS first. Either way you see what it finds before you change anything.