Midjourney
The community was the demo, classroom and distribution channel
89 companies: 1 extended case, 73 source-backed briefs and 15 evidence briefs. Also classified Product Led 60, Human Led 51, Partner Led 21. [Inference] These companies share a research classification. The details and boundary conditions vary by segment and period.
The customer buys through the marketing experience without a salesperson closing the deal. Content, paid media, or a creator campaign can also support other motions, so a channel name alone does not settle the classification.
Marketing creates the purchase without a salesperson closing it, commonly through ecommerce. (The Revenue Engine, manuscript pages 32–33)
Subtypes direct response · ecommerce · paid acquisition · content to checkout
How we classify the four GTM motions Understand Your GTM Motion Options
Often appears with Land and expand (18) Community (8) Freemium (7) Developer tools and communities (6) Technical customer success (6) Education (5)
The community was the demo, classroom and distribution channel
A founder-recruited pilot became a team-by-team adoption engine
A simple meeting experience fed distinct self-serve, inside-sales and field-sales routes
The shared file became distribution; the paid plan became a capacity and workflow upgrade
A failed app builder found a recognizable entry point in documents
Designer advocates translated product love into organizational adoption
The AI pivot changed the first useful moment, then enterprise demand changed the sales motion
A low-friction research bundle converted a beta community, then needed agency-specific workflows
Product-demonstrating education carried a data product before a sales team appeared
Self-service acquisition fed a sales organization designed largely for expansion
A minimal willingness-to-pay test preceded content-driven distribution
An agency’s internal dashboard became a free product, then a business workflow
Founder networks proved the pipeline, then marketplaces and onboarding widened adoption
An agency's own coordination problem became a product clients could carry elsewhere
Turn anonymous account interest into a platform sale
Pre-sell the handoff problem, then earn influential references
[Inference] Create a business-model category, then build the field organization to implement it
[Inference] Teach the future buyer at university, then scale inside sales into an enterprise platform
[Inference] Sell a small analytical win, then build the governance needed for enterprise expansion
[Inference] Build the audience before the product, then prove marketing can create revenue
[Inference] Sell an immediately understandable employee workflow, then expand through a shared data platform
[Inference] Win content adoption, then connect enablement to revenue performance
[Inference] Follow the budget owner from rep productivity to forecast accountability
[Inference] Finance a valuable data asset through focused founder selling, then specialize the revenue engine
Operational expertise and a sharply simpler developer offer created a wedge in cloud infrastructure.
Developer trials needed a manager’s mandate and founder-built trust to become team purchases.
Developers supplied adoption; security teams supplied the budget.
Targeted outbound found demand; real-time technical help made inbound trials survive.
Manual onboarding established repeat use before a public launch; transparent consumption pricing followed.
Consulting exposed a repeatable analytics job; practitioners and service partners carried the tool to new companies.
An existing developer audience solved the community cold start; commercial buyers came through different products.
Curated participation came before software; the valuable audience later supported paid promotion.
The founders invited a gaming community to give live feedback, then monetized enhanced participation.
Category education was paired with a measurable customer operating system
A provocative category message made the delivery-model change memorable
From a Bay Area delivery wedge to retailer infrastructure
Local marketplace density governs the promise
A differentiated seller community becomes the product
Trust infrastructure followed a surprisingly small first transaction
Books created a focused starting point for a broader commerce ambition
Standardized gigs lower buying friction; larger jobs change the motion
Local support accompanied international demand expansion
A Microsoft launch became a multi-brand travel system
Free property information created the entry point
Matching a project to a professional creates two customer journeys
Transparent bidding meets a trust-intensive resale category
Seller experience is an explicit founding leadership function
A Malaysian taxi-safety wedge preceded the superapp
Payments and logistics emerged from marketplace obstacles
Shopee’s early growth was financed inside a broader platform group
Customer communications became part of service reliability
Flexible supply depends on host economics and traveler trust
Restaurant software and diner demand reinforce different sides of the sale
Audience adoption and advertiser conversion are different GTM systems
A failed college project preceded the disappearing-photo experiment
Grassroots audience building preceded scale
Service design and postage economics mattered before streaming
A founder audience jump-started experimentation; retention drove the next stage
A clear fee proposition lowered the barrier to first investing
A tiny demonstration of calm became an acquisition idea
In-person teaching revealed the need for an at-home product
Five cyclists mattered before the next million users
Campus concentration supplied the early network
The company reset its objective from engagement to dates
The first retailer changed the required product
Begin where early technology costs can be absorbed
Sell the class experience, then build the delivery system around it
Crowdfunding established a narrow proposition before enterprise expansion
Trusted trainers opened doors; pricing lowered the next barrier
Embeds supplied distribution before the audience was monetized
Core accounting and unit-based pricing removed two adoption barriers
Tie the consumer promise to transaction activity instead of overdraft fees
A cross-border spending wedge expanded toward everyday finance
Use the smartphone shift to challenge an incumbent banking experience
A household problem became financial software at scale
A faster loan journey in an established market
Customer demand for control changed the offer
Condition-specific services broadened into a care brand
Household administration is the product boundary
A narrow care market funds a broader stated ambition
Creators bring both supply and distribution
Unused wardrobes become local marketplace supply
Curation makes an overwhelming category shoppable
Free scheduling built supply before marketplace monetization
An integrated visit makes complex sensing tangible
Recurring payments create a different growth denominator
A new discovery channel creates a measurement problem
Education and qualification focus the restaurant sales engine
Teaching lawyers supplied the early feedback channel