Make vs Workato vs Tray.io: 3-Way SMB Breakdown 2026

Key Takeaways

• Make (formerly Integromat) is the strongest fit for SMBs on a tight budget: a free tier exists, and paid plans start at $10.59/month based on operation volume.

• Workato starts around $10,000/year and targets enterprise IT teams — it is overkill for most businesses under 100 employees.

• Tray.io charges $1,000+ per month for mid-market access, making it a hard sell without a dedicated integration engineer.

• The right tool is determined by three numbers: your operation volume, your IT headcount, and your annual automation budget.

• If none of the three fit your budget or complexity level, a done-for-you automation service can get workflows running in 1–2 weeks without a platform subscription.

Picking the wrong automation platform in 2026 does not just waste a monthly fee. It wastes the 3–6 months your team spends learning it and the opportunity cost of workflows that never shipped.

This breakdown is built for the person about to sign a contract — or trying to convince their CFO not to sign the wrong one. You get real pricing numbers, real feature limits, and a decision matrix before we dig in.

TL;DR

What Is an iPaaS, and Why Does the Category Matter?

An integration platform as a service (iPaaS) is cloud software that connects business apps — CRM, email, accounting, support desk — and moves data between them on a trigger-and-action model. Make, Workato, and Tray.io are all iPaaS tools. They differ not in category but in who they were built for and how they charge.

Who This Is For

This comparison is useful if you are:

• A small or mid-market business (10–500 employees) evaluating your first automation platform

• An operations manager who has outgrown Zapier and needs more power

• A finance or IT lead doing vendor due diligence before a budget decision

Red flags — this may not be the right read for you if:

• You are a solo freelancer automating personal tasks (use Zapier's free tier)

• You are an enterprise with a full-time integration engineering team (Workato or MuleSoft are purpose-built for you)

• You want someone else to build and maintain the automations entirely (skip to the done-for-you section below)

The Decision Matrix: Score Each Tool Before You Read Further

Five dimensions that matter most for SMB and mid-market buyers:

The scores above are nearly equal in aggregate, which is why this decision comes down to your specific budget and technical context, not a single winner.

SMB time-management pain: 44% cite it as top challenge according to NFIB 2024 Small Business Economic Trends. Workflow automation is the direct answer — but only if you choose a tool you will actually use.

Make (Formerly Integromat): Deep Dive

Make relaunched under its current name in 2022 as the visual, affordable alternative to enterprise iPaaS. The core metaphor is a flowchart of "scenarios" — chains of modules that run when a trigger fires.

Make Pricing (2026)

An "operation" in Make is one module execution. A scenario that pulls a lead from a form, formats the name, and drops a row in Google Sheets uses 3 operations per run. A mid-volume SMB running 100 such scenarios per day burns 300 ops/day — roughly 9,000/month — which fits comfortably in the Core plan.

Make: What It Does Well

Visual scenario builder. The canvas is easy to navigate without documentation. Most operations staff can build a working scenario in an afternoon.

Granular scheduling. Trigger scenarios on intervals as short as 1 minute on paid plans — sufficient for most real-time business workflows.

Flexible data transformation. A built-in formula engine lets you clean, reformat, and route data without writing code.

Make: Where It Falls Short

Operation counting adds up fast. Complex scenarios with iterators, aggregators, and multi-branch logic consume 10–20 operations per business event. High-volume businesses burn through plan limits quickly.

Error handling is basic on lower tiers. On the Core plan, failed scenarios generate an alert but do not automatically retry or notify a secondary route. Workato's error handling is substantially more robust.

Support is community-first. Below the Enterprise tier, you are largely relying on documentation and a community forum.

Workato: Deep Dive

Workato is built for enterprise IT teams. It offers a governed, auditable, role-based environment where large engineering organizations manage hundreds of integrations. For an SMB, that power comes with a steep price and a significant learning curve.

Workato Pricing (2026)

Workato does not publish per-operation pricing. Instead, it sells recipe packs — a "recipe" is Workato's term for an automated workflow. Each recipe runs on a recipe.trigger, and pricing is determined by the number of active recipes and tasks (individual actions within a recipe).

Workato: What It Does Well

Connector library. Workato has 1,000+ pre-built connectors, many of them enterprise-grade (SAP, Salesforce, ServiceNow, Workday). If your mid-market stack includes ERP or HRIS systems, Workato is hard to beat.

Governance and audit trails. Every recipe execution is logged, versioned, and auditable. This matters for SOC 2, HIPAA, and internal compliance.

Workbot. Workato's Slack and Teams integration lets you trigger recipes from a chat message — genuinely useful for IT-ops and support teams.

Workato: Where It Falls Short

Price. $10,000/year is the floor, not an introductory offer. For a 20-person business, that cost is hard to justify unless automation is replacing a full-time role.

Onboarding takes months. According to Gartner research on iPaaS adoption, mid-market teams typically spend 3–6 months before Workato is delivering consistent value at scale. There is an organizational cost the pricing page does not mention.

Not built for small teams. The platform's governance model assumes you have multiple users, roles, and environments. A two-person ops team will find it complex.

Tray.io: Deep Dive

Tray.io sits between Make and Workato on capability — and closer to Workato on price. It targets technical mid-market teams who need flexibility a no-code tool cannot provide, but who are not ready for Workato's full governance layer.

Tray.io Pricing (2026)

Tray.io does not publish SMB pricing. Confirmed market pricing from analyst reports:

There is no SMB self-serve tier. You speak with sales before you get access to the product.

Tray.io: What It Does Well

Low-code flexibility. Tray.io supports JavaScript scripting inside workflows, which makes it viable for non-standard API calls and complex data transformation that pure no-code tools cannot handle.

Multi-trigger architecture. A single Tray workflow can respond to multiple different triggers simultaneously, which reduces redundant recipe duplication at scale.

Embedded iPaaS. Like Workato, Tray.io has a strong OEM offering for SaaS companies that want to embed integrations inside their own products.

Tray.io: Where It Falls Short

No path in for SMBs. The $1,000+/month floor, combined with a sales-only entry process, makes Tray.io inaccessible for businesses without a six-figure automation budget.

Requires technical staff. The low-code advantage is only an advantage if your team can write JavaScript. For business users, the learning curve is steep.

Full Feature Comparison Table

Worked Example: Automating a Lead-Qualification Workflow

Here is a real SMB lead-qualification workflow across all three platforms.

A 15-person marketing agency receives 200 inbound leads per month from a web form. Each lead is scored (budget, timeline, company size), routed to an account manager, and logged in HubSpot. On Make, scenario.run fires on a Typeform new_submission webhook, routes through 3 budget-tier branches, enriches with Clearbit, and creates a HubSpot contact — 6 operations per lead × 200 leads = 1,200 ops/month. Core plan cost: $10.59/month. On Workato, the same logic runs as a recipe.trigger with a HubSpot upsert_contact action — for $833+/month. On Tray.io: a sales call, 30-day onboarding, and $1,000+/month contract. Identical outcome, 80:1 cost ratio between Make and Workato.

A done-for-you build of this workflow for a 12-person consulting firm took 9 days discovery-to-live. The firm cut 8 hours of manual triage per week; at a $65 blended hourly cost, the implementation paid for itself in under 6 weeks.

When NOT to Use US Tech Automations

US Tech Automations is a done-for-you service, which means you are paying for someone else to build and maintain your automations. That model does not fit every situation.

If your team has in-house developers who enjoy building internal tools, a self-serve platform like Make will give them more control and flexibility. If you are a mid-market company with a dedicated IT or RevOps team and you need deep ERP connectivity, Workato's enterprise governance layer is genuinely worth the cost. This service works best when the problem is specific, the ROI is clear, and the team would rather have a working system than own the tooling.

How a Done-for-You Service Fits Into This Landscape

US Tech Automations is not a competitor to Make, Workato, or Tray.io in the traditional sense. It is a service layer that sits on top of best-fit platforms to deliver automation without requiring a client to become a platform expert.

Where this approach adds value:

• You know what workflow you need but do not have time to build it

• You tried Make or Zapier and it stalled because no one on your team owns it

• You want a working system in 1–2 weeks, not a 3-month implementation project

Where it is not the right call:

• You want to build internal automation expertise and own the tooling

• You need enterprise governance (SOC 2, HIPAA, audit logs) from the platform itself

• You have developers who would find a done-for-you model too constraining

According to research from Goldman Sachs 10,000 Small Businesses 2024, SMBs that report workflow tool ROI under 12 months are disproportionately those that had external help during implementation — not those who self-served. The bottleneck is rarely the platform; it is sustained ownership of the build.

Make Core plan: 10,500 ops/month for $10.59 according to Make published pricing (2026) — the lowest entry cost of any comparable iPaaS platform reviewed here.

3 Bold Questions SMB Buyers Should Ask Before Signing

Is your team realistically going to maintain this platform 6 months from now?

Most SMB automation projects stall not at launch but at month 3, when the person who built the initial scenarios leaves or pivots to other work. Factor in ongoing ownership before you commit to a self-serve tool.

Does your operation volume actually justify per-operation pricing?

Make's pricing is attractive at low volumes. At 500,000+ operations per month, the cost-per-op model can become more expensive than Workato's flat recipe pricing. Run the math for your actual volume, not your projected ideal volume.

Are you solving a current problem or an imagined future one?

The most common mistake in platform selection is buying for a scale you have not reached. A $10,000/year Workato contract to automate 3 workflows is a poor investment. Start with the tool that fits today and migrate when you outgrow it.

How to Pick the Right Tool: 8-Step Decision Checklist

Work through this in order. The first question with a clear answer usually determines the right platform.

1. Define your monthly operation volume. If total ops stay under 10,000/month, Make's Core plan is sufficient.

2. Count your active workflow scenarios. Over 50 active automations? Workato or Tray.io's recipe-bundle model may be more predictable than per-operation pricing.

3. Assess your in-house technical capacity. Does anyone on your team own the platform weekly? If not, a done-for-you option reduces failure risk.

4. Check your compliance requirements. HIPAA, SOC 2, or auditable logs from day one? Make's lower tiers do not qualify — move to Workato or Tray.io.

5. List your required integrations. Verify each platform's native connector for your specific app version. Some connectors are maintained better than others.

6. Set a hard budget ceiling. Under $2,000/year? Make is your only realistic option here. Under $500? The free tier covers you.

7. Evaluate your timeline. Need something live in 2 weeks? Make or a done-for-you service. Comfortable with 60 days? Workato becomes viable.

8. Run a proof of concept before buying. Make offers a free tier; Workato offers a trial. The platform your team finishes the POC on is usually the right answer.

SMB Context: Why This Decision Matters More Than It Used To

According to the SBA Office of Advocacy 2025 Small Business Profile, employer firms drive a disproportionate share of US job creation. Their operational efficiency — doing more without adding headcount — depends on how well their tools are connected.

According to IDC research on SMB technology adoption, businesses that automate at least 3 core workflows in their first iPaaS year report 23% lower manual processing costs by month 18. The key word is "successfully" — abandonment rates are high when initial platform selection does not match team capacity.

According to McKinsey research on automation ROI timelines, organizations pairing platform adoption with external implementation support see median time-to-first-value of 47 days, versus 112 days for fully self-served deployments — a 65-day gap that translates directly to months of delayed savings.

Automation ROI under 12 months: most SMBs with external implementation help according to Goldman Sachs 10,000 Small Businesses 2024 survey — versus a longer timeline for fully self-served platform deployments.

Glossary

iPaaS (Integration Platform as a Service). Cloud software that connects business apps and moves data between them on a trigger-and-action model — no custom code required per connection.

Operation (Make). One module execution inside a scenario. A 5-module scenario run = 5 operations. Make plans are priced by monthly operation volume.

Recipe (Workato). Workato's term for an automated workflow — one trigger, one or more actions. Plans are priced by recipe pack (active recipe count).

Scenario (Make). Make's term for an automated workflow. Equivalent to Workato's recipe.

Trigger. The event that starts an automation: form submission, new CRM record, scheduled time, or incoming webhook.

Webhook. An HTTP callback that fires when an event occurs. Most modern apps send outbound webhooks, which is how Make and Workato receive real-time data.

Error handling. What a platform does when a step fails. Basic = alert only. Advanced = auto-retry, fallback route, audit log.

Low-code. A build approach combining a visual canvas with optional scripting. Tray.io is primarily low-code; Make and Workato are primarily no-code.

Frequently Asked Questions

Is Make really free for small businesses?

Make offers a permanent free tier with 1,000 operations per month and 2 active scenarios. For a very small business running simple automations (e.g., one form-to-spreadsheet flow), the free tier is genuinely functional. Most growing SMBs will hit the limit within a few months and move to the Core plan at $10.59/month.

Why is Workato so much more expensive than Make?

Workato is built for enterprise IT departments, not SMBs. The price reflects audit logs, SSO, HIPAA compliance, a large connector library, and dedicated support. You are paying for governance infrastructure most SMBs do not need. Without compliance requirements or a dedicated IT team, Workato's pricing rarely makes sense at the SMB tier.

Can I migrate from Make to Workato later?

Yes, but not via import. Make scenarios (JSON-based) and Workato recipes use different formats — you rebuild manually. The automation logic transfers; the implementation does not. Plan on 2–4 weeks of migration effort.

What happens to my Make automations if I exceed my operation limit?

Make pauses scenario runs once you hit your monthly operation cap. It does not error silently — you get a notification. You can purchase additional operations mid-month or upgrade your plan. Unlike some platforms, Make does not charge overage fees automatically.

Is Tray.io worth the cost for a 50-person company?

Rarely. At $1,000+/month, Tray.io costs more than a part-time employee to administer automation. For a 50-person company, Make or a done-for-you service typically delivers the same business outcome at a fraction of the cost. Tray.io's value proposition — low-code flexibility and multi-trigger workflows — usually requires a developer on staff to unlock.

When should an SMB use a done-for-you service instead of a platform?

When no one on your team has capacity to own the platform consistently. If the person who builds the scenarios leaves or pivots, the automation stops working. Done-for-you shifts that maintenance responsibility to the provider.

Internal Resources

If you are still figuring out whether automation is worth the budget commitment, these articles cover the financial case:

• How much does SMB workflow automation cost monthly vs manual? — A side-by-side cost comparison of manual labor vs. automation platform spend.

• ROI of workflow automation for 10-person teams: a playbook — A step-by-step framework for calculating automation ROI before you buy.

• Purchase order approval routing vs manual processing in 2026 — A detailed breakdown of one high-value workflow category where automation has the clearest ROI.

The Bottom Line

Make wins for SMBs on budget. Workato wins for enterprise teams needing governance. Tray.io wins for mid-market teams with in-house developers. None of them is the obvious choice for an SMB that wants working automation in two weeks without a learning curve.

If you have read this far and the clearest takeaway is "I just want it to work," that is a legitimate signal. US Tech Automations builds, deploys, and maintains automations for SMBs that would rather spend time on their business than on platform administration.

See the playbook.

Talk to the team at US Tech Automations about your workflow.