Neoflow is built against a single day: the day a lead becomes a paid, delivered, invoiced project. Twelve steps, in order, from the enquiry landing to asking for the testimonial. Every feature has to serve one of them.
The rule sounds like a product principle. In practice it is mostly a way of saying no, which is the part that actually matters.
What it has already stopped
- A site builder. Agencies have one, and it is not our craft.
- A storefront. Nothing in the twelve steps sells a product off a shelf.
- A directory of other agencies. Interesting business, different business.
- A campaign scheduler. Publishing is not the day we are running.
- A generic automation canvas. That is a way of making the customer build the product.
Every one of those was a reasonable idea. Reasonable ideas are how software becomes forty features that each work a bit.
Why one workflow beats one platform
A tool that covers a whole workflow can act. It knows that the delivery was approved, so it knows the invoice is due; it knows the invoice was paid, so it knows the testimonial request is now well-timed. A tool that covers one step of five different workflows can only display.
That is the entire argument for the scope. Not that a narrow product is tidier, but that a narrow product is the only kind that can do the work instead of showing it to you.
What happens when the day changes
Agencies differ, and the twelve steps are not a claim that every studio runs identically. They are a claim about shape: enquiry, agreement, money, production, approval, delivery, money again. A studio that never takes a deposit still has step four; it just runs it later. The steps are the skeleton, not the uniform.
When we get one of them wrong, we would rather hear it from an agency in the first month than discover it in year two. That is what the founding cohort is for.