Customer story · BrewTech

One agency, hundreds of agents, one runtime.

BrewTech builds bespoke AI agents for small businesses. They build every one on Swirls, so the agents they ship are observable, auditable, and rebuildable from the first deploy.

The problem

No storefront agent will ever understand the business.

Small businesses run on systems no off-the-shelf agent will ever understand. So BrewTech builds the agent around the business.

Every SMB has the same shape underneath. A quoting tool. An ERP exporting a CSV to some network drive at 2am. A front desk that knows things no one ever wrote down. The work happens across all of it, and the glue is a person remembering where everything lives.

You can buy an agent off a storefront, but you get exactly the capabilities it shipped with. The moment a client needs it wired into a system it has never heard of, you’re stuck. You can’t pull the definition into your own code and extend it.

BrewTech took the opposite bet. Build a custom agent for each business, around how that business actually runs, and make every piece of it code you own. The hard part was never the prompt. It was everything underneath: the auth, the observability, the audit trail, the thing that has to keep working when the business depends on it.

The future isn’t one agent. It’s hundreds of specialists that talk to each other, under one orchestrator.
Ben BrewerVP of Engineering, BrewTech IT
What they built

The work that ate the most human time, as agents.

Their first client, a manufacturing SMB, runs on Global Shop for ERP and Paperless for quoting. BrewTech turned the highest-friction work into specialist agents, each declared in a .swirls file and deployed straight to the runtime.

Quoting agent

Live
Reads a request, runs it through Paperless end to end, and comes back with the quote. The dropdown work the team used to do by hand now happens over the agent’s own tool calls — a quote handled without a human in the dropdowns.

Serial-number agent

In progress
A caller reads off a serial number and asks if it’s under warranty. The agent answers, and everything staff used to click through runs behind the response. Drop-downs become a sentence.

Delegator agent

Coordinator
The orchestrator. It knows which specialist owns which job and routes work down to the right one. Add a specialist and the delegator already knows how to reach it — one front door for every agent in the business.
The request path
staff / caller
  → chat interface (AI SDK transport → Swirls endpoints)
    → delegator (routes to specialist)
        → quoting agent    → Paperless
        → serial-no agent  → Global Shop

Every agent is chattable through the Swirls UI the moment it deploys. No channel wiring, no glue service in between.

How they build

Write the files, deploy, done.

No N8N to babysit. No infrastructure to stitch. BrewTech’s whole workflow collapses into a loop a coding agent can run. Write a .swirls file that declares the agent and its workflow, run swirls deploy, and the new capability is live. The agent can even write and deploy its own Swirls files, which means the loop closes without anyone touching a Git repo.

That matters for who BrewTech can serve. A client doesn’t need to be a developer. They sign in, talk to a Swirls engineer agent in the portal, and it writes the files on their behalf. The barrier that used to require a coding harness disappears.

When BrewTech inherits a client’s existing automation, they don’t rebuild from scratch. They export the old workflow, hand it to the agent, and get a Swirls file back. It works, and it’s now a tool the rest of the business can reach.

Why Swirls

BrewTech ships agents. Swirls keeps them running.

Frameworks with similar primitives all leave the same homework: write the code, host the infrastructure, wire the auth, build the observability, and hope it survives the first change. Swirls hands BrewTech the runtime — so they spend their time on the thing clients pay for, the agent itself, and ship something traceable and auditable from the first deploy.

  • Observable — every run traced.
  • Auditable — hash-chained logs.
  • Secure — scoped access by design.
  • Portable — declared, redeployable.
  • Context — metering and compaction built in.
  • Connected — reaches the systems SMBs already run.
What it enables

What it lets BrewTech actually do.

  • Any department. One agent per specialty, all under one orchestrator, all able to talk to each other.
  • Non-devs build. Clients build by talking to an agent in the portal. No coding harness required.
  • Clients own it. Every agent is code the business keeps, extends, and redeploys. Never a locked storefront product.
  • 800+ systems (roadmap). Third-party systems through connectors, including the Microsoft stack every SMB lives in.
  • Full trail. Hash-chained audit logs and full run traces, so a regulated client can see exactly what an agent did.
  • Pipeline. Existing clients and a networking room full of SMBs asking BrewTech to put AI into their business.
“What’s in place lets me build an entire agency on top of it. I take it and run.”
Ben BrewerVP of Engineering, BrewTech IT — on the Swirls runtime

Declare it. Ship it.

Write .swirls files locally. Deploy for free to inspect the project in Swirls Cloud.

Browse the cookbook