A control on the Contract tab with two modes. SELL bumps the recurring exclusivity quantity (prorated, optionally charged immediately or on the next cycle) and raises the billed count. COMP registers the competitor contractually with no billing change at all. Either way the live competitor list is extended and an addendum carrying the same legal terms is appended.
Also called: territory protection · don't sell to my competitor · exclusivity · lock out my rival · protected competitor
- 1Add one or more competitor names, each with an optional email and contact.
- 2Choose SELL or COMP; SELL also chooses charge now or ride the next invoice.
- 3The signed contract document is never rewritten — every addition is an append-only addendum entry.
- 4Complimentary grants are marked so they extend the obligation without inflating the billed quantity.
- 5A 20-competitor cap is enforced before anything is charged.
- 6A test/live processor key mismatch is returned as a readable message naming which key is wrong, not a 502.
The route carries the invariant in capitals: 'FREEZE INVARIANT: the signed contract_document is NEVER rewritten. Every addition is an append-only entry in landing_signups.exclusivity_addenda (carrying the same legal terms via buildExclusivityAddendum).' The two modes exist because an obligation and an invoice are different things — COMP 'registers the competitor contractually (so we're obligated not to onboard them) with NO Stripe mutation and NO bump to the billed count.'
- Exclusivity agreed after signing had no home in the contract.
- Editing the contract to add a competitor would have altered a signed document.
- A complimentary grant and a billed one used to be indistinguishable.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →