Estimating · Connected system
Estimating Command Center
M1–M6 · demo-mode sandbox mirror · production on Azure
Ellicorp's bid-to-award pipeline runs in its own production application — every GC solicitation from first email to award decision. Framed below is the live demo-mode sandbox mirror of that app, running on mock data; the authenticated production system stays exactly where it is, on Azure.
Demo-mode sandbox · opens in a new tab
Loading demo-mode mirror
The sandbox SPA is booting in mock-mode. A SANDBOX banner appears inside the app once it loads.
The mirror is a dense desktop app. For full use on a phone, open it in its own tab.
Demo-mode sandbox · opens in a new tab
System map
Six modules, one pipeline
The production app walks a pursuit from the first GC email to the award decision. Counts below are demo data shaped like the live API.
- M1
Email Log
Every GC email — bid solicitations, addenda, award notices — captured off the estimating inbox and threaded to its BID number.
Last intakeJun 08, 2026 · BID-1250 - M2
Projects to Bid
The live board of work GCs have invited Ellicorp to price — tracked from documents received through bid day.
Active bids7 pursuits - M3
Estimate Form
Takeoff to sell price under one EST number — plastic-laminate casework, veneer paneling, solid surface, and Blum hardware, line by line.
In active pursuit$4,050,500 - M4
Submitted Bids
Quotes out the door with bid-day values, and where each one stands in GC leveling.
Awaiting GC decision3 of 7 - M5
Awarded / Lost
Decisions land here. Awarded work hands off to project management; losses keep their pricing history for the next pursuit.
Latest awardBID-1247 · $1,385,000 - M6
Client Info
The canonical GC roster — contacts, divisions, and bid history for every general contractor Ellicorp prices for.
GC partners8 on file
Integration status
What flows where
Three planned feeds between the Hub and the Estimating Command Center keep every surface current without anyone retyping a number.
- M2 · M4 → /dashboardView pipeline
Active bids feed the pipeline
Open pursuits and submitted bids surface in the Dashboard's In-pursuit table — same BID numbers, same dollars, no retyping.
- M5 → /pm/*Open SOV
Awards hand off to project management
An award in M5 becomes the live project. SOV, submittals, RFIs, and pay applications spin up under BID-1247 · FW #31247.
- M6 → hub-wide
Client info stays canonical
The GC roster in M6 is the single source for contractor names across quotes, transmittals, and pay applications.
How this connects
Data flows from the Estimating Command Center (Active bids, Awards, Client info) through the Estimating API into the Hub sync skill, which keeps the Dashboard + PM tabs current.
Demo data — the Hub ↔ Estimating sync ships in the integration phase. Until then, both sides of the Hub read the same demo dataset, so every figure already reconciles.