Vibe coding for CPOs in professional services.
At an agency, a consultancy or a firm, the CPO is often a new title for the person productising what the partners used to sell as hours. The tension is that the product you are building is fed by client work, and the prototype that proves it works needs client documents and client numbers that engagement letters say may not leave the firm's systems.
What is true about software in professional services before you write a prompt.
Agencies, consultancies, law firms and accounting practices sell time and expertise, and most of their software is a compromise: the practice management system, the time tracker, the client portal that nobody likes. Executives at these firms are building their own: a client dashboard, a proposal generator, an intake workflow, a utilisation report. Every one holds client confidential information.
Client confidentiality is the business
A tool that lets one client see another's project, or exposes a document to the wrong staff member, ends a relationship and possibly a licence. Access control per client is the first thing to build and the first thing to check.
The engagement letter has terms about data
Clients often specify where their data may be stored and who may process it. A tool on a personal hosting account in the wrong region breaches contracts the firm signed.
Billing must reconcile
Time, rates, expenses and invoices have to agree with the accounting system. A utilisation tool or a billing dashboard that drifts from the books causes arguments with clients and auditors.
Professional rules apply to software
Legal privilege, accounting standards and industry codes constrain how records are kept and who may access them. The tool has to fit those rules, not the other way round.
What a CPO in professional services builds first.
01The productised service as self-serve
The audit, assessment or report the firm delivers by hand, turned into a web app a client can run themselves. Built first for one friendly client so you learn what the partners' judgement was doing that the tool does not.
02The client portal for one account
Status, deliverables, invoices and the next meeting in one place, scoped so each client login sees only its own engagement. Built as a beta for one account before the practice management system is touched.
03The proposal generator from past work
Scopes, pricing and case studies pulled from previous statements of work, with client names stripped, so a partner can draft a proposal in an hour instead of over a weekend.
CPOs in every industry tend to build the same four things. The CPO page has that list.
Client deliverables used as test data
To make the generator convincing you load three years of client reports into the prototype and into an AI provider with no data agreement. Those reports are confidential under engagement letters, some are privileged, and the provider's terms may allow it to retain them. The cost is a breach of contract with every client whose work went in, and a managing partner who has to make that phone call.
The pattern underneath is the one every CPO hits: sales saw the demo. A customer signed. Now the exploratory build with no error handling and no tests has a contract attached, and 'we will rebuild it properly' has no date.
What a safe build in professional services usually runs on.
Builds run on a standard web stack with Postgres, private document storage, single sign-on for staff and a scoped client login, and integrations with the practice management, time and accounting systems through read-only keys where possible. Client-facing pages are separated from internal ones from the start.
What changes for a CPO in professional services.
A CTO in your corner draws the line between discovery and production, and helps you cross it on purpose. Prototypes stay cheap and disposable. The ones that are going to live get the ten things production needs before a customer touches them. When engineering takes over, it comes with a written account of what was decided and why. Discovery stays fast. The handover stops hurting.
What CPOs in professional services ask.
A CTO who has read professional services apps before yours.
Thirty minutes, free, no card. What you built, what is going on with it, whether we can help.
In your corner.