Finding a collaborator: a practical checklist before you commit

Most collaborations don't fail because someone lacked skill. They fail because expectations were never said out loud: how many hours, who decides, who owns what, and what happens if one person stops.

Use this checklist before you commit to building something together.

1. Start from the gap, not the person

Write down the two or three skills the project needs that you don't have. A developer usually needs someone who can reach and understand users; a designer often needs someone who can ship working software. Look for complementary strengths, not a copy of yourself.

2. Match on availability and pace

Someone with 4 hours a week and someone with 30 will both be frustrated. Agree on realistic weekly hours and the rhythm that suits you both — mostly asynchronous, regular calls, or a mix.

3. Run a two-week trial project

Before agreeing to anything long-term, pick a small, finishable piece of work: a prototype, five user interviews, a landing page test. You'll learn more about working together in two weeks of real work than in hours of conversation.

• Define what “done” looks like on day one.
• Share progress at least twice a week.
• Hold a short, honest retrospective at the end: what worked, what didn't, continue or not.

4. Agree the basics in writing

A one-page document is enough at the start. It should cover:

1. Roles and who makes the final call in each area.
2. Expected hours per week and how you'll communicate.
3. Who owns the code, designs and content created so far, and what happens to them if someone leaves.
4. How any future revenue or equity will be discussed (even if the answer is “we'll decide at milestone X”).
5. How either person can step away gracefully.

For anything involving equity, money or company formation, get advice from a qualified professional. A simple written agreement now prevents most painful disputes later.

5. Watch for early warning signs

• Repeatedly missed commitments without a heads-up.
• Reluctance to put agreements in writing.
• Pressure to pay before any trial work.
• Claims you can't verify — ask to see past work.

6. Make it easy to say no

Not every promising conversation should become a partnership. Ending a trial politely is a success: you learned cheaply. On KAIOS BUILD, you can hide a suggested match at any time, and nobody is notified.