At ten people the founder still runs every deal, and every pilot depends on something engineering has not shipped yet. Flori keeps the deal, the pilot plan and the requests on one record, while your engineers keep working in Cursor or Codex.
Fig. 1 · DemoThe pipeline the week Lumen Health started its pilot
Lumen Health signs a 60-day pilot. The success criteria sit in a doc nobody opens until day 55, and the day-30 check-in never happens.
Northwind and Harbor Bank both ask for an audit log export, a week apart. The ticket has no names on it, so nobody tells either of them when it ships.
Six people spend forty minutes saying what they did, because the CRM, the issue tracker and the pilot doc each hold a third of it.
Link the pilot to its deal and start it from the same template every time: kickoff, data import, day-30 check-in, success review. When the customer owes you something, mark the task Waiting so it shows up in sync instead of in someone’s memory.
Project templates: Core and up
What a customer asks for on a call becomes a task linked to their account. Review captured meeting notes and accept the relevant tasks with an owner; check the saved result before relying on a handoff to engineering.
Meeting notes: Core and up
Mark a task Ready for AI and one assistant claims it, so another connected assistant can see the claim and wait. The result waits for review with the pull request link, and once it merges the release shows on the project for whoever sells.
Home shows what your assistants propose, today’s tasks and the next seven days. Put the pipeline by stage, active pilots and tasks waiting on customers on one dashboard, and the Monday meeting becomes decisions instead of updates.
Fictional example: An example from Quillmark, which sells document workflow software to logistics and health companies.
Sync takes fifteen minutes. Everyone reads one dashboard: deals by stage, two pilots, four tasks waiting on customers.
Maya’s call with Harbor Bank ends. The Fireflies notes become tasks, and Claude saves the export request to their account.
Jordan marks the export’s tests Ready for AI. Codex claims them and saves the result with the pull request link.
The release shows on the project. Maya emails Northwind and Harbor Bank from their records before lunch.
Free covers 3 active projects and 200 customer records, enough before your first pilot. Core adds unlimited projects, pilot and onboarding templates, GitHub on the project, Slack and meeting notes. Your engineers’ assistants are never seats.
Core $12 per person a month, or $10 billed yearly
Start freeUsually around the first pilot, or once you have 15 to 20 live conversations and cannot remember who asked for what. Starting then is cheap, and the history exists when your first sales hire or an investor asks for it.
Yes. Plenty of teams keep their tracker for sprints and use Flori for customers, pilots and the requests that come from them. If you want to drop the tracker, see Flori vs Linear.
No. Assistants are never seats, and Flori sells no AI credits. Each engineer connects the assistant they already pay for, to one project or the whole workspace.
Core is $12 per person a month, or $10 billed yearly, so $60 to $72 a month for six people. Guests, such as an advisor or a pilot customer, are free. See pricing.