Skip to content
01 Portfolio Overview
As of 22 Oct 2026Synthetic case-study dataSynthetic · as of 22 OctV6 input · imported 22 Oct, 02:25

Solutions Value & Ops Excellence

01 · Portfolio Overview

Where are we deploying Solutions capacity, on what types of use cases, and how mature is our footprint?

A portfolio view of where we invest scarce Solutions capacity across industries, use case types, deployment environments and lifecycle stages.
Use Cases

50

44 active · 2 on hold · 4 stopped

Accounts

16

Across 5 sectors

Allocated Solutions Capacity

28.6 FTE

Oct 2026 plan · not headcount

Live / Scale UC

18

36% of the portfolio · 12 Live, 6 Scale

Sector Allocation

Where is Solutions capacity invested?

  • Share of 44 active use cases
  • Share of Oct 2026 capacity

Owner Staffing + Solutions Ops (proposed)·Source USE_CASES, ACCOUNTS, SOLUTIONS_EFFORT

Portfolio Composition

What are we building?

Use-case family
Deployment environment

Owner Deployment Strategist / Solutions Ops (proposed)·Source USE_CASES

Lifecycle Maturity

How mature is our footprint?

Current state of each use case

Owner Deployment Strategist / Solutions Ops (proposed)·Source USE_CASES, GATE_DECISIONS

02 · Customer Value

Are we delivering the value our customers expect?

Customer value is assessed throughout the use case lifecycle:

  1. define the expected business outcome at scoping
  2. validate its potential during the pilot
  3. measure realized value after deployment through adoption, business impact and sponsor satisfaction.

Technical quality is a prerequisite at every stage.

01 DefineScoping · kick-off

Value Defined

72%

36 / 50 approved use cases

KPI, baseline and target documented (proxy)

02 ValidatePilot exit

Value Validated

52%

14 / 27 pilot exits

Go, measured gain, adoption at target · Pilot Go alone 22 / 27

03 Realize90 days after go-live

Value Realized

31%

5 / 16 live for 90+ days

KPI and adoption targets, quality Pass, measured

Customer Value by Type of Use Case

How each value step reads by sector and by use-case family

Share of 16 use cases live for 90+ days that realized their value

By sector

By use-case family

Owner Deployment Strategist / CSM; Solutions Ops computes (proposed)·Source USE_CASES, ACCOUNTS, GATE_DECISIONS

Sponsor Satisfaction

Latest sponsor rating, 1 to 5: a relationship signal kept apart from value realized

3.5 / 5

18 / 35 sponsors responded51%

Positive Sponsor Signals

Sponsor Relationships to Watch

Owner CSM + sponsor (Deployment Strategist before handover) (proposed)·Source USE_CASES

03 · Mistral Value

Are we turning Solutions engagements into scalable product revenue?

Solutions combines paid implementation sprints with recurring model and platform revenue. We assess what we monetize, the additional product business we unlock, and the Solutions capacity required to generate it.

Monetize→Unlock→Leverage

Year to date 1 Jan 2026 – 22 Oct 2026 · recognized revenue, not ARR · Oct 2026 partly provisional

MonetizeServices Revenue

€4.16m

Recognized from 98 sprints · €4.90m booked

MonetizeProduct Revenue

€5.18m

All product lines, incl. pre-existing

UnlockProduct Pull-through

€1.97m

38% of product revenue, a subset

LeverageSolutions Investment

€5.22m

Illustrative loaded cost · 8% shared

Monetize

Revenue Mix by Sector

What share of our revenue comes from product rather than services?

  • Services revenue
  • Product revenue

Owner Finance / RevOps (proposed)·Source SERVICE_SPRINTS, PRODUCT_REVENUE, ACCOUNTS

Unlock

Product Pull-through vs Solutions Investment

Attributed product revenue against the Solutions capacity each account absorbed

↑ Product pull-through, YTD

€0€100k€200k€300k€400k€0€200k€400k€600k€800kMeridian CapitalDefense Operations CommandVale International BankAsterion Bank

Solutions investment, YTD →

Recent accounts carry cost before product revenue matures: no quadrants, no ROI cut-offs.

Owner Finance / RevOps + Staffing (proposed)·Source ACCOUNTS, USE_CASES, SERVICE_SPRINTS, PRODUCT_REVENUE, SOLUTIONS_EFFORT

04 · Operational Excellence

Where does value get lost between scoping and scale?

We track Go/No-go decisions across the use case lifecycle to identify where delivery stalls, understand the underlying reasons, and prioritize systemic improvements that accelerate customer value realization and product growth.

Where→Why→Improve

  1. Scoping
  2. POC
  3. Pilot
  4. Build
  5. Live
  6. Scale
POC and Pilot can be skipped · handover is a milestone, not a stage
Time to Production

259 d

P50 · P75 281 d · 18 launches

Open Gate Exceptions

12

Adverse latest decision, no stage entry since · 2 on hold

Adverse Gate Outcomes

32 / 50

Use cases with a No-go or Conditional Go · 41 decisions

Top Issues with an Action

4 / 5

None with a committed date yet

Where

Gate Decision Outcomes

At which gates do use cases struggle to progress?

  • Go
  • Conditional Go
  • No-go
Scoping exit47 use cases evaluated

47 Go 100%

POC exit32 use cases evaluated

27 Go 84%1 Conditional Go 3%4 No-go 13%

Pilot exit27 use cases evaluated

22 Go 81%4 Conditional Go 15%1 No-go 4%

Build → Live25 use cases evaluated

18 Go 72%3 Conditional Go 12%4 No-go 16%

Live → Scale6 use cases evaluated

6 Go 100%

Owner Deployment Strategist / Solutions leadership (proposed)·Source GATE_DECISIONS, USE_CASES

Why

Top 3 Gate Issues

What recurring issues prevent use cases from progressing?

Owner Deployment Strategist / Solutions leadership (proposed)·Source GATE_DECISIONS

Improve

Priority Improvement Opportunities

Which recurring constraints should we address to unlock more value across projects?

Recurring issueUse casesImprovement hypothesisOwnerDueStatus
1134%Agree minimum enterprise release criteria (IAM, audit logs, vulnerability remediation, rollback) with Product before any Build-to-Live submission.Product Platform + Solutions Engineering · TBDProduct Platform + Solutions EngineeringTBDProposed
825%At kick-off, identify each client security and governance approver and book the production review window.Account Team + Client Security · TBDAccount Team + Client SecurityTBDProposed
825%At scoping exit, name the client data owner and test read access to an approved, representative evaluation sample.Deployment Strategy + Client Data Owner · TBDDeployment Strategy + Client Data OwnerTBDProposed
516%No action assignedUnassigned · TBDUnassignedTBDNeeds decision
413%Before Build, complete one end-to-end test of client identity, network routes and target APIs in staging.Solutions Engineering · TBDSolutions EngineeringTBDProposed

Owner Solutions Ops + the accountable Product or Solutions lead (proposed)·Source GATE_DECISIONS, IMPROVEMENT_ACTIONS