LT.Solutions, Technology Consulting & Software[Atlassian consultancy] Est. London

Atlassian, configured for the work you actually do.

Forge-native apps and hands-on consultancy for Jira Service Management and Jira Assets: schemas, CMDB structure and the operating model around them.

Two apps live on the Marketplace.

yoursite.atlassian.net / launchpad / schema library
LaunchPad schema library, showing the schema catalogue grouped by family with inspect and deploy on each card

Not the shipping UI

LaunchPad, schema library

Two apps live on the Atlassian MarketplaceAsset Sync in Marketplace reviewConsultancy engagements openJira Service Management & AssetsITAM & CMDB designNIST CSF 2.0Forge-native engineering
01 / Products & IP

Live apps, new products, and the method behind them.

LaunchPad and Second Chance are live. Asset Sync and LT Census extend the product family with reporting and controlled infrastructure discovery.

LaunchPad

for Jira Service Management
Live

Install a structured Jira Assets layer into the service desk you already run. LaunchPad reviews your Jira Service Management setup, recommends asset models that fit the way your teams work, and deploys a working schema without starting from a blank page.

[Forge][Jira Assets][Free up to 10 users][From $4.53 per user]
Explore LaunchPad
LaunchPad schema library
Free / Live

Second Chance

for Jira Service Management

Give every request another chance at self-service. Second Chance surfaces relevant knowledge after a request is raised, so users and agents resolve common issues before they become avoidable ticket work.

[Confluence required]

Needs Confluence connected as the Jira Service Management knowledge base.

Explore Second Chance
Second Chance in the request portal
Free / In review

Asset Sync

for Google Sheets™

Pull Jira Assets data into Google Sheets as reports you refresh with one click. Pick a schema, choose object types and columns, and Asset Sync writes the objects into your spreadsheet as a saved report. One-way by design: it reads from Assets and never writes back.

[AQL][Reads, never writes]

LT Census

Connect + Discovery
Not released

Keep Jira Assets aligned with the systems that already know what exists. LT Census is a family of two products. Connect brings SaaS and device sources into a controlled lifecycle through connectors such as Workday and Zluri. Discovery finds cloud infrastructure on Google Cloud.

[Connect][Discovery][Google Cloud][Zluri]
Explore LT Census

LaunchPad Playbooks

Paid IP / Implementation IP, not an app

The method behind LaunchPad, written down. Self-guided training paths, operating models, governance routines and schema-maintenance guidance for teams putting LaunchPad into production and keeping it running.

Talk to us about Playbooks
02 / Consultancy

When you need it built, not bought.

Our apps cover the common cases. The rest is bespoke. We work with operations leads, ITSM teams and platform owners on the parts of Atlassian that no Marketplace listing can solve.

01

Assets schema design

Object types, relationships and reference data that match how your business operates, not the templates Atlassian ships with.

[Jira Assets][AQL]
02

Jira Service Management rollouts

Request types, queues, automation rules, permissions and knowledge links, from migration scoping through to go-live.

[JSM][Automation]
03

Forge app builds

Custom Forge apps for internal tools or Marketplace products, from concept and build through security review to release.

[Forge][Security review]
04

Platform health

Reviews of existing Jira and Confluence estates: what to fix first, and whether the answer is cleanup, redesign or rebuild.

[Audit]
05

Governance and compliance

Controls, evidence and risk modelled as structured Assets data. Framework-ready structure, not a compliance claim.

[NIST CSF 2.0][ISO 27001]
06

Handover and training

We build, document and brief your team so they can own the result from day one, with an optional support window after go-live.

[Handover]
Discuss an engagement Discovery call / Written scope / Build and hand over
03 / Operating approach

Structure that survives after go-live.

LaunchPad and our consultancy work from the same principles: structure run as an ongoing service, not a one-off project handover.

The operating difference

Most CMDBs fail.

We would rather build for those odds than pretend they are not real.

Illustrative LaunchPad service model showing object types and relationships
Illustrative schema pattern
Five principles we work to
01

Start with outcomes, not an inventory

Model what improves incident, change or asset decisions. Skip the trophy cabinet.

02

Scope lean. Begin where it hurts

Five to ten critical services first. Only attributes that support a real decision.

03

Automate data in. Keep it fresh

Stale data kills trust. Bulk workflows today, and scheduled sync is not shipped.

04

Make ownership non-negotiable

Named owners from day one, with governance that reinforces accuracy over time.

05

Watch health continuously

Catch drift before teams work around the CMDB instead of using it.

Run it as a service, not a project

CMDBs that survive are operated continuously. The ones that fail are delivered once and left to drift.

LaunchPad ships schema accelerators, the Workbook Engine and setup analysis today. Governance Intelligence and sync tooling are not shipped. The full method is documented in LaunchPad Playbooks.

04 / Proof

What LaunchPad reads on a live site.

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.

service desks read across 4 projects.
2
Live JSM scan
request types analysed, with their forms and fields.
50
Live JSM scan
custom fields mapped, across 272 request-type references.
123
Live JSM scan
to finish the scan, start to report.
8 sec
Live JSM scan
Built to sit inside AtlassianSecurity & CAIQ
Runtime

Built on Forge

Atlassian’s native app platform, with no separate hosting to trust.

Boundary

Runs inside Atlassian

The apps operate within your Atlassian tenancy, not a third-party cloud.

Data

No needless data export

We keep customer data where it belongs and move only what a feature needs.

Experience

Real JSM and Assets delivery

Fifteen years inside Jira Service Management and Assets, from the buyer’s side.

05 / Get in touch

Install one of our apps, or talk to us about the work behind it.

We use analytics cookies to understand how the site is used, only if you accept. Read our privacy policy.