top of page

Can Trial Pricing work in Logistics & Supply Chain Technology with operational risk?

Logistics software gets purchased after a costly failure, so a trial should resolve an actual shipment, inventory or hiring workflow rather than show a feature list. Veeqo gives sellers free core shipping functionality and sells additional inventory capability; Tenstreet uses tailored enterprise pricing based on fleet and recruiting scope. Neither proves a fixed-duration Trial Pricing offer here. A warehouse that connects one channel may still suffer overselling elsewhere; a carrier cannot assess driver compliance from a fabricated application.

See how top FinTech companies built an enterprise sales motion, and how they made that call, in Business Core.

✓ Skip the success story. Get the decisions behind it  ✓ Not a case study. A teardown you can copy from.

Business Core breaks down top FinTech companies' motion, from go-to-market and expansion to the moat, so you can see what each one built and why it held.

40 Foundational Decisions

34 Model Frameworks

80 Strategy Patterns

4 Pillars of any Business

Backed by evidence
On which a company is built on
Of proven growth & expansion 
Model · Market · Money · Motion

✓ Find relevant precedents in under 2 minutes   ✓ Updated every 6 months    ✓ 6 ARR stages, from pre-$1M to $100M+

Pick a decision or a strategy.
Go deep on companies that made it

Your exact comparables, one filter away.

The companies you study didn't build by instinct alone.
Neither should you.

Stop studying companies that never faced your call.
Famous case studies won’t fit your decision. These will.

​

With a Situation or Strategy you need insight on

​

Open results to see exactly how they did it - and how you can do the same.​

​

The framework walks you through every layer of how the company was built, grown & sustained big

Product & Business Model Decision
Business Model

Red Ant

Fal.ai

Duolingo

Clay

Medallia

Brex

Harvey

Wedding Planning Assistant

Bridgit

Whova

PlannerHub

ClickHouse

Melio

✓ Get the Full list of companies under each   ✓ Unlock in-depth intel on each company
From “what should we do?” to a written plan in one sitting

DISTRIBUTION MODEL

What makes an enterprise sales motion different in FinTech than in other software?

Because the buyer is guarding money, risk and regulation, a FinTech enterprise deal has more people in the room and a longer path to go-live than a normal software sale. Banks and treasury teams involve technology, risk, compliance, product and procurement before anyone signs. I'd plan for implementation to be part of the sale, not something that happens afterwards.

Why do FinTech enterprise sales cycles take so long to close?

• Too many stakeholders have a veto. A core-banking or treasury purchase pulls in CIOs, CTOs, risk, compliance, product and procurement, and any one of them can stall it.

• Switching cost is real. Replacing a legacy ledger or a treasury system means migrating live money flows, so buyers want a staged, scoped migration rather than a big-bang cutover.

• Security and regulatory review comes before commercial discussion. Build your evidence pack for that review early, not after the demo goes well.

• Plan for proof-of-value first. Treasury and finance leaders usually want a pilot that shows a measurable return before they commit a multi-year contract.

• Be honest about what a self-serve funnel can do here. Kyriba's research notes say plainly that self-serve doesn't fit its buyer, because implementation is complex and multi-stakeholder.

Which FinTech companies built enterprise sales motions around complex buyers?

Look at who sits on the buying committee in each case, because that tells you what the motion has to handle.

• Kyriba sells to treasury and finance leaders at mid-size and large companies, and its bank and ERP partnerships supply qualified pipeline.

• Thought Machine runs a structured process with bank CIOs, transformation leaders, risk, compliance, product and procurement, combining direct sales, Tier 1 references, analyst relations and implementation partners.

• Soldo sold spend-control software to enterprises including Mercedes-Benz, Sony and Toyota, with finance, procurement, IT, security and ERP integration all involved.

• Soldo's route is a useful contrast: it moved from small-business cards to enterprise governance rather than starting at the top.

How did FinTech companies prove an enterprise sales motion was worth building?

They proved it with one demanding customer and one measurable result, not with pipeline volume. Thought Machine put heavy effort into Lloyds Banking Group and used it as the Tier 1 reference. Kyriba used proof-of-value pilots with an ROI framework. The lesson is to earn one reference that other buyers in your market recognise.

How do I get a first enterprise reference customer in FinTech?

• Shipments completed with correct inventory deduction.


• Verification time for a qualified driver application.


• Use a contained operational lane: one channel-to-shipment flow or one verified driver application, with a rollback path and signed success criteria.

What did Kyriba, Thought Machine and Soldo do to prove their enterprise case in FinTech?

Each company proved the case in a different place, so compare the proof rather than the product.

• Kyriba was founded in 2000 around cash visibility and risk for multinational companies, then launched cloud-based cash management and built adoption through direct sales.

• Thought Machine began developing Vault Core in 2014 as a cloud-native, API-first alternative to legacy banking infrastructure; Lloyds Banking Group became the first Tier 1 client.

• Its 2022 Series C was funded directly by Tier 1 client banks, which is about as strong a signal of customer belief as a vendor can show.

• Soldo started in 2015 with prepaid Mastercard cards and rules, signed its first customer in 2017, and then proved that decentralised teams could spend within limits before moving up to enterprises.

Which enterprise sales choices did FinTech examples like Kyriba and Soldo make?

They chose to enter through a narrow, high-friction workflow and sell it to a senior owner, instead of pitching a broad platform. Kyriba chose treasury cash management for complex multi-bank groups. Thought Machine chose the core ledger. Soldo chose spend control for teams that were leaking money. Each then expanded from that foothold.

How do I choose which FinTech buyer to sell to first?

• Choose the buyer who owns the pain and the budget. In treasury that's usually the treasury leader; in spend control it's the finance leader.

• Start where the workflow is narrow enough to deliver completely. Kyriba's notes describe building the narrowest complete capability and expanding into adjacent modules only after the core is reliable.

• Let the first deployment be one team, one category or one entity, then spread. Soldo's adoption often begins with one team or spending category before growing across the company.

• Decide early whether you need partners. Kyriba leans on bank and ERP partnerships for qualified pipeline, and Thought Machine uses implementation partners.

• Price for the buyer's footprint. Kyriba's core cash and liquidity for 10 to 50 entities is typically $75,000 to $200,000 a year, so price follows entities and banks.

Which FinTech companies chose multi-year contracts or modular pricing for enterprise buyers?

Pricing shows what the company believes the buyer is paying for.

• Thought Machine uses negotiated contracts of three to five years, with an annual platform fee paid in advance and account-based usage pricing above a threshold.

• Kyriba uses modular, subscription-based pricing that scales with the customer's treasury and banking footprint.

• Soldo publishes tiered monthly plans, with an entry plan from £27 a month and a fixed 1.5% foreign-exchange fee, and customises enterprise pricing.

• The difference is clear: the further up the market, the more pricing moves from a price list to a negotiated contract.

How to build an enterprise sales motion in FinTech

Start with one workflow where a large buyer's current tools create risk, cost or delay, then build the narrowest complete product that fixes it. The first decision is which reference customer you can win and deliver well, because everything after that borrows its credibility. The caution to respect is that enterprise adoption doesn't convert into fast growth: long sales cycles and implementation cost can slow you down, and expanding into too many modules too early leaves you as a thin layer against better-distributed rivals.

Business Core shows each company's go-to-market, expansion strategy and how-to-copy steps, so you can see how enterprise motions were sequenced.

Check the revenue risks and cautions behind each enterprise approach in Business Core, such as implementation cost and customer concentration, before you hire your first sales team.

1-model (6).png

Which FinTech revenue risks come with building an enterprise sales motion?

Customer concentration, implementation cost, pricing pressure from bundled incumbents and module sprawl. Large accounts dominate the book, so losing or renegotiating one hurts. Deployment is slow and expensive, and legacy vendors can package comparable features with wider distribution. Set your plan so no single contract can break the year.

How do I limit the revenue risk of a few big FinTech customers?

• Track concentration from the first big deal. Kyriba's notes flag that large enterprise customers dominate the book, so a few churns or renegotiations can move the whole line.

• Convert custom migration work into reusable assets. Thought Machine's risk list says custom migration and regulatory assurance can squeeze gross margin if not productised.

• Add modules only when the core is reliable. Expanding into too many modules increases maintenance and dilutes the original edge.

• Watch the delivery calendar. Core-banking programmes can run for years, and delays push back usage-based revenue.

• Price the cost of serving, not only the licence. Soldo's notes warn that ERP mapping, permissions and change management raise cost-to-serve.

Which revenue risks did Kyriba, Thought Machine and Soldo face in FinTech?

The risks follow from how each company sells, so read them as a checklist for your own plan.

• Kyriba: revenue concentration, high implementation cost, competitive pricing pressure from SAP Treasury and FIS Quantum, and module sprawl.

• Thought Machine: migration delay, Tier 1 customer concentration, implementation intensity and incumbents such as Temenos, FIS and Fiserv modernising their existing cores.

• Soldo: implementation drag, interchange and foreign-exchange pressure, enterprise concentration and accounting platforms adding cards, approvals or bill pay.

• Taken together, the pattern is that the same size of customer that makes the deal attractive also makes the revenue fragile.

How do FinTech buyers react when a vendor tries to sell to the enterprise?

They slow down, ask for proof and bring in more people. A treasury leader names a pain point such as cash visibility, FX risk or fraud, compares you with legacy systems and spreadsheets, and wants a pilot that shows return. Larger buyers then add procurement, security review and multi-year contract terms. Your job is to make each of those steps easy to clear.

How do I handle a FinTech buyer who wants a pilot before they sign?

• Say yes, but scope it. Agree the question the pilot answers, the data it uses and the date you'll both decide.

• Tie the pilot to an ROI frame the buyer can take to their CFO. Kyriba's process runs on proof-of-value and ROI, not on feature lists.

• Bring implementation capacity with you. A pilot that stalls for lack of integration help looks like a product failure.

• Have your security and compliance pack ready on day one, so review runs in parallel with the pilot.

• Offer a clear path from pilot to contract: which modules, which entities, which term. Without it, a successful pilot can still drift.

How did buyers of Thought Machine, Kyriba and Soldo decide in FinTech?

The buying path is where an enterprise motion either works or stalls, so note the trigger and the first step.

• A bank usually starts with a strategic core-modernisation review, evaluates architecture, security, regulatory fit and migration capability, then runs a scoped migration, with adoption widening as it works.

• A treasury leader identifies a pain point, evaluates Kyriba against legacy systems and spreadsheets, and commits after a proof-of-value pilot; larger enterprises add procurement and security review.

• A finance leader evaluates Soldo after expense leakage, reconciliation delays or a control problem, then starts with one team or category.

• In all three the first deal is small or scoped, and the larger contract follows the evidence.

What did FinTech companies get wrong when they tried to sell to enterprises?

They sold the technology without the migration, or the flexibility without the configuration. Thought Machine's caution is not to sell modern architecture without migration economics, and not to let every bank fork the product. Soldo's is not to sell enterprise flexibility without productised configuration, and not to rely on cards alone.

Which mistakes should a FinTech startup avoid in its first enterprise deals?

• Don't promise custom controls for every buyer. Soldo's notes say custom controls can destroy margin if they aren't productised.

• Don't let each customer fork your product logic. Thought Machine's caution is that this recreates the legacy complexity you were selling against.

• Don't assume enterprise adoption means quick growth. Kyriba's caution is that long sales cycles and implementation cost slow expansion.

• Don't make one feature the whole product. A card on its own is easy to copy without budgets, auditability and accounting integration.

• Don't add modules before the core is dependable, or you'll compete as a thin layer against better-distributed vendors.

Which pits and cautions apply to FinTech enterprise sales at Kyriba, Thought Machine and Soldo?

Each caution names the move that would weaken that company's own motion.

• Kyriba's pits: implementation cost, where long deployment cycles slow growth and raise churn risk, and module sprawl.

• Thought Machine's pit: modern architecture without migration economics, which can win technical evaluations but fail commercially if migration consumes the customer's transformation budget.

• Soldo's pits: card issuing as the entire product, which becomes commoditised without budgets, approvals and reconciliation, and enterprise flexibility that outruns configuration.

Enter business core

Does Business Core show how companies built their go-to-market?

Yes. The Motion pillar covers each company's expansion, competitive strategy, growth engine and go-to-market, and each pillar opens with the founder decision the company faced.

Does Business Core list the revenue risks that sit behind a sales approach?

Reliable recruiting or verification under the carrier’s real operating requirements.

Can I filter companies by the founder decision they faced?

Yes. Founder decision is one of the filters, and each matching company opens on its own page for you to read and compare.

Does Business Core include steps I can copy?

Yes. Each company page ends with how-to-copy steps: the standard to follow, the sequence of steps and a caution.

Business Core
Everything You Need To Build a Winning Business

Own the
playbook of companies 

that won

One-time payment · No subscription · No seat fees

Lifetime Access

Business Core

$180

180

​

​

Valid until canceled

SSL Secure Checkout. Instant access.

Companies broken down on the same 56 fields 

Filter by 40 decisions carried out by SAAS Cos.

114 model & strategy labels executed by Top Cos.

See what worked, failed and why

Leave with an ARR-stage replication blueprint

Turn proven patterns into your own strategy

​​​​

Your Business Core access is automatically added to your account on purchase.

The strategic intelligence gap closes the moment you open it.

Walk in with the decision; Walk out with companies that already made it - Here's what's INCLUDED :

MODEL

• Business Models  • Distribution Model  • Model Insights  • How to Apply it  • Opportunities & Risks

MARKET

• Market Type  • Market Entry & Foothold Strategy  • Growth Model  • Market Intelligence  • Playbook

​

MONETIZATION

• Revenue & Pricing Model  • Target Audience  • Customer Buying Behaviour  • Patterns  • Pricing Intel

MOTION

• Competitive Strategy  • Growth & Expansion Strategy • GTM Summary  • Growth Engine  • Sustaining Moats

​

bottom of page