The AI orchestration platform you can start with now is one where a second person can take over, recover, and explain your first task: Make or Zapier for a manageable chain with someone to maintain it, Microsoft Copilot Studio if you already have a Microsoft administrator, n8n Cloud with a skilled builder, self-hosted n8n only with a permanent technical administrator, and a configured product such as Bombos if you do not want to build workflows at all.
This page is for a business without an IT department. It provides no ranking, because none exists without your task and your people. It provides starting criteria: what you can do now, what should wait, what an approval step actually does, starting costs per completed task, and how to avoid lock-in. All sources were opened on September 30, 2026. All except CBS sell software themselves. Product features below come from the makers’ documentation. We have not tested them in our own accounts.
The short answer
- Who maintains the system determines your starting choice more than the builder interface. n8n lists Cloud maintenance as “Handled by n8n” and self-hosting as “Your responsibility”. n8n, September 30, 2026
- A free trial is not a working start: the Copilot Studio trial lets you build and use test chat, but “you can’t publish the agent”. Microsoft Learn, updated August 3, 2026
- Make says its new agent feature is “in open beta, so product functionality and pricing may change”. Make, February 2, 2026 version
- Approval is only safe if rejection and no response do not trigger execution. In Zapier, the builder can configure the workflow to continue after rejection, and the run still says “Success”. Zapier, updated May 29, 2026
- Entry prices range from free to € 173,30 per month: n8n Starter € 20 with annual billing, Make from $ 9, Zapier Professional from $ 19,99, and Copilot Studio € 173,30 for 25,000 credits. All four count different units. n8n, Make, Zapier, Microsoft
- All four support export, but always to the same product and with limits. Zapier requires Team or Enterprise. Make requires files under 2 MB and recreated connections. Zapier, Make
- AI use among small Dutch businesses rose from 11 percent in 2023 to a provisional 27 percent in 2025. Those that considered it but did not adopt it mainly cite “lack of experience” (73 percent, translated). CBS, December 12, 2025
- Start with one bounded task, proposals, and approval. Postpone self-hosting without an administrator, broad write permissions, and chains without a recovery route.
What is an AI orchestration platform, and which types can you buy now?
An AI orchestration platform connects the steps of a task: something arrives, an AI step reads or decides, a system is updated, and a person approves. “Orchestration” means directing those steps, including who does what when and what happens if something goes wrong.
For a small or midsize business, that term covers roughly three types of offer. First, building platforms where you or a builder draws the chain: Make, Zapier, and n8n. Second, a building environment within a large ecosystem: Microsoft Copilot Studio, which relies on your Microsoft 365 environment and permissions. Third, configured products where a vendor sets up the chain around your task and your team then approves and corrects, such as Bombos.
Zapier’s own overview also includes developer tools, data tools, and cloud infrastructure in the category. Zapier, January 9, 2026 Those immediately fall away for you. The remaining question is who builds the chain and who keeps it running.
Within its product, Make distinguishes a fixed workflow, a workflow with one AI step, and an agent that decides for itself with changing inputs. It advises against the last option for high-risk financial decisions and sensitive data, among other uses. Make, February 2, 2026 version A chain where AI prepares a proposal therefore carries different risks from an agent that acts itself. We explain this in AI orchestration versus ordinary automation.
Which AI orchestration platform fits a business without an IT department?
The right platform is one whose management you have already assigned. Without an IT department, the available administrator is decisive, rather than the number of integrations or AI features. How to arrange this is covered in implementing an AI agent for administrative processes. This table compares the routes. “Fits when” is our inference from documentation, rather than a measured ranking.
| Route | Fits when you start with | What you or an administrator must arrange | First limit to check |
|---|---|---|---|
| Make | A bounded visual chain with fixed steps and possibly one AI step | Someone responsible for fields, exceptions, and monitoring unfinished work | Free limit of 1,000 credits, beta agent feature, storage of unfinished work disabled by default (Make, Make) |
| Zapier | A manageable chain between supported apps | An owner for Zaps, connections, and reviewers | Pro only sends approval requests to yourself; export starts at Team (Zapier) |
| Microsoft Copilot Studio | Work where your Microsoft administrator can arrange environment, permissions, and publication | License, environment, access, and usage | Trial cannot publish; pay-as-you-go requires an Azure subscription (Microsoft) |
| n8n Cloud | One specific workflow built by a skilled coworker or builder | Workflow management and account access; n8n handles hosting | 2,500 executions on Starter, support through the forum (n8n) |
| Self-hosted n8n | Work with firm requirements for your own environment, plus a permanent technical administrator | Hosting, updates, recovery, security, and workflow management | Who fixes it when the builder is on vacation? (n8n) |
| Configured product, such as Bombos | Handing over recurring work without becoming a workflow builder | A process owner, examples, corrections, and approvals | Ask to see the entire first task and exit package |
Self-hosting deserves a separate warning. Dutch comparisons often present it as free and private. n8n describes installing, configuring, and keeping it running, and assigns that work to you. n8n, September 30, 2026 The saved subscription price moves into someone’s calendar. The AI step also often uses an external model provider you pay separately, as Make documents for your own provider connections. Make, September 30, 2026 Consider your data’s entire route, alongside where the workflow runs.
To learn how Bombos arranges management and access without your own IT, read using AI without an IT department. The complete purchasing process, including quotes, testing, and contract, is in choosing an AI orchestration platform.
What does an AI orchestration platform cost to start with?
Starting license costs range from zero to several hundred euros per month. Those amounts cannot be compared without your work volume, because each product counts a different unit. n8n charges per workflow execution, “regardless of complexity”. Make charges credits, with “1 operation equals 1 credit” for steps without AI. Zapier counts tasks and sells agents and chatbots separately. Copilot Studio sells credits per tenant.
| Product | Free entry | First paid step | Billing unit | Source |
|---|---|---|---|---|
| n8n Cloud | Not established in this research | Starter € 20 per month with annual billing: 2,500 executions, 5 concurrent. Pro € 50: 10,000 executions, 20 concurrent | Workflow execution | n8n |
| Make | 1,000 credits per month, at least 15 minutes between scheduled runs | At 10,000 credits: Core $ 9, Pro $ 16, Teams $ 29 per month | Credit per step; AI steps separately | Make, Make |
| Zapier | 100 tasks per month, two-step Zaps | Professional from $ 19,99, Team from $ 69 per month (Team lists 25 users) | Task; agents and chatbots as add-ons | Zapier |
| Copilot Studio | Trial: building and testing, no publication | € 173,30 per month for 25,000 Copilot credits, tenant-wide; also pay-as-you-go through Azure | Copilot credit | Microsoft |
Two qualifications apply. Make and Zapier’s pricing pages showed both billing periods without making clear which toggle was active. Read these as displayed prices, rather than quotes. VAT and currencies have also not been standardized.
A calculation shows the difference in units. Suppose you process 400 cases per month, each passing through 6 steps without AI. In Make that is 400 × 6 = 2,400 credits, before AI usage, retries, and checks. If each case is one n8n workflow run, that is 400 executions. This is a counting difference, rather than a sixfold price advantage. AI costs and your own time come on top for both.
The triggering method matters too. An n8n workflow checking for new work every 5 minutes runs 12 × 24 × 30 = 8,640 times in 30 days, even if only ten cases arrive. Once an hour means 24 × 30 = 720 times. That saves 7,920 executions per month, more than three times the whole Starter plan. Choose a trigger that fits the work, such as incoming email, rather than a clock.
The largest cost difference usually lies outside the license. Suppose a cheaper alternative saves € 40 per month but requires more human time at € 60 per hour. The benefit disappears at 40 minutes of extra management per month (€ 40 / € 60 = 0.67 hours). Both amounts are example assumptions, rather than market rates. The full comparison is in AI orchestration platform pricing.
Is free testing the same as starting with an AI orchestration platform?
No. Free testing shows whether you understand the building interface. Starting means letting your team run daily work through it. Between them lie three stages that vendors also distinguish: trying, limited use, and relying on it.
Copilot Studio draws a clear boundary. Its trial allows building and test chat, followed by: “However, you can’t publish the agent.” Microsoft Learn, updated August 3, 2026 A successful test chat therefore says nothing about use by coworkers. Make’s boundary lies in the feature itself. Its new AI Agent app is “available in open beta, so product functionality and pricing may change”. Your own AI provider connections require paid plans. Make, February 2, 2026 version Building your most important process on it today means building on something its maker says may change. Zapier’s free plan stops at two-step Zaps. Reading, searching, proposing, and approving quickly require more steps. Zapier
The test phase should answer whether the employee who will use it can make the next change themselves, alongside whether it works. This comes from practice. A Reddit user asks: “Is there an easier alternative to Make for building AI agents?” because the nodes and connections became overwhelming. r/n8n, accessed September 30, 2026 One post proves nothing about all users, but it is the right test. A trial that finds real errors is explained in testing an AI agent before automating. Employee changes are covered in letting employees adjust AI workflows themselves.
What does an approval step actually do in an AI orchestration platform?
An approval step does exactly what its builder configures. That does not automatically match its name’s promise. n8n, Zapier, and Make all provide ways for a person to review. Approval only exists when rejection and no response demonstrably do not trigger execution.
n8n documents: “You can require human approval before an AI Agent executes a specific tool.” Approval executes the action; rejection cancels it, through nine channels including Teams, Gmail, and Outlook. The builder must enable this for each action. n8n, September 30, 2026
Zapier allows more freedom, and therefore more mistakes. After rejection, the builder chooses whether to continue or stop. The same applies to a timeout. Zapier, updated May 29, 2026 The status page is direct: a step gets Success when “The Human in the Loop step is configured to continue running when the reviewer declines.” Zapier, updated May 29, 2026 A green check mark does not prove someone approved. Approval also cannot involve coworkers on the cheaper plan: “If you’re on a Pro account, you can only send requests to yourself.”
Make reveals another gap: “Incomplete executions are disabled by default.” A run that stalls halfway through is not stored for later resumption by default. Make, September 30, 2026
The minimum starting test therefore shows three outcomes: an approved proposal, a rejected proposal, and a proposal nobody responds to. For an external action, such as a customer email or payment, the latter two must not execute. Never count rejected or pending proposals as completed work. Responsibility when AI makes an error is explained in errors and review.
How do you avoid AI orchestration platform lock-in?
Before starting, demonstrate what you can take when leaving. Recognize that the workflow is only part of what you build. All four building platforms export. None documents an export you can open in a competitor.
| Product | Documented export | Main limitation | What still needs demonstration |
|---|---|---|---|
| n8n | Workflows as JSON: “n8n saves workflows in JSON format.” (n8n) | Export contains connection names and IDs; HTTP steps imported from cURL may contain credentials in headers | Operation with all data in a new environment |
| Make | A blueprint: “You can export a blueprint of the scenario as a .json file.” (Make) | Recreate connections after import; import under 2 MB | Recovery of the whole task, including data outside the blueprint |
| Zapier | “You can export all of your Zap workflows as a JSON file.” (Zapier) | Team and Enterprise only, excluding Free and Professional | Which data and dependencies must transfer separately |
| Copilot Studio | “You can export and import the solutions that contain your agents from one environment to another.” (Microsoft) | Requires suitable roles and your own solution; some components must be added separately | Operation outside your own Power Platform environment |
This table corrects a persistent claim. A Dutch comparison from June 2026 says Zapier workflows use a proprietary format “without an export option to other platforms” (translated). Timmermans Media, updated June 12, 2026 That suggests nothing can be exported, which is incorrect. Zapier documents JSON export, conditional on subscription. But the opposite conclusion, “so Zapier has no lock-in,” is equally wrong. An export file and a working replacement are different things.
Distinguish four dependencies: the AI model, workflow environment, business knowledge, and party doing the work. Replacing a model removes only the first. The third is most expensive to lose: rules, exceptions, and corrections your team adds in the first months. None of the JSON exports holds those as readable agreements, only settings whose reasons nobody remembers.
The strongest test is a handover trial with a second authorized person. Have them open a copy, restore connections, run examples, and identify unfinished work. Keep passwords out of handover files. Do not publish an export of real customer work as proof: n8n warns exports may contain credentials. Create accounts in your company’s name, rather than the builder’s. This also arises in practice: builders openly ask “how to deploy the workflow on the client side” and how to connect customer credentials. r/n8n, accessed September 30, 2026
What can you do with an AI orchestration platform now, and what should wait?
Start with tasks where AI prepares a proposal a person can see and reverse. Complex infrastructure can wait; the recovery route cannot. The documentation above supports this distinction: approval, resumption, and export exist, but are often not enabled.
| First task to try now | Starting condition | Later, after evidence |
|---|---|---|
| Classify email and connect it to a file | An employee sees incorrect assignments and can reverse them | Independently handling exceptions across departments |
| Prepare data from an attachment as a proposal | Source, fields, and missing data are visible | Broad write access across software packages |
| Draft a reply with the file data used | External sending waits for explicit approval | Independently making customer promises |
| Pass work to another specialist | Recipient, status, and next step are visible | Adding handovers because the platform supports them |
| Record working agreements and corrections | A coworker can read and challenge them | Relying on memory you cannot inspect or take with you |
Postpone self-hosting without a permanent administrator, permissions broader than the task, and chains where nobody sees what stalled. This is no reason to postpone harmless preparatory work. It is a reason to separate permissions. A recognizable first task is email to file. Other suitable tasks are in which processes to automate first.
How many AI agents do you start with on an orchestration platform?
Start with one task, which does not necessarily mean one agent. “Starting small” concerns work scope, rather than the number of AI workers involved. Incoming email, file search, proposal, approval, and result can be handled by several agents, provided every handover is visible and recoverable.
At each handover, you need to see who holds the work, its status, and the next step. A public discussion asks exactly that: “Can you see exactly what the agent did”, and can you replay a failed run? r/nocode, accessed September 30, 2026 That question applies equally to one agent or five. Adding handovers because a platform supports them is a mistake when the task does not need them. Agent count is a design choice, rather than a quality measure. One agent doing everything is not automatically cheaper or better. Five without visible handovers are not automatically smarter. The distinction is explained in AI agent platforms versus standalone AI tools. Business adoption is covered in AI workflow automation for Dutch small and midsize businesses.
Which starting criteria do you use before handing over the first task?
Use eight criteria, showing evidence for each instead of accepting promises. This is our assessment sheet, rather than a certificate or industry standard. “Unknown” means not yet ready for that action, rather than a bad product.
| Criterion | Evidence to show | If missing |
|---|---|---|
| Task boundary | One sentence with trigger, processing, and recognizable end result | Define the scope first; no company-wide rollout |
| Owner | Named process owner, reviewer, and replacement | No independent execution |
| Actual system action | An example from your task with minimum access | Demonstrate only with test data |
| Approval | Results after approval, rejection, and no response | External actions stay disabled |
| Recovery | Visible unfinished work and one recovery action without duplicate results | Limit use to proposals |
| Management | Who handles changes and outages, and how they can be reached | Assign management first |
| Costs | One ordinary task and one exception on the usage meter | No open-ended volume commitment |
| Departure | Readable rules, examples, access list, and export tested by a second administrator | Do not build broader dependency |
The minimum starting setup in plain language: one work source, one bounded task, recorded working agreements, a proposal list, a reviewer with a replacement, one recognizable result in the target system, and a visible unfinished-work list. Available vendors are covered in AI automation platforms available immediately. Implementation duration is in which AI agent platform is quick to implement.
Why does the AI orchestration platform with the easiest building interface not win?
Our position: for a business without an IT department, the best starting choice is a platform where a second person can take over, recover, and explain the first task. Ease of building wins the demonstration. The second person wins the year.
This follows from three facts comparison sites do not put together. Self-hosting puts all maintenance on you. Approval can continue after rejection and still report “Success”. Export takes the workflow, but leaves behind the reason for its settings. Each becomes visible when the builder is absent: on vacation, after a changed software connection, or when a rejected proposal gets stuck somewhere.
A calculation shows why this outweighs the license. Suppose 400 tasks currently take 6 minutes manually: 40 hours per month. If review takes 2 minutes per task, recovery takes an extra 10 minutes for 10 percent of tasks, and management takes 4 hours, the total is 800 + 400 + 240 minutes = 24 hours. You gain 16 hours. If review takes 4 minutes because nobody except the builder understands the proposals, the gain is 40 - (1,600 + 400 + 240) / 60 = 2 hours and 40 minutes. All inputs are fictional. Two extra review minutes per task consume most of the gain. Review time falls when a second person can read the rules.
Test this position at your own start: measure how much help a second person needs to check an example, recover an error, and adjust a working agreement. The useful measure is “correctly completed tasks within the agreed time, at total cost”. A correct proposal still waiting does not count. Neither does a technically successful but rejected action.
Where is this heading?
Building is becoming cheaper and more accessible. Management does not automatically follow. Measured adoption: AI use at small Dutch businesses rose from 11 percent in 2023 to 19 percent in 2024 and a provisional 27 percent in 2025. That is 16 percentage points in two years, 2.45 times the 2023 level. CBS, December 12, 2025 Illustratively extending 8 percentage points per year gives about 43 percent in 2027. This is our calculation, rather than a CBS forecast. It measures general AI use, rather than orchestration. CBS identifies knowledge rather than money as the barrier: 73 percent of businesses that considered AI but do not use it cite lack of experience.
Our expectation: by September 30, 2027, at least three of Make, Zapier, n8n, and Copilot Studio offer a continuous route where a non-programmer describes a task in ordinary language, inspects the resulting steps, configures human approval, and restores a previous version, without custom code.
The reasoning: visual building, agents, approval per action, and export already exist separately in the documentation cited above. The next step is one beginner route. The hypothesis fails if fewer than three platforms show all four components in public documentation and a reproducible demonstration on that date. A paid enterprise demonstration still requiring custom development does not count.
The second-order effect matters more than the hypothesis. When building costs almost nothing, a business creates more automations than it can oversee. Scarcity shifts toward understanding: why a rule applies, what happens to exceptions, and who recovers stalled work. Recorded agreements and visible backlogs become more valuable. A replaceable model helps but does not replace that layer. By then, Bombos wants your team to teach the fifth task using the same readable rules and approval boundaries as the first, so more automation does not mean more management. We follow changes in the field daily in the newsletter.
What can this not yet do?
No orchestration platform decides task ownership for you. Documentation shows approval, resumption, and export exist. It does not show they are correctly configured for you. That requires demonstration.
This page’s limits, plainly stated: we have not tested the platforms in our own accounts. Everything above is documented behavior on September 30, 2026. We found no independent measurement of implementation time, return, or management burden at Dutch businesses of this size, and do not invent one. Make and Zapier prices have unclear billing periods. No export feature proves you can move to a different product. Self-hosting does not automatically make your data flow private. This page gives no legal GDPR assessment.
The same standard applies to a configured product. Ask us too to demonstrate the entire first task, including a rejected proposal, one with no response, and the exit package: rules, corrections, and unfinished-work status. Knowledge only in someone’s head is in no system. Bombos interviews the people doing the work so that knowledge is recorded and transferable.
How does Bombos approach this?
Bombos is for people who want to do more work, at a higher quality, with the same team, without becoming workflow builders. You start with two permanent workers: Chef distributes incoming work to the right specialist. Wegwijzer guides you, explains, and helps set boundaries. The specialists around them are built around your task, in your systems, with your rules.
Bombos reads documents and email at all connected addresses. It finds the customer and file in your own software, such as Exact, Dutch accounting software, AFAS, Dutch business software, or Syntess, software for installation companies. It prepares a supported proposal. You approve, change, or reject in Bombos. The software contains only the result after approval. A correction then becomes a rule, including for coworkers. This brings the second person from our position into the first task: one person’s correction applies to the other too.
Payments, customer messages, and contracts wait for your approval by default. This boundary is technically enforced and enabled. You cannot disable it yourself. Bombos can do so at your request, at your own risk. The model is replaceable: what Bombos learns resides in approvals and corrections.
We set up the first task with you in a three-month pilot for € 2.000. Afterward, it costs € 1.000 per month, the same for everyone. That task is the beginning. Your own team then teaches Bombos the next task without needing technical skills. We guide you, then you can do it yourself. Existing software is covered in letting AI work with the software you already have.
Sources
Each source was opened on September 30, 2026, and each original quotation appears verbatim in it. Dutch quotations above are labeled as translations. Except for CBS, all sources sell software or services around these products. Where no publication date exists, the access date is the reference date. Our calculations are identified above.
- n8n: Plans and Pricing. Undated pricing page, accessed 30-09-2026. Vendor.
- Make: Pricing & Subscription Packages. Undated pricing page, accessed 30-09-2026. Vendor.
- Zapier: Plans & Pricing. Undated pricing page, accessed 30-09-2026. Vendor.
- Microsoft: Copilot Studio, product and pricing information. Undated product page, accessed 30-09-2026. Vendor.
- n8n: Choose how to use n8n. Undated documentation, accessed 30-09-2026. Vendor.
- n8n: Export and import. Undated documentation, accessed 30-09-2026. Vendor.
- Make: Scenario blueprints. Undated documentation, accessed 30-09-2026. Vendor.
- Zapier: Import and export Zap workflows in your Team or Enterprise account. Updated 29-05-2026, accessed 30-09-2026. Vendor.
- Microsoft Learn: Get access to Copilot Studio. Updated 03-08-2026, accessed 30-09-2026. Vendor.
- Microsoft Learn: Create and manage solutions in Copilot Studio. Updated 29-04-2026, accessed 30-09-2026. Vendor.
- Make: Introduction to Make AI Agent (New). Describes the 02-02-2026 version, accessed 30-09-2026. Vendor.
- Make: Credits. Undated documentation, accessed 30-09-2026. Vendor.
- n8n: Human-in-the-loop for tools. Undated documentation, accessed 30-09-2026. Vendor.
- Zapier: Request approval to keep your workflow running with Human in the Loop. Updated 29-05-2026, accessed 30-09-2026. Vendor.
- Zapier: Special step run statuses in Human in the Loop actions. Updated 29-05-2026, accessed 30-09-2026. Vendor.
- Make: Incomplete executions. Undated documentation, accessed 30-09-2026. Vendor.
- n8n: Host n8n. Undated documentation, accessed 30-09-2026. Vendor.
- CBS: Businesses use AI most often for marketing or sales. Published 12-12-2025, accessed 30-09-2026. Independent statistics; 2025 figures are provisional.
- Zapier: The 4 best AI orchestration tools in 2026. Published 09-01-2026, accessed 30-09-2026. Zapier recommends itself.
- Timmermans Media: n8n vs Make vs Zapier. Published 27-05-2026, updated 12-06-2026, accessed 30-09-2026. Sells automation.
- Reddit r/n8n: Is there an easier alternative to Make for building AI agents?. Exact date not established, accessed 30-09-2026. Public question, rather than a representative sample.
- Reddit r/nocode: shortlist for structured records, generative outputs, and human review. Page shows “5mo ago”, accessed 30-09-2026. The quoted commenter promotes their own product; only the question was used.
- Reddit r/n8n: how to deliver the worflow to the client. Page shows “5mo ago”, accessed 30-09-2026. Public question from a builder.