A versioned, testable sales practice with evidence, steps, success signals, risks and human-review points.
- Problem + target user
- Evidence required
- Measurable success/harm signals
- Version + review points
Community members can contribute code, playbooks, practice rubrics, learning modules, evaluation datasets, connectors and documentation. Start with the user problem, make the change reviewable, and show how we will know it helped without creating avoidable risk.
A versioned, testable sales practice with evidence, steps, success signals, risks and human-review points.
A realistic exercise or evidence task that helps people build capability rather than passively consume content.
A scoped integration proposal for CRM, calendar, email, social or another authorized system.
Synthetic or lawfully sourced data used to test scoring, recommendations, safety or fairness.
A user problem, workflow improvement or platform capability proposal with a measurable outcome.
A reproducible defect, regression, accessibility issue or confusing behaviour.
A contributor should be able to state what the change does, who benefits, what inputs it needs and where it can fail.
Material behaviour needs a deterministic test, evaluation set, rubric, smoke test or other reproducible check appropriate to the feature.
Do not commit customer confidential data, credentials or unnecessary personal information. Document permissions, retention and human control.
Changed behaviour, schemas, evaluation rules and operational requirements must be reflected in the repository documentation.
Pull requests must pass TypeScript checking and the production Next.js build before merge.
You do not need to redesign the platform. Useful first contributions include improving one confusing sentence, adding an ambiguous practice scenario, documenting a failure case, expanding a lawful synthetic evaluation set, or proposing a measurable local sales/community workflow.
A contribution can be clever and still be unsafe or unhelpful. The platform favors changes that are understandable, testable, reversible, documented and respectful of user data. Maintainers should explain why material changes are accepted, changed or declined.