How the Build With Quality family fits together.
Operational data stays with the apps and their users. Platform is the public/account/commercial control plane; Exchange carries bounded collaboration facts; Archive retains supported history.
Current public MVP
The current public MVP/pilot is free. Pricing and final paid seat allowances are not published. Existing Platform subscription and entitlement code is future-ready infrastructure, not a public price promise.
Seats are people with roles
A seat means an entitled person in a relevant account/project context. Keep the role set bounded. A seat does not become ownership of copied project truth.
Customer authority is distinct
The Customer is the highest customer-side authority over their own project relationships. Customer-side oversight, approvals, evidence and appointments are not merely contractor staff permissions.
Contractor and store responsibilities
Contractor organizations can distribute execution work between relevant staff. Hardware Stores can distribute quotation/order/fulfilment work between the minimum useful store roles.
Local truth stays local
A Contractor database, Customer record or Hardware Store ledger remains owned by that app/user. Platform should not become the operational data store.
Standalone still works
Each app should remain useful without another BWQ participant, without continuous internet and without realtime synchronization.
Controlled cross-app collaboration
The sender remains responsible for what it says.
Identity, revision and provenance travel with the fact; Exchange is not a shared database.
Receiving an external claim must not silently rewrite authoritative local records.
Business acceptance remains distinct from transport receipt.
The user can still tell who supplied the information and which message/revision it came from.
Offline-first boundary
SQLite/local storage remains the default for operational apps. Manual import/export and explicit Exchange packages are valid MVP workflows. There is no requirement for a realtime sync engine.
What Platform is for
Public product explanation, account/recovery, support and future subscription/entitlement capability. It should not store normal BOQs, daily logs, site photos, stock ledgers or customer house records.
What future paid plans should mean
Paid plans, when validated, can fund useful account, entitlement, seat and service capability. They should not make operational data ownership conditional on payment.
What is deliberately not here
No Stripe/payment-processor integration, no realtime sync, no AI/OCR, no marketplace logic, no enterprise IAM and no invented public pricing.