A project tool holds one project. This holds how you work.
FlowGenica sits one layer above tasks, on the shape of the engagement and the commitments made to the client, the layer most agencies keep in a spreadsheet and a partner’s memory.
In build, design partners are shaping it now
Four ideas, and that is the whole model.
The template
Your delivery process, written once: stages in order, who owns each, how long each usually takes, what has to be true before it can close, and which stages depend on which.
One definition of how your agency delivers.
The engagement
Each client runs on a copy of the template with real dates, calculated from the start date and your working calendar. Divergence from the template is visible rather than quietly normal.
Every client on the same shape, with their own dates.
The movement
When a stage slips, the dates after it move through the dependencies. Nobody has to notice and nobody has to re-plan, the plan already says what the slip cost.
A delivery date that is true today rather than true at kickoff.
The view
One link for the client showing where their engagement stands, what is waiting on them, and what is next. Internal notes, margins and other clients stay on your side of it.
A status your client checks instead of asking for.
What it will do.
- Workflow templates
- Define how your agency delivers once, stages, owners, durations, dependencies and what has to be true before a stage can close. Every new engagement starts from it instead of from memory.
- Engagements on the template
- Each client runs on a copy of the template, with real dates calculated from the start date and the working calendar. Change the template and you decide what happens to work already in flight.
- Owners and load
- Who is responsible for each stage, across every engagement at once, so the week somebody is carrying four handovers is visible before it happens rather than after.
- Deadlines that mean something
- Dates move forward through dependencies. When a client returns feedback three days late, the delivery date moves and everyone sees it move, instead of the slack being absorbed silently by whoever is last in the chain.
- A client view worth sending
- One link showing your client exactly where their engagement stands, what is waiting on them, and what comes next. No login for them to lose, nothing internal exposed.
- What actually happened
- Which stages always overrun, which clients are always late, which engagements were profitable, measured from the record of the work rather than from the story told at the retrospective.
What it deliberately will not do.
Replace your task tracker
Your team keeps working where it works. FlowGenica is not trying to own the checklist inside a stage.
Time-tracking surveillance
Duration is a property of a stage, learned from how long stages actually take. It is not an instrument for watching people.
Invoicing and payroll
Two well-solved problems we have no intention of solving again, badly.
Chat
You have chat. What you do not have is a shared answer to where this engagement stands.
Where it is.
The product is being built with a small group of agencies running real engagements on it. We publish no launch date, because a date announced before the model is right is a promise made with someone else’s calendar.
If your delivery problem is urgent, the consulting engagement solves the part that software was never going to solve anyway: knowing what your process actually is.
Shape it around your agency.
Design partners get early access, direct influence over the model and preferential pricing. It costs about an hour a month and one real engagement.
or write to hello@genica.org