For the founder who builds
You built the product. Now build the company.
You can architect systems, ship features, and debug anything. But setting direction for a team, structuring compensation, knowing when to prioritise speed over quality — and the commercial playbook on top of all that? Those are different disciplines. Nobody teaches them.
The gaps no one talks about
Building things is not the same as leading people.
Technical founders are superb builders. But the commercial playbook — pricing, positioning, sales hiring, board management, fundraising narratives — is a separate discipline entirely. It has its own patterns, its own failure modes, its own muscle memory.
Then there's the leadership playbook. You've always earned well, so you have no reference for what a Head of Marketing should cost — or that the right commercial hire might take less base and more commission because that's how they're wired. You respect autonomy because that's how you liked to work as an engineer. But not setting direction isn't the same as not micro-managing — it's how teams end up optimising for code quality when the company needs product-market fit.
The engineering instinct is to build things right. The CEO's job is to build the right things first. Those are different disciplines, and the company follows whichever signal you send.
The problem isn't ability. It's that you're making high-stakes decisions — commercial and leadership — without counsel who's seen the pattern before.
That counsel now exists.
Decisions you'll face
The calls that don't come with a Stack Overflow answer.
Pricing your product
You’ve built something valuable but you’re undercharging because you’re pricing like an engineer, not a market.
Founder-led sales
The first ten customers need to come from you. You know this. You don’t know where to start.
Hiring commercial leadership
VP Sales, Head of Marketing, CFO — who first? What does good look like when you’ve never managed the role?
Board management
Your investors want a board narrative. You have a product roadmap. Those are not the same thing.
Go-to-market direction
Product-led, sales-led, community-led — each is a bet. You need to pick one and commit.
Fundraising narrative
You can explain the technology. Can you explain the market, the wedge, and why now?
Compensation and incentives
You’ve always earned well. You have no reference for what a Head of Marketing should cost, how to structure sales commission, or when equity is worth more than salary to the right hire.
Setting direction without micro-managing
Your instinct is to give smart people space. But without clear priorities, teams default to what they know — technical debt, code quality, infrastructure — not what the company needs right now.
Speed vs polish
Your engineering instinct says ship when it’s ready. Your runway says find product-market fit before the money runs out. Those are different timelines.
Decision session
Counsel in practice.
This is a direction problem, not a management problem. Your team is not wrong to value stability — that's good engineering instinct. But they're following that instinct because you haven't given them a stronger signal. Setting direction is not micro-managing. It is the job. Try this: state the company's single priority for the quarter in one sentence. Make speed to learning the explicit measure of success, not code quality. Then let the team figure out how. You are not telling them what to build. You are telling them what matters most right now.
Why this is not ChatGPT
Not a chatbot. Private counsel.
Primed, not generic
Lucumo’s counsel is shaped by the playbook from CEOs who learned these lessons in the field — commercial and leadership. Not a Wikipedia answer. The answer a seasoned CEO would give over dinner.
Structured sessions
Decision sessions, weekly reviews, board prep. Frameworks, not open chat. Each session produces artifacts that persist.
Decisions compound
Your decision journal tracks what you decided and why. Months in, your counsel references your history: “You faced something similar last quarter.”