Vibe coding for COOs in professional services.
In a professional services firm the COO manages capacity: who is on which engagement, who is free next month, which projects are over budget and which invoices are stuck in partner review. The tension from this seat is that your resourcing tool decides people's weeks and clients' fees at the same time, so a wrong allocation is both a morale problem and a write-off.
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 COO in professional services builds first.
01The resourcing board
Every person's committed hours per week against every engagement's budget, four weeks forward, read from the time system and the project tool. Built first because the Friday staffing meeting runs on a spreadsheet only one partner understands.
02The unbilled work in progress ageing
Hours logged but not yet invoiced, by client and by how old they are, with the partner who has to approve them. Ninety-day-old unbilled work is where the firm's cash quietly goes.
03The intake and conflict check workflow
A new matter or engagement request checked against the client list, the adverse party list and the staff who have worked for the other side. Law and accounting firms need this before the engagement letter, not after.
COOs in every industry tend to build the same four things. The COO page has that list.
The resourcing board leaks client names to staff
Staff need the board to plan their week, so the AI made it visible to everyone logged in. Now a junior on one engagement can see that the firm is staffing a competitor's acquisition, with names and budgets. A conflict wall the firm promised in writing is breached by a screen nobody thought of as confidential, and the partner hears about it from the client.
The pattern underneath is the one every COO hits: three months in, the app is the only place the real status of anything lives. Then the database is changed by hand, or the hosting bill lapses, and there is no copy.
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 COO in professional services.
A CTO in your corner treats your ops tool as what it is: production software that the company runs on. Before the first team uses it, someone has checked how the data is stored and backed up, who can change what, and what happens when an integration fails. Every database change goes through a written migration you have tested on a copy first. You still build it. It just does not fall over when it matters.
What COOs 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.