Example
Work outside the contract
Two extra product pages were never in scope. Nobody priced the six hours.
Map your procedures
SOPs and PDFs turned into rules Flo checks
Flo · AI agent for agencies and manufacturers
Every request, handled. Every decision, yours.
Flo checks requests, orders and contracts against your procedures and drafts the reply. Flowpanel Code builds the fix.
Product preview: a project manager asks Flo about a client request. Flo reads the contract in Google Drive, checks Linear and Slack, answers with sources, and after approval Flowpanel Code writes, tests and deploys the change, then closes the task with its cost.
Trusted by agencies and manufacturers
The problem
Small requests are where margin leaks. A clause nobody checked, a discount above your rule, an hour nobody priced.
Example
Margin lost to a rule nobody checked
An 18% discount above your rule and unbilled work, both approved in a hurry.
Example
A team booked past its plan
January ends near 28 hours on a 24-hour plan. The client hears it last.
How Flo works
Three steps, every time. Flowpanel is the workspace your team and clients share. Flo is the agent inside it.
- Step 1
Reads every request
Email, Slack, call notes and orders land in one place, matched to the right client and procedure.
- Step 2
Checks it against your procedures
Each request is checked against scope, your procedures and past work, with sources.
- Step 3
Drafts the reply, a person approves
Flo drafts the reply, the change order or the order. Your team clicks approve.
Your client's view
Your clients ask Flo, not your PM. Answers come with sources, and the PM steps in only when needed.
Christine asks Flo: "When will I get the next update on my project?" Flo checks the task tracker in Linear, the project plan in Google Drive and what waits for approval. Answer: the team sends the next update on Fri 23 Oct with the first product pages on staging. Before that, Homepage v2.1 waits for approval until Tue 20 Oct. Launch stays on Thu 12 Nov. Every claim links to its source: the task tracker, Homepage v2.1 and the project plan.
Workflows
Client work, checked by Flo. Intake, client portal, scope and team workload.
Agency workflows
Pick a workflow to see how Flo works
Each client message is checked against your intake procedure. Clear fields go to the brief, gaps become one-click questions.
See it in a demoClients see plan, requests and invoices, and ask Flo instead of waiting. Every answer cites its source.
See it in a demoNew work from calls becomes a draft change order. Margin per client is checked every day against your target.
See it in a demoWorkload comes from Linear, Jira or ClickUp. Flo flags overload early and drafts the handover.
See it in a demoFactory workflows
Pick a workflow to see how Flo works
An email, an Allegro message or a phone note becomes a checked draft order with prices, stock and credit.
See it in a demoEach complaint lands on its batch and supplier. Three on one batch reach quality the same day.
See it in a demoSupplier invoices flow into margin per product and channel, with a Monday review of what moved.
See it in a demoBring the PDF you already have. Flo turns it into rules and checks every order against them.
See it in a demoA 30 minute call. Bring one procedure, we show you Flo checking it.
Book a demo Flowpanel Code
The AI dev team that built Flowpanel. Flo picks the agents for each task, and a person approves every merge.
-
Flo builds the team for each task
Sonnet where the work is routine, Opus where a mistake costs, Codex when it fits. You change the plan in chat and press run.
-
Agents talk to each other
Agents message each other and Flo, then leave a report instead of a chat log. Nobody copies context between windows.
-
A real environment per team
Its own branch, its own server on its own port and a browser the agent drives. A person can take over at any moment.
-
Every change has a receipt
Time, tokens and cost per card, team and agent, straight from the agents’ transcripts.
47 of the 52 cards on its own board were built by Flowpanel Code, in three days and one night. Numbers from its analytics, 28 to 31 Oct 2026, at API list prices.
The full loop
From a client message to a checked fix and a reply. Every run shows what it cost.
01 · Client request
A client email, Slack message or portal request becomes a ticket with an owner, so nothing waits in someone’s inbox.
02 · Context from your tools
Flo reads what the team already knows: the Linear project, the client thread, recent deploys, the contract and the hours left in scope.
03 · Plan from Flo
Flo proposes one team: Sonnet for the routine fix, Opus to review the form every client sees. You can change the plan before it runs.
04 · Built in Flowpanel Code
The team works in its own branch and worktree. Tests run, a review agent leaves notes and Flo asks a person before anything merges.
05 · Production check
An agent opens the live page in its own browser, checks that spam is blocked and real comments still post, and reads the logs.
06 · Reply and PM update
Flo drafts the reply to Anna with what changed. The PM approves it and the ticket closes in Linear.
07 · What the run cost
Every run is costed from the agents’ own transcripts. A measured run (fpc-43): 40 minutes of agent work, 40.7M tokens, $16.45 at API prices.
Receipt from a real Flowpanel Code run (fpc-43), at API list prices. Client, ticket and messages are illustrative.
Inside Flowpanel
Everything your client sees, in one place. Progress, budget and approvals, answered by Flo with a source.
Approvals in one click
What is waiting on the client, when it is due and what happens next.
Talk to Flo by voice
Clients and your team can just ask out loud. Flo answers by voice, with the same sources.
Every question, answered
Every answer cites its source. What Flo cannot answer goes to the PM.
Budget you can see
Spend against plan, milestones and invoices on one line.
Nothing slips past
Replies from the team, Flo answers and overdue invoices, as they happen.
Integrations
Flo works inside the tools you already run. Read access by default. Write access only where you switch it on.
- Slack Messages
- Gmail Email
- Outlook Email
- Linear Projects
- Jira Projects
- ClickUp Projects
- Notion Docs
- HubSpot CRM
- Google Drive Files
- Fakturownia Invoicing
- iFirma Accounting
- Stripe Payments
- BaseLinker Orders
- Allegro Marketplace
- Shopify Store
- WooCommerce Store
- Subiekt GT ERP
- Comarch ERP ERP
Missing one? We add connectors during your rollout.
See all integrations Rollout
Live in a few weeks, on your own procedures. A paid rollout: we set Flo up and run it next to your team.
Example rollout plan
paid, a few weeks
- Week 1–2
- Week 2–3
Connect your tools
Read access first: email, Slack, Linear, ERP
- Week 3–6
Flo runs next to your team
Every draft approved by a person, rules tuned weekly
- Week 6
Go live
Write access only where you switch it on
Live
FAQ
Questions we hear on the first call. Ask us anything else live.
What does Flo actually do?
Flo reads messages, orders and documents against your procedures, prepares the next step and shows its sources. A person approves before anything leaves the company.
Is it for agencies or manufacturers?
Both. Agencies use it for intake, the client portal, scope and team workload. Manufacturers use it for orders, complaints, costs and procedure checks.
Do we have to change our tools?
No. Flo connects to the tools you already run and starts with read access. Write access is switched on per tool, when you are ready.
What if Flo gets it wrong?
Flo never acts alone. Every draft shows its sources and waits for a person, so a wrong answer is caught before anything leaves the company.
What do clients see, and what stays internal?
Clients see their plan, requests, files and invoices, and can ask Flo about them. Margin, team workload and internal notes stay with your team.
How does the rollout work?
A paid rollout of a few weeks: we map your procedures, connect the tools and run Flo next to your team until the answers match how you work.
Where is our data stored?
In the EU. Your data is not used to train models, and every action Flo takes is logged with its source.
What does it cost?
A rollout fee and a monthly subscription per company. We quote after a short call about your processes.
See Flo run on your own procedure
A 30 minute call. Bring one procedure, we show you Flo checking it.
Paid rollout in a few weeks. Read access first, write access when you are ready.