← Home
Allometry OS · Master PRD

Product Requirements Document

The underwriting and control layer for physical revenue. Layer 1 — 16 Action Modules. Layer 2 — The Platform. Single source of truth.

Version 2.0 Architecture Two-Layer Updated April 2026 Author Taylor Gendron Status Pre-seed · Design Partner Build

Table of Contents

01 Product Overview

What is Allometry?

Allometry is the underwriting and control layer for physical revenue. We help asset-heavy operators (HVAC, EV, telecom, security, pallet manufacturing, smart lockers, solar) decide which work to pursue, how to price it, and how to execute it — with margin visibility at the address level, before the job starts. ABM × CPQ, applied to asset-heavy operators. Every account gets a Pulse.

Core Primitive — the Address

The address (location / site / deployment unit) is the atomic object. Every quote, job, deal, contract, and health signal relates to it. Unlike CRMs (contact-first) or ERPs (order-first), Allometry is address-first. A 50-location HVAC operator has 50 different unit economics, and the Pulse tracks every one.

The Pulse

One scoring primitive per account, per address. Composite score: margin · EV · risk · expansion. Continuously updated with every closed job, every contract change, every supplier shift. The moat: every module trains it. At 10K jobs we set the industry margin benchmark. At 50K we are the underwriting layer for every deployment in North America.

Two-Layer Architecture

The product is structured in two layers. Modules complete work. The Platform is how you see, call, connect, brand, host, and extend that work.

LayerRoleWhat It ContainsPricing
Layer 1Action Modules — complete work16 modules across 4 loops (Price · Deploy · Expand · Govern)Per-module / per-loop / full OS
Layer 2Platform — how you access workAnalytics · API · Integrations · Whitelabel · Infrastructure · ExtensionsIncluded with every tier

Key consequence: Analytics, API, and Integrations are not modules. They are platform capabilities, included by default. You pay for work completion; dashboards, APIs, and integrations come with the product.

The 4 Loops

LoopRisk DimensionQuestionModules
PriceFinancial"Can you price it right?"01 Quoting · 02 Margin · 03 Cost · 04 Contract
DeployOperational"Can you deliver & keep it running?"05 Location · 06 Job Costing · 07 Design · 08 Asset Intel
ExpandGrowth"Which accounts are worth winning?"09 Deal Room · 10 Outbound ABM · 11 Health · 12 Forecasting
GovernMarket & Governance"Is the system trustworthy?"13 Market Intel · 14 Compliance · 15 Risk Scoring · 16 Vendor Intel

The Flywheel

Price → Deploy → Expand → Govern → Price. Each loop feeds the next. Quoting data trains cost models. Job costing reveals expansion-worthy accounts. Expansion signals refine targeting. Governance surfaces outliers. Every closed job sharpens the Pulse.

Target User (ICP)

Asset-heavy operators with 5-2,500 locations, $5M-$500M revenue, multi-address customers, variable margin per location, long sales cycles. Initial wedge: Quebec HVAC, solar, pallet manufacturing, smart locker networks. Expansion: SF, NYC; $10M-$50M operators as primary ICP.

02 Design Principles

  1. Address-first, not contact-first. Every view, every decision, every metric anchored to the deployment unit. The address is the row in every table.
  2. Modules complete work. Platform is how you access it. 16 units of work completion. 6 horizontal capabilities. Never confuse the two.
  3. Every decision gets underwritten. Not reported. Not logged. Underwritten — scored against margin and EV before commit.
  4. Before the job starts. Margin visibility must land before execution commits resources. Month-end is too late.
  5. Agents handle 90%, humans validate 10%. Autonomous by default. Humans validate exceptions — relationships, strategy, outliers.
  6. Loops, not features. Users think in workflows, not module lists. Navigation organizes around risk dimensions.
  7. Data creates optionality. Every quote creates data that feeds every other module. Users start with 1 loop and expand naturally because the data is already there.
  8. No drift. What you quote is what you deploy. Single source of truth from proposal to invoice. Address-level accuracy, always.
  9. Embedded, not adjacent. Allometry sits on top of existing tools (CRM, ERP, FSM). We govern decisions the others can't make.

03 System Architecture

Tech Stack

FrameworkNext.js 16 · React 19 · App Router
LanguageTypeScript
DatabasePostgreSQL · Drizzle ORM · pgvector
Auth & SSOWorkOS (SAML, OIDC, Directory Sync)
HostingVercel · edge-first · multi-region
StylingTailwind CSS 4 · shadcn/ui
AIAnthropic Claude (via SDK) · multi-stage RAG · tool use
MapsLeaflet · react-leaflet
ChartsRecharts · D3 · Tremor
EmailResend · Nodemailer
PaymentsStripe
MonitoringSentry · OpenTelemetry
ComplianceSOC 2 Type II · Quebec Law 25 · GDPR · data residency (CA/US/EU)

Multi-Workspace Isolation

Each customer gets an isolated workspace. Workspace-scoped database queries. Row-level security enforced at the data layer. Users can belong to multiple workspaces with distinct roles. Tenant_id is injected from session context on every read/write.

Core Data Model — Address as Root

04 6 Data Primitives

The 16 action modules are surfaces on 6 shared engineering systems. Adding a module = adding a lens, not a codebase.

System 1 · Pricing Engine

Margin models, cost structures, volume tiers, contract terms. Powers Modules 01-04 (Quoting · Margin · Cost · Contract).

Tables: pricing_rules · cost_items · contracts · quote_line_items · margin_models

System 2 · Territory / Geo

Geocoded addresses, route optimization, coverage analysis, deployment scheduling, asset lifecycle tracking. Powers Modules 05, 06, 08 (Location · Job Costing · Asset Intelligence).

Tables: locations · territories · deployments · jobs · assets · asset_telemetry

System 3 · Intelligence Layer

Multi-stage RAG, scoring models, predictive analytics, account intelligence. Powers Modules 10, 11, 12, 13, 15, 16 (Outbound ABM · Customer Health · Demand Forecasting · Market Intel · Risk Scoring · Vendor Intel).

Tables: signals · health_scores · demand_forecasts · enrichments · risk_flags · vendor_scores

System 4 · Content / Render

Proposals, branded portals, floorplans, AI renders. Powers Modules 07, 09 (Deployment Design · Deal Room).

Tables: deal_rooms · proposals · designs · assets_uploaded · renders

System 5 · Governance Plane

Policy engine, approval flows, regulatory frameworks, audit trails. Powers Module 14 (Compliance) — all governance, approval, audit, and regulatory concerns fold into one module surface.

Tables: policies · approvals · audit_log · compliance_events · regulatory_frameworks

System 6 · Pulse Core Primitive

The scoring primitive beneath every module. Composite scores (margin · EV · risk · expansion) per account, per address, per commercial decision. Trained on every closed job. Retrained on realized outcomes.

Tables: account_pulse · address_scores · decision_log · training_signals · model_versions

Platform capabilities (Analytics, API, Integrations, Whitelabel, Infrastructure, Extensions) are not data primitives. They are Layer 2 — horizontal capabilities on top of the 6 systems. See Section 9.

05 Layer 1 · Loop 1 — Price Financial Risk

"Can you price it right before you commit?" — Every deployment starts with a pricing decision. This loop ensures no quote leaves the system without being underwritten.

01
Quoting Engine
P1 · Wedge

Purpose: Configure, price, quote in 60 seconds. Every quote scored against margin and EV before it leaves the system. The door-opener — the demo moment — the entry wedge.

Core Features

Agent Behavior

Inputs
SKU catalog · pricing rules · cost data · contract terms · inventory · ICP score · account Pulse
Outputs
Quote object · line items · margin calc · Pulse scorecard · proposal PDF · deal room · approval request
Key Metrics
Time to quote (<60s) · quotes/user/day · avg margin · quote-to-close rate
Powers
System 1 · Pricing Engine · writes to Pulse Core
02
Margin Protect
P1

Purpose: Defend margins on every deal. Real-time guardrails at quote-time, not month-end.

Core Features

Inputs
Line items · cost data · target margins · rep/region overrides · historical realized margins
Outputs
Margin flags · approval triggers · leakage reports · adjusted floors
03
Cost Engine
P2

Purpose: Unified cost truth. SKU-level + labor + logistics + supplier intelligence. The real number behind every line item.

Core Features

Inputs
Supplier feeds · material prices · labor rates · logistics costs · vendor scores
Outputs
Cost floor per SKU · forward cost projections · reorder signals · supplier recommendations
04
Contract Intelligence
P2

Purpose: Contracts that quote themselves. Active MSAs drive quoting logic automatically — no manual term lookups.

Core Features

Inputs
Uploaded MSAs · usage data · contract templates · benchmarks
Outputs
Structured contract terms · renewal alerts · negotiation recommendations

06 Layer 1 · Loop 2 — Deploy Operational Risk

"Can you deliver it — and keep it running?" — What happens after the quote is signed. No drift between what you promised and what you execute.

05
Location Intelligence
P1

Purpose: Territory as a first-class object. Geocoded addresses, scored, mapped, optimized.

Core Features

06
Job Costing
P2

Purpose: The truth loop. Actual vs. estimated on every job, every location. Tells you whether your quotes were right.

Core Features

07
Deployment Design
P3

Purpose: Design it, visualize it, sell it. AI-generated floorplans, equipment layouts, deployment previews.

Core Features

08
Asset Intelligence
P2

Purpose: Deployment lifecycle — from install through uptime through decommission. What you deployed, how it's performing, when to act.

Core Features

Parallel module: Asset Intelligence (08) tracks deployed assets. Vendor Intelligence (16) tracks suppliers. Two lenses on the physical world — internal vs upstream.

07 Layer 1 · Loop 3 — Expand Growth Risk

"Which accounts are worth winning — and keeping?" — How you win more and grow what you have. Turns deployment data into pipeline weighted by margin potential.

09
Deal Room
P1

Purpose: Where the quote becomes a sale. Branded portal, engagement tracking, e-signatures — all tied to the Pulse.

Core Features

10
Outbound ABM
P2

Purpose: The agent tells you who to call. Account-based prospecting scored by margin potential, not just firmographic fit.

Core Features

11
Customer Health
P2

Purpose: Know before they churn. Predict before they expand. Composite account health from quoting frequency, margin trends, engagement, support load, renewal timing.

Core Features

12
Demand Forecasting
P3

Purpose: Predict before they ask. Turn historical deployment patterns into forward-looking demand signals per region, product, season.

Core Features

08 Layer 1 · Loop 4 — Govern Market & Governance Risk

"Is the system trustworthy and accountable?" — The layer that monitors external signals, governs internal decisions, scores portfolio risk, and tracks supply-chain health. Four corners: External · Policy · Portfolio · Supply.

13
Market Intelligence
P2

Purpose: Outside-world signals. Competitive pricing, win/loss patterns, market shifts, answer engine visibility. The eyes and ears of the OS.

Core Features

14
Compliance
P1

Purpose: The policy plane. Every decision the Pulse makes is gated, logged, and compliant by construction. Replaces separate "Governance" + "Audit" + "Regulatory" concerns.

Core Features

Absorbs: Governance rules · audit trail · regulatory posture · approval flows · contract lifecycle governance. One action module instead of three overlapping surfaces.

15
Risk Scoring
P2

Purpose: Portfolio-level risk detection. Flag outlier accounts, concentration risk, and anomalies before they hit the P&L.

Core Features

16
Vendor Intelligence
P2

Purpose: Upstream risk. Score supplier reliability, monitor SLAs, detect concentration and vendor failure risk before it affects deployments.

Core Features

Parallel module: Asset Intelligence (08) tracks deployed assets. Vendor Intelligence (16) tracks suppliers. Two lenses on the same physical world — internal vs upstream.

09 Layer 2 — The Platform Horizontal · Included

The 16 action modules are Layer 1 — what you buy. The Platform is Layer 2 — how you see, call, connect, brand, host, and extend those modules. Included with every tier, horizontal across all 16 modules.

P1
Analytics See the work
P2
API Call the work
P3
Integrations Connect the work
CategoryIntegrationsSync
CRMSalesforce · HubSpotBi-directional
ERPNetSuite · SAPBi-directional
FSMServiceTitan · JobberRead
AccountingQuickBooks · XeroPush
CalendarGoogle · OutlookBi-directional
CommunicationSlack · Teams · EmailNotifications
EnrichmentApollo · Clearbit · SnitcherPull
PaymentsStripeBi-directional
P4
Whitelabel Brand the work · Enterprise
P5
Infrastructure Host the work
P6
Extensions Extend the work

10 User Roles & Permissions

RoleAccessTypical User
AdminFull: settings, users, billing, all modules, all dataCEO, Founder
ManagerAll modules · approval authority · team management · reportsVP Sales, VP Ops
RepQuoting · deal rooms · territory view · own pipelineSales Rep, Account Exec
OpsJob costing · asset intel · location mgmt · crew assignmentOperations Manager, Dispatcher
FinanceMargin analytics · cost engine · contract mgmt · compliance reportingCFO, Controller
ComplianceCompliance module · audit log · regulatory postureDPO, Risk Officer
ViewerRead-only dashboards & reportsBoard Member, Investor
PartnerPartner portal · own deals · commissions · co-branded deal roomsChannel Partner
APIProgrammatic access via scoped API keyDeveloper, Integration

11 UX Principles

  1. Loop-first navigation. Main nav organizes by Price · Deploy · Expand · Govern — not by module name. Users think in workflows.
  2. Location is always in context. Every screen shows which address(es) are active. The location picker is always one click away.
  3. Pulse is persistent. A scorecard — Margin / EV / Risk / Expansion — is visible on every quote, deal, and account view.
  4. Agent activity feed. A persistent sidebar shows what agents are doing: quotes generated, alerts fired, approvals pending. Makes the "work getting done" visible.
  5. Progressive disclosure. Start with 1 loop (typically Price). Reveal complexity as the user expands. Don't show 16 modules on day one.
  6. Platform is invisible. Analytics, API, Integrations live in "Settings" — not in the primary nav. The user's focus stays on action.
  7. Mobile-ready for field. Rep view works on mobile: quick quote, location lookup, deal room access, asset status.
  8. Dark mode default. Matches brand. Light mode available with one click.

12 Build Roadmap

Phase 1 — Wedge (Current → Month 3)

Goal: First design partners live. Prove the quoting wedge.

Module#PriorityStatus
Quoting Engine01P1Live (DPs)
Margin Protect02P1Live (DPs)
Location Intelligence05P1Live (DPs)
Deal Room09P1Live (DPs)
Compliance14P1Scaffolded
Platform · P1 AnalyticsP1Scaffolded
Platform · P5 Infrastructure (SOC 2 base)P1In progress

Phase 2 — First Loop (Month 3-6)

Goal: Complete Price loop. Design partners expanding into Deploy & Expand.

Module#PriorityStatus
Cost Engine03P2Planned
Contract Intelligence04P2Planned
Job Costing06P2Planned
Asset Intelligence08P2Planned
Outbound ABM10P2Planned
Customer Health11P2Planned
Market Intelligence13P2Planned
Risk Scoring15P2Planned
Vendor Intelligence16P2Planned
Platform · P2 APIP2Planned
Platform · P3 IntegrationsP2Planned

Phase 3 — Full OS (Month 6-12)

Goal: All 4 loops live. Full platform. $1M ARR. Seed raise.

Module#PriorityStatus
Deployment Design07P3Planned
Demand Forecasting12P3Planned
Platform · P4 WhitelabelP3Planned
Platform · P6 Extensions (SDKs, Sandbox)P3Planned
Marketplace (Extensions P6)P3Future

13 Success Metrics

Product Metrics

MetricMonth 3Month 12
Time to first quote< 60s< 30s
Quotes per user per day10+50+
% quotes above margin floor90%98%
Quote-to-close ratebaseline+20%
DAU / MAU40%60%
Modules per customer2-38+
Loops per customer13-4
Pulse score accuracy (margin prediction)±15%±5%

Business Metrics

MetricMonth 6Month 12
Design partners (paying)1020+
MRR$10K$83K
ARR$120K$1M
ACV$15K$50K+
Net revenue retention150%+
Gross margin80%85%

14 Technical Risks

RiskImpactMitigation
Pulse accuracy (margin prediction)High — wrong scores = lost trustHuman-in-the-loop on all quotes in Phase 1. Confidence intervals. Progressive automation as accuracy improves. Realized-margin feedback retrains the scorer.
Data quality from integrationsHigh — garbage in, garbage outValidation layer on all imports. Reconciliation checks. Manual override capability. Structured schema at connector layer.
Multi-tenant isolationCritical — data leak = company-endingWorkspace-scoped queries. Row-level security. Regular penetration testing. SOC 2 audit on schedule.
Scale of address dataMedium — maps can be slow with 10K+ pinsClustering, viewport-based loading, WebGL rendering for large datasets.
Agent hallucination in proposalsHigh — fabricated data in customer-facing outputGrounded generation only. All agent outputs cite source data. Validation layer before user-facing output.
Solo founder bus factorHigh — if Taylor is unavailable, product stallsCodebase well-structured. First engineering hire triggered by paying-customer milestones post-raise.
Regulatory complexity (multi-jurisdiction)Medium — Law 25 (QC), GDPR (EU), SOC 2 (US), HIPAA optionalCompliance module (14) is built as a first-class product surface, not bolted on. Frameworks are configurable per workspace.

// Allometry OS · Master PRD v2.0 · Two-Layer Architecture
April 2026 · Taylor Gendron · taylor@allometry.com · allometry.com