Everyman Brand Archetype
Automotive
Business Intelligence
Systematic
Became trusted software for mission-critical decision-making by combining deep domain expertise with secure, interoperable platforms for defence, healthcare and critical infrastructure, despite long public procurement cycles and high compliance barriers.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Systematic built a repeatable advantage in mission-critical decision software: SitaWare for military command and control, Columna for healthcare workflows, and solutions for national security and utilities. Its advantage is not generic software but the combination of domain workflows, security accreditation, interoperability standards and reference deployments across NATO-aligned defence and public-health systems.
Question this model answers
We need to decide what to build first.
BUSINESS MODEL
Licensing
HOW THEY BUILT IT
'- Founding positioning: build decision-support software for complex, high-stakes public-sector operations.
- Product architecture: SitaWare command-and-control suite and Columna healthcare suite, supported by integration, data and AI capabilities.
- Operating model: sell licenses, subscriptions, implementation and long-term support to governments, hospitals and critical-infrastructure operators.
- Infrastructure: secure, interoperable platforms designed for defence networks, clinical systems and critical infrastructure.
- Build sequence: establish defence credibility first, then apply the mission-critical software model to healthcare, national security and utilities.
HOW TO ARCHITECT IT
1. Choose a high-stakes decision workflow where bad information or delay creates severe consequences.
2. Build the domain model before the interface: entities, statuses, permissions and decision paths.
3. Make interoperability and security first-class product requirements.
4. Win one credible institutional reference before expanding to adjacent institutions.
5. Convert deployment knowledge into reusable modules, certifications and support contracts.
DISTRIBUTION MODEL
Enterprise Sales, Direct Sales, Partnerships, Events
HOW THEY OPERATIONALIZED
'- Direct enterprise sales targeted defence ministries, armed forces, hospitals and public agencies.
- Defence exhibitions, NATO-related programs and government procurement processes created qualified institutional demand.
- Partnerships with technology and defence companies extended integration and delivery capacity.
- Reference deployments across NATO and allied nations reduced perceived adoption risk.
HOW TO REPLICATE WHAT WORKED
What Worked
Use a credible institutional reference to enter a high-trust market, then expand through adjacent agencies and geographies.
Trap if Copied Blindly
Government distribution fails when certifications, security clearances and local implementation requirements are underestimated; the cost is long sales cycles and stalled deployments.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — AI DECISION SUPPORT WITH HUMAN CONTROL. Critical institutions need recommendations, anomaly detection and scenario planning, but cannot delegate final decisions to a black box; human-in-the-loop AI is the commercial wedge.
GOLDMINE 2 — CROSS-DOMAIN RESILIENCE PLATFORMS. Defence, health, utilities and ports increasingly share risks—cyberattacks, disruption and data fragmentation; a common operational picture can serve multiple critical sectors.
GOLDMINE 3 — SOVEREIGN SOFTWARE AND DATA GOVERNANCE. Governments increasingly want local control, auditability and secure data residency; compliance-first architecture can become a procurement advantage.
THE TRAP TO WATCH
THE PIT — CUSTOM-PROJECT DRIFT. Mission-critical customers often demand customization; without reusable modules, the business becomes a systems integrator.
THE SECOND PIT — OVER-CLASSIFICATION. Excessive security constraints can slow product iteration and prevent commercial reuse.
MOVE WITH CAUTION
Do not enter defence or healthcare without a credible security, compliance and support model; a failed deployment can create national-level operational and reputational risk.
2
MARKET
MARKET TYPE
Fragmented Market
WHY THEY WON
Mission-critical public-sector software is fragmented by country, agency, procurement regime and legacy system. Defence command-and-control, hospital information systems and infrastructure monitoring each have specialized incumbents. Systematic’s opening was that institutions needed a common operational picture across units, systems and organizations. Its advantage came from reusable platforms—SitaWare and Columna—combined with local deployment and compliance capability.
Defence, healthcare and critical infrastructure relied on fragmented legacy systems, manual coordination and specialized hardware. Systematic digitized decision-making workflows—command and control, clinical documentation, patient flow and infrastructure monitoring—where adoption depended on security, reliability and regulatory compliance rather than consumer-style convenience.
Question this model answers
We need to enter a traditional or under-digitized industry.
ENTRY STRATEGY
Brownfield Entry
EXECUTION
Systematic entered by modernizing existing command, clinical and operational systems rather than creating a new category. Its initial bet was that defence organizations would adopt software-based command-and-control tools if they improved situational awareness and interoperability. This required military-domain knowledge, secure architecture and credible references. The approach was viable because legacy coordination processes were slow, fragmented and high-risk.
FOOTHOLD STRATEGY
Lighthouse Customer Strategy
THE HOW
The foothold was early defence and national-security customers whose adoption validated Systematic’s ability to operate in secure, mission-critical environments. These buyers were reachable through defence procurement and industry networks, could pay through national budgets, and created reference value for NATO-aligned forces, hospitals and infrastructure operators.
MARKET TYPE PLAYBOOK
RULE 1 — BUILD FOR THE DECISION, NOT THE DASHBOARD. The buyer needs a shared operational picture and a reliable action path.
RULE 2 — MAKE SECURITY A PRODUCT FEATURE. Accreditation, data control and interoperability determine adoption.
RULE 3 — REUSE THE CORE ACROSS SECTORS. Defence, healthcare and infrastructure share coordination, data and resilience needs.
RULE 4 — FAILURE MODE: excessive customization prevents platform economics; entry remains rational only with reusable modules.
Fragmented critical-sector markets reward vendors that combine reusable platforms with local trust and compliance.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Choose a workflow where the cost of poor decisions is visible and severe.
RULE 2 — Build interoperability before promising replacement.
RULE 3 — Use one credible institutional deployment to establish trust.
RULE 4 — Reject the approach when the buyer cannot commit to the security, governance and implementation requirements.
Brownfield entry fits when legacy systems create coordination failures, compliance risk or operational delay.
A lighthouse customer is a high-credibility institution whose adoption validates the vendor for similar buyers.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Select a customer with operational scale and reputational weight.
RULE 2 — Use the deployment to create reusable certifications, workflows and references.
RULE 3 — Expand only after the lighthouse deployment is operationally proven.
RULE 4 — Failure occurs when the lighthouse deal is so customized that it cannot be replicated.
Anduril used early defence contracts to establish credibility before expanding into border security and military platforms.
HOW TO APPLY MARKET ENTRY STRATEGY
Palantir entered government and defence through decision-support deployments, then expanded into commercial enterprises; failure occurs when data access, governance or political trust is not established.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN INSTITUTIONAL TRUST-LED SALES:
1. References outweigh advertising. Public institutions rely on peer deployments and procurement history.
2. Standards create adoption pathways. NATO interoperability and healthcare data standards reduce integration uncertainty.
3. Long-cycle relationships compound. Once a vendor is accredited and deployed, expansion is easier than initial entry.
WEAKNESS
Institutional sales can become dependent on political budgets, procurement delays and a small set of anchor customers.
GROWTH CAMPAIGNS
Defence exhibitions and NATO-aligned industry events; SitaWare and Columna customer references; government procurement and framework agreements; AI decision-support product campaigns; partnerships with defence technology and healthcare-system providers.
| So What
The commercial mechanism is converting one high-trust deployment into a repeatable platform sale across allied institutions.
| Key Learning
In critical sectors, credibility compounds through reference customers, certifications and operational continuity.
| How to Use
If selling into high-stakes institutions, secure one lighthouse customer whose success makes the next procurement decision easier.
3
MONEY
REVENUE MODEL
Licensing Fees, Subscription, Service Fee
Systematic combines product licenses, subscriptions, implementation and long-term support into multi-year public-sector contracts. Its 2024/25 revenue reached €299.6 million, up 37.5%, with EBIT of €107.6 million; growth was driven partly by stronger-than-anticipated license sales and increased activity across business segments.
Question this model answers
We need to build a predictable revenue model.
PRICING STRATEGY
Custom Enterprise Pricing, Quote-Based Pricing, Value-Based Pricing
WHY THEY WON
Governments, hospitals and infrastructure operators pay license or subscription fees for platforms, plus implementation, integration and support fees. Revenue expands through additional users, modules, countries and long-term maintenance contracts.
TARGET AUDIENCE
Defence ministries and armed forces (enterprise; want command-and-control and battlefield awareness); hospitals and health authorities (enterprise; want clinical documentation and patient-flow systems); critical-infrastructure operators (enterprise; want monitoring and resilience); government security agencies (enterprise; want secure intelligence and coordination tools).
Systematic uses negotiated enterprise pricing based on deployment scope, users, modules, security requirements and support commitments. The meter is institutional scale and mission scope, not individual seats alone; multi-year support and implementation contracts create revenue durability.
CUSTOMER BUYING BEHAVIOUR
The trigger is modernization programs, security threats, regulatory requirements or operational failure. Buyers evaluate through tenders, security reviews, reference visits and pilot deployments; procurement involves political, technical and operational stakeholders. Decisions are slow but contracts are long.
WILLINGNESS TO PAY
CORE INSIGHT
Critical institutions pay for trusted decisions under pressure.
RULES OF ADOPTION
RULE 1 — PRICE THE CONSEQUENCE OF FAILURE. A delayed decision, clinical error or infrastructure disruption costs more than software.
RULE 2 — SELL INTEROPERABILITY. The platform’s value is connecting existing systems, units and data sources.
RULE 3 — MONETIZE CONTINUITY. Support, upgrades and security accreditation create recurring budget lines.
RULE 4 — WATCH THE VENDOR COST TRAP. Compliance, customization and field support can turn software into a services business.
The buyer is really buying operational certainty, proven by the defence, health or infrastructure budget.
REVENUE RISK
Procurement cyclicality: government budgets and tenders create uneven revenue timing.
Customer concentration: defence ministries and large health systems can represent major revenue concentrations.
Political risk: changes in government, alliances or defense spending can delay programs.
Compliance burden: security accreditation and healthcare regulation increase cost-to-serve.
Customization risk: mission-specific requirements can erode product leverage if not converted into reusable modules.
Systematic is privately held; its 2024/25 revenue of €299.6 million and EBIT of €107.6 million are disclosed, but ARR is not separately reported.
4
MOTION
Systematic sells mission-critical platforms to governments, hospitals and infrastructure operators through tenders, security reviews and multi-year contracts. Deals require executive sponsorship, technical validation, compliance evidence and implementation planning—characteristics of a structured enterprise sales motion.
Question this model answers
We need to build an enterprise sales motion.
GROWTH EXPANSION MODEL
Platform Expansion, Geographic Expansion
HOW THEY EXPAND
Systematic expanded from Danish defence software into NATO-aligned markets, healthcare systems in Denmark, Finland and the Netherlands, and a new National Security & Infrastructure unit. Platform expansion connected SitaWare, Columna and infrastructure solutions, while geographic expansion followed defence cooperation and public-sector modernization programs.
COMPETITIVE STRATEGY
Sales-Led Growth
HOW THEY COMPETE
Enterprise sales and institutional references create initial platform deals. Deployment activates the customer through secure integration and workflow adoption. Successful operations expand into additional units, hospitals, agencies and countries. The engine compounds when reusable modules reduce implementation cost; it weakens when every deal becomes a bespoke project.
GTM
Systematic uses an enterprise-led, trust-driven GTM.
$5–10M ARR
Direct sales targets defence, health and infrastructure buyers; industry events and government procurement create demand; partners support integration and delivery. Reference customers reduce perceived risk, while long-term support contracts expand account value. The primary motion is enterprise sales, reinforced by institutional credibility.
SUSTAINING MOATS
Regulatory Advantage
The moat is regulatory advantage: Systematic’s platforms are built for security accreditation, interoperability standards and mission-critical compliance. These requirements make it difficult for a generic software vendor to enter defence, healthcare or critical infrastructure quickly.
| Why This Moat Lasts
Regulatory advantage lasts when compliance, security and operational trust become prerequisites for purchase.
| Standard Rules
RULE 1 — ACCREDITATION BARRIER. Defence and healthcare systems require security review and operational validation.
RULE 2 — INTEROPERABILITY DEPTH. Integration with existing systems creates technical and organizational switching friction.
RULE 3 — REFERENCE-CUSTOMER EFFECT. Public buyers trust vendors with comparable mission-critical deployments.
| The Signal
SitaWare’s use across NATO-aligned forces and Columna’s hospital deployments indicate institutional trust; the moat does not protect against changing procurement rules, political shifts or better-funded competitors.
ARR
JOURNEY
Pre-$1M ARR
PROVE MISSION-CRITICAL SOFTWARE: Build early command-and-control capability and establish credibility in defence.
$1–5M ARR
WIN INSTITUTIONAL REFERENCES: Secure defence customers whose deployment validates security and reliability.
$5–10M ARR
PRODUCTIZE THE PLATFORM: Turn custom decision-support work into reusable SitaWare capabilities.
$10–50M ARR
EXPAND INTO HEALTHCARE: Apply the mission-critical model to Columna clinical and patient-flow systems.
$50–100M ARR
INTERNATIONALIZE: Expand across NATO-aligned defence markets and European healthcare systems.
$100M+ ARR
EXPAND INTO RESILIENCE: Build National Security & Infrastructure and AI decision-support products; 2024/25 revenue reached €299.6 million.
BREAKDOWN
THE STANDARD
Build trust-first software for a high-stakes decision workflow, then reuse the platform across adjacent critical sectors.
THE SEQUENCE
1. Choose a decision workflow where delay, error or data fragmentation has severe consequences.
2. Build security, interoperability and domain logic before interface features.
3. Convert one institutional deployment into reusable modules, certifications and reference proof.
Systematic’s defence credibility enabled expansion into healthcare and critical infrastructure, with 2024/25 revenue of €299.6 million and EBIT of €107.6 million.