Vibe coding for every seat at the table. By role, by industry.
CEOs, CFOs, marketing managers, operations managers, customer service leads and the rest of the company are building their own software with Claude Code and OpenCode. Each page below is written for one role in one industry: what you will build first, what breaks, and what a CTO in your corner changes.
Executives and managers are building software. The job changes what to check.
Vibe coding is building working software by describing what you want to an AI tool and letting it write the code. It has moved from a hobby to something people do at work on a Sunday afternoon: a dashboard the data team said would take a quarter, a customer portal the agency quoted at $60,000, an internal tool nobody would prioritise.
The tools do not care what your title is. Your job does. A CFO's first app touches money and books. A marketing manager's touches customer data and the public website. An operations manager's touches the process the whole shift runs on. The risks are different, and so is the first thing to check before anyone else uses it.
Pick your role. Then pick your industry. Every page is specific to that combination, and every one ends the same way: a free call with a CTO who has read hundreds of apps like yours.
Pick your seat.
Vibe coding for CEOs
Vibe coding for CEOs: build the thing yourself, without becoming the person who broke it.
Vibe coding for COOs
Vibe coding for COOs: the operations tool you always wanted, built by you, before it runs the company.
Vibe coding for CMOs
Vibe coding for CMOs: ship the landing page, the calculator and the campaign tool without a ticket to engineering.
Vibe coding for CFOs
Vibe coding for CFOs: the model, the reconciliation and the dashboard, built by the one person who knows what the numbers mean.
Vibe coding for CIOs
Vibe coding for CIOs: the shadow IT problem is now an executive problem, and also your best opportunity in years.
Vibe coding for CPOs
Vibe coding for CPOs: from a spec that describes the product to a build that is the product.
Vibe coding for CROs
Vibe coding for CROs: the pipeline tool, the quote builder and the deal desk, built by the person who carries the number.
Vibe coding for CHROs
Vibe coding for CHROs: the onboarding, review and people tools you always wanted, built with the most sensitive data in the company.
Vibe coding for marketing managers
Vibe coding for marketing managers: build the page, the tool and the report yourself, and stop waiting for a developer.
Vibe coding for social media managers
Vibe coding for social media managers: the scheduler, the analytics and the content tool that fit how you actually work.
Vibe coding for purchasing managers
Vibe coding for purchasing managers: the supplier portal, the approval flow and the spend report the ERP never gave you.
Vibe coding for operations managers
Vibe coding for operations managers: the tracker, the checklist and the dashboard your team runs on, built by the person who runs it.
Vibe coding for customer service managers
Vibe coding for customer service managers: the macro tool, the escalation queue and the dashboard the helpdesk never shipped.
- Vibe coding for CEOs →
- Vibe coding for COOs →
- Vibe coding for CMOs →
- Vibe coding for CFOs →
- Vibe coding for CIOs →
- Vibe coding for CPOs →
- Vibe coding for CROs →
- Vibe coding for CHROs →
- Vibe coding for marketing managers →
- Vibe coding for social media managers →
- Vibe coding for purchasing managers →
- Vibe coding for operations managers →
- Vibe coding for customer service managers →
Then pick your industry.
Every role page links to its industry pages. The rules below decide what has to be true before anyone else uses what you built.
SaaS
Every table has a customer ID and every query must filter by it. The AI often forgets on the second screen. The first check on any SaaS build is whether customer A can see customer B.
Healthcare
Names with appointment times, email addresses with a condition, a photo of a form. If it can identify a patient and relates to their care, it is protected health information and it cannot sit in a default database on a personal hosting account.
Fintech
Floating-point arithmetic rounds. The AI uses it by default. A ledger, a fee calculation or a payout built that way will be wrong by pennies that add up to an audit finding.
E-commerce
Payment details go through the payment provider and nowhere else. A tool that touches a card number, even briefly, brings PCI obligations the company does not want. The AI will happily build a card form. Do not let it.
Real estate
Rental applications hold income, identification, employment and sometimes credit information. Fair housing and privacy laws apply, and a tool that stores it needs real access control and a retention policy.
Professional services
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.
Education
FERPA in the United States, GDPR in Europe, and rules about children's data almost everywhere. A tool that stores a student's name, grades or attendance is regulated, and a tool used by under-13s has additional consent requirements.
Logistics
Carrier APIs change, EDI feeds drop, keys expire. A tool that stops syncing without an alert leaves two systems disagreeing about where the freight is, and nobody finds out until a customer calls.
Whatever your title, the first call is free.
Thirty minutes with a CTO who has read hundreds of apps like the one you are building. What you built, what is going on with it, whether we can help.
In your corner.