You have the market. I do not start from scratch.

Why project by project

Every project gets its own agreement, without a shared company, merger or open-ended commitment. If a project dies, that costs that one project and the partnership stays intact.

You keep your own company, I keep mine. Only once the pattern repeats two or three times do we talk about something firmer.

What each side brings

We split the work into two sides. There are no further task agreements.

You

The market and the customers. Domain knowledge I do not have and cannot pick up in a few weeks. The judgement on which idea is worth building, and the first conversations that prove someone will pay for it.

Me

The product. Agents, automation, data and the infrastructure around it. A working base that already exists and gets stronger with every project, plus the maintenance once real users are on it.

What compounds

Every build reuses the code and agents of the last one. That is why a working product stands in weeks instead of months.

It compounds on your side too: every deal adds sector knowledge and warm contacts that make the next project easier.

Three models, one per project

We know which model applies before we start. Dividing things afterwards is where partnerships break.

Paid build

You want something built and want to own it outright. Fixed build price, agreed up front. Ownership fully yours; I keep only my own generic tooling.

Shared venture

We both believe in it enough to build without payment. Time and network instead of money, costs shared pro rata. The split is agreed up front based on what each side brings. Not automatically 50/50.

Venture with a domain expert

You have the knowledge and the idea but cannot build. You pay an entry stake serious enough to test commitment, and keep the larger share. I take a minority stake for the build and the growth.

What is running

Three products, each with the model it was built under, including the one I do not own.

• Signal Matchshared venture

  Turns a candidate CV into a client-ready profile in the agency’s own house style, anonymisation built in.

  Running at recruitment agencies since May 2026.

  signal-match.nl
• Business Boosterspaid build

  Finds B2B prospects for targeted outreach.

  Built, not owned: the client owns the brand and the product.

  business-booster.app
• Marketingburosshared venture

  An independent database of marketing agencies, with a wizard that assembles a shortlist.

  Online and still being built out.

  marketingburos.nl

What we put on paper before the first line of code

One page with five points, even when we know each other well. It takes half an hour and keeps you from having this conversation only once there is finally something to divide.

01 · Model

Which of the three it is.

02 · Contribution

What each of us brings: money, hours, code, network.

03 · Split

How revenue and ownership are divided.

04 · Decisions

Who decides what. Daily calls with whoever owns the domain, big calls together.

05 · Exit

What happens if one of us wants to stop or the project dies.

Why now

Building a product no longer costs what it cost three years ago. Where you needed a team and a funding round, two people with the right division of roles now get far. That changes which ideas are worth building: a market that was too small for a startup is big enough for a product.

I do this alongside my client work. The client work pays the bills and keeps me sharp on what companies actually need; the products test whether I can also build something people pay for without a client asking.

What this is not for

If you want someone to build your software on your bill, that is model one, the paid build, and otherwise a normal engagement. Fine, but do not call it a partnership.

If you are looking for capital, I am the wrong party: I bring build time, not money.

I also do not take on a run of partners each year to see what sticks. A few run at a time, because I can only do a few builds well at once.