Inbox operations
Sort incoming mail, pull out the work that needs a response, and send a useful daily brief.
- Outlook triage
- Shared mailbox routing
- Follow-up drafts
For managed service providers
Turn client problems into monthly services.
Build a working automation for one client. Reuse it for the next. Swirls hosts every client’s copy and keeps their systems, rules, and runs separate.
Build once
Reusable base
Per client
Separate setup
Charge monthly
Managed service
What you can sell
Start with work clients already need done.
You do not need an AI practice before you start. Pick a process with a clear owner, a clear result, and enough repetition to justify a monthly service.
Sales operations
Keep the CRM current and move handoffs forward without another person copying data between tools.
- Email-to-CRM sync
- Lead routing
- Customer onboarding
Client service
Turn rate cards, service history, and business rules into workflows your client can actually use.
- Quote generation
- Service-desk intake
- Account reporting
The service economics
Sell AI as a service with better margins.
A client tells you about a problem. You build the system that fixes it, deploy it, and charge monthly to keep it running.
80% margins on the monthly fee you charge each client.Most tools an MSP resells earn 40 to 60%.
Build the service. Keep the relationship.
You choose the process, package the offer, and manage the client. Build the system once, deploy it to every client that needs it, and bill for it monthly. Swirls hosts and runs each copy.
See the MSP operating modelThe delivery model
The next client does not start from zero.
Keep what repeats. Make each client’s differences explicit. Deploy and update every account on its own schedule.
- 01
Find one expensive process
Start with work the client already pays people to repeat: triage, quoting, updates, reporting, or intake.
- 02
Build the working version
Write the steps, rules, tools, and approval points into files your team can review and keep in source control.
- 03
Deploy it for that client
Connect the client’s systems, add their rules, and run their copy independently from every other customer.
- 04
Package what repeats
Keep the reusable parts as your template. The next client starts with a working service instead of a blank page.
After the demo
Run the service without building another platform team.
Swirls handles the execution layer. Your team stays focused on the client process, the service, and the relationship.
Controlled releases
Every deployment is an immutable version. Update one client first, then roll the proven change into the template.
Separate client access
Connections and secrets are scoped to the client project that uses them. They do not live in the template.
A record of every run
See what ran, where time was spent, which tools were called, and where a job failed.
Approval where it matters
Pause a workflow for a person to approve or reject before it sends, changes, or publishes anything important.
You own the offer
Choose the process, scope the work, and decide what belongs in the monthly service.
You own the client
Keep the relationship and the business context. Swirls stays underneath the service you deliver.
You can show your work
Use deployment history, traces, and approval records when a client asks what changed or what ran.
An MSP using Swirls
BrewTech builds bespoke agents for small and mid-sized businesses on Swirls.
“Swirls lets me build an entire agency on top of it. I take it and run.”
Ben BrewerVP of Engineering, BrewTech IT
BrewTech used Swirls to ship client-specific agents, connect them to the systems each business already runs, and keep the runtime work out of its delivery team.
Read the BrewTech storyCommon questions
Before you put it in the catalog.
- Is Swirls another SaaS license for us to resell?
- No. Swirls is the platform your team uses to build and run the service. You define the client outcome, manage the engagement, and charge for the ongoing service.
- Do all clients have to use the same workflow?
- No. Start from one template, then give each client their own copy, connections, rules, and release schedule. A useful client-specific change can later move back into the shared template.
- What does Swirls run?
- Swirls runs deterministic workflows and tool-using agents together. Runs can start from a schedule, form, webhook, or chat and continue without your team keeping a process open.
- Can we keep a person in the loop?
- Yes. A workflow can stop at a review gate and wait for approval or rejection before continuing.
Start with one client
Pick one process.
Turn it into a service.
Build the first version, run it for one client, and keep the parts worth selling again.