./i-need-a-partner

Your technical counterpart.

Some products are a project. Yours is a company. What it's missing is someone who holds the technical side of the business with you, for years, not weeks.

That's a different relationship. A contractor executes decisions. A counterpart argues with you before the decision gets made.

What this looks like

Ongoing engagement, typically a set number of days per month. Within that:

  • Architecture and decisions. Stack, data model, build versus buy, fix now versus later. Documented, so decisions outlive conversations.

  • Hands-on building. The features I specify, I build. Strategy and keyboard, same person.

  • Managing developers. Reviewing work, setting standards, running the technical side of hiring. Your team gets someone they can be honest with.

  • Business thinking. Pricing, retention, which feature actually moves revenue. This is the part most technical people skip, and it's why this site says "I build businesses, not just software."

  • Investor conversations. Technical diligence, architecture questions, the story behind the stack.

What I bring

Products of my own, shipped end to end: App Store, Google Play, paying users, the whole unglamorous middle. I know what breaks after launch because it broke on mine first. The expensive mistakes are already made, on my own money.

What makes it work

Real decision-making access, honest numbers, and room to disagree. The whole value of a counterpart is that he can tell you no.

FAQ

What's the difference between this and hiring a freelancer?
A freelancer takes your decisions and executes them. A counterpart is accountable for whether the decisions were right. Different work, different relationship, different price.
Are you available full-time or exclusive?
I run my own products alongside, and that's precisely what makes this valuable: you get someone who's currently shipping. I take a small number of partnerships at a time.
Can this convert into a co-founder arrangement?
It's happened. Equity follows from working together well, so the first conversation stays about the work.
Can I start smaller?
Yes. Most partnerships start as a blueprint or a single build. That's the sensible way to find out how we work together.