AI scribe for dietitians
Healthcare
The scribe listens in during a consultation and writes the report in the dietitian’s own template. The dietitian approves, nothing goes out on its own.
/ Co-invest
A company together. We’re the CTO.
Co-invest is our model for people whose plan runs on software but who lack a technical partner. We set up a company together, split shares and IP 50/50, and take the CTO role. You bring the industry, the customers and the operations.
Pitch your ideaWhy
Software is your core, but the CTO is missing.
You’ve known your industry for years and your customers are waiting for a solution. But finding a good CTO is hard, building a development team is expensive, and hiring a vendor feels like outsourcing the heart of your company.
So we step in. Not as a vendor on an invoice, but as a co-owner who builds the product and keeps it running. We only earn when it sells. That keeps us sharp.
- Structure
- A separate company, founded together
- Shares and IP
- 50% you, 50% KangaCoders
- Your role
- Sales, operations, customers
- Our role
- Product, tech, hosting, the CTO role
- Revenue model
- Recurring, ideally a licence per user
- How many
- A handful at a time
Every deal is different. This is where we start from.
Who we look for
We say no more often than yes.
Yes
- You’ve been in your industry for years and know the problem from the inside
- There’s a clear business case: customers who pay, or already ask for it
- You take on sales and operations yourself, full time
- The product makes people’s work or lives noticeably better
No
- An idea without an experienced founder behind it, however good it sounds
- A product without a clear payer
- Something where you’re really just looking for a cheap developer
A co-invest takes years. That’s why we only run a handful at a time.
How it runs
From first talk to company in five steps
- 01
Pitch
Half an hour, at our table or on a call. You tell us what’s missing in your industry and who would pay for it.
- 02
Thinking phase
Together we find out whether it makes sense technically and commercially: scope, first version, cost. If it doesn’t, we say so.
- 03
The company
Shares, IP, roles and what each side brings. All agreed before there’s a single line of code.
- 04
Build
Short sprints, something to test every few weeks. You test along with real users from your industry.
- 05
Live and grow
Launch, sell, improve. We keep the product running, you take it to customers.
The CTO role
What you actually get
Not an adviser who drops by now and then. A technical co-owner with a team behind them.
- Architecture and security
- The choices that decide whether your product still runs in five years, and who gets to your data.
- Build and host
- Our team builds, tests and hosts the product. You don’t manage developers.
- At the table with customers
- The technical side of every customer conversation, every security review and every integration question.
In progress
What it looks like
Questions
What you’re probably wondering
Who owns the product?
The company we set up together. You and we each hold 50% of the shares, and so of the IP. No small print afterwards.
What does a CTO partner actually do?
Architecture, team, releases, security, hosting, and the technical side of every customer conversation. You don’t manage developers: you have one at the table who co-owns the company.
How many co-invests do you run?
A handful at a time. Each one takes years, so we’re strict in the thinking phase.
Do I need to be technical?
No. You need to know your industry and your customers. The technical side is our job, and we explain it in plain language.
Can it work without setting up a company?
Yes. With IP discount we build on our platform and you pay less. On assignment you pay everything and the code is yours.
Know your industry and miss the CTO?
Three sentences will do: what’s missing, for whom, and who pays for it. We’ll talk through the rest at the table.