Every vendor is adding a copilot — a chat window on top of their app. FlowClick is the runtime the work already runs in, so every person in your account gets something different: a persistent assistant that remembers, pays attention, hands work off, learns how the company runs, and acts within limits you set. It lives where the work happens, and it belongs to you.
Available in every FlowClick account · one Brain per person · one account, one tenant, hard-isolated
The tables, the flows, the durable processes, the task inbox, the audit trail, and the approval spine are already here. A Brain doesn't integrate with the place where work happens — it is a principal in it, with the same permissions, the same audit, and the same kill switch as everything else.
Lives in a chat window. Forgets when you close it. Can read what its connector allows and does whatever that connector permits — all or nothing.
Useful for one job in one tool. No memory of your company, no idea who else is involved, no way to hand work to a colleague, and no record you can audit later.
Remembers, watches, suggests, acts within its autonomy, hands off to other people's Brains, proposes automations for what it sees you repeat — and explains every move from the records.
Conversations persist. It keeps facts, preferences, decisions, glossary, and who-owns-what, cites where each one came from, and lets you see, edit, or delete every one. Team knowledge lives in shared memory the whole account can draw on — under the same permissions as everything else.
It watches the real signals of your work — record changes, tasks, inbound mail, alerts. A cheap first pass decides whether something needs you at all; only then does it think properly. The result is one of four things: nothing, a note in your feed, a suggestion one tap away, or an action taken on your behalf.
A handoff between two people is a durable process between their two Brains — it survives a weekend, a restart, and an audit, and pulls each human in only where their settings require. Out of office? It routes to your delegate or escalates to your manager using the org graph.
Slack, Microsoft Teams, a mailbox address of its own, and a phone app with push. Approve, counter, or decline a handoff from a card in the chat you already use. Quiet hours and a daily action budget keep it from nagging.
Over time the Brains see who does what, how fast, and what gets handed to whom. When they notice a recurring human pattern they propose a Flow to automate it; a person approves; the company's implicit process becomes an explicit, governed one. No copilot vendor can copy this, because none of them own the process runtime and the approval spine.
Any app built on FlowClick can declare its own tool pack, persona, work-item kinds, and memory-worthy records with zero code. Its people log in once to one identity across every app in the account — and the Brain sees each app only through that app's own permissions.
Every Brain acts at a level its person sets, capped by an account-wide ceiling an administrator controls. Start low, raise it per person as trust builds. It can never exceed the ceiling, and it can never do what its person cannot.
Watches and remembers. Says nothing unless asked. The right setting for a first week.
Surfaces what it noticed and what it would do. You do it. Right for anything new.
Drafts the action and waits for one tap — in the feed, in Slack, on your phone. The everyday setting for real work.
Executes inside its bounds and reports, with an explanation on file. Reserve for well-worn, low-risk flows.
Every action is recorded as "Dan's Brain, on behalf of Dan, did X" in the same audit trail as human actions. Explain this action shows the records behind any move — assembled from the audit rows, never from a model's recollection.
One person's Brain is an assistant. A company's Brains, all addressable to each other on one platform, are a nervous system.
No ops person, nothing drops. Each Brain watches the apps its person works in; handoffs and cover route automatically when someone is out; the miner notices client onboarding, proposals, and invoicing repeating and proposes the Flow. A small team punches above its weight.
Inbound mail, alerts, and record changes are triaged before anyone reads them. The routine gets filed and actioned within budget; the exceptions arrive as suggestions with the evidence attached; the weekly “your week” profile shows where the time actually goes.
Each client is its own account with its own Brain that can never see yours. You operate or support it through a scoped, expiring, auditable delegation. You're no longer selling apps — you're selling apps plus an AI that runs them.
Every Brain is an MCP surface. Point Claude, or any assistant, at your account with a scoped token and it can ask your Brain, check its status, recall what it remembers, or hand work to a colleague — under exactly the authority you hold. Administrators operate the whole fabric over the same MCP tools they use for everything else.
brain.ask · brain.status · brain.recall · brain.handoff for each personBring three people and the apps they work in. We'll stand up their Brains, bind Slack, and show you the first handoff and the first proposed automation.