Everyman Brand Archetype
Automotive
Billing Software
Thought Machine
Won Tier 1 core-banking migrations by replacing rigid legacy cores with a cloud-native, API-first Vault platform that lets banks configure products and scale safely, despite Temenos’s installed base and multi-year migration risk.
• BUSINESS MODEL
• REVENUE
• MARKET TYPE
• MARKET ENTRY
• GROWTH MODEL
• MOAT
• EDGE
1
MODEL
Thought Machine entered core banking, an industry dominated by decades-old ledger and product systems, custom code forks, batch processing, and slow product launches. Rather than selling digitization broadly, it sold a cloud-native core that separated infrastructure, core capabilities, and product logic. Lloyds Banking Group became its first Tier 1 client, followed by Standard Chartered, ING, SEB, Intesa Sanpaolo, and JPMorgan Chase; this proved that a modern core could be adopted by the most complex banks, not only challengers.
Question this model answers
We need to find a narrow beachhead.
BUSINESS MODEL
SaaS
HOW THEY BUILT IT
'- Founded in 2014 by former Google engineer Paul Taylor; built Vault Core as a cloud-native, API-first core banking and payments platform.
- Used a three-layer architecture separating cloud infrastructure, core banking capabilities, and product logic, aiming to eliminate custom vendor-code forks.
- Enabled banks to define products through configurable “smart contracts” rather than hard-coded core-banking logic.
- Won Lloyds Banking Group as its first Tier 1 client, creating a reference that unlocked larger global banks.
- Raised $83 million in Series B, $200 million in Series C at a $1 billion-plus valuation, and $160 million in Series D in 2022; its 2022 valuation reached $2.7 billion.
- Surpassed $100 million revenue for fiscal 2025, grew 57% year over year, crossed $100 million ARR in Q2 2026, and served 68 banks including 18 of the world’s largest institutions.
HOW TO ARCHITECT IT
1. Identify a regulated industry where the core system is old, rigid, and blocks product innovation.
2. Build a modern core that separates infrastructure, business logic, and customer-facing products.
3. Make the core configurable through a controlled language or model rather than custom code forks.
4. Win one demanding reference customer whose adoption proves the system can handle regulated, mission-critical scale.
5. Build implementation, migration, and compliance capability before pursuing multiple Tier 1 accounts.
6. Price on a usage or account-based meter that grows with the customer’s success.
7. Avoid promising a rapid rip-and-replace migration; sequence the core replacement by product, geography, or customer cohort. The common mis-build is selling modern architecture without solving migration, reconciliation, and regulatory assurance.
DISTRIBUTION MODEL
Enterprise Sales, Direct Sales, Events, Analyst/Research Relations
HOW THEY OPERATIONALIZED
'- Direct enterprise sales targeted bank CIOs, transformation leaders, and product executives undertaking core modernization.
- Lighthouse clients such as Lloyds, Standard Chartered, ING, SEB, Intesa Sanpaolo, and JPMorgan Chase created reference value for subsequent Tier 1 deals.
- Industry events, banking-conference positioning, and analyst relations shaped evaluation around cloud-native core transformation.
- Implementation partnerships and systems integrators supported migration delivery, testing, and regulatory assurance.
- Client-led investment in the Series C round aligned major banks’ commercial success with Thought Machine’s platform roadmap.
HOW TO REPLICATE WHAT WORKED
What Worked
Use one credible, high-risk reference customer to convert an unfamiliar modern architecture into a bankable enterprise decision.
Trap if Copied Blindly
Lighthouse-led enterprise distribution fails if every deployment requires bespoke engineering; the vendor must convert each migration into reusable product capability or it becomes a slow, capital-intensive services business.
Insight on Untapped Business Model / Gaps / Pitfalls
GOLDMINE
GOLDMINE 1 — CORE-MIGRATION FACTORY. Banks need repeatable migration tooling for data reconciliation, parallel running, product mapping, and rollback; productizing this layer can reduce implementation cost and increase win rates.
GOLDMINE 2 — REGULATED PRODUCT STUDIO. A marketplace of prevalidated banking products—savings, lending, cards, deposits—could let banks launch compliant products faster without custom development.
GOLDMINE 3 — CORE-ADJACENT AI CONTROLS. AI can improve reconciliation, anomaly detection, product configuration testing, and migration assurance; the opportunity is governed AI inside the core, not another chatbot.
THE TRAP TO WATCH
THE PIT — MODERN ARCHITECTURE WITHOUT MIGRATION ECONOMICS. A cloud-native core can win technical evaluations but fail commercially if migration takes years and consumes the customer’s transformation budget.
THE SECOND PIT — CUSTOMIZATION CREEP. If every bank changes the product engine, the vendor recreates the legacy-code-fork problem it was built to eliminate.
MOVE WITH CAUTION
Do not pursue every Tier 1 bank simultaneously; each migration can consume scarce engineering and delivery capacity, while a failed high-profile program can damage credibility across the entire market.
2
MARKET
MARKET TYPE
Consolidated Market
WHY THEY WON
Core banking is a Consolidated Market dominated by established vendors such as Temenos, FIS, Fiserv, and Oracle, with high switching costs, regulatory scrutiny, and multi-year implementation cycles. Thought Machine’s opening was architectural: legacy cores coupled product logic to infrastructure, making product innovation slow and upgrades risky. Its cloud-native, API-first, event-driven architecture changed the basis of competition from system maintenance to product velocity and cloud scalability. The lesson is that a consolidated market can be entered when the incumbent’s architecture has become the constraint on the customer’s strategic agenda.
Thought Machine entered core banking, where many institutions still relied on legacy ledgers, batch processing, and vendor code forks. The adoption barrier was not awareness of digital banking but the risk of replacing the system that runs accounts, payments, and ledgers. Thought Machine entered by selling a cloud-native core with configurable product logic, then proving it through Tier 1 migrations such as Lloyds, Standard Chartered, and JPMorgan Chase.
Question this model answers
We need to enter a traditional or under-digitized industry.
ENTRY STRATEGY
Brownfield Entry
EXECUTION
Thought Machine entered by replacing or modernizing existing core-banking systems rather than creating a parallel banking product. It targeted banks with legacy cores and offered Vault as a cloud-native replacement that preserved essential banking functions while enabling configurable products and APIs. The critical bet was that a Tier 1 bank would accept migration risk in exchange for product velocity, scalability, and freedom from vendor code forks. The prerequisite was deep banking-domain expertise, security, reliability, and migration delivery capability; the approach would fail if the vendor could not support regulatory assurance and large-scale data migration.
FOOTHOLD STRATEGY
Lighthouse Customer Strategy
THE HOW
Thought Machine’s foothold came through Lloyds Banking Group, its first Tier 1 client and one of the first major institutional shifts to a cloud-native core. Lloyds had the scale, regulatory complexity, and reference value to validate Vault for other large banks. The initial pain was legacy-core rigidity and slow product innovation; the bank could pay because core modernization was a strategic transformation priority. The path outward was from Lloyds to other global banks, then to challenger banks, regional institutions, and payments-led use cases.
MARKET TYPE PLAYBOOK
RULE 1 — TARGET THE STRATEGIC PAIN, NOT THE FEATURE GAP: Banks did not need another module; they needed freedom from rigid product logic and legacy migration risk.
RULE 2 — PROVE SURVIVAL AT THE HIGHEST STAKES: A Tier 1 deployment validates reliability, compliance, and scale.
RULE 3 — MAKE CONFIGURATION SAFE: The platform must let banks change products without creating unmaintainable custom code.
RULE 4 — FAILURE MODE: A modern core fails if migration economics overwhelm the promised innovation benefit.
In a Consolidated Market, entrants win by exploiting an architectural constraint that incumbents cannot remove without disrupting their installed base.
GENERAL RULES
WHAT HAPPENS IN THIS MARKET TYPE
RULE 1 — Preserve critical functions and regulatory controls during migration.
RULE 2 — Sequence replacement by product, geography, or customer cohort rather than promising a single disruptive cutover.
RULE 3 — Build reconciliation, parallel-run, and rollback capability before selling the migration.
RULE 4 — Reject brownfield entry if the customer cannot tolerate migration risk or if the incumbent can modernize without a full replacement.
Brownfield entry is appropriate when the incumbent system is deeply embedded but constrains the customer’s strategic future.
A lighthouse customer strategy works when one credible customer validates a high-risk product for a broader market.
HOW TO APPLY FOOTHOLD STRATEGY
RULE 1 — Select a customer whose scale and regulatory complexity exceed the target market’s average.
RULE 2 — Ensure the deployment produces a named, specific proof point rather than a vague case study.
RULE 3 — Convert the lighthouse implementation into reusable product and migration capability.
RULE 4 — A lighthouse fails when the engagement is so customized that its success cannot transfer to the next customer.
Thought Machine’s foothold came through Lloyds Banking Group, its first Tier 1 client; failure occurs when the engagement is so customised that its success cannot transfer to the next bank.
HOW TO APPLY MARKET ENTRY STRATEGY
Thought Machine replaced and modernised existing core-banking systems with its Vault platform rather than creating a parallel product; failure occurs when the customer cannot tolerate migration risk or the incumbent defends the account.
PATTERNS OF THIS MARKETING MODEL
PATTERNS IN REFERENCE-LED ENTERPRISE FINTECH:
1. MARQUEE CUSTOMERS CREATE CATEGORY CREDIBILITY. A Tier 1 bank deployment reduces perceived risk more effectively than product marketing.
2. CLIENT INVESTMENT SIGNALS ALIGNMENT. When customers invest in the vendor, they signal strategic dependence and create a commercial alignment mechanism.
3. ANALYST VALIDATION SUPPORTS LONG-CYCLE EVALUATIONS. In core banking, independent research and analyst positioning help banks justify multi-year transformation decisions.
WEAKNESS
Reference-led growth can concentrate revenue among a few large clients and create delivery bottlenecks if every account requires bespoke migration work.
GROWTH CAMPAIGNS
Tier 1 reference-led enterprise sales; Lloyds, Standard Chartered, ING, SEB, Intesa Sanpaolo, and JPMorgan Chase deployments; banking-conference and analyst-relations positioning; cloud-native core migration campaigns; smart-contract product configuration positioning; client-led Series C investment; global engineering and delivery expansion.
| So What
Thought Machine’s most powerful commercial campaign was the Lloyds reference: it transformed Vault from a promising cloud-native architecture into a credible Tier 1 core-banking platform.
| Key Learning
In regulated, high-risk categories, the first marquee customer is not merely revenue; it is the market’s evidence that the vendor can survive the buyer’s worst-case operational conditions.
| How to Use
Select an early customer whose success creates transferable proof for the next tier of buyers, and invest disproportionately in making that deployment referenceable.
3
MONEY
REVENUE MODEL
Subscription, Usage-Based
Thought Machine priced Vault on a subscription basis, typically under three-to-five-year terms, with an annual platform fee and a pay-as-you-grow account-based charge above a threshold. The account meter maps to the bank’s actual scale: more customer accounts mean more core workload, more value delivered, and more revenue. This aligns pricing with customer success while preserving a predictable multi-year platform commitment.
Question this model answers
We need to choose the right pricing metric.
PRICING STRATEGY
Custom Enterprise Pricing, Value-Based Pricing, Volume-Based Pricing
WHY THEY WON
Banks pay recurring subscription fees for Vault Core and related platform access, plus account-based usage charges as customer accounts scale. Revenue expands as banks migrate more products, geographies, and customer cohorts onto Vault. The model is recurring and contract-backed, but implementation timing affects when usage revenue begins. Gross margin depends on cloud infrastructure, migration delivery, support, and the degree to which deployments reuse standard platform capability rather than bespoke engineering.
TARGET AUDIENCE
Tier 1 global banks (enterprise contracts; want cloud-native core replacement and product velocity); regional and challenger banks (enterprise contracts; want modern banking infrastructure without legacy constraints); fintechs and new banks (platform contracts; want configurable products and rapid launch).
Thought Machine uses negotiated enterprise contracts, typically lasting three to five years, with an annual platform fee paid in advance and account-based usage pricing above a threshold. The account-based meter becomes cheaper per account as volume grows, aligning cost with bank scale while preserving a high-value enterprise commitment.
CUSTOMER BUYING BEHAVIOUR
A bank typically begins with a strategic core-modernization review, evaluates cloud-native architecture, security, regulatory fit, and migration capability, then runs a scoped migration. Decision-making involves CIOs, CTOs, risk, compliance, product, and procurement stakeholders; adoption expands as additional products, countries, or customer cohorts move onto Vault.
WILLINGNESS TO PAY
CORE INSIGHT
Banks are not buying software licenses; they are buying the ability to launch and change regulated products without destabilizing the core.
RULES OF ADOPTION
RULE 1 — PRICE THE ACCOUNT AS THE UNIT OF BANKING SCALE: Accounts grow with customer success and make the vendor’s revenue track the bank’s operating scale.
RULE 2 — USE MULTI-YEAR COMMITMENTS TO MATCH TRANSFORMATION RISK: Core migration requires years, so contracts must provide revenue visibility across the deployment period.
RULE 3 — PRICE CONFIGURATION, NOT CODE FORKS: The value is a bank’s ability to change products without creating unmaintainable custom code.
RULE 4 — WATCH THE MIGRATION COST TRAP: The vendor’s hidden cost is implementation and data migration; pricing must recover delivery cost or convert it into reusable migration assets.
The buyer is really buying product velocity and core resilience, evidenced by multi-year transformation budgets.
REVENUE RISK
Migration delay: Core-banking programs can take years; delays postpone usage-based revenue and increase delivery cost.
Customer concentration: Tier 1 banks represent large contracts, so a delayed or lost program can materially affect growth.
Implementation intensity: Custom migration and regulatory assurance can pressure gross margin if not converted into reusable deployment assets.
Incumbent response: Temenos, FIS, Fiserv, and other incumbents can modernize existing cores and use installed-base relationships to defend renewals.
Regulatory and security risk: A core-banking failure or compliance lapse can damage credibility across the entire market.
Funding/valuation: Thought Machine was valued at $2.7 billion in 2022; it surpassed $100 million revenue in fiscal 2025 and crossed $100 million ARR in Q2 2026, based on company-disclosed audited and operating figures.
4
MOTION
Thought Machine sold high-value, multi-year core-banking transformations through a structured enterprise process involving bank CIOs, transformation leaders, risk, compliance, product, and procurement. Its motion combined direct enterprise sales, Tier 1 references, analyst relations, implementation partners, and multi-year contracts. The 2022 Series C was funded directly by Tier 1 client banks, reinforcing the strategic-account nature of the motion.
Question this model answers
We need to build an enterprise sales motion.
GROWTH EXPANSION MODEL
Land & Expand, Geographic Expansion
HOW THEY EXPAND
Thought Machine first landed Lloyds Banking Group, then expanded geographically and across bank tiers to Standard Chartered, ING, SEB, Intesa Sanpaolo, JPMorgan Chase, Atom Bank, and Arvest Bank. Within accounts, it expanded from initial core migration to additional products, customer cohorts, geographies, and payments workloads. It also expanded its engineering and delivery footprint, including a Lisbon hub, to support global Tier 1 implementations. By 2026, it served 68 banks, including 18 of the world’s largest institutions.
COMPETITIVE STRATEGY
Sales-Led Growth
HOW THEY COMPETE
A bank identifies core rigidity or a transformation mandate → Thought Machine runs an enterprise evaluation with CIO, risk, product, and compliance stakeholders → a lighthouse reference such as Lloyds reduces perceived risk → the bank signs a multi-year migration contract → initial products or cohorts move onto Vault → additional products, countries, and accounts migrate → account-based usage and subscription revenue expand. The loop compounds when each Tier 1 deployment becomes a reference for the next large bank. It requires deep migration capability and regulatory credibility; it breaks if implementations remain bespoke, delivery capacity becomes constrained, or migration timelines erode customer confidence.
GTM
Thought Machine runs a sales-led, reference-driven enterprise GTM.
$5–10M ARR
Direct sales targets banks undertaking core modernization; lighthouse clients validate the platform; analysts and industry events shape evaluation criteria; implementation partners support migration; account teams expand usage after initial deployment. The primary motion is enterprise sales, with product-led elements limited to configuration and developer experience inside the bank. The transferable implication is that in regulated core-system markets, the vendor must sell migration certainty and reference proof before selling product innovation.
SUSTAINING MOATS
High Customer Lock-In
The moat is the bank’s dependence on Vault as the system of record for accounts, payments, ledgers, and product logic. Once customer accounts, transactions, and product configurations run on Vault, replacement requires a multi-year, high-risk migration. The moat strengthens as banks move more products, countries, and customer cohorts onto the platform; it weakens if deployments remain narrow or if migration costs prevent broader adoption.
| Why This Moat Lasts
Core-system lock-in lasts when the platform becomes the operational and regulatory system of record.
| Standard Rules
RULE 1 — SYSTEM-OF-RECORD DEPENDENCE: Accounts, payments, and ledgers cannot be replaced without a high-risk migration.
RULE 2 — CONFIGURATION DEPTH: Product logic, customer accounts, and payment flows accumulate inside Vault, increasing switching cost.
RULE 3 — TIER 1 VALIDATION: Deployments at Lloyds, Standard Chartered, ING, Intesa Sanpaolo, and JPMorgan Chase make the platform credible for other large banks.
| The Signal
Thought Machine reported 68 bank clients, including 18 of the world’s largest institutions, and crossed $100 million ARR in Q2 2026. The moat does not protect against a failed migration, regulatory incident, or incumbent modernization that reduces the perceived need for full core replacement.
ARR
JOURNEY
Pre-$1M ARR
BUILD THE MODERN CORE. From 2014, Thought Machine developed Vault Core as a cloud-native, API-first alternative to legacy banking infrastructure.
WATCH: banking-domain depth and platform reliability.
$1–5M ARR
WIN THE FIRST TIER 1 REFERENCE. Lloyds Banking Group became the first Tier 1 client, validating Vault for large-scale regulated banking.
WATCH: migration delivery and regulatory assurance.
$5–10M ARR
CONVERT REFERENCE VALUE INTO GLOBAL BANKS. Standard Chartered, ING, SEB, and other institutions adopted or evaluated Vault, expanding geographic reach.
WATCH: delivery capacity and customization control.
$10–50M ARR
SCALE THE ENTERPRISE MOTION. Thought Machine raised $83 million in Series B and built direct sales, implementation, and global engineering capability.
WATCH: long sales cycles and cash conversion.
$50–100M ARR
DEEPEN TIER 1 EXPANSION. The company raised $200 million in Series C at a $1 billion-plus valuation, with client banks participating; JPMorgan Chase later committed to moving its U.S. consumer core to Vault.
WATCH: migration sequencing and gross margin.
$100M+ ARR
PRODUCTIZE MIGRATION AND SCALE. Thought Machine surpassed $100 million revenue in fiscal 2025, grew ARR 59%, crossed $100 million ARR in Q2 2026, and reached 68 bank clients.
WATCH: whether migration becomes repeatable enough to sustain operating profitability.
BREAKDOWN
THE STANDARD
Enter a regulated core-system market by proving survival at the highest-stakes customer, then turn migration into a repeatable product capability.
THE SEQUENCE
1. Identify a legacy core that blocks the customer’s strategic product velocity.
2. Build a modern core with separated infrastructure, business logic, and product configuration.
3. Win one demanding reference customer and invest disproportionately in its successful deployment.
4. Convert the migration into reusable tooling, reconciliation workflows, and product templates.
5. Expand by product, geography, or customer cohort rather than promising a single disruptive cutover.
Lloyds validated Vault at Tier 1 scale, enabling Thought Machine to win subsequent global banks and reach $100 million ARR.