Anatomy of a great builder profile on KMRWW

Your profile is the first conversation you have with the rest of the community, even if you're not talking. If it's empty, the right people scroll past; if it's full of words without substance, the right people also scroll past. A great profile answers three questions in under 30 seconds of reading.

Three questions, nothing more

1. What do you bring that's useful to others? Not "passionate entrepreneur": "I design consumer products, run user research, worked 4 years in digital retail".
2. What are you looking for? Not "growth": "technical cofounder for a B2B marketplace idea, or to join a validated product that needs design".
3. How much real availability do you have? Hours per week, full-time or moonlighting, time zone.

If your profile answers these three, you're already above 80% of the profiles we see in other communities.

What belongs on it

• One or two projects with a verifiable outcome. Not an endless list. Two well-told projects beat ten decorative lines.
• A specific vocabulary for your role. "Product designer focused on discovery" beats "creative full-stack designer".
• Something personal that isn't decoration. "I prefer building in small cohorts of 2-4 people" is useful info; "passionate about innovation" isn't.

What clutters it

• A stack list with no context. React, Node, Python, AWS, SQL, NoSQL, GraphQL. Great — for what?
• Adjectives about yourself. Disciplined, proactive, creative. Show it with facts; don't declare it.
• Aspirational profile without evidence. "Building the next unicorn" — fine, tell me in 3 lines what you actually shipped this month.

A rule about tone

Your profile should sound like you. If someone meets you afterwards and you sound nothing like what you wrote, you've already lost trust. Write it like you'd tell a colleague over coffee, not like you're applying to a fund.

The final test

Read your profile from the perspective of someone finding you for the first time. Would they know whether they want a call with you this week or not? If the answer isn't a clear yes or no, keep editing.