Packages as a scope matrix.
Packages are combinations of components. The matrix below separates the listed platform price from components that are scoped individually.
Listed platform pricing
Monthly prices belong to the five listed setups and are subject to confirmation. They cover the platform setup only.
Separately scoped components
CRM, Manager API access, payments, liquidity, hosting, branding, website, marketing and company formation. Each needs its own scope, dependencies and acceptance criteria.
Costing method
Create a table with components as rows and one-off, monthly and optional as columns. Fill it from written quotes and add your operating costs. Review it at each milestone.
Maintaining the matrix
Update the scope matrix at each milestone with actual costs, changes and open dependencies. Keep versions. A maintained matrix is both a budget tool and a change record.
Example matrix rows
Platform setup: monthly, listed. CRM: one-off and monthly, quoted. Manager API: one-off, quoted. Payments: provider fees, separate. Hosting: monthly, quoted. Each row has owner, dependency and acceptance test.
How the bundles fit together
| Bundle | What it combines | Listed pricing |
|---|---|---|
| Gray label start | A gray label setup with optional support or a migration route | $2,000–$2,400 / month (listed, subject to confirmation) |
| White label build | A white label setup, including the Prop Ready option | $2,200–$2,500 / month (listed, subject to confirmation) |
| Add-ons | CRM, Manager API access, branding, website, hosting, company formation | Scoped and quoted separately |
Questions we hear
Are the packages fixed?
They are guides. Scope and price are confirmed per setup.
Can components be added later?
Yes, as change requests with their own scope.