Transparency
We publish what we charge (when amounts are set), what the product does today, what we’re building next, and what we refuse to build. We say when something is limited. Your rental revenue never sits in our account. Your data exports with you.
If a handbook page disagrees with the app, the handbook is wrong — tell us and we’ll fix it.
What we publish
- Full commercial model and fee amounts (see Pricing — amounts currently TBD)
- Roadmap and what we’re not building
- Feature limits (“Limits, honestly” on every feature page)
- Changelog of user-visible changes
- Who we are and that we build with outfitters, not only for them
- Data export / no-hostage policy
- Stripe Connect: deposits and rental payments go to your account
- Who this is for — and who it isn’t
- How support works (hello@outfitterhq.ca; we read every request)
What we don’t publish
Transparency isn’t dumping the server room on the lawn. We keep private:
- Platform admin internals and how we run the company day to day
- Partner commercial terms
- Unit economics and internal cost ledgers
- Security details that would help an attacker
- Database / infrastructure procedures and environment specifics
- Customer PII, contracts, and payment artifacts
- Other outfitters’ rates or configs without their permission
- Exact custom/pilot discount numbers (we’ll say custom rates exist; your invoice shows yours)
Charter (short)
Publish the product truth. Protect operators’ private data and anything that makes the platform less safe. Prefer a blunt “we’re not building that” over a vague “thanks for the feedback.”