It waits at every handover.
Sales, finance and delivery pass it along, and someone has to remember to chase.
The operations platform
AI agents do tasks. Floowed runs whole operations.
AI agents help with single tasks. The rest still runs by hand, passed between people, inboxes and spreadsheets. Floowed runs all of it, from first request to final outcome, however many steps, handovers or systems it crosses, and however long it takes.
$80 of credits to start. No card, no sales call.
Supplier onboarding · Case 3308
Liang Brothers Trading, approved
- Started
- Mon 10:05
- Approved
- Thu 16:15
- Steps
- 9
- Systems
- 3
- Chases
- 2
- You stepped in
- 0 times
- GatherBank letter, license and insurance requested from Liang Brothers Trading
- ActDraft supplier record opened in Xero
- InterpretBank letter read: the account name doesn’t match the license
- ChaseSupplier asked for a letter in the licensed name
- ActBuyer told in Slack what it’s waiting on
- ChaseSupplier chased again, buyer given a new date
- Waits a day for the supplier
- InterpretNew bank letter read: the names match
- DecideAll 5 of your rules pass
- ActSupplier approved in Xero, first PO unblocked
- GatherPulls what the case needs from people, inboxes and systems.
- InterpretReads and checks what actually arrives, in whatever shape it comes.
- ChaseFollows up with whoever still owes something, until they answer.
- DecideApplies your rules, the same way on every case.
- ActWrites to your systems and keeps people posted, at every step, not only at the end.
Every case runs these five stages, as often as it needs and for as long as it takes.See how it works→
Running on Floowed
However you run it today, Floowed runs it for you.
Most teams still run their operations by hand. Some have added an AI agent. The difference is where the work waits.
It waits for your next prompt.
The agent does the task you ask for, then stops. You still run the process.
It keeps moving.
Floowed runs every step, chases whoever hasn't answered and only asks you when a rule says so.
An agent finishes a task. Floowed finishes the case.
The operations no single system owns.
Your CRM, accounting and project tools each run their own step. The work between them, the handovers, follow-ups and checks, still runs by hand. Floowed runs all of it, in any team and any industry: routine cases go straight through, and the ones that snag get chased and sorted instead of dropped.
A new customer signs
Every timeSets up billing, books the kickoff and updates the CRM.
When it snagsThe PO doesn’t match the contract, so it asks the customer for a corrected one.
CRME-signatureAccountingSlackA new supplier joins
Every timeCollects the form, certificate and bank letter, checks the registry and adds the supplier to your accounting.
When it snagsThe bank details don’t match the registration, so it asks their finance team and holds payment.
EmailDriveAccountingA contractor starts a project
Every timeSends the contract, then sets them up in payroll and the project tool.
When it snagsThe rate is over budget and the NDA isn’t signed, so it gets the lead’s OK and chases the signature.
E-signaturePayrollProject toolA client asks for a change
Every timeChecks it against the scope, prices it, then updates the plan and the invoice.
When it snagsIt isn’t in the signed scope and nobody approved the cost, so it asks the account owner before any work starts.
Project toolContractAccounting
These are examples, not a menu.
If an operation repeats, crosses people or systems, and takes work to get from request to outcome, Floowed can run it.
One place to set the rules and see the work.
Write the rules in plain words or code, follow every case with its evidence, test each new version on past cases before it goes live, and see how every operation performs.
DashboardOperations/New customer handover
v7 livev8 draft
9 deals running noweach at its own step · 31 this month
Rules
Set up billing74% of deals
when PO matches the contract and Payment terms match and Tax form is valid and AP contact confirmed
Ask finance10% of deals
when PO is below the contract value then assign @finance before billing
Chase the customeredited16% of deals
when A document is missing or doesn’t match then chase their AP team every 48h 24h up to 3 times and after that ask the deal owner in Slack
# new-customer-handover v8 draftrule set_up_billing when po.amount == contract.value and po.terms == contract.terms and tax_form.valid and ap_contact.confirmed then netsuite.billing, calendar.kickoff, slack.notify #csrule ask_finance when po.amount < contract.value then assign @financerule chase_customer when any(document.missing or document.mismatch)- then chase customer.ap every 48h max 3+ then chase customer.ap every 24h max 3 after max notify deal.owner via slack
Sources
people, inboxes and systemsHS
HubSpot: deal marked closed wonStarts the case, with the deal owner and amount
triggerDS
DocuSign: the signed contractValue, payment terms, start date
system@
The customer’s AP teamPO and tax form, by email or upload link
personXE
XeroIs this customer already billed somewhere?
systemLast 30 days
- Deals started
- 31
- Everything found without asking
- 19%
- People asked per deal
- 2.4
Read on case 2217 · Tessaro Foods
3 documents, 2 sourcesPDF
Signed contract, from DocuSign$36,000 a year · net 30 · starts Oct 1
99%JPG
PO, a phone photo from their AP$36,000 · net 60, the contract says 30
86%PDF
Tax form, scannedLegal name matches the contract
98%≠
Checked against each otherPayment terms disagree, so the PO goes back
1 mismatchModel
- Default
- open-weight
- Below 90% confidence
- frontier model
- Escalated, 30 days
- 8%
Message to Tessaro’s AP team
emailTo ap@tessarofoods.com · cc your deal ownerSubject Corrected PO for your Castell Freight contract
Hi Priya, thanks for the PO. It shows net 60, but the signed contract is net 30. Could you send a corrected PO so we can start billing on October 1?
Upload corrected POSchedule
v8- nowFirst request
- +24hReminder 1 of 3
- +48hReminder 2 of 3
- +72hReminder 3 of 3
- afterAsk the deal owner in Slack
When billing is set up
4 systems, 2 teamsXE
XeroCustomer and billing schedule, from the 1st
createHS
HubSpotDeal moved to Live, documents attached
updateGC
Google CalendarKickoff booked with the customer and CS
book#
Slack, #customer-successCS told, with the contract and contacts
postAudit
Every write is logged with the rule and version that caused it, so any outcome can be traced back.
Build with Floowed
v8 draftDO
Customers’ AP teams take days to send the PO. Chase them every day instead of every two days.
F
Done. Chase the customer now follows up every 24h, up to 3 times, then asks the deal owner in Slack.
12 of 12 tests pass
Replayed on 90 past deals0 outcomes change
- v7
4d 6h- v8
2d 20h
Describe a change…
Cases
Open38Waiting on someone14In review5Overdue2
Case 2217Chase
New customer handover · Tessaro Foods
HubSpotDocuSignAP inboxXero4 systems · 3 people
Waiting on Tessaro’s AP teamCorrected PO, net 30
- Mon 09:12
Deal closed in HubSpot, contract pulled from DocuSign
- Tue 11:02
PO arrived as a phone photonet 60, the contract says 30
- 11:03
Asked Tessaro’s AP for a corrected POdeal owner in cc
- Wed 11:03
Reminder 1 of 3 sent
- 16:00
Reminder 2 of 3scheduled
848 credits so far
Case 0391Decide
Customer account changes · Rosales Shipping
EmailHubSpotXeroContracts4 systems · 4 people
Waiting on TaxNew parent is in Canada
- 10:24
Customer letter, CRM record, billing account and contract pulled
- 10:25
New entity: Rosales Shipping Inc., TorontoHubSpot updated, Xero still bills the old entity
- 10:26
Rule: cross-border changes wait for taxrules v12
- now
Waiting on @tax in Slack
656 credits so far
Case 4410Chase
Client change requests · Ferrante Wines
EmailAsanaHubSpotQuickBooks4 systems · 4 people
Waiting on Ferrante Wines’s sponsorChange order signature · overdue
- Fri 14:02
Request from the client’s email, project plan and SOW
- 14:10
PM estimate: 18 hours, $2,700 over the SOW
- 14:11
Client asked to sign the change order
- Mon 14:11
Reminder 2 of 2, no reply
- now
Ask their sponsoroverdue
552 credits so far
Case 2229Decide
New customer handover · Okonjo Design
HubSpotDocuSignAP inbox3 systems · 3 people
Waiting on FinancePO $4,000 below contract
- 09:58
Contract, PO and tax form in
- 09:59
PO covers $48,000, the contract is $52,000
- 10:00
Rule: PO below contract valuerules v7
- now
Waiting on @finance in Slack
752 credits so far
Case 5530Interpret
Order changes · Dunmore Outfitters
EmailHubSpotXeroWMS4 systems · 2 people
Waiting on FloowedReading the buyer’s email and new PO
- 10:46
Email, order 5530, stock and contract pulled
- 10:47
Quantity changed, delivery date moved up 3 days
- next
Check stock and the pricing rule
72 credits so far
Case 3310Act
Supplier onboarding · Marchetti Steel
EmailCompany registryXeroSlack4 systems · 3 people
Waiting on FloowedCreating the vendor in Xero
- Mon
Supplier form, bank letter and insurance certificate in
- Tue
Supplier chased once for a missing tax form
- 10:48
Rule: documents valid, registry matchrules v11
- 10:49
Vendor created in Xero, procurement told in Slack
384 credits so far
Case 2233Gather
New customer handover · Duarte Clinics
HubSpotDocuSign2 systems · 1 person
Waiting on FloowedPulling contract and deal
- 10:49
Deal closed in HubSpot
- now
Pulling the signed contract from DocuSign
24 credits so far
Usage/September 1 to 24
Team · 250,000 credits
Credits used181,64073% of plan
Cases run399+18% on August
Ran without a person86%+4 pts on August
Median time to outcome2d 20hrequest to outcome
Credits per day
by operationSep 1Sep 8Sep 15Sep 24
HandoverAccount changesChange requestsOrder changesSuppliers
By operation
this month| Operation | Cases | Credits | Auto |
|---|---|---|---|
| New customer handoverv7 | 31 | 38,440 | 71% |
| Customer account changesv12 | 64 | 46,080 | 78% |
| Client change requestsv4 | 42 | 20,160 | 83% |
| Order changesv9 | 240 | 57,600 | 91% |
| Supplier onboardingv11 | 22 | 19,360 | 86% |
| Customer offboardingdraft | – | – | – |
| Total | 399 | 181,640 | 86% |
Live in minutes.
No IT project, no consultants. Start in Slack, Teams, email or the Floowed Dashboard.
- 1
Pick or describe an operation
Start from a template, or describe it in Slack, Teams or the Floowed Dashboard. Anything your team runs by hand.
- 2
Floowed sets it up
It connects your tools, writes the rules in plain language and asks only what it can’t work out.
- 3
Let it run
Every new case runs from request to outcome. You step in only when a rule says so.
“We’re an agency, so our work lives between clients, freelancers and a dozen tools. Floowed took over freelancer onboarding first, then client onboarding and change approvals. Contracts, paperwork and sign-offs now chase themselves, and my team spends its time on the work clients actually pay us for.”
Founder, Akcelo
“Our team used to spend hours on every file: reading documents, checking numbers by hand, reconciling one against another. Now Floowed reads everything that comes in, applies our rules and has a decision ready in minutes.”
Founder, Alon Capital
Questions
What is Floowed?
Floowed is the operations platform. It runs a business operation from first request to outcome, across every system and person involved: it gathers what a case needs, reads the documents that arrive, chases whoever still owes something, applies your rules and acts in your systems. You set it up in Slack, Microsoft Teams or the Floowed Dashboard, and it's live in minutes.
Why not just use ChatGPT, Claude or another AI assistant?
An AI assistant does one task when you ask it. Floowed runs the operation around the task, for as long as the case takes: it keeps every case open, remembers who it is waiting on, follows up without being asked, applies the same rules every time and writes the outcome to your systems, with a record of each step. Floowed uses models like these under the hood and picks the right one for each step. An assistant or agent can also do a step inside a Floowed operation. AI agents do tasks. Floowed runs the whole operation.
How is Floowed different from Zapier or n8n?
Zapier and n8n move data between tools when a trigger fires, and they stop when something is missing or unclear. Floowed runs the whole case: it reads what arrives, chases what’s missing, waits if someone owes an answer, and applies your rules until the case reaches its outcome. It works alongside the automations you already have.
What kind of work is Floowed for?
Recurring work that crosses teams and systems: the cases that go straight through, and the ones that wait on people or documents. Examples: new customer handovers, customer account changes, client change requests, order changes and supplier onboarding. If an operation repeats, crosses people or systems, and takes work to get from request to outcome, it fits. Floowed isn’t built for one-off tasks or a single step inside one system.
Do I have to use Slack?
No. Slack is one way in, alongside Microsoft Teams and email. The Floowed Dashboard is where you build and version operations, start from templates, follow every case, and see usage and how many cases ran without a person, per operation. Cases can also come in by upload, API or MCP.
How does pricing work?
Start free with $80 of credits, no card and no sales call. Credits pay for the work Floowed does on each case, so you pay for use, not seats. Paid sizes start at $100 a month for 10,000 credits, with every feature and integration included, billed monthly and cancellable any month. Custom set-ups are quoted.
How many credits does a case use?
It depends on the work. A light case uses about 80 to 250 credits, a standard case 250 to 800, and a heavy one 1,500 to 4,000. One credit is one cent, so the free $80 covers roughly 10 to 30 standard cases.
How long does it take to go live?
Most operations are live in minutes. Describe the operation in Slack, Microsoft Teams or the Floowed Dashboard and Floowed builds it, then tests your rules on past cases. If you’d like, we’ll build the first one with you.
Do I need IT or a consultant to set it up?
No. Describe the operation in Slack, Microsoft Teams or the Floowed Dashboard and Floowed builds it: it connects your tools, drafts the rules, tests them on past cases and asks only what it can’t work out. When an operation needs custom rules, a private deployment or a special integration, we set it up with you.
Does Floowed replace my CRM, ERP or other systems?
No. Your systems of record stay where they are. Floowed sits above them: it reads from them, runs the steps between them and writes the outcome back, through 400+ integrations and an API in both directions.
What happens when someone doesn’t reply?
Floowed follows up on the schedule you set, by email, Slack, Microsoft Teams or the channel you choose, then escalates to whoever you name. The case stays open and nothing gets lost. A chase can go to a person, a system or another agent.
What happens when a case doesn’t fit the rules?
Floowed asks the right person instead of guessing. You choose how much it handles on its own: every case, only the routine ones, or none, and you can move that line as you go.
What can it read?
Whatever actually arrives: PDFs, scans, phone photos, spreadsheets, emails and handwritten forms. It checks documents against each other and against your systems, not just one at a time.
Which AI models does Floowed use?
Floowed is model-agnostic. It routes each step between open-weight and frontier models on cost, latency and data residency, and sends hard documents to a larger model when confidence drops. You choose which models run your cases, including private deployment.
Can I see why a case went the way it did?
Yes. Your rules run in a deterministic policy engine, and every case keeps a full record: what was read, who was asked, which rule and version decided it, and what was written where. You can replay a rule change on past cases before it goes live.
Can other AI agents work with Floowed?
Yes. Floowed has an API and MCP in both directions. Your agents can open cases and check their status, and Floowed can hand a step to an agent and wait for the result.
Which tools does it connect to?
Slack, Microsoft Teams, email and 400+ integrations, including ERPs, CRMs, accounting and HR systems, plus an API and MCP in both directions. Your systems of record stay where they are.
How do you handle security?
Every case keeps a full record of what was read, who was asked and which rule and version decided it. You choose which models run your cases, model routing respects data residency, and private deployment is available. SOC 2 is on our roadmap, not yet certified.
Every operation that waits on someone. Handled.
Start free with $80 of credits. One rate at every size, no seats. See pricing