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 cloud infrastructure companies like Koyeb expanded into serverless GPUs, in Business Core.

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

Business Core shows the ARR journey of top cloud companies stage by stage, so you can see how each one grew from $1M to $10M ARR.

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

Xero

LeadSquared

Requity Homes

ClearCompany

Bridgit

Semrush

Slack

Exercise.com

UserGems

Hightouch

ServiceTitan

Databricks

WalkMe

✓ 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

How can a smaller cloud platform win AI teams against hyperscalers and GPU clouds?

Combine a simple deployment experience with prices developers can compare directly. Koyeb's H100 rate of $2.50 an hour is below many serverless GPU offers, for example Modal's per-second H100 price works out at about $3.95 an hour, and developers can see that difference in a pricing calculator before they deploy anything.

Price alone isn't enough, though. Specialised GPU clouds also compete on hourly rates, so Koyeb's pitch paired lower prices with the same deploy-in-seconds, autoscaling experience it offered for containers.

Which growth channels suit a serverless GPU platform between $1M and $10M ARR?

• Published GPU prices and a pricing calculator, so AI teams can compare costs with other platforms before signing up.

• Comparison pages against hyperscalers and GPU clouds, which catch developers researching where to run inference.

• Quickstarts for popular AI models, taking a team from model to live endpoint in minutes.

• AI agent sandbox positioning for short-lived, secure compute, a new workload that fits serverless billing well.

How did Koyeb's GPU pricing and AI positioning bring in new teams?

Koyeb's campaigns at this stage paired AI positioning with clear, lower GPU prices.

• AI inference positioning across CPUs, GPUs and accelerators as generative AI demand emerged.

• Serverless GPU price cuts to $0.70 an hour for L4, $1.20 for L40S, $1.60 for A100 and $2.50 for H100.

• Pricing calculators, quickstarts and comparison pages for developer-led adoption.

• AI agent sandbox positioning for ephemeral, secure compute.

What did cutting GPU prices do to Koyeb's risk?

It made utilisation the deciding number. Lower hourly rates attract more AI teams, but serverless GPU demand is spiky, so if GPUs Koyeb operated sat idle between bursts, the lower price left little margin to absorb the cost.

Price pressure didn't stop either. Specialised GPU clouds and hyperscalers could cut their own rates, a few high-volume inference customers could dominate capacity, and teams still expected instant scaling without paying to keep GPUs warm.

How should a GPU platform protect margins after cutting prices?

• 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.

How did lower GPU prices change Koyeb's margin risks?

These risks grew as Koyeb added GPUs and cut prices to win AI teams.

• GPU utilisation risk, as serverless GPU demand is spiky and idle capacity can destroy margin.

• Price pressure, since specialised GPU clouds and hyperscalers can undercut raw hourly rates.

• Workload concentration, because a few high-volume inference customers can drive revenue but also capacity and support load.

• Cold-start expectations, as customers may expect instant scale without accepting warm-capacity costs.

What did Koyeb avoid while adding AI workloads?

It avoided reserved GPU contracts and long commitments for customers. Per-second billing with no commitment kept the serverless promise, even though reserved deals would have made capacity easier to plan.

It also kept GPUs on the same platform as containers, rather than launching a separate GPU product. Developers used the same console, CLI and deployment flow, which made AI a feature of Koyeb rather than a different service.

Why should a serverless platform add GPUs to its existing product, not a separate one?

• Developers already know the deployment flow, so adding GPUs to it removes the learning curve.

• One platform lets teams run their app and their model together, which is simpler than two providers.

• Shared scheduling and routing spread engineering costs across every workload.

• A separate product would compete for attention with the core platform and confuse the message.

How did Koyeb layer AI workloads onto its platform?

The order shows GPUs and accelerators being added to the same deployment and billing model.

• Serverless containers with global autoscaling and self-serve tools came first.

• GPUs, accelerators and AI inference positioning were added as generative AI demand grew.

• GPU prices were cut, with H100 falling to $2.50 an hour, and agent sandboxes were positioned for secure compute.

• Pro, Scale and Enterprise plans for production teams followed.

Adding serverless GPUs at $1–10M ARR, as Koyeb did

The principle is to add specialised workloads only when they reuse the platform, with the gate being that each addition improves retention or account value without undermining unit economics.

For Koyeb, that meant serverless GPUs and accelerators on the same container platform, with H100s at $2.50 an hour.

The caution is not to add GPUs before proving utilisation and workload demand, and not to market scale-to-zero without being clear about cold starts and warm-capacity costs.

Business Core gives each company's ARR journey, growth campaigns and how-to-copy steps, so you can see how platforms added AI workloads.

Read the caution in each how-to-copy plan in Business Core before you cut prices on expensive hardware.

1-model (6).png

What told Koyeb it was time to build paid plans for production teams?

Teams running important workloads and asking for governance, support and predictable costs. Once AI inference and production apps ran on Koyeb, companies needed role controls, higher limits and someone to call when something broke, which free and pay-as-you-go use didn't offer.

That pointed to the Pro, Scale and Enterprise tiers, which turned usage from teams already in production into recurring plan revenue.

Which signals show a usage-based platform needs paid team plans?

• Several engineers from the same company use one account, and they ask for roles and access controls.

• Production workloads make up a growing share of usage, raising the need for support and uptime guarantees.

• Customers ask for predictable bills, which a plan with included compute can provide.

• Larger companies arrive through developers and need governance before their security teams approve the platform.

Which companies added team plans on top of usage billing?

These examples show companies combining usage-based billing with plans for teams.

• Koyeb added Pro, Scale and Enterprise plans on top of per-second compute billing.

• Modal added a $250 Team plan and custom enterprise pricing on top of per-second compute.

• Spendesk combined a fixed platform fee with transaction-based fees.

• Team plans add steady revenue to usage that rises and falls.

How did Koyeb's activation rule guide its AI expansion?

In serverless infrastructure, prove activation and retention before adding specialised capacity that increases fixed costs. Koyeb added GPUs only after its container platform had shown developers would deploy and stay, so AI workloads arrived on a platform with proven adoption.

The rule's second half still applied: every GPU added raised fixed costs, so utilisation had to keep pace with each new rack.

How do you add expensive capacity without breaking the rule?

• Add hardware in stages tied to real demand, rather than buying ahead of what customers have shown they need.

• Start with GPU types your existing users ask for most, so new capacity fills quickly.

• Measure contribution margin per active compute hour, not just revenue, to see whether each GPU pays for itself.

• Keep billing per second with clear prices, so customers can start small and grow usage over time.

Which companies added capacity in step with demand?

These companies grew expensive capacity only as fast as their users' workloads.

• Koyeb added GPUs as developers began running AI inference on its platform.

• Modal scaled multi-cloud GPU capacity as enterprise and agent workloads grew.

• Flywheel strengthened hosting operations as agencies moved whole portfolios onto it.

• Matching capacity to demand protects margins when usage is uneven.

What do serverless GPU platforms get wrong at $1–10M ARR, and how did Koyeb avoid it?

Many buy large amounts of GPU capacity ahead of demand to look competitive, then carry the cost when usage is spiky. Others compete on price alone and end up with thin margins and no reason for customers to stay when someone cheaper appears.

Koyeb added GPUs to a platform developers already used, paired lower prices with a simple deployment experience and kept billing per second.

Why do GPU platforms struggle with profitability?

• Demand is spiky, so expensive GPUs sit idle between bursts of usage and cost money without revenue.

• Price wars with specialised GPU clouds push hourly rates down faster than costs fall.

• A few large customers can dominate capacity, leaving the business exposed if they leave.

• Customers expect instant response but resist paying for capacity kept warm for them.

Which companies paired competitive prices with a simpler experience?

These examples help you decide whether to compete on price, ease of use or both.

• Koyeb paired $2.50-an-hour H100s with deploy-in-seconds serverless containers.

• Modal paired per-second GPU billing with a Python SDK that removed infrastructure work.

• TaxJar paired self-serve prices with automated filing for online sellers.

• Price wins attention, but simplicity is what keeps customers when rivals cut prices too.

Enter business core

Does Business Core show how companies grew from $1M to $10M ARR?

Yes. Each company's ARR journey covers its focus at each stage, including the $1–10M range, with the decisions behind it.

Can I compare GPU pricing between infrastructure companies?

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

Does Business Core show price cuts in a company's journey?

Yes. The ARR journey and growth campaigns note pricing changes where they shaped growth.

Can I see workload concentration risks?

Yes. Each breakdown lists revenue risks, including dependence on a few large customers where it applies.

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