Make automation for small businesses
Make automation for small businesses: how MILabs sets up scenarios that move data between the software your team already uses.
Updated 2026-09-25
What Make is
Make is a cloud-based visual automation platform. A user builds a scenario by placing modules on a canvas, with each module representing an app or a step, and linking them so that data passes from one to the next. A scenario can start from a webhook, a set schedule or a change in another app. Along the way it can filter records, branch into different paths and reshape data before it reaches its destination. The platform is operated by its vendor, Make (Celonis), so scenarios run in the vendor's cloud rather than on a server the business manages itself. Teams use it to move information between the software they already rely on, so that a booking, an invoice or an enquiry appears where it is needed without being copied by hand. Its strength is the middle layer, handling repetitive routing and handoffs while people keep the judgement calls and the final decisions.
Make in plain language
Make is a cloud service for connecting software that was never designed to share information. Many small businesses run a booking tool, an accounting package, a shared inbox and a spreadsheet, and staff often copy figures between them by hand. A platform like Make takes over that copying by carrying information across whenever a set condition is met.
The working unit is the scenario, a sequence of steps a reader can follow from left to right. Because the steps appear as a diagram, a person who did not build the scenario can still see where a value came from, what changed along the way and where it ended up. That readability is the main reason teams pick a visual tool over scripts that only a developer can open.
Scenarios also fail in ordinary ways. A field gets renamed in one app, a login expires, or a record arrives in a shape the next step did not expect. Treating these failures as normal events, with a named owner and a clear alert, works better than treating them as surprises. A documented scenario is easier to keep running than one known only to its builder.
What businesses use it for
- Routing new enquiries from a web form into the customer records and the right inbox
- Copying booking or order details between a calendar, a spreadsheet and an accounting package
- Sending reminders and follow-ups when a quote, invoice or appointment needs attention
- Collecting approvals before a document or payment is released
- Posting a summary of sales or jobs to a shared channel for the team
Who it suits
- Owners who already use several cloud apps and want them to exchange data
- Teams with repetitive handoffs between sales, admin and operations
- Businesses ready to name one person who maintains each scenario
How MILabs sets it up
MILabs starts with a conversation with the owner or team lead about which jobs should move first and which should stay manual. We then choose the Make plan together, based on how the business expects its scenarios to grow, and confirm the account belongs to the business rather than an individual. Next we connect the systems already in use, such as email, calendar, accounting or customer records, and test each link with real examples before anything runs unattended. Permissions are set so each connection has only the access it needs, and every scenario has a named owner. Finally we agree who looks after changes and who receives failure alerts.
Connects to
- HubSpot
- Salesforce
- GoHighLevel
- Pipedrive
- Zoho CRM
- Xero
- QuickBooks
- Sage Accounting
- Dext
- OfficeTools
- Xero Practice Manager
- Karbon
- Ignition
- InfoTrack
- Cliniko
- Halaxy
- Nookal
- Best Practice
- ezyVet
- Insly
- ServiceM8
- simPRO
- Tradify
- AroFlo
- Fergus
- Jobber
- ServiceTitan
- Procore
- PropertyMe
- Rex
- VaultRE
- Reapit
- Ailo
- Timely
- Fresha
- Mindbody
- Setmore
- Calendly
- Rezdy
- Cloudbeds
- Glofox
- WordPress
- Webflow
- Wix
- Squarespace
- Shopify
- WooCommerce
- BigCommerce
- Maropost Commerce (Neto)
- Cin7
- Unleashed
- Katana
- Brightpearl
- Starshipit
- NetSuite
- Dynamics 365 Business Central
- SAP Business One
- Odoo
- Square
- Lightspeed
- Kounta
- SumUp
- Epos Now
- Deputy
- Tanda
- KeyPay
- BambooHR
- Bullhorn
- Microsoft 365
- Google Workspace
- monday.com
- DocuSign
- Notion
- Slack
- Microsoft Teams
- Aircall
- Zoom
- Twilio
- 3CX
- Zendesk
- WhatsApp Business
- Mailchimp
- Klaviyo
- ActiveCampaign
- Brevo
- Campaign Monitor
- Hootsuite
- Trustpilot
- Reapit PM (formerly Console Cloud)
- Sage 50
- Square Appointments
- Lightspeed Retail (X-Series)
- Stripe
- GoCardless
- Afterpay
- Wise Business
- Freshdesk
- Asana
- ClickUp
- JobAdder
- Pabau
- Harvest
- Mr Yum
- Power Diary (Zanda)
- Airtable
- Zoho Books
- Sentral
- storEDGE
- Nexudus
- Rentman
- Current RMS
- OWNA
- ChiroTouch
- Pool Brain
Builds it fits
Industries it fits
Make in practice
In a business that runs Make well, the day to day change is often small on screen. Staff keep working in the tools they already know. The difference is that a website enquiry now produces a contact record, a note in the shared inbox and a task for whoever handles that kind of work, without anyone copying details between windows.
The work usually begins with one handoff that everyone complains about, such as a booking that never reaches the invoicing system. The team agrees the trigger, the expected result and which fields must never be overwritten. The scenario is then built and checked against a few records the staff already know well before it is switched on for everyone.
Over time the scenarios grow in layers. A scenario that moves a paid invoice into the ledger might later feed a weekly summary, and a booking flow might gain a second branch for cancellations. Each addition gets a short written note covering its trigger, its outputs and the person to contact when it fails, so the map stays readable for whoever takes over next.
Frequently asked questions
- What is Make?
- Make is a visual automation platform by Make (Celonis). Users assemble scenarios on a canvas by linking modules, each an app or a step, so information moves between tools without manual copying. It suits businesses whose existing software should share data. MILabs uses it where a visual, readable workflow suits the team better than custom code, and explains each scenario so the owner can follow it.
- Can I self-host Make?
- No, Make is delivered as a cloud service, so scenarios run on the vendor's infrastructure rather than on servers the business controls. Where data handling is strict, MILabs maps what each connected app stores and where before any scenario is built. It can show which systems would pass through Make and flag each step where the business should decide whether that data movement is acceptable.
- Which builds work well with Make?
- Make suits builds that move data between systems on a trigger, such as a form submission that should create a customer record or a booking that should prompt a reminder. Lead routing, invoice chasing and calendar and CRM sync are common first builds. Assistant-style builds that read or write text can connect too, with a person keeping the final call. MILabs picks the build after reviewing the handoffs the team repeats most often.
- How do I get my team to use Make?
- The easiest first step is to say hello through the enquiry form, and we'll take it from there. Let the people who feel the repeated handoff most see the first scenario run on their own work. Keep scenarios few at first, and write a plain note for each describing its trigger and who to contact when it fails. MILabs builds this into the handover so the team can read and report on each scenario.
- How does MILabs set up Make?
- MILabs begins with the owner or team lead, chooses the Make plan together, and connects the systems the business already runs. Permissions are limited to what each connection needs, every scenario gets a named owner, and the team agrees who handles changes and failure alerts. Each scenario is tested with real examples before it runs unattended. The business keeps the account, so it is not tied to any one person at MILabs.
