Getting started
What flo.space is, and what the first week looks like.
flo.space connects to the tools you already use, prepares the next action as a draft, and waits for a person to approve it. Nothing sends itself.
About 15 minutes: create a workspace, connect your first tool read only, and let the queue start filling. Most teams review their first prepared actions within a day.
No. flo.space reads your tools in place. There is nothing to install, no data to move, and no rip and replace. Disconnect any time and your tools are exactly as they were.
The queue fills from live activity, not history: flo.space proposes from what is happening now, so a quiet inbox produces a quiet queue. Read the first drafts against what you would have written, then approve one when it earns it.
Connections and data
What connects, what gets read, and how leaving works.
60+ apps connect, including Gmail, Salesforce, QuickBooks, Google Docs, Google Drive, Google Calendar, Outlook Mail, HubSpot Contacts, Xero. Whichever one you pick, it starts read only and nothing writes back until you approve the action. Every one of them is listed on the integrations page.
No. Every connection is a standard OAuth sign-in with the provider, and flo.space requests read only scopes first. Your password never passes through us.
Instantly, from either side: in flo.space settings, or from the provider's own security page. Reading stops immediately, pending actions that depended on the tool are cancelled rather than silently executed, and working context from that tool is deleted per the privacy policy.
The working context it needs to prepare actions, read from the tools you connected. Data is encrypted in transit, deletion follows the privacy policy when you disconnect, and the details are written plainly on the security page.
Approvals and control
The part that makes the rest safe.
No. Sending requires two things: a permission grant on the connection, and a per action approval by a person. There is no autopilot mode to switch on.
Yes. On the Team plan, each Rep approves their own cards, and the Owner can approve every card. Business adds the Manager role, so managers approve for their own teams. Roles are explained in the team roles guide.
Edit it in plain language or decline it. Every edit produces a new draft you read before approving, so you always approve the exact text that sends. Declines are kept on the trail too: judgment exercised is part of the record.
Pricing and seats
The numbers, the same ones the pricing page publishes.
Starter is $149.99 per month for one owner, solo only. Team is $249.99 per month with the first user included, plus $49.99 per added user per month, up to 5 users. Business is $499.99 per month with the first user included, plus $49.99 per added user per month, up to 25 users. Custom starts at 26 users and is priced for each company. Annual billing takes 10% off every rate. The whole thing fits on the pricing page.
The first 100 customers lock the rate they join at, for as long as they stay. It is the only offer we run, and the details live in the early access terms.
No. Joining the list takes an email, not a card. Billing only ever starts with a plan you chose yourself.
Security and privacy
Who sees what, and where the record lives.
Access follows role and team, not tool: a Rep sees their own cards, a Manager (Business and Custom only) their team’s, and the Owner every card. Removing a seat hands its cards to no one.
Each action’s full life: the sources read, the draft, the reasoning, every edit, the decision with who and when, and the exact result the tool returned. Nothing that executed can be deleted from the record, and the owner can export all of it.
On the security and privacy page and in the privacy policy, both written to be read rather than skimmed.
Ask the missing question
Early access means a person answers, usually the person building the thing.
Email hello@flo.space with the question this page did not answer, or pick a time that suits you.
