ELLI HUB
Demo data

Ellicorp · Elli NY Design Corp

Every Ellicorp system,one front door.

The Ellicorp-owned portal shell: the estimating command center, eight project-management workflows, ElliHub Finance, and the Fieldwire bridge — one address, one sign-in, one place where the numbers reconcile.

Live project
BID-1247 · FW #31247
Revised contract
$1,415,200
Contract complete
66.1%
Active pipeline
$4,050,500 · 7 bids

The registry

Twelve tabs, one frame.

The tab registry is the Hub's information architecture — Isabella's structure, kept exactly as published. Dashboard, estimating, eight project-management workflows, accounting: every tab is a working surface, not a link farm.

Navigation order and grouping as published — improved in execution, never in architecture.

How it connects

Field data in. Issued documents out.

Fieldwire job #31247 holds the field truth for Tisch School of the Arts — Wing B Renovation — the sheets, specs, tasks, and photos the crews actually work from. The bridge pulls that record into org-level Claude skills, and the skills draft the documents a millwork subcontractor actually issues: the proposal package in Word, the schedule of values in Excel. Every number in the Hub traces back to this flow.

FW #3124714 sheets6 specs22 tasks12 photosDemo data

Connection diagram — BID-1247 · FW #31247

Data flows from Fieldwire job 31247 (14 sheets, 6 specs, 22 tasks, 12 photos) through the Fieldwire bridge into the Tisch Proposal Workflow skill, which produces Tisch_WingB_Proposal_Rev2.docx and Tisch_WingB_SOV.xlsx.

Demo data — the bridge automations are a separately scoped proposal; the Hub visualizes exactly where they land. Outbound documents are always reviewed and sent by a person.

The systems

Three systems. One address.

The Hub doesn't replace what works — it wraps it. Estimating stays in production, finance stays with its vendor, the bridge stays scoped. Every one of them answers at the same front door.

Estimating Command Center

Production

Six modules that run the bid book — from the GC's invitation in the inbox to awarded-or-lost. In production today; the Hub embeds it as a tab.

  • M1 — Email Log
  • M2 — Projects to Bid
  • M3 — Estimate Form
  • M4 — Submitted Bids
  • M5 — Awarded / Lost
  • M6 — Client Info
React · NestJS · Postgres · Azure/estimating/app

ElliHub Finance

Connected system

Post-award accounting — requisitions, retainage, job cost. Built by a partner vendor on Supabase; the Hub gives it a first-class tab and a clean embed seam.

  • Requisitions
  • Retainage
  • Job cost
  • AR / AP
Supabase · partner vendor/accounting

Fieldwire Bridge

In design

The automation layer between field and office: pulls sheets, specs, tasks, and photos from Fieldwire into the skills — linked by project UUID, never by name.

  • Sheets
  • Specs
  • Tasks
  • Photos
Fieldwire API · scoped proposalSee the flow

Project management — 01–08

Eight workflows, drawn to working scale.

Isabella captures how Ellicorp actually runs a job and publishes each workflow as an org-level Claude skill. The Hub gives every one a tab — these eight surfaces are how a millwork package gets managed from notice-to-proceed to closeout.

The front door

Built for Ellicorp.
Owned by Ellicorp.

Not a vendor's portal with Ellicorp's logo on it — the shell itself belongs to the company. One domain, one sign-in, one registry that every system plugs into. hub.ellicorp.com, when the DNS catches up.