For studios Development, product & design studios

Keep builds moving through review, approval and handover.

Plan the full client delivery in one place, including design, development, testing and sign-off. Your team sees what can start next, while clients see the work you share with them.

Start free See pricing

✦ Free forever for two people · Clients never cost a seat · Runs alongside your issue tracker

Acme: Checkout rebuild · live flow

A software build mapped in Flowral: the API contract and auth service complete, the checkout build in progress, and the production deploy blocked until review and QA are both in.

Where projects slow down

Make every prerequisite visible

🔌

Start with agreed requirements

Keep build work on hold until the required design or specification is ready.

👀

Require the right reviews

Set the approvals that must be complete before work can move forward.

🧾

Include client work

Add client copy, legal review and sign-off to the same project plan.

📦

Plan the handover

Track documents, credentials and walkthroughs before the project is closed.

How a build looks

A delivery plan that follows the right order

Connect each task to the work and approvals it needs.

Choose how many approvals are required

A task can wait for every reviewer, a specific pair or a set number of approvals.

✓ Sub-tasks per node for the implementation detail, with estimates that roll up to the parent
✓ The client's tasks are in the flow too, so their delay shows as their delay
✓ The activity feed doubles as a changelog you can send without writing it
✓ Handover modelled as work, not as a checklist someone half-remembers

✓Agree API contractbackend · doneJD

✓Auth servicebackend · doneJD

▸Build checkout flowready · in progressMR

🔒Client UAT on stagingblocked · needs build

🔒Ship to productionblocked · needs 2 of 3 + UAT

Before it's scoped

A Brainstorm for the build, before it's a build

Most rebuilds start messier than a backlog can hold. Get every idea and risk out on an open canvas first, then scope the actual work once the shape is clear.

Acme's checkout rebuild started as a Brainstorm: why customers were dropping off, what "good" could look like, which building blocks already existed. The team tagged risks and assigned owners right on the ideas, well before any of it became a task in the flow above.

See how Brainstorms work →

Where it sits in your stack

Works alongside your issue tracker

Keep engineering issues in Jira or Linear. Use Flowral for the wider delivery plan: client input, approvals, testing and handover.

In the editor

Check what's ready without leaving VS Code

The delivery plan sits next to the diff, not in a tab you have to remember to open.

Flowral for VS Code

✓ My Work, Available and In Progress as sidebar trees
✓ A status bar count that updates the moment a review or sign-off clears
✓ The dependency graph for a build, read-only, beside your code
✓ Link the PR that closes a task from the command palette

Get it on VS Code Marketplace See all developer tools

FLOWRAL · sidebar

▸Build checkout flowMy Work · in progress

✓Client UAT on stagingAvailable · unblocked

🔒Ship to productionblocked · needs 2 of 3 + UAT

Studio questions, answered

Does Flowral replace Jira or Linear?

No. Keep Jira or Linear for engineering work. Use Flowral for the client-facing plan, approvals, testing and handover.

Can a task wait on code review and QA and the client?

Yes. A task can wait for all required approvals or for a set number of them before it becomes available.

Can we give the client visibility without giving them our backlog?

Yes. Clients see only the projects you share with them. They do not see your other projects or internal workspace.

Does it integrate with GitHub or CI?

Not today. Tasks are marked complete by people rather than automatically from GitHub, GitLab or a deployment pipeline.

Also built for creative & marketing agencies, consultancies, game studios and AI agents.