You build inside other people’s companies, so the work is split between their repos, your notes and the email thread where they keep asking for an update. Flori keeps each client, the build and its GitHub status on one record, and lets Cursor, Codex or Claude Code take tasks scoped to that one client.
Fig. 1 · DemoKestrel Labs launch site, milestone two
You deployed on Tuesday. The client finds out on Friday when they ask, because the release lives in GitHub and the client lives in your inbox.
Kestrel Labs agreed the blog was phase two. Three weeks later a pull request for it is open and nobody can say who asked for it.
Monday starts with three GitHub orgs, two client Slacks and your notes app, just to work out what is due this week.
Connect GitHub and the client’s project shows deployments, releases and pull request status next to the tasks and the milestone they belong to. The scope you agreed sits in the project brief, so the PR for phase two has something to be checked against.
GitHub: Core and up
Connect Cursor, Codex or Claude Code to one client’s project instead of your whole workspace. Mark a ticket Ready for AI, one assistant claims it, and the result waits for you with the pull request link before anything counts as done.
Publish milestones to the client’s page. They see what is on staging, approve it from one link and stop asking in Slack. Nothing reaches them until you publish it, and clients never pay for a seat.
Client pages: Core and up
Inquiries from your site form land as leads. Past clients stay as accounts with the builds you shipped for them, so the maintenance renewal or phase two is a deal on the board, not a thought in March.
Forms: Core and up
Fictional example: An example from Birchline, a three-developer shop.
My work shows everything due across four clients. Kestrel’s milestone is Friday, and one task is Waiting on their copy.
The form validation goes Ready for AI on the Kestrel project only. Cursor claims it and opens PR #48.
You request one change, approve the second pass and merge. The staging deployment shows on the project.
Milestone two goes on Kestrel’s client page. Their marketing lead approves the staging build from the link.
Free lets you connect Cursor, Codex or Claude Code and run 3 active projects, enough to try the queue on a real build. Core adds GitHub on the project, client pages, forms for inquiries and templates for your standard build.
Core $12 per person a month, or $10 billed yearly
Start freeNo. Code, issues and pull requests stay in GitHub. Flori shows deployments, releases and pull request status on the client’s project, on Core and up, next to the scope and the client.
Yes. Connect it to a single project instead of the whole workspace, with read-only or update access. Connection details are on the Flori MCP server page.
A founder builds one product for their own customers. You build several products for other companies, so Flori is set up around the client: one project per build, a client page per client, and assistants scoped to one client. See Flori for freelancers too.
Core is $12 per person a month, or $10 billed yearly, so $30 to $36 a month for three. Clients and assistants are never seats. See pricing.