Community Guidelines

• Say what you actually do and what you actually want. A precise headline beats an impressive one.
• Show evidence — links to real work, shipped things, writing. Claims without evidence get ignored.
• Keep availability and status current. If you are no longer looking, say so.

• State the problem before the solution. Be honest about the stage you are really at.
• Be specific about the roles you need and what you can offer in return — equity, pay, learning, credit, or simply good company on a hard problem.
• Post updates as the work moves. The build log is more useful than a launch.

• Send a real message, not a template. Reference their work and say why you specifically.
• One thoughtful message beats ten copies. Do not mass-message.
• Take “no” or silence gracefully. Do not follow up more than once.

• Agree the basics early — scope, time, ownership, and how you will make decisions and split anything of value.
• Put agreements in writing between yourselves. Foundbrew is not a party to your collaboration.
• If it is not working, end it cleanly and honestly. Update your profiles and, where relevant, the project.

• Write from real work. Concrete beats abstract; specific numbers beat vibes.
• Do not publish others’ private information, unpublished work, or confidential details without permission.
• Mark speculation as speculation. Correct mistakes openly.

Code of Conduct · Acceptable Use Policy · Terms of Service