About Clientflow
The studio behind the blueprint.
A UK software studio, founded in 2023 by Zac Santer and Sohail Chowdhary. We design and build bespoke client portals, internal tools and apps for established teams, at a fixed price scoped from a blueprint, and the client owns every account and the code.
Founders
Who you would be working with
The people who scope a build are the people who deliver it. There is no sales team in between.
Zac Santer
Co-founder and design lead
Zac scopes every build and writes the number on every quote.
Sohail Chowdhary
Co-founder and technical lead
Sohail designs the architecture, builds the backend and reads every change before it ships.
- Founded
- 1 August 2023
- Registered as
- Clientflow Ltd, a private limited company
- Works with
- UK and US teams
- Contact
- hello@clientflow.ai
What we build, and what we say no to
What we build
Software for the part of the work that is being done twice: in a spreadsheet, in an email thread, or in a tool that almost fits.
- Client portalsYour clients see and act on their own records: jobs, documents, approvals, invoices, requests.
- Internal toolsThe approvals, requests, boards and audit trails that run the work, with your team on the other side of the same data.
- AppsThe same system on the web, macOS, Windows, Linux, iOS and Android.
What we say no to
Some blueprint calls end with a recommendation and no invoice. A build that does not pay for itself is a bad reference and a worse relationship.
- Builds under £10,000Not that the work cannot be done. It cannot be done well at a fixed price.
- A standard workflow a product already servesIf a product fits, the product wins, and we will point you at the setting.
- A process that is still changing every monthRun it by hand for a quarter, then build the version that survived.
- A build with no owner inside the businessWithout a decision-maker, a build stalls and you pay for the stall.
How a build runs
- 1
Blueprint call
FreeDay one
Twenty minutes with the people who would scope the build, to work out what version one should contain, or whether to build at all.
Apply for a blueprint callTwenty minutes on Google Meet - 2
Blueprint
ScopedWeeks 1 to 2
Scope, users, integrations and risks written down, with a clickable prototype, so the build is agreed before it starts.
- 3
Build
BuiltWeeks 3 to 8
Designed and built, AI-assisted for speed and senior-reviewed, wired into the systems you already run.
- 4
Launch and handover
OwnedHandover
Code, environments and documentation transferred to you, your team trained, and a warranty after launch.
What you own, and how we price
Yours from the first week
Owning software is the point, and it is arranged before the build starts rather than negotiated at the end.
- The codeA repository in your name from the first week.Yours
- The accountsHosting and database opened in your name, in the region you choose, paid by you directly.Yours
- The intellectual propertyAssigned to you under the agreement. UK law does not hand it over by default; the agreement does.Assigned
- The stackNext.js, TypeScript, Supabase, PostgreSQL and Vercel. Standard and documented, so the next developer is useful on day one.Standard
- At handoverYou hold every account outright, including the ability to remove us.Yours
One price, from the blueprint
No hourly rate. The blueprint turns a band into one price in writing, and it moves only if the scope does.
- Three bands£10k to £25k, £25k to £50k and £50k and above, with what moves a build between them.
- A warranty window, then a choiceAnything that does not do what the blueprint says is fixed at no cost. After that, support is a fixed monthly fee and optional.
What we publish, and how we check it
The guides put real numbers on what software costs, what it costs to run, and when not to build. Every third-party figure links to its source with the date it was read, and each guide carries the date it was last verified.