Looking for a technical partner for my SaaS project — honest status report

as a dev: i usually skip "no salary, just equity" posts. not because i don't believe in equity, but because most posts lack proof the product actually works.

you have three companies using it and two are paying. that's the most valuable part of your post, put it right at the top.

when offering equity, set up a vesting schedule. a one-year cliff followed by three years of vesting is a common structure.

keep this in mind when budgeting: partnership agreements and share transfers incur notary and consulting fees. it's not a small amount, factor it in from the start.

moving to the tech side, a question: what's the current state of the prototype? if the person taking over will have to rewrite it from scratch, you should say so upfront.

the difference between taking over and rewriting from scratch completely changes the partnership conversation. if it's going to be rewritten, i think that person should be considered a co-founder.

The cheap-looking path usually ends up costing more later. If you're offering equity instead of salary, also state what you're offering in return.

Proven by experience.

I'm in the same situation that's why I'm asking. Mistakes made on the partnership side are usually reversible but expensive.

The discussion got scattered, let me summarize. When we decide without measuring, we always end up in the same place.

Just because everyone does it doesn't mean it's right. This is my opinion, I'm not claiming it's absolute truth.

following. honestly valuation methods for exits must be defined by formula; "market value" isn't enough.

just leaving this note it might be useful.

I went through the same thing.

Correct in theory, but it doesn't work that way in practice. Are you looking for a partner or a co-founder? They are two different things.

Trying to do this alone is the most expensive way. Of course, it varies if your situation is different.

Thanks for posting.

The opposite happened to me, that's why I'm writing. If it's your first time, start small; scaling comes later.

The harder it is to reverse a decision, the slower you should make it. This is my opinion, I'm not claiming it's absolute truth.

i went through the same thing two years ago but taking notes for two weeks yields better rsults than a six-month estimate.

when you try to change everything at once, nothing settles and just leaving this note, it might be useful.

this is exactly what we experienced.. but trying to do this alnoe is the most expensive way.

the answer varies greatly by industry; there is no one-size-fits-all rule. honestly good luck with that.

Let me share my experience. Everyone rushing into partnership gets stuck at the same point.

If you post the result here, it will help others too.

i disagree with you on this point. anyway if you don't write this down from the start, it leads to arguments later.

if you post the result here it will help others too.

I partly agree, partly disagree. Partnership isn't a decision to make without working together first.

If you post the result here, it will help others too.

Let me write how it's done in practice. Partnership isn't a decision to make without working together first.

Dont hesitate to ask; those who dont ask always pay more. honestly correct me if Im wrong.

You're right. When making decisions write down the worst-case scenario too, not just the best.

That's all sorry if I went on too long.