00 — The Model

Your business, as a model for your team and Claude.

Not the business model, the sales plan, or the financial model — all of them, encoded as one. Every worksheet that matters, combined into one model that updates from your sources. Someone signs off on every change.

Scroll

Files

A workbook, a deck, a PDF, your CRM export. Flat surfaces with no dimension between them. The work is already there — nothing connects a number to the document that produced it.

Data Product

Files, model, Claude — three layers that close into one addressable unit. It carries its own sources, its own definitions, and the ability to answer for itself.

Model

The whole business, addressable end to end. Ask a question at any point and the structure carries you back to the source that answers it.

The Harness

Governance in motion around the model. Every change checked, every claim sourced, every answer kept current as the material underneath it moves.

Actionable Deliverables

The orbits open and the model hands back the work products you already live on — dashboards, board reports, completed DDQs. Same artefacts, now produced by the model and kept current by it.

Questions

What people ask before the first hub.

The smallest unit Proxa works with: the source files, the model that describes them, and Claude working over both, closed into one addressable object. It carries its own definitions and can answer for itself.

Two grouping layers. A hub holds the data products of one domain — finance, legal, diligence, construction — as a single surface a team works against. A workspace stacks those hubs so the relationships between domains stay intact instead of being rebuilt in every report.

No. Workbooks, decks, PDFs and system exports stay where they are. Proxa reads them as sources and keeps the model in step with them.

Sources are watched. When one changes, the affected data products recompute and every deliverable that depends on them is flagged. Nothing publishes until someone signs off.

Inside each data product, not on top of an undifferentiated pile of documents. Claude works against the structure, so an answer resolves to the worksheet and the source behind it.

The artefacts you already produce — dashboards, board reports, completed DDQ responses — generated from the model and maintained by it rather than rebuilt by hand each cycle.

Weeks, not quarters. We start with one domain, build it alongside your team, and expand once it holds under real work.