Vibe coding for CEOs in professional services.
You run an agency, a consultancy or a firm, and you sell your own time, so every tool you build is paid for in billable hours you did not work. The tension is that the CEO's utilisation dashboard or client portal touches every engagement, and partners will trust its numbers before they check them.
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 CEO in professional services builds first.
01The client portal that replaces the status email
Milestones, deliverables and open questions per engagement, so clients stop asking for updates. The first thing to prove is that a client logging in cannot list the other clients, because the AI will build that list by default.
02The pipeline and capacity view
Proposals in flight against the hours your team has free next quarter, so you stop selling work you cannot staff. It reads from the CRM and the time system, and it should never write back to either.
03The proposal and scope generator
Past scopes, rates and templates assembled into a draft in minutes. Rates and margins from every prior client are now in one tool, and that tool needs access limited to the people who price work.
CEOs in every industry tend to build the same four things. The CEO page has that list.
Partners running the firm on a dashboard that drifts
Your utilisation tool pulls time entries nightly, and a change to the time system's export silently drops one office's hours. For two months the partners see that office as underused, cancel a hire and lose a lead. Nobody checked the tool against the accounting system because the CEO built it, and questioning it felt like questioning you.
The pattern underneath is the one every CEO hits: you demoed it, a customer bought it, and now the first version, built to look right rather than be right, is what the company sells. Nobody planned the handover because there was never going to be one.
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 CEO in professional services.
A CTO in your corner does not slow you down. Before you prompt, you get the ten-minute conversation about what to build and what not to. Before you show it to a customer, someone has read how it stores data and who can see it. When you hand it to a team, it comes with a written account of what it is and how it works. You keep building at CEO speed. The company stops paying for it later.
What CEOs 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.