PEMB OS · SHOWCASE5-min walkthrough

Move the job,
not the paperwork.

ForgeFrame PEMB is the PEMB-specific operating system for builders, erectors, dealers, and suppliers across North America. Capture scope in the 3D concept designer, qualify it with completeness scoring, and ship it to your manufacturer software without retyping.

Rigid frameClear spanMulti-spanR-panelIMPStanding seamAnchor-bolt planReactionsStamped drawings

What ships

Six guardrails, one operating system.

01 — CONCEPT

Capture scope, not surveys

The 3D concept designer collects dimensions, roof form, cladding, colors, openings, site, and timeline. Concept only — never labeled engineered, permit-ready, or fabricated.

02 — STRUCTURE

PEMB vocabulary, end to end

Rigid frame, clear span, multi-span, R-panel, IMP, standing seam, anchor-bolt plan, reactions, stamped drawings — labels and units your estimators already speak.

03 — LEAD

Qualified lead, not a form fill

Leads land with completeness and urgency scoring. Sales knows which prospects can be estimated without a callback, and which need a site visit first.

04 — EXECUTION

Project workspace, not a CRM dump

Manufacturer, engineering, permits, foundation, delivery, erection, inspections, deficiencies, change orders, files, and closeout — each project, each stage, no renumbering.

05 — HANDOFF

Neutral export, vendor adapters

Canonical scope is versioned JSON/CSV. Manufacturer-specific mappings live in adapters — your UI never couples to a vendor API or rev.

06 — GUARDRAILS

Budgetary ranges, never binding

Price ranges are labeled budgetary until reviewed by your estimating team. No takeoff, no cut list, no engineered claims — let your manufacturer software own that.

The loop, in five stages

Lead → project → handoff.

Every step has structured state, every transition has proof, every handoff keeps a paper trail.

  1. 1

    Marketing → 3D concept designer

    The home CTA funnels traffic into the configurator instead of a generic contact form.

    Proof

    Routes: /, /design, /contact

  2. 2

    Designer → structured lead

    Dimensions, roof form, cladding, colors, openings, site, loads, timeline all become structured fields with completeness scoring.

    Proof

    Validated types in lib/lead-completeness.ts, lib/integrations/canonical-scope.ts

  3. 3

    Lead → budgetary proposal

    Sales advances opportunity stages and builds a budgetary proposal. Pricing ranges, not binding quotes.

    Proof

    Stages: New → Qualified → Proposed → Accepted

  4. 4

    Accepted → project workspace

    Manufacturer, engineering, permits, foundation, delivery, erection, inspections, deficiencies, change orders, files, closeout — every stage tracked.

    Proof

    lib/workflow/pemb.ts, lib/workflow/commercial.ts

  5. 5

    Project → manufacturer handoff

    A neutral, versioned canonical scope exports to the builder’s proprietary manufacturer software — without retyping.

    Proof

    lib/integrations/adapters.ts (manufacturer adapters)

What this is

  • Lead-to-project operating system for PEMB builders.
  • Concept design + structured lead capture + project workspace + manufacturer export.
  • Branded custom Supabase auth (no Clerk).
  • Versioned canonical scope, isolated manufacturer adapters.
  • Public-by-default marketing pages; demo seed data when Supabase is absent.

What this is not

  • No takeoff, cut list, BOM, or fabrication calculations.
  • No engineered, permit-ready, or fabrication-ready claims.
  • No binding price quotes until reviewed by your estimating team.
  • No Clerk auth — custom branded Supabase auth only.
  • No generic SaaS dashboards unrelated to the PEMB lead-to-project loop.

ForgeFrame · PEMB OS · 2026

Open the concept designer and see scope turn into a qualified lead.

Looking for the 5-minute scripted walkthrough? /demo.