Contractor
For the people responsible for site execution and project delivery.
- Projects, phases and budgets
- Daily records, labour and materials
- Requests, approvals and procurement
- Project status and practical site evidence
Product family
One construction-management family, with an app for each actor.
The current public MVP/pilot is free. Pricing and final paid seat allowances have not been published. The Platform already has future-ready entitlement foundations, but this page describes only the product we can validate today.
Hardware Store
For stores supplying construction projects while retaining authority over their own quotations, orders and fulfilment records.
- Receive requests for quotation
- Record prices and prepare quotations
- Handle accepted orders
- Record fulfilment and delivery handoff
Customer
For the project customer: the customer-side authority who needs oversight and decisions, not a contractor-style execution screen.
- Understand what is happening and what remains unresolved
- Review money committed/spent and changes requiring approval
- Keep evidence and quality observations
- Understand responsibilities, appointments and authority
Archive
The safety and retention app for supported BWQ data that no longer needs to stay active in an operational app.
- Retain supported project/archive packages
- Verify and protect long-term records
- Support migration/update safety
- Remain separate from live synchronization
How seats and roles are intended to work
A seat is a person who has been given an entitled role in the relevant account or project context. The MVP keeps this bounded: enough roles to distribute real responsibility, without an enterprise permissions engine.
Contractor organizations distribute execution responsibility.
Staff roles should expose only the contractor actions they actually need.
The Customer is not merely another contractor seat.
The customer has broader customer-side oversight and decision concerns and may involve several other people.
Hardware Stores use the minimum useful store roles.
Store workflow can be distributed without creating a large permission matrix.
Who owns the data?
Each app remains authoritative for its own local records. Cross-app information keeps provenance and does not silently overwrite receiver-owned truth.
- Exchange carries bounded, explicit facts
- Transport receipt is not business acceptance
- Receiving workflows may stage/review/accept external claims
- Platform does not centralize operational construction databases
Current commercial state
The public MVP/pilot is free. No published price is implied by the subscription code already present in Platform. Exact seat allowances remain pilot configuration that still requires product validation.
Future paid capability
Future plans can add account, entitlement, support and seat value cleanly because the Platform already has stable product identifiers and signed entitlement foundations. Paid plans should add service value without taking ownership of operational data.
Use what exists now
The website should sell the workflows currently implemented and under validation—not future automation, realtime sync, AI, OCR, marketplaces or pricing that has not been decided.