For consultancies Advisory, professional & specialist services

Every engagement, phase-gated — and visible to the client.

Discovery, analysis, draft, review, handover. The phases are the same every time; what changes is which client is late reviewing which deliverable. Flowral maps each engagement as a flow of dependent work, so no deliverable slips quietly and no consultant has to ask what's next.

✦ Free forever for two people · Clients never cost a seat · Unlimited engagements on every plan

Acme: Operating model review · live flow
A consulting engagement mapped in Flowral: discovery and draft deliverable complete, client review in progress, and final handover blocked until sign-off lands.
The consultancy version of the problem

The engagement is sold on outcomes. It's delivered through dependencies.

A statement of work lists deliverables. It doesn't say which one can't start until the client's finance team hands over three years of data.

📥

You're blocked on the client and it's nobody's job to say so

The data extract, the stakeholder interviews, the sign-off on the interim findings. Every one is a dependency you don't control, and every delay silently becomes your overrun.

🔀

Consultants are split across engagements

Someone is on three at once. Without a live view of what's genuinely ready, they optimise for whichever partner asked most recently.

🗓️

The status call exists to reconstruct status

Forty-five minutes a week, per engagement, spent assembling information that already existed but wasn't anywhere the client could see.

📄

Every engagement is rebuilt from the last one's folder

The shape is 80% identical each time. It gets recreated by hand each time, and the bit that was forgotten is different each time.

How an engagement runs

Phase gates that hold, and a client who can see them

Map the engagement once. The client's own tasks sit in the flow beside yours, which is what turns "we're waiting on you" from an awkward email into a visible fact.

The delay shows up as the client's delay

When the review task is in the flow, assigned to the client, with the date it's been sitting since, the conversation about the timeline stops being a negotiation about whose fault it was.

  • Phase gates — analysis can't begin until the data hand-over is genuinely complete
  • Reusable engagement templates so the eightieth review starts fully mapped
  • Workload across every live engagement, before you commit a consultant to a fourth
  • A client view that replaces the status call, updated by the work itself
Discovery workshopsphase 1 · doneSP
Data hand-overclient · doneClient
Interim findings reviewready · with client · 4 daysClient
🔒Final recommendationsblocked · needs review
🔒Handover & closeblocked · needs sign-off
What it isn't

This is not a PSA suite, and it won't invoice anybody

Professional-services automation tools handle time capture, rates, utilisation targets, resourcing forecasts and billing. Flowral does none of that. There is no timesheet, no rate card and no invoice, and adding them badly would be worse than not having them.

What Flowral does is the part those suites treat as an afterthought: the actual dependency structure of the delivery, enforced, with the client inside it. If your problem is "we can't tell what our utilisation will be next quarter", buy a PSA tool. If it's "a deliverable sat waiting on a client review for two weeks and we found out at the steering meeting", that is the problem this solves.

Most consultancies that adopt it keep their time and billing system exactly where it is. The two don't overlap enough to be a decision.

Map one engagement. Share it with the client.

Free for two people, forever. Client and guest access costs nothing on any plan — including the client whose review is holding everything up.

Start free, no card needed

Consultancy questions, answered

Does Flowral track time or produce invoices?

No. There is no timesheet, no billing rate and no invoicing, and there is no plan to bolt them on badly. Flowral tracks what is done, what is ready and what is blocked. Keep your time and billing tool; this sits next to it.

We run the same engagement shape repeatedly. Can we reuse it?

That is what templates are for. Save a completed engagement as a template — phases, dependencies and sign-off gates intact — and every future engagement starts fully mapped instead of being rebuilt from the last client's folder. Saving new templates is a Pro feature; starting from templates you already have is not.

Can two clients ever see each other's work?

No. Guests see only the specific flows shared with them, never the workspace as a whole and never each other. If you need harder separation than that — different clients in different workspaces — workspaces are unlimited on every plan.

Our engagements change scope constantly. Doesn't a dependency map break?

Gates are set per task, not globally, so you use them where a real handoff exists and leave the rest of the flow open. A flow is edited the same way a plan is: drag in the new phase, draw what it waits on. The point is not rigidity — it is that a genuine blocker cannot hide.

Can a client see progress without us running a status call?

That is the usual reason consultancies adopt it. Share the engagement flow and the client sees, live, what is complete, what is in progress and what is waiting on them — including their own review tasks, with the date they have been sitting since. Client access is free on every plan.

Also built for creative & marketing agencies and dev & product studios.