top of page
Business & Enterprise
Cloud Technology
iPaaS/Integration Platform
Make (formerly Integromat)
Built a profitable visual-automation platform by giving technical operators deeper endpoint access and workflow control than Zapier, despite competing in a category where integration breadth and AI-native automation are rapidly commoditizing.
1
MODEL
BUSINESS MODEL
PaaS
- Built a visual, no-code scenario canvas for multi-step workflows across apps and APIs. - Prioritized endpoint depth, data transformation, routers, filters and error handling over simple two-app triggers. - Offered a free tier and monetized through monthly credits consumed by each module action. - Expanded from individual automations to teams, templates, governance, on-prem agents and enterprise integrations. - Added AI agents, MCP server access and custom code execution, extending the platform from workflow automation to agentic operations.
1. Identify a workflow where users must connect systems that do not naturally exchange data. 2. Build the execution engine and integration layer before adding templates or marketplace features. 3. Make the visual interface powerful enough for technical operators, even if it requires a learning curve. 4. Meter the unit that reflects execution cost and customer value, such as module actions or credits. 5. Add collaboration, governance and enterprise controls only after individual builders prove retention. 6. The common mis-build is optimizing for simplicity before the platform can handle real operational complexity.
DISTRIBUTION MODEL
Make’s founders built internal integration systems for Czech enterprises before launching Integromat publicly in 2016. They prioritized a visual scenario builder, broad API endpoint coverage and complex workflow logic before investing heavily in sales, reaching $10 million revenue, 250,000+ customers and 375,000+ users while bootstrapped.
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Product-Led Growth, SEO, Community-Led, Partnerships
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Free plan: 1,000 monthly credits and unlimited users let builders test real workflows before paying. - SEO and comparison content: Make captures demand around automation, integrations and competitor alternatives. - Community and templates: Makers share scenarios, templates and use cases, reducing onboarding friction. - Partner and enterprise channels: Celonis, systems integrators and enterprise app partnerships extend Make into larger organizations.
What worked: Let users experience the full product through a generous free tier, then monetize execution volume rather than restricting core capability. Trap if copied blindly: Free automation can create high infrastructure cost and low-intent usage; the vendor must ensure free scenarios lead to recurring operational dependence or paid execution.
| PATTERNS OF THIS MODEL
PATTERNS IN USAGE-METERED AUTOMATION PLATFORMS: 1. EXECUTION-VOLUME ECONOMICS. Revenue scales with workflow complexity and frequency, but so does infrastructure and support cost. 2. BUILDER-LED COMPOUNDING. Each scenario, template and integration makes the platform more valuable to the next builder. 3. GOVERNANCE UNLOCKS ENTERPRISE. Teams adopt automation broadly only when permissions, auditability and security are available. THE WEAKNESS: Credit-based pricing can create bill shock and cause customers to optimize scenarios in ways that reduce platform consumption.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — PROCESS-MINING-NATIVE AUTOMATION. The opportunity is not merely connecting apps but discovering which workflows are slow, error-prone and worth automating; process intelligence can prioritize automation ROI. GOLDMINE 2 — GOVERNED AGENT OPERATIONS. Enterprises need AI agents with permissions, audit trails, rollback and human approval; automation platforms can become the control plane for agent execution. GOLDMINE 3 — OUTCOME-BASED AUTOMATION PACKAGES. Selling a completed workflow outcome—invoice processing, lead routing or ticket resolution—can capture more value than selling raw credits. THE PIT — CREDIT-ONLY PRICING. Customers may reduce usage, split workflows or move execution in-house to avoid unpredictable bills. THE SECOND PIT — INTEGRATION BREADTH WITHOUT RELIABILITY. Thousands of connectors create little value if authentication, error handling or API changes break production workflows. MOVE WITH CAUTION — Do not build a general automation platform without a clear owner for workflow reliability; otherwise support costs rise faster than credit revenue.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Make entered automation against Zapier, Microsoft Power Automate, Workato and Tray.io. It differentiated through a visual scenario canvas, broader endpoint access, complex branching and lower-cost execution, targeting technical operators rather than only simple task automation.
MARKET TYPE
Red Ocean
ENTRY STRATEGY
Brownfield Entry
WHY THEY WON
iPaaS and workflow automation is mature and crowded, with Zapier owning mainstream simplicity and enterprise platforms owning governance. Make’s opening was the underserved technical operator who needed more control than Zapier but less cost and complexity than enterprise iPaaS. The structural blind spot was that many tools optimized either ease of use or enterprise depth, not both. The transferable lesson is that a crowded market can be entered by serving the “power operator” between consumer and enterprise.
EXECUTION
Make entered by replacing custom integration work and simpler automation tools with a visual platform. Its initial bet was that technical users would trade a steeper learning curve for deeper control and lower execution cost. This required broad API coverage, reliable execution infrastructure and flexible data transformation. The founder-level lesson: brownfield entry succeeds when the entrant offers a materially better control-to-cost ratio, not merely a different interface.
FOOTHOLD STRATEGY
Wedge Strategy
Make’s initial wedge was complex multi-app automation for technical operators, agencies and operations teams. The pain was that Zapier was too limited for branching logic and custom integrations required developers. These users were reachable through SEO, no-code communities and product-led trials, and could pay because automation replaced manual operations. The path outward was teams, templates, enterprise governance and AI agents.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Make’s strongest campaigns convert a technical capability into a business outcome: fewer manual processes and faster operational execution. KEY LEARNING: A template library becomes a growth asset when each template solves a recognizable operational problem and exposes the platform’s execution value. HOW TO USE: Publish templates by role and process—finance ops, lead routing, support triage or inventory sync—and measure activation from template to active production scenario.
KEY LEARNING
THE STANDARD: In a Red Ocean, entrants win by choosing a distinct operator profile and changing the value metric from task count to operational leverage. RULE 1 — SEGMENT BY TECHNICAL DEPTH: Simple users want speed; technical operators want control, branching and error handling. RULE 2 — PRICING PRESSURE: Automation is increasingly commoditized, so vendors must monetize reliability, governance and AI execution. RULE 3 — SUCCESSFUL ENTRANT BEHAVIOR: They build a strong execution engine, then add collaboration and enterprise controls. RULE 4 — COMMON FAILURE: Competing only on connector count or price leads to thin differentiation and high support burden. MARKET TYPE: Red Ocean (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN PRODUCT-LED AUTOMATION GROWTH: 1. FREE EXECUTION AS ACTIVATION. Users understand value only after connecting real systems and running a scenario. 2. TEMPLATE-LED ONBOARDING. Prebuilt workflows reduce time-to-value and teach platform capability. 3. COMMUNITY-GENERATED DISTRIBUTION. Makers create tutorials, scenarios and integrations that attract new users. 4. THE WEAKNESS: Free users may consume infrastructure without converting if the platform does not meter execution carefully.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Brownfield entry is appropriate when existing tools are too simple or too expensive for the customer’s workflow complexity. RULE 1 — Target the capability gap: identify what users cannot do in the simple tool and will not pay enterprise prices to solve. RULE 2 — Build reliability before breadth: execution logs, error handling and API stability determine production adoption. RULE 3 — Make migration incremental: users should be able to automate one workflow without abandoning existing systems. RULE 4 — Reject the approach if the incumbent can add the missing capability quickly and the entrant lacks a cost or ecosystem advantage. Example: Airtable entered between spreadsheets and databases by serving teams needing structure without enterprise database complexity. Failure pattern: A powerful but unintuitive tool can win experts yet fail to expand into broader teams without templates and governance.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A wedge is a narrow, high-value automation use case that proves the platform’s control and economics. RULE 1 — Choose a workflow with recurring execution volume and measurable manual-effort savings. RULE 2 — Target builders who can create scenarios without vendor-led implementation. RULE 3 — Expand into teams and governance only after individual builders demonstrate production usage. RULE 4 — Failure occurs when the wedge is a one-time integration rather than a recurring operational process. Example: Zapier began with simple app-to-app task automation before expanding into broader workflow orchestration. Failure pattern: A free automation tool that attracts one-off projects can generate usage without durable retention.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Make prices by credits, where most module actions consume one credit and advanced AI features can consume more. Its plans range from Free with 1,000 credits to Enterprise with custom volume, overage protection and dedicated support; this aligns revenue with execution load.
REVENUE MODEL
Subscription, Usage-Based
PRICING MODEL
Freemium, Usage-Based Pricing, Tiered Pricing
WHY THEY WON
Customers pay a recurring platform fee and consume credits for each scenario action. Revenue expands with active scenarios, execution frequency, data volume, AI usage and enterprise seats. Margins depend on compute, API orchestration, data transfer, support and AI inference costs.
Make offers Free with 1,000 credits/month, Core from $9/month with 10,000 credits, Pro from $16/month, Teams from $29/month and Enterprise at custom pricing. Each module action generally costs one credit; advanced AI and code execution can consume more, and extra credits can be purchased in bundles.
TARGET AUDIENCE
Individual automation builders (Free/Core; app-to-app workflows); operations and RevOps teams (Pro; complex scenarios, execution logs and custom variables); agencies and multi-team organizations (Teams; collaboration, roles and templates); enterprises and process-intensive companies (Enterprise; SSO, audit logs, on-prem agents and custom integrations).
CUSTOMER BUYING BEHAVIOUR
The trigger is usually manual data transfer, disconnected SaaS tools, integration-project cost or a need to automate a recurring process. Builders test a real scenario, evaluate connectors and execution reliability, then expand from individual use to team-wide governance.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Customers pay for eliminated manual work and reliable operational execution, not for the number of apps connected. RULE 1 — PRICE THE ACTION, NOT THE SEAT. Credits reflect the actual work performed across systems and scale with workflow value. RULE 2 — MAKE THE FREE TIER A LEARNING ENVIRONMENT. Limited credits let users build real workflows while protecting infrastructure economics. RULE 3 — MONETIZE RELIABILITY AND CONTROL. Execution logs, priority processing, governance and enterprise integrations justify higher tiers. RULE 4 — WATCH THE USAGE-ANXIETY TRAP. If customers cannot forecast credits, they disable scenarios or over-engineer alternatives, reducing expansion. The buyer is really buying operational leverage; the credit-and-platform budget proves that value.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
Platform dependency: Automation depends on third-party APIs, whose pricing, authentication and rate limits can change without notice. Credit-price resistance: Customers may reduce actions, batch processes or move work to code to control spend. Commoditization: Zapier, Microsoft, Workato, n8n and AI-agent platforms compete on connectors, price and automation breadth. Support-cost risk: Broken production scenarios create urgent support demand and can erode trust. Enterprise sales complexity: Moving upmarket requires security, governance and implementation resources that can strain a product-led model. Funding/valuation: Integromat was acquired by Celonis in 2020 for roughly $100 million and rebranded as Make in 2022; standalone revenue and profitability are not publicly disclosed.
Where the model can break
4
MOTION
motion ge cs
Make’s free plan, self-serve signup, visual builder and template library support product-led adoption for individuals and small teams. Enterprise customers require sales, value engineering, security review and custom integrations, creating a hybrid motion.
GROWTH EXPANSION MODEL
Platform Expansion, Product Line Expansion
HOW THEY EXPAND
Make expanded from individual app automation into teams, templates, enterprise governance, on-prem connectivity, custom apps and AI agents. Its Celonis ownership added process-mining context and enterprise distribution, while the MCP server and AI toolkit extended it into agentic automation.
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Against Zapier, Make differentiates through deeper endpoint access, visual branching and execution control. Against Workato and Tray.io, it differentiates through lower-cost self-serve adoption and a broader maker community.
GROWTH ENGINE
GTM
Content Flywheel
A user builds a free scenario → the automation removes recurring manual work → the user adds more apps, branches and frequency → credit consumption rises → teams adopt shared scenarios and governance → enterprise expands into custom apps, on-prem systems and AI agents. The loop compounds when each new scenario becomes operationally embedded. It breaks if credits are exhausted, API integrations fail or the user cannot justify execution cost.
Make’s GTM is product-led at entry and enterprise-assisted at scale. Free self-serve usage and SEO capture builders; templates and community content reduce onboarding friction; Celonis, partners and enterprise sales expand into larger organizations. The transferable components are free execution, template-led onboarding and governance-led expansion; they require reliable infrastructure and predictable usage economics.
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is accumulated scenario complexity: connections, credentials, logic, error handling, execution history and team permissions. Once business processes run through Make, replacement requires rebuilding workflows and revalidating integrations.
| MOAT INTELLIGENCE
THE STANDARD: Switching costs last when automation becomes part of production operations. RULE 1 — WORKFLOW DEPTH: Multi-step scenarios encode business logic across systems. RULE 2 — OPERATIONAL DEPENDENCE: Scheduled, real-time and error-handled processes create replacement risk. RULE 3 — TEAM GOVERNANCE: Roles, shared connections and audit history increase organizational switching friction. THE SIGNAL: Make reports 3,500+ apps, 4,000+ companies and a visual builder with unlimited active scenarios on paid plans; the moat does not protect against API changes, AI-native platforms or customers rebuilding automations internally.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — BUILD THE EXECUTION ENGINE. The founders spent years building a visual integration system from enterprise integration work before public launch. WATCH: API reliability and scenario complexity. $1–5M ARR — PROVE PRODUCT-LED DEMAND. Integromat launched publicly in 2016 and grew through self-serve usage, SEO and community adoption. $5–10M ARR — SCALE WITHOUT EXTERNAL CAPITAL. By 2020, it reached $10 million revenue, 250,000+ customers and 375,000+ users while bootstrapped. $10–50M ARR — ENTER THE ENTERPRISE PATH. Celonis acquired Integromat in 2020, adding enterprise distribution and process-intelligence context. $50–100M ARR — REBRAND AND EXPAND. Make relaunched as a Celonis business unit in 2022, adding teams, templates and enterprise automation. $100M+ ARR — AI-AGENT EXPANSION. Make added Maia, AI Agents, MCP Server and enterprise governance; it now reports 3,500+ apps and 4,000+ companies, though standalone revenue is not disclosed. Rule: Build a reliable execution engine first, monetize real workflow usage, then add governance and AI only when production adoption is proven.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Build a reliable execution engine for a complex workflow, monetize actual usage, then expand into collaboration and enterprise governance. SEQUENCE: 1. Build the integration and execution layer before marketplace breadth; prerequisite: deep understanding of the customer’s technical workflow. 2. Use a free tier to prove real-world value; prerequisite: metering that protects infrastructure economics. 3. Add team governance and AI only after individual builders create production scenarios; prerequisite: reliable execution, logging and error handling. WORKED: Make’s endpoint depth, visual scenario builder and credit-based model attracted technical operators without a large early sales team. CAUTION: Do not copy the free tier without cost controls; do not prioritize connector count over reliability, because broken production workflows destroy retention.
bottom of page