Active work first
Finished tickets should not crowd the thing that is on fire. The dashboard hides completed work by default because attention is the scarce resource.
Our story
Crafted for calmer client work.
Flowgrid exists because client work is not classic project management. It is a messy stream of email, requests, boards, meetings, and invoices. The tools never fit that shape.
Born in the studio
Built by someone who runs the work
Dan Heselton built Flowgrid on the North Shore after years of gluing apps together for agency and freelance delivery. The product is opinionated because the days are.
The goal was never enterprise software. It was one calm surface for the loop that pays the bills, with polish you do not have to apologize for in front of a client.
How we decide
Three bets we keep making
Bill from real hours
If the timer ran, the invoice can start there. Studios deserve billing that matches the day they actually lived, not a reconstructed Friday fiction.
Clients should not need another login
Status, files, and tickets belong on a branded portal URL. Asking a client to create an account for every vendor is how trust frays.
The path
From duct tape to a daily driver
The mess
Notion for notes. ClickUp for tasks. Gmail forever open. Spreadsheets for hours. A graveyard of almost-working stacks.
The daily driver
Flowgrid became the pinned tab for real client work: inbox to board to invoice, with meeting notes and a portal that clients actually use.
Open to studios
What started as one studio's operating system is opening to freelancers and small teams who recognize the same loop.
