Make on your desk or A system we deliver
A dark run.
Name the opener.
Picture a scenario that looks finished until a run dies while its author is with a customer. Make gives you a visual canvas for that picture. Beginning it can be a written prompt. It can be modules placed by hand. It can be MCP. AI agents live on that canvas next to workflows, not in a separate product. The published catalog is 3,000+ integrations, and Make says the organizations already running there number more than 400,000. Version one can come from a Make.com consultant. Keeping it is a different question. The canvas is a sound home when a colleague will treat redrawing as part of their week and will come back after a failure. Pass the job to us when that colleague does not exist.
Quick verdict
Keep the drawing in Make when a colleague will take the scenario and can come back to the canvas after a run dies. Have us deliver the system when that same job should continue without anyone living on the canvas. Charges, arrival times, discounts, growth in scope, and any claim that is new all remain drafts until someone on your team agrees.
Side by side
Make on your desk vs A system we deliver at a glance.
A scenario a colleague is able to redraw on the canvas, set beside a system we hand across and continue operating after the opening drawing.
| Dimension | Make on your desk | A system we deliver |
|---|---|---|
| The surface | One visual canvas. A prompt can start the work, dragging can place the modules, and MCP is a third way in. AI agents and workflows share that surface. | Nothing for your team to keep drawn. We shape a workflow for this job and remain with the result after version one. |
| Reach | Make reports a catalog of 3,000+ integrations, and it reports that the organizations on the product already exceed 400,000. | Connections follow the apps this job touches. Width in a catalog helps only where this workflow actually calls an app. |
| Who edits next month | Whoever you name. Version one can be drawn by a Make.com consultant. Later edits belong to a colleague when the team is running Make on its own. | Edits are ours. You are told what moved. Agreement from whoever understands the work still comes before a customer receives output. |
| Trust statements | make.com lists GDPR, and after that SOC 2 Type II, and after that SOC 3. Read those sentences in their current form before any data moves. | Make is who those sentences describe. A delivery from us names an owner and an approval, and it does not wear the make.com compliance line. |
| A failed run | The colleague follows the modules inside the scenario until the stop is clear. Use that shape when the colleague is real. | We open the failed run, name the cause, and fix it. The approver on your side is pulled in only if a customer would notice. |
| Choose this when | One screen can hold the scenario, and a named colleague will redraw it as the job shifts. | Every week the job matters, and asking someone who already has a trade to live on the canvas would invent a second one. |
Notes on the builder, how many integrations are listed, how many organizations are claimed, and the compliance lines sit on make.com. Look there before customer data enters a scenario.
Choose Make on your desk
When this path fits.
- A colleague actually wants the visual canvas and will still be editing the scenario after version one ships.
- A prompt, a dragged module, or MCP is a familiar route when that person changes a branch.
- Make's agents and Make's workflows should share one builder with the rest of the scenario.
- You have checked make.com and the 3,000+ integrations include the apps this job calls.
- After a failure, the reader is obvious: that same colleague, not a message back to the person who drew version one.
Choose A system we deliver
When this path fits.
- Day one would look correct, and day thirty would have no editor.
- A Make.com consultant would finish the drawing and leave a canvas nobody opens on a normal week.
- The job should get done without a colleague having to learn modules, routers, and run history.
- Output might reach a customer, so agreement on the wording has to come from your team first.
- The work repeats, which means "someone will glance at the scenario later" is not a plan.
How we would actually decide
Remain with Make when the canvas has a resident.
Work that still sits on a desk is what we turn into systems running on AI, and a named person stays in charge of every commitment the business would make to a customer. Make is reasonable to operate yourselves. The canvas is visual. A prompt can open it, dragging can build it, and MCP can open it too. Agents sit with workflows. Make's own count of organizations is more than 400,000. If a colleague will own the canvas afterward, a Make.com consultant is a fair way to get version one drawn.
We ask something blunt before that recommendation. On a weekday, when a run dies, who opens the scenario? Make is the right stay when a colleague can indicate a module and describe what it was meant to do. Silence in the room means the tidy picture is a liability.
Silence is when we deliver, and the failed run is ours to open. Wording a customer would see still needs your person's agreement: the charge, the arrival, any discount, any larger scope, and any claim not made before. The scenario you had not drawn yet can come to Get your free Systems Plan. Once delivery is the answer, Read the working loop is how the work proceeds.
Frequently asked
Make on your desk vs A system we deliver questions answered.
When is a Make.com consultant the whole answer?
A Make.com consultant is often enough for the drawing and not for the month after it. From a prompt or from a pile of apps, they can produce a scenario on the visual canvas, with drag-and-drop or with MCP, across the published Make catalog of 3,000+ integrations. The limit appears when nobody employed by you will open that scenario later. Delivery is the better ask when the canvas would stay closed until another failure, at which point you would be searching for whoever made the drawing. More than 400,000 organizations on the product does not put an editor in your room.
Does Make give you agents as well as fixed scenarios?
Both are in the product. AI agents are offered, and workflows are offered, so this is not a tool that can only march down a path you froze in advance. Starting points are a prompt, modules you place by dragging, or MCP. An agent belongs where the step must read and then choose. A fixed module belongs on a branch you can already state. The canvas still has to be opened by a colleague who can follow what happened. An agent does not brief a room that never learned the picture.
When should the team keep working inside Make?
Remain there when a colleague will treat the scenario as their own work and can reopen it after a failure. The advantage is concrete. They see the path, they change a module, and they can tell what the run did without a wait for us. Before customer data is placed in a scenario, read make.com, where Make states GDPR, then SOC 2 Type II, then SOC 3. The organizations already using it, more than 400,000, mean the builder is widely used, not a curiosity. That advantage ends if the only person who can see the path is about to leave.
What do we lose if nobody on the team learns the canvas?
Weekday redraws without a call to us. That is a real loss if somebody on the team wanted the control. Skip the regret when the canvas would only have been a picture with no maintainer. Delivery, in that second case, leaves repair with the people who built the system. Your hours move to agreement on what a customer would receive: the charge, the arrival time, any discount, any larger scope, and any new claim.
Can the job begin in Make and move to a system we keep?
It can. Use an early drawing to find out which branches actually fire. Make should keep the scenario while a colleague is still changing it and can explain a failure. Move when memory, rather than the picture, is what keeps the scenario alive, and that person is departing or was never employed. Get your free Systems Plan can take the drawing you already have and say if the canvas should keep it or if we should rebuild it and watch it.
How should we make this choice before the week ends?
Limit the week to one job that was about to become a drawing. Ask the colleague who would reopen a failure whether they truly will. A yes means draw it in Make, and a consultant can hurry the first pass if you want speed. A no means stop the drawing and ask us to deliver the system. Wait on any second product until this job has a named editor or a build. Customer wording waits until someone on the team has agreed.
More comparisons
Other decisions worth getting right.
Next step
Show the job before any scenario exists.
Whoever knows the job sits with us, and then we say whether Make should remain their canvas or whether the system should be handed across.