01 · Workflow agents
Zapier · n8n · Make
The specialists, the tools they reach for, the memory they build, the controls you keep — and where it all runs.
AI agents aren't one thing. They sit on a spectrum — from rigid task runners to general assistants to a new third category Lifter is built for.
01 · Workflow agents
Zapier · n8n · Make
02 · Personal assistants
Claude · ChatGPT · Copilot
03 · Operator agents
Lifter
Connectors, skills, memory, agents, approvals, audit — all in one place. Set up once. Distribute across the org. Govern centrally.
Managed in one catalog. Connect Shopify, Gmail, Slack, Stripe once. Allocate to the right teams and agents. Revoke instantly.
Shared library. Pre-built handbooks for common operations. Author your own. Distribute to every relevant agent across the org.
Organisational, not personal. Agents share institutional knowledge — house style, customer history, decisions made — not one person's chat log.
Single pane. Access control, permissions, data policy, audit — one place to set the rules and one place to see what happened.
The compounding effect. Every skill written, every connector configured, every lesson learned accrues to the company — not a single inbox.
Three parts your team can read and edit. A specialist is a self-contained unit with its own permissions, its own memory, and a clear way of working — not a black box.
A · Handbook
A written brief. How to triage a ticket. When to escalate. Your tone of voice. Your refund policy. Authored by retail operators, editable by anyone on your team.
B · Tools
An allow-list of connectors. Shopify orders. Klaviyo flows. Gorgias tickets. Each tool gets a permission stance: allow, ask, or deny.
C · Memory
Plain text the specialist reads and edits over time. Products, customers, policies, the tone your last reply used. Versioned. Auditable. Yours.
Native packages for the tools we hand-tune to retail: Shopify, Klaviyo, Gorgias, Cin7, Dotapparel. MCP (the open standard for AI tool access) for the rest of the ecosystem. New connectors land every week.
Customer-defined workflows. Customer-defined columns. Typed transitions. Some auto-fire and wake the next agent; some require human approval.
Built on building blocks already in the runtime. Capability tools, confirmations, scheduling. Workflows aren't a separate product; they're the shape your team gives the platform.
Ask the agent what matters about your store today. It composes a dashboard from the tools and data it has access to. Persistent, shareable, updated on a schedule.
Holly's narrative
Yesterday's lift came from the winter-essentials bundle. Three SKUs accounted for 38% of revenue. Worth checking inventory depth before Friday's email send.
7-day revenue
Different from generic BI. The agent already knows your business (memory) and can act on what it sees (tools). The dashboard is an artifact of the work, not a separate product to maintain.
Plain text your team can audit and edit. Memory belongs to your business — not the model, not us.
i · Remembers
Products. Customers. Tone of voice. Refund policy. Launch process. What worked last quarter and what didn't.
ii · Readable
Memory is plain text, organised the way a person would organise a wiki. Open it up, change what's wrong.
iii · Portable
Switch the underlying model and the specialist keeps everything it learned. Memory belongs to your business.
Every tool a specialist can use gets one of three stances. The risky ones route to the channel your team already uses.
Low-risk, reversible, audited. Runs without human approval. Drafting an email, building a dashboard, summarising a thread.
Pauses for a human in the channel your team already uses. Default for anything that touches a customer, costs money, or changes inventory.
The tool isn't available to that specialist at all. They don't see it. They can't try to use it.
Order #48201 arrived damaged. Photo on file. Refund $186.50?
Approved. Add a $20 store credit too.
Done. Refund processed, store credit issued, customer notified.
Hub is optional. On-prem, customer VPC, air-gapped: pick the deployment that survives your security review.
Hosted
Multi-tenant operator UI, OAuth flows, connector catalog: all in Hub. Your data stays in your Gateway.
Self-managed
Gateway loads its own config, holds its own credentials, exposes its own tools. Nothing leaves the perimeter.
When a security team asks where the data goes, the answer is: wherever you put the Gateway. We do not require a phone-home.
The Hub is fully white-label. Your brand, your colours, your typography. To your team it feels like a tool your company built, because for all intents and purposes, it is.
The Lifter-default brand. What you'd see if you signed up today without customising anything.
The same platform, configured for Acme. Different palette, different typeface, different name. Same engine underneath.
Your wordmark and app icon throughout.
Your accent applied across the UI.
Choose from a curated typeface set.
ai.yourco.com instead of ours.
Today we ship our own purpose-built operational agent. The platform is designed so other AI agents — Claude, Codex, Copilot, and the ones that don't exist yet — can plug into the same controls without rebuilding anything.
The Lifter platform
Whichever agent runtime you plug in, the controls below stay the same.
The model changes; the guarantees don't. Memory, approvals, audit, scheduling — all stay the same when you swap the AI underneath.
A 30-minute call. We'll show you Lifter running against the integrations your team already uses, and tell you what it would take to deploy.