Exclusivity is agreed in your proposal and agreement, before development begins — and it's worth settling explicitly rather than assuming.
What to clarify in the agreement
- Ownership — who owns the delivered code.
- Exclusivity — whether the same solution can be built for others, and for how long.
- Redistribution rights — whether you can resell the technology. On DSP Acquisition these are available as an add-on; see What's included, and what's an add-on.
- Competitive scope — whether exclusivity is absolute or limited to your market or vertical.
Why it matters
If your platform's advantage rests on a bespoke capability, exclusivity is the thing protecting it. If the feature is operational rather than differentiating, exclusivity may cost more than it's worth — and non-exclusive work is usually cheaper.
Full ownership
DSP Acquisition transfers full source code ownership, giving you control over the platform itself as well as anything built on it — see DSP License vs DSP Acquisition.
Get it in writing. Verbal assurances about exclusivity are the most common source of later disputes in bespoke software. If it matters, it belongs in the agreement.
Related: Can I request features that aren't in the standard products?