top of page

Systematic

Technology

Saas Platforms

Command-and-Control Software / Government & Defense Tech

Won by compounding four decades of trust with a single home-government customer into a NATO-standard product that 50+ allied nations now depend on for battlefield interoperability.

1

MODEL

BUSINESS MODEL

SaaS, Infrastructure Platform

model bm

HOW THEY BUILT IT

- Founded 1985 in Aarhus, Denmark, by Michael Holm and Allan Schytt, two software engineers at state-owned Datacentralen who designed a system for tracking Baltic Sea warship movements.
- First contract: a command, control and information system for the Royal Danish Navy -- effectively its sole customer relationship for years before internationalizing.
- Remained privately held for 40 years (founder Michael Holm explicitly ruled out a sale in 2023, favoring an ownership foundation); grew from 2 employees (1985) to 1,100+ across 13-14 international offices, with revenue reaching EUR 218 million (FY2023/2024, +13.5% YoY) and EUR 299.6 million more recently.
- Its SitaWare command-and-control platform, first adopted by Denmark and Slovenia, is now used by 45-50+ nations and was selected by NATO after a global tender as the digital foundation for its Future Land Command and Control capability, alongside expansion into healthcare (Columna) and library management software.


HOW TO ARCHITECT IT

1. Win your hardest customer (your own national military) with a bespoke, mission-critical system, because a government-grade reference customer with genuinely high stakes is credibility no marketing budget can buy.
2. Turn a bespoke national system into a horizontally reusable product before selling internationally, because allied militaries need a standardized platform for coalition interoperability, not a one-off.
3. Diversify into structurally adjacent but distinct sectors (healthcare, libraries, utilities) that share your core competency -- managing complex, high-stakes data for critical decisions -- because it reduces dependency on defense budget cycles without diluting expertise.
4. Stay privately held and resist acquisition even at scale, because government and defense customers value continuity of ownership and mission focus over the growth-at-all-costs incentives a financial buyer would impose.

DISTRIBUTION MODEL

Enterprise Sales, Direct Sales

dm

HOW THEY OPERATIONALIZED

- Government-to-government and defense-procurement-led direct sales, requiring country-level defense ministry relationships (Denmark, UK, US, Australia, Germany, and NATO itself).
- International expansion followed a deliberate country-office-opening pattern (UK, USA, Australia, Germany, UAE, New Zealand, Sweden, Romania) as contracts justified local presence.
- Landed its largest order to date (~USD 222 million, US Department of Defense) decades after founding, reflecting a slow-build, trust-compounding sales motion rather than rapid land-grab growth.

HOW TO REPLICATE WHAT WORKED

What worked: building a track record with the hardest possible reference customer -- your own national defense ministry -- over decades before expanding, since defense buyers explicitly require software 'proven in real operations,' and Systematic could point to actual ISAF/Afghanistan deployment history.
The trap: this sales motion is inherently slow (decades, not quarters) and requires deep specialized domain knowledge; a founder trying to copy 'sell to government' without patience for multi-year procurement cycles and real operational credibility will find the category simply won't move faster for them.

|  PATTERNS OF THIS MODEL

PATTERNS IN PRIVATELY-HELD MISSION-CRITICAL SOFTWARE:

1. WIN YOUR HARDEST CUSTOMER FIRST. A high-stakes government reference makes every subsequent conversation a reference call.

2. PRODUCTISE THE BESPOKE SYSTEM BEFORE SELLING ABROAD. One-off national builds do not travel; interoperability requires a standard.

3. DIVERSIFY INTO SECTORS SHARING YOUR COMPETENCY, NOT YOUR CUSTOMER — decoupling from one budget cycle without diluting expertise.

4. STAYING PRIVATE IS A COMMERCIAL ARGUMENT IN GOVERNMENT MARKETS. Continuity of ownership is what these buyers value; a financial owner's incentives damage the proposition.

What companies with this model reveal

|  OPPORTUNITY INTELLIGENCE

GOLDMINE 1 — WIN YOUR HARDEST CUSTOMER FIRST.
Standard: a Royal Danish Navy command system is credibility no budget buys.

GOLDMINE 2 — PRODUCTISE THE BESPOKE SYSTEM BEFORE SELLING ABROAD.
Standard: allied militaries need standardised interoperability, not a one-off. SitaWare now serves 45–50+ nations and was chosen by NATO after global tender.

GOLDMINE 3 — DIVERSIFY INTO SECTORS SHARING YOUR CORE COMPETENCY.
Standard: healthcare and libraries share high-stakes data management, reducing defence-budget dependence without diluting expertise.

THE PIT — FORTY YEARS PRIVATE FORECLOSES OPTIONS.
Continuity is genuinely valued by defence buyers, and it means no acquisition currency, no employee liquidity, and growth funded entirely from cash flow at €218M scale.

THE SECOND PIT — DEFENCE REVENUE IS POLITICAL, NOT COMMERCIAL.

MOVE WITH CAUTION — PATIENCE IS ONLY A STRATEGY WITH A FUNDING MODEL THAT TOLERATES IT.

Untapped Business Model / Gaps / Goldmines / Pits

Patterns & Insights

2

MARKET

mkt mt es

MARKET TYPE

Consolidated Market

WHY THEY WON

Military command-and-control software for NATO-interoperable forces is consolidated and high-barrier -- few vendors can meet the security certifications, interoperability standards, and operational track record required. Systematic won by being the first mover from a small, NATO-aligned nation (Denmark) building genuinely interoperable, allied-tested software rather than trying to unseat larger US defense primes head-on. Transferable principle: in a consolidated, high-trust market, a smaller player can win not by out-spending giants but by being the most operationally proven, standards-compliant option available when an alliance needs one.

ENTRY STRATEGY

Greenfield Entry

EXECUTION

Systematic built its command-and-control software directly for the Royal Danish Navy with no channel partner or acquisition involved, evidenced by its 1985 founding contract being a first-of-its-kind bespoke build for its home country's own navy.

FOOTHOLD STRATEGY

fs

Lighthouse Customer Strategy

The Royal Danish Navy and later Danish Army served as the foundational lighthouse customer, with real operational deployment -- including ISAF/Afghanistan -- proving SitaWare's battlefield reliability; that Danish operational track record then became the evidence base used to win Slovenia, Sweden, and eventually NATO's own Future Land Command and Control tender.

GROWTH CAMPAIGN

CAMPAIGNS THAT WORKED

Real coalition operational deployments (Denmark, Slovenia, and Sweden using SitaWare together during ISAF operations in Afghanistan) served as the most credible growth campaign possible -- allied militaries training and fighting alongside each other on the same system; more recently, public NATO/AI demonstrations (SitaWare Insight at NATO Headquarters, Brussels) and named contract announcements (British Army, German Bundeswehr, Austrian Armed Forces) function as ongoing credibility campaigns.

KEY LEARNING

If your buyer is a government or highly risk-averse institutional customer, your best growth campaign is a real, high-stakes deployment your product has already survived -- not a case study, an actual operational record. If you're expanding into adjacent sectors, as Systematic did into healthcare and libraries, lead with the same core competency (managing complex, high-stakes data for critical decisions) rather than presenting it as an unrelated diversification.

gc

Market Context

|  MARKET INTELLIGENCE

THE STANDARD: In a consolidated, high-trust market, a smaller player wins by being the most operationally proven, standards-compliant option available.

RULE 1 — CERTIFICATION IS THE BARRIER AND THE OPENING. Years of accreditation deter entrants and let a small vendor compete with primes on equal footing.

RULE 2 — NEUTRALITY IS AN ASSET WHERE BUYERS DISTRUST SINGLE-COUNTRY DEPENDENCE. Sovereignty is a commercial position, not a political one.

RULE 3 — DEPLOYMENT HISTORY IS THE ONLY CREDIBLE PROOF. "Used in this operation" outperforms any feature list.

RULE 4 — PROGRAMME TIMING DRIVES REVENUE, NOT SALES EFFORT. Dual-use diversification is the standard hedge against that lumpiness.

MARKET TYPE: Consolidated Market (defence command and control).

|  MARKET ENTRY PLAYBOOK

THE STANDARD: A FIRST CONTRACT WITH A NATIONAL INSTITUTION IS BOTH FOUNDING CAPITAL AND PERMANENT CREDENTIAL — customer-funded entry, with the customer choosing your product.

RULE 1 — BESPOKE WORK FOR A DEMANDING BUYER IS A LEGITIMATE START IF YOU KEEP THE IP.
A first-of-its-kind build for a national navy funded the company and produced a product; without IP retention it would have produced a consultancy.

RULE 2 — DEFENCE AND HEALTHCARE REFERENCES TRAVEL BETWEEN NATIONS.
Sovereign buyers evaluate what allied nations deployed. One national reference opens a decade of export.

RULE 3 — LONG CERTIFICATION AND SECURITY CYCLES ARE THE MOAT AND THE CASH CONSTRAINT.
Accreditation takes years, which excludes fast entrants and requires patient ownership.

EVIDENCE: founded 1985 in Denmark with a bespoke command-and-control build for the Royal Danish Navy, no channel partner or acquisition; privately held and expanded into defence, healthcare, police and library software across multiple countries.

How to enter

|  FOOTHOLD STRATEGY PLAYBOOK

THE STANDARD: IN DEFENCE AND OTHER TRUST-CRITICAL SECTORS, THE ONLY REFERENCE THAT COUNTS IS OPERATIONAL DEPLOYMENT UNDER REAL CONDITIONS. Demonstrations do not transfer; battlefield use does.

RULE 1 — WIN YOUR OWN NATION'S FORCES FIRST. A home military is reachable, politically motivated to support domestic industry, and provides the operational record no commercial customer can.

RULE 2 — THE PROOF POINT MUST BE A REAL DEPLOYMENT, NOT AN EXERCISE. Use in an actual operational theatre is what converts a national supplier into an international one.

RULE 3 — ALLIANCE MEMBERSHIP IS THE DISTRIBUTION NETWORK. Interoperability standards and shared procurement mean one member's adoption creates a path to the others, culminating in alliance-level tenders.

RULE 4 — DEFENCE PROCUREMENT IS DECADE-LONG IN BOTH DIRECTIONS. Cycles are brutally slow and contracts, once won, are close to permanent — which requires a capital structure that tolerates the wait.

EVIDENCE: The Royal Danish Navy and later the Danish Army were the foundational lighthouse customers, with real operational deployment including ISAF in Afghanistan proving SitaWare's reliability. That Danish operational record became the evidence base used to win Slovenia, Sweden and eventually NATO's Future Land Command and Control tender. Systematic is privately held; revenue is reported in Danish filings rather than summarised reliably elsewhere.

How to get the first strong position

MARKET PATTERNS & PLAYBOOK

3

MONEY

money rev pri

REVENUE MODEL

Licensing Fees, Contract Revenue

PRICING MODEL

Value-Based Pricing

WHY THEY WON

Enterprise licensing agreements with national defense ministries (Denmark's DALO extended SitaWare licensing to an unlimited number of users via an enterprise license agreement) plus large fixed-value government contracts (the ~$222M US DoD order, the 28M EUR NATO FLC2 contract) -- a founder can replicate the 'unlimited enterprise license' structure once a customer's usage has proven valuable enough that per-seat licensing becomes an obstacle to full adoption.

Government and defense pricing is negotiated per contract based on scope, user count, and mission criticality rather than published rates -- reflected in Systematic's move from limited licenses to enterprise-wide unlimited-user agreements once a customer (Denmark) had already proven the software's value across a smaller deployment.

TARGET AUDIENCE

CUSTOMER BUYING BEHAVIOUR

tg cb

National defense ministries and NATO/allied militaries needing command-and-control and battlefield interoperability; hospitals and regional health authorities needing electronic health record and patient-flow systems; public library systems needing consolidated library-management infrastructure.

Long-cycle, procurement- and tender-led government purchasing requiring security certifications (CMMI Level 5), operational proof points, and multi-year negotiation -- a trust-first purchase where a track record of real deployments matters more than a sales pitch.

PRICING INTELLIGENCE

What makes this model effective & make customers pay 

THE STANDARD: In defence and healthcare, price against certification and consequence. Software that must be accredited before use is bought on a different curve entirely.

RULE 1 — ACCREDITATION IS THE MOAT AND THE COST BASE TOGETHER.
Security clearance, clinical safety approval and interoperability standards take years and exclude every competitor without them. Treat certification spend as direct investment in pricing power.

RULE 2 — LONG PROCUREMENT CYCLES PRODUCE LONG CONTRACTS AND EXCEPTIONAL RETENTION.
Multi-year public contracts mean slow growth and revenue that persists through downturns. Fund the business for that shape rather than fighting it.

RULE 3 — MISSION-CRITICAL FAILURE COST IS THE ANCHOR, AND IT IS NOT MONETARY.
Where the consequence is a patient or a soldier, price is measured against harm avoided. That supports contract values commercial software cannot approach.

RULE 4 — DOMAIN DEPTH ACROSS UNRELATED VERTICALS IS A DELIBERATE HEDGE.
Serving both defence and healthcare diversifies exposure to any single government's budget cycle, at the cost of focus.

DISCLOSURE: Systematic (Denmark) does not publish list pricing; contracts are tendered and terms are rarely public.

THE WILLINGNESS-TO-PAY INSIGHT: The buyer is procuring under public scrutiny and personal accountability. Certification, auditability and vendor longevity outrank every feature — which is why accredited incumbents in these sectors hold pricing that no better product can dislodge.

PRICE & REVENUE

Revenue Risk - The biggest threat to revenue stability

Unlimited enterprise licensing produces durable revenue and removes seat-based expansion permanently — growth must then come from new modules, countries or renegotiation, each a full cycle.

Sovereign customers concentrate risk by design: a handful of relationships carry the business, and one procurement decision is a material revenue event.

Defence budgets are politically cyclical in both directions, and sovereignty rules cap how far a national vendor can travel.

Large milestone-based programmes are not ARR; they recognise unevenly and slip on political timetables.

Privately held; national filings, not press estimates, are the reliable source.

Where the model can break

4

MOTION

LinkedIn: https://www.linkedin.com/company/systematic-a-s (limited public social presence, typical of a defense contractor -- verify before use)

GROWTH EXPANSION MODEL

COMPETITIVE STRATEGY

motion ge cs

Geographic Expansion, Market Development (New Customer Segments)

HOW THEY EXPAND

The sequence: Danish Navy and Army (1985-mid 1990s), international office expansion (UK, USA, then Australia, Germany, UAE, New Zealand, Sweden, Romania) alongside NATO ally adoption (Slovenia, Sweden during ISAF), then market development into new customer segments entirely -- healthcare (Columna, from 2011) and library management (Cicero, from 2018) -- diversifying revenue beyond defense budget cycles while reusing the same core data-management competency.

Differentiation, Focus Strategy

HOW THEY COMPETE

Rather than competing broadly against large US defense primes on cost or political leverage, Systematic focused specifically on being the most NATO-interoperable, allied-proven command-and-control vendor -- a focus strategy that won it the NATO Future Land C2 tender against much larger competitors by being the option multiple allied nations had already operationally validated together.

GROWTH ENGINE

GTM

ge n gtm

Network Effects, Partnership Growth

Because SitaWare's core value is coalition interoperability, every additional allied nation that adopts it makes the platform more valuable to every other nation already using it -- a genuine network effect in a category where that's rare; it strengthens with each new NATO member or partner nation onboarded and would only weaken if a rival standard achieved comparable multi-nation adoption.

Government-to-government relationship building and defense-exhibition presence (Eurosatory, NATO Headquarters demonstrations); named contract announcements used as ongoing credibility signals to other prospective allied customers; direct engagement with coalition partners during real military exercises and deployments as the primary proof mechanism.

SUSTAINING MOATS

Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)

moat

Once a nation's armed forces have trained an entire command structure on SitaWare and integrated it with coalition partners' systems, switching means retraining personnel across every level of command and potentially breaking interoperability with allies mid-relationship -- a lock-in that deepens with every joint exercise and real operation conducted on the platform, compounded by the deep security certifications and government trust a new entrant would need years to replicate.

|  MOAT INTELLIGENCE

THE STANDARD: Certification and clearance are the slowest barriers to entry in software, and therefore the most durable. Money cannot shorten them.

RULE 1 — ACCREDITATION IS A TIME BARRIER, NOT A COST BARRIER. National health IT certification, defence clearance and interoperability approval take years of process a well-funded rival cannot compress.

RULE 2 — MISSION-CRITICAL SYSTEMS ARE REPLACED IN DECADES. Clinical records and command-and-control software carry consequences of failure that make replacement a political decision rather than a procurement one.

RULE 3 — NATIONAL-SCALE DEPLOYMENTS ARE CONCENTRATION RISK IN MOAT'S CLOTHING. A handful of government contracts means every renewal is existential and every one is subject to political change.

THE SIGNAL: certification moats are the most durable and least scalable combination in software. Each new country is a fresh accreditation programme, so growth is measured in national wins — and the business must be capitalised for that rhythm rather than for pipeline velocity.

Why this company remains defensible

ARR & TAKEAWAY

ARR Journey - what to do at each stage

PRE-$1M — SELL WHERE FAILURE IS UNACCEPTABLE
Defence, healthcare and public safety software wins on reliability, certification and long-term support — not on velocity.
Founder-led, slow, deep domain building is the only credible entry. Expect years before the first material contract.

$1–5M — CERTIFICATION AND CLEARANCE ARE THE MOAT
Security accreditation, national approvals and cleared staff are barriers competitors cannot shortcut.

$5–10M — NATIONAL PROCUREMENT IS ONE CUSTOMER AT A TIME
Each country is a separate market with separate rules. Treat expansion as market entry, not sales territory.

$10–50M — CONTRACT DURATION IS THE ASSET
Multi-decade support agreements make revenue predictable and make the business valuable to long-horizon owners.

$50–100M — STAY PRIVATE IF THE HORIZON IS LONG
Systematic has remained privately held with a long-term ownership structure, which is what allows decade-long product cycles.
Verify current revenue in Danish filings; figures date quickly.

$100M+ — DEFENCE DEMAND IS NOW STRUCTURAL, NOT CYCLICAL
European defence spending increases have repriced this category. Capacity, clearance and delivery — not sales — are the constraint.
Rule: in mission-critical public software, patience is the strategy and ownership structure is what makes patience possible.

COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid

THE STANDARD: Where buyers require proof in real operations, credibility is accumulated over decades and cannot be bought. Read this as a lesson about structural advantage, not a template.

SEQUENCE:
1. Win and serve the hardest domestic reference for years; that relationship is the credential.
2. Accumulate genuine operational deployment history, because "proven in operations" is the literal procurement requirement.
3. Expand to allied buyers who evaluate on identical criteria.
4. Diversify into adjacent regulated verticals to smooth procurement lumpiness.

WORKED: Operational credibility no amount of capital can shortcut.

CAUTION:
1. THE CYCLE IS DECADES, NOT QUARTERS. Without patience for multi-year procurement, the category will not move faster for you.
2. GOVERNMENT BUDGETS ARE POLITICAL — one election can reset a pipeline.

bottom of page