PropSuite Review: Economics, Dependency & Due-Diligence Passport
PropSuite combines white-label technology with capital, payout coverage and operating responsibilities. That makes it structurally different from normal SaaS and increases the importance of separating price, dependency and control.
Buyer snapshot: public model shows $2,749 setup, $0 monthly platform fee and 50% of defined net profit to the founder, while PropSuite states it carries trader payouts.
Published commercial structure
| Setup | $2,749 one time |
|---|---|
| Monthly platform fee | $0 |
| Founder share | 50% of defined net profit |
| Account fee | $5 per sale in provider's published model |
| Transaction fee | 5% of sales in provider's published model |
| Trader payouts | Provider states PropSuite covers them, subject to agreement |
Buyer Dependency Layer
| Dependency layer | Current evidence state | What the buyer still needs to establish |
|---|---|---|
| Exit & portability | unknown | Full exit-export rights, schema, timing, retention and deletion obligations are not publicly established in the reviewed evidence. |
| Control & authority | partial | Provider-stated operating model concentrates risk/compliance and payout responsibility; exact buyer override and approval rights require contract review. |
| Integration dependency | unknown | Integrations are described, but buyer-controlled API/webhook portability, credential ownership and termination access are not publicly established. |
| Operational continuity | partial | Public terms describe an uptime objective without uninterrupted-access guarantee; migration rollback, remedies and post-termination support are not publicly established. |
See the Buyer Dependency Model methodology →
PFV Due-Diligence Passport
| Area | PFV evidence state | Buyer implication |
|---|---|---|
| Brand / customer relationship | Provider-stated / terms-backed branding | Public material says the operator owns the brand and trader relationship; full data portability still needs explicit contract language. |
| Data export | Unknown / not publicly specified | No complete public exit-export specification was located. Ask for objects, format, timing and post-termination access. |
| Technology ownership | Primary-source evidenced: vendor-owned | Terms say PropSuite retains the underlying technology/platform architecture while branding/customization belongs to the client. |
| SLA / uptime | Provider-stated, not guaranteed | Terms say PropSuite strives for 99.9% uptime but does not guarantee uninterrupted access. Buyers should not treat a marketing uptime figure as a contractual SLA. |
| Payout responsibility | Provider-stated core model | Public material says PropSuite supplies capital and carries trader payouts. Contract definitions, limits and exclusions are critical. |
| Dependency concentration | High | Technology, capital, payouts, risk/compliance and integrations are intentionally concentrated. This can reduce operator burden while increasing switching complexity. |
| Risk authority | High dependency / contract needed | Provider publicly positions risk/compliance inside its operating model. Exact breach, override and payout approval rights should be written. |
| API / portability | Unknown | Do not assume integration availability equals buyer-controlled data portability. |
Why this model needs a different comparison
A normal SaaS vendor is mainly a technology dependency. PropSuite's public model combines technology with capital and payout risk. Compare retained economics, control, continuity and exit complexity—not just the software invoice.
Contract questions before signing
- Define “net profit” and every deduction before the 50% split.
- Define payout coverage, exclusions, reserves, dispute handling and capital availability.
- Confirm who controls merchant/payment accounts and trader funds.
- Specify trader/customer data ownership and machine-readable export rights.
- Specify termination obligations, post-termination trader liabilities and migration support.
- Define breach/risk override authority and auditability.
- Clarify service availability, support response and remedies in the signed agreement.