Capabilities
Capabilities are listed only where at least one built product demonstrates them. Each one links to the evidence.

Multi-tenant systems for agencies, service companies, coaches and builders: queues, approvals, inboxes, reports.
Storefronts, portals and installable PWAs that price on the server and work on slow connections.
Durable queues, approval chains, retries and dead letters so that failed work is visible and recoverable.
Row-level security, restricted roles, hashed tokens, signed links and immutability triggers designed before the first screen.
Drafting, parametric 3D and inventory models tied to real data: massing tied to units, scanned layouts to block maps.
Unit, integration and journey suites with axe at three viewports in every built product.
Product story line

Every product above is the same five layers arranged for a different business. The layer names below are the ones used in the actual code and documents.
Storefronts, portals and apps where customers book, approve, pay or log. Server-priced, consent-aware, mobile first.
The desks the team actually sits at: Today queues, dispatch boards, pipelines, inboxes and approval flows.
State machines for bookings, approvals, cost sheets and publishing, with retries, dry runs and dead letters where work can fail.
Row-level security, restricted database roles, hashed tokens and sessions, immutable invoices and audit surfaces.
Adapters for messaging, payments, storage and models, sandboxed until keys and approvals exist, never assumed live.
Send an enquiry first. We set up a call, walk through how the work runs today and show you a sample template. Nothing is built or priced until you decide.


Describe the workflow, who runs it and what breaks today. Rough notes are fine.
We reply with questions and a written summary of what we understood, so nothing is assumed.
A working session on the system shape: roles, data, boundaries, phases. No quote or timeline is promised before this.