Salon Guild CRM
Sign inGet started

Guild Contribution and Governance Policy

Salon Guild CRM, part of the Opti Flo ecosystem

Last updated: 28 July 2026

This document is not legal advice and should be reviewed by a solicitor before publication.

Salon Guild CRM is built differently from a typical CRM. The word Guild reflects that it's shaped by input from the salons, spas, and beauty businesses actually using it, not designed in isolation and handed down. This policy explains how that works in practice, what involvement salon owners actually have, and what it does and doesn't entitle you to.

1. What the Guild is

The Guild is the community of businesses using Salon Guild CRM. As a Guild member, you have a direct channel to suggest changes to the product and a vote on what gets prioritised next. This policy governs that process. It supplements, and should be read alongside, our Terms of Service.

2. How contribution works

Any Operator using Salon Guild CRM can submit a contribution through the platform. A contribution might be a new contact field, a pipeline stage, a feature request, or a workflow idea specific to how salons, spas, or beauty businesses actually operate. Submitted contributions enter a review queue, visible to other Guild members.

3. How voting works

Every Operator on Salon Guild CRM can vote on any pending contribution in the queue, not just their own. Each Operator workspace carries one equal vote per contribution, regardless of subscription tier, size of business, or length of time as a customer. Votes determine the priority order of the queue (contributions with more support move higher), but voting does not itself guarantee a contribution will be built.

We may take reasonable steps to prevent abuse of the voting system, such as removing votes from fraudulent, duplicate, or automated accounts, and reserve the right to disregard votes cast in a way that circumvents the one-workspace-one-vote principle.

4. Final decisions rest with us

The Opti Flo Apps Ltd product and engineering team, referred to internally as the maintenance layer, reviews every contribution for quality, security, technical feasibility, and fit with the wider platform, and makes the final decision on what is actually designed, built, and shipped. Community voting informs and prioritises this process. It does not bind it. We may decline to build a highly-voted contribution where it conflicts with security, legal, technical, or product considerations, and we'll aim to explain why where practical.

There is no guaranteed timeline for review, and no guarantee that a submitted or voted-for contribution will ultimately be built. This is a genuine channel of influence over the product's direction, not a commitment to build everything requested.

5. Ownership and use of contributions

By submitting a contribution, you agree that:

If you don't want a particular idea used under these terms, don't submit it through the Guild contribution process.

6. Conduct expectations

When submitting contributions or voting, you agree to:

We may remove a contribution, or restrict an account's ability to submit or vote, where this policy or our Acceptable Use Policy is breached.

7. This is not a governance body or equity stake

Guild membership, contribution, and voting rights described in this policy are a product feedback and prioritisation mechanism. They do not constitute membership of a cooperative, a governance body with binding authority, a share or equity interest in Opti Flo Apps Ltd, or any right to participate in the company's management or decision-making beyond product prioritisation as described here.

8. Changes to this process

We may adjust how contribution and voting work as the Guild and the platform grow (for example introducing categories, weighting, or additional review stages). Material changes will be communicated to Operators through the platform or by email before they take effect.

9. Contact us

Opti Flo Apps Ltd
SIU Offices, 4-6 Greatorex Street, London, E1 5NF, United Kingdom
support@optiflo.app