KOMPOSE · Commercialisation intelligence · Early access
Turn a validated engineering concept or a new growth opportunity into commercial models your team can compare, challenge and test before committing investment.
Critical assumption
Fleets will pay a recurring fee for a measurable uptime benefit.
Illustrative scenario. No customer results or financial projections are implied.
The commercialisation gap
A validated concept can become a product sale, a subscription, a managed service or an outcome-based contract. Each choice changes the buyer, capabilities, partners, cash flow and risk.
From opportunity to decision
The KOMPOSE workflow brings discovery, design, evaluation and the next move into one shared view. Here is how an EV battery health concept could progress.
Define the fleet problem, buyer, market context, alternatives and evidence gaps.
Build connected options across demand, core, value proposition, supply and ecosystem.
Expose assumptions and compare market fit, delivery capability and economics under scenarios.
Document the rationale and define the smallest pilot that could change the decision.
Illustrative workflow; availability of individual capabilities will be discussed during early access.
The business architect in your corner
An illustrative walk-through using an EV battery health concept. Each step builds on the same shared model.
Illustrative scenario. No customer results or financial projections are implied.
Business model architecture
Start with a structured model, then change it together. A shift in buyer, offer or contract changes the delivery system and economics. Select a block to see the decisions it contains.
Evidence discipline
AI can write a convincing strategy even when the evidence is thin. The intended evidence model distinguishes sourced facts, reasoned inferences, assumptions and unknowns, so teams know what to verify next.
Established and sourced. You can see where it came from.
Reasoned from facts, with the reasoning visible.
Believed, not yet proven. Each one gets a hypothesis to test.
Named openly, with the evidence that would settle it.
Examples for illustration.
Compare and decide
The most useful output is a reasoned next move. The comparison below illustrates how the same EV battery health concept could lead to different business models.
| Decision lens | Option ADiagnostics license | Option BFleet subscription | Option CUptime contract |
|---|---|---|---|
| Customer promise | Battery insight for fleet teams | Ongoing monitoring and intervention | Contracted availability outcome |
| Revenue logic | Software license | Fee per vehicle or fleet | Fee tied to a defined outcome |
| Delivery dependency | Reliable data connection | Data + service response | Data + service + risk underwriting |
| Critical unknown | Will buyers act on alerts? | Will they pay for avoided downtime? | Can performance risk be priced? |
| Illustrative next move | Validate buyer workflow | Run a fleet pilot | Model risk before offering |
Illustrative options and reasoning. No ratings or outcomes are drawn from customer data.
How KOMPOSE compares
Teams today shape business models with consultants, spreadsheets or general-purpose AI. KOMPOSE is designed to keep the model, the evidence and the reasoning in one place.
| What matters | KOMPOSEDesigned to | Consulting engagementTypical | Spreadsheets and slidesTypical | General AI chatTypical |
|---|---|---|---|---|
| Starting point | A concept or opportunity, structured into five linked blocks | A scoped engagement and a bespoke deck | A blank file | A prompt |
| Evidence | Facts, inferences, assumptions and unknowns kept separate | Depends on the team | Assumptions mixed with data | Fluent output, sources often unclear |
| Alternatives | Options compared side by side on shared lenses | Often one recommended option | One scenario per tab, built by hand | One answer at a time |
| Assumption testing | Each assumption has a hypothesis and a status | Workshops, not always tracked | Sensitivity tables, if built | Not tracked |
| Rationale retained | Questions and decisions stay linked to the model | In a report | In people's heads | In a chat thread |
General characterisation of typical approaches. KOMPOSE is in early access, and capabilities will be confirmed for each use case.
What KOMPOSE is being built to support
These capabilities share the same evolving model. Early-access conversations will clarify which parts are available for a particular use case.
Structure an opportunity and explore model options across the five linked blocks, with relevant market and industry context.
ComposeChange an assumption and inspect how it affects economics, capabilities and risks across competing options.
EvaluateCarry the selected model into a validation plan with a pilot hypothesis, resources and decision milestones.
PlanDesigned for teams
Strategy, finance, product and operations work from one model, so disagreements are about choices and evidence, and the reasons behind each decision stay with the model.
If we promise lower downtime, which battery signals can we access across the fleet?
2 replies · linked to SupplyThe subscription only works if service cost stays below the recurring fee. Let us test response cost first.
Assumption added · linked to Unit economicsFleet interviews point to uptime first. Diagnostic detail matters when it prompts an action.
Evidence added · linked to Value propositionThe KREAT flow
KOMPOSE is the commercialisation layer for concepts from KRAFT. Teams can also begin with a standalone growth opportunity.
Questions
A canvas is a useful starting view. KOMPOSE is designed to connect the model choices to market evidence, operating dependencies, assumptions, scenarios and the next decision.
No. A physics-validated concept from KRAFT is one starting point. A company can also begin with a growth opportunity or an existing business model it wants to improve.
No. The team owns the judgment. KOMPOSE is designed to help structure alternatives, expose evidence gaps and document the reasoning behind the decision.
KOMPOSE is in development. Contact our team to discuss an early-access use case and the current scope of the product.
Early-access conversation
Tell us what your team is considering. We will discuss the model alternatives, evidence gaps and the smallest useful next test.
Talk to KREAT
Our contact form routes your enquiry to the right person on the team.
Discuss an early-access use caseContact KREAT
Describe it in plain language. You do not need equations, CAD models or PLM integration to start.
What do you need?
What happens next
This preview is not connected to an inbox, so nothing has been sent. The text below is what the team would receive.