Floowed

Tool snapshot
Best fitProductivity · Design · Sales
In one lineFloowed runs recurring business cases across people and systems, using document interpretation, follow-ups, rules, and recorded actions.

Floowed is an operations platform for recurring work that passes between people and systems. Examples include supplier onboarding, customer handovers, and change requests. The official workflow explanation describes a case that can stay open while documents arrive, follow-ups run, and approvals wait.

Defining the operation

You can describe an operation in Slack, Microsoft Teams, or the Floowed Dashboard. The platform drafts rules and connects the work to supported systems. Rules can be expressed in plain words or code.

Start with the event that opens a case and the conditions that close it. Define missing-document paths and who handles an exception. Floowed's intended use is recurring cross-system work, so a process with repeated handovers is a more relevant evaluation than an isolated writing task.

Gathering and checking information

Each case uses five stages: gather, interpret, chase, decide, and act. Floowed can read PDFs, scans, photos, spreadsheets, and emails, then compare documents with each other and system records. It records source evidence down to page and line level.

Follow-ups run on your schedule and can escalate to a named person. A case can loop through the stages while waiting for a corrected document or answer. In a trial operation, inspect both a complete case and one with missing information to see whether the configured exception path matches your process.

Rules, approvals, and version review

The publisher says a deterministic policy engine applies your rules, while models read documents and draft messages. You can require approval for every case or only for exceptions. Each case records the rule version and actions taken.

Before publishing a change, you can replay a rule version on past cases. The dashboard reports waiting points, time to outcome, human involvement, and case costs. Use those records to review the effect of a rule change rather than relying on a demonstration's sample outcome.

Credits and deployment considerations

The pricing page offers 8,000 free credits, equivalent to $80, without a card. Paid Team sizes start at $100 monthly for 10,000 credits, shared across the team without seat charges. Free credits do not expire; paid credits roll over for one month.

Case cost depends on document volume and follow-up work. Private deployment is available, while the homepage states that SOC 2 certification is on the roadmap and has not yet been obtained. Assess the required controls and connected-system permissions before running a production operation.