The build is not late. The feedback is.
Web design agency software is usually sold as a project board, and a project board is honest about only one thing: whose turn it is. It cannot tell you that the client has had the staging link for nine days, that the copy for two pages never arrived, and that the invoice for the deposit is still a draft. Neoflow watches those three and does something about each.
The week you actually have
Four builds in flight, each one waiting on something a client owes you, and a launch date that was quoted before any of it was known.
Waiting is invisible
A task sits in "In review" for two weeks and the board looks exactly the same on day one and day fourteen. The cost of the wait lands on the launch date, and nobody sees it until the date does.
Content is the critical path
Every studio knows the project is blocked on copy and images the client has promised. Chasing it is nobody’s job, so it happens when somebody remembers, which is usually after the slip.
The scope moves in conversation
A second language, a booking form, one more template — each agreed in a reply, none of them in the proposal, all of them in the build.
What this changes
Three specifics, rather than a feature list
A chase that goes out on its own
When something has been with the client for longer than it should be, the follow-up is written, addressed to the contact you designated, and put in front of you to approve. The wait becomes an event rather than a silence.
The scope, in writing, in one place
Proposals carry the scope and the number, and an acceptance is recorded against the client. When a request arrives that is not in it, you have the document to point at without going through a mailbox.
The deposit invoice, drafted at acceptance
The moment a proposal is accepted the invoice exists as a draft with the right amount and the right client on it. Sending it is a decision; writing it is not.
Where the weeks actually go
Ask a studio why a six-week build took eleven and the answer is almost never design or development. It is three days here waiting for logins, a week there waiting for copy that was "coming Monday", and one round of feedback that arrived as a phone call and had to be reconstructed from memory.
None of that is visible on a board, because a board shows state and the problem is duration. Neoflow measures the duration: how long a thing has been with somebody, whose turn it has been, and what has not moved since the last time anybody looked.
What the operator does about it
It writes the chase. Not a notification telling you to write one — the message itself, in your voice, quoting the specific thing that is outstanding, addressed to the contact designated for that client, ready for you to send or edit. On the projects where you have said so, it can send it and tell you afterwards.
- Staging link sent nine days ago, no reply: a follow-up, drafted, quoting the date.
- Two pages of copy outstanding: a list of exactly which, not "the content".
- Proposal accepted this morning: the deposit invoice, drafted, waiting on you.
- A request that is not in the accepted scope: flagged against the proposal that says so.
It is not a design tool, and it does not want to be
Nothing here touches Figma, a code repository or a deployment. The work happens where it already happens. What changes is everything around the work: who owes what, how long they have owed it, what was agreed, and what has been billed.
The client sees a portal with their project, their approvals and their invoices, which removes the second-largest category of email a studio gets — "where are we?" — without anybody writing a status update.
Questions people ask about this
Do our clients have to log into anything?
Only if they want to. The portal exists and some clients use it, but every approval and every chase also works over mail or WhatsApp on whichever contact you designated. A client who never opens a link is still inside the loop.
Can it chase a client without me seeing it first?
Only if you switch that on for that kind of message, and only for a reply to somebody who just wrote in. A first chase is an outbound message and outbound messages wait for approval — the ceiling is enforced in the database, not by a setting on a screen.
How does it know what was in scope?
From the proposal you sent and the client accepted, which is stored with its body, its amount and the date of acceptance. It is not inferring scope from conversation; it is reading the document both sides agreed to.
We bill fixed-price, not hourly. Does that matter?
No. Projects can be fixed-price, retainer or milestone-billed, and the finance side is built around those three rather than around timesheets. There is no time tracking in the product and none is required.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
Continua a leggere
Point it at one client and see what it prepares.
Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by tomorrow morning. Free to start, and nothing leaves without you.