Setup is four steps, and most teams finish in about 15 minutes. Nothing can send during any of them: connections start read only, and sending requires both a later permission grant and a per-action approval.
1. Create your workspace. Join through early access, name the workspace after your business, and you land in an empty Action Center. That emptiness is correct: flo.space has nothing to prepare until it can read a tool.
2. Connect your first tool. Start with the tool where most of your admin lives, usually the inbox (Gmail or Outlook) or QuickBooks. Each connection is a standard OAuth sign-in with the provider; flo.space never sees your password and requests read-only scopes first. Tool-specific walkthroughs: Gmail, QuickBooks, Shopify, Stripe.
3. Let the queue fill. Within a day, prepared actions appear: a reply drafted for a customer thread, an invoice implied by a confirmed quote, a follow-up for a conversation that went quiet. Each card shows the draft, the source record it was built from, the reasoning, and a risk level. Read a few without approving anything; grading the drafts against what you would have written is the fastest way to calibrate trust.
4. Approve your first action. Pick a low-risk one, check the draft against its cited source, and approve. That grant-plus-approval is what allows the write; the action executes in the real tool and lands in the audit trail. From here, the daily rhythm is one short sitting: open the queue, clear the decisions, done.