US Carpentry · Internal planning

Tom's First Import, Research & Checklist

This page is the plan for bringing Tom English's industrial project research (122 projects, as of Sep 25, 2026) into the US Carpentry CRM. It covers the research team that finds addresses, contacts and current status, and the CRM leads and pipeline redesign questions.

Status: planning only. Nothing has been written to the CRM, and no one has been contacted.

122 projects31 states29 contractor routesNothing written to CRMNo outreach

1Overview: what Tom's data is

Source: Tom's workbook US_Carpentry_Industrial_Project_Pipeline_2026-2031.xlsx (tabs: Start Here, Projects, Contractor Outreach) and the 54-page companion PDF. The research is dated Sep 25, 2026 and covers construction opportunities through Sep 2031. By the file's own rule, investment figures are not totaled, and "no open labor order is implied."

122
Project / campus records
P01–P122, 22 columns each
36
Pursue now
Known contractor route + active or upcoming work
71
Qualify next
Confirm GC, package buyer or start date first
15
Monitor
Too uncertain for a mobilization forecast

Top states (31 states total)

Sectors (17 labels in the sheet)

Market groups (Start Here tab)

  • Data centers, including power campuses: 51
  • Standalone power supply: 33
  • Aerospace and marine manufacturing: 15
  • Other industrial prospects retained: 23

Five "first calls" are listed: TIC/Kiewit, BE&K/HITT, Whiting-Turner, Fortis/Mortenson, Brasfield & Gorrie. These are for reference only. Outreach is on hold.

29 contractor routes (Contractor Outreach tab)

These reference 60 of the 122 project IDs. Every row's outreach status is "Not contacted."

GCs (14)
TurnerMortensonDPRJE DunnHensel PhelpsClayco / CJ AdventuresWalbridgeHoffmanMcCarthyFortisHITT / BE&K-HITT JVWhiting-TurnerBrasfield & GorrieSamsung E&C America
EPCs (5)
BechtelTIC / Kiewit / TSL Power PartnersFluorWorleyPerformance Contractors
Specialty (2)
H.J. Martin & SonRyan Central
Owner / referral routes (8)
VantageSpaceXQTS / LanciumCompassEnergy Northwest / CascadeMicrosoftBrookfield / NextEra (Paducah)Boeing / Jacobs (St. Louis)

Gaps in the data

  • No contact people. There are no named people anywhere, and the whole workbook has just one project inbox and one estimating line. Everything else is a portal or web route.
  • No street addresses or ZIPs. Location is city or county only, but the CRM requires street, city, state and ZIP on every lead.
  • 74 of 122 projects say the GC is "not verified."
  • 61 of 122 projects have no investment number.
  • 62 of 122 projects aren't tied to any of the 29 outreach companies (52 Qualify next, 10 Monitor). All 36 Pursue-now projects have a route.
  • Assigned to, Next follow-up and Conversation notes on the Contractor Outreach tab are all empty (0 of 29).
  • The CRM side has no lead value field, no tags, no lead-to-company link and no hard delete.

2Decisions: decided vs. open

These are from the open-questions list in the import plan, updated with John's decisions as of Nov 20, 2026, 9 AM CT.

Decided

Decided
Addresses: dash it, then research.

At import, fill in whatever address data exists (city from Location, plus state). Any required field that's missing (street, ZIP) gets a dash "-". The research team then finds the exact address for every project and updates the lead.

Decided
Research team after the import.

Cloud agents research every project for the exact site address, contact people (decision makers, GC and package buyers) and more metadata. The results get assembled in the CRM.

Decided
The CRM itself is part of the research.

This covers a possible small redesign of the leads and pipeline UI, including how companies link to leads. It gets reviewed after the research comes back.

Rule
Nothing gets written to the CRM until John approves.

No one gets contacted. Tom's 36 Pursue-now targets stay on hold for outreach until John says so. The import is research and setup, not outreach.

Proposed / open

Under John's review
Q1 Layout: one lead per project (122), named by ID + project

Example: "P01 Meta Hyperion - phases 1 and 2." The 29 contractors become companies. John is still weighing whether every other row detail (owner, sector, investment, construction team, sources…) should go into custom fields, and he may set it up differently.

Open
Q3 Areas:

One area ("Industrial Pipeline 2026-31"), regional corridors from the PDF (TX/Gulf, Mid-South, Southeast, Midwest, Mountain/Pacific, Mid-Atlantic), or one per state (31)?

Open
Q4 Company types:

Use the payable "Vendor" type plus a Relationship field, or ask NokNok for GC and Owner types?

Open
Q5 Scope:

Import all 122 including the 15 Monitor rows, or only Pursue now and Qualify next? Importing isn't working the targets, but that needs confirming.

Open
Q6 Simulation:

A box dry run first (A), then a [SIM] pilot (B)? Is John OK with pilot records only being archivable, never deleted?

Open
Q7 Tom's empty columns:

Should Assigned to, Next follow-up and Conversation notes become CRM fields or tasks?

Open
Q8 PDF attachment:

Attach the PDF to records? That would mean John using the CRM file picker, or Drive.

Open
Q9 File check:

Confirm by checksum that John's attachments are the same files as Tom's Nov 16 forwards.

Answered
Q2 Address:

Dash placeholders now, real addresses from research. See Decided.

3Import checklist

Check items off as they're done. Progress is saved in this browser only (localStorage). Nothing on this page writes to the CRM.

0 / 0

4Research team plan

The research team runs after the import as cloud agents, with projects split into batches (for example by priority or state). Each agent returns a structured file. Rex merges and dedupes the results and shows them to John before anything is written to the CRM.

Ground rules for every agent

  • Research only. No calls, emails, forms or messages to anyone.
  • Public sources only. Every value comes with a source URL and the date it was checked.
  • Never invent. If something can't be found, it stays a dash "-" and is marked not found.
  • Return files to Rex. Agents never write to the CRM directly, and writes happen only after John approves.

A · Exact site addresses

Scope: all 122 projects. Every lead starts with "-" for street and ZIP.

What they look for
The street address and ZIP of the site, from owner announcements, county or parish filings, permits, utility or regulatory filings and contractor project pages.
Returns
Project ID, street, city, state, ZIP, source URL, date checked, and confidence (exact site vs. nearest parcel/road vs. not found).
Lands in the CRM
update_lead_info replaces the dashes. The address source goes in a custom field once the layout is approved.

B · Contacts & decision makers

Scope: all 122. The file has no named people today.

What they look for
GC project executives and preconstruction leads, package buyers for concrete and interiors (framing, drywall, finishing, painting), EPC subcontracts managers for power work, and owner construction leads. This follows the PDF's buying paths.
Returns
Name, title, company, role on the project, the public business route (portal, office line or project inbox), source URL and date checked. Nothing personal.
Lands in the CRM
create_related_contact on the lead (commercial leads require a title) and create_vendor_contact on the company. They're added as records only. No one is contacted.

C · Project metadata & status updates

Scope: all 122. The data is as of Sep 25, 2026.

What they look for
Current status and milestones since September, GC verification for the 74 "not verified" projects, investment figures for the 61 blanks (with the stated basis, never totaled), and trade-package and buyout dates.
Returns
Project ID, field, old value, new value, source URL and date checked.
Lands in the CRM
update_custom_fields on the lead. Tom's original row is kept as-is (for example in a Raw Row field) so updates never overwrite his research.

D · Contractor / buyer mapping (62 projects)

Scope: the 62 projects with no outreach company (52 Qualify next, 10 Monitor).

What they look for
The GC, CM or EPC, and any awarded concrete and interiors subs, for each project. They also check whether any of the existing 29 companies already covers it.
Returns
Project ID, company, role, public vendor or prequalification route, evidence (primary award vs. reported), and source URL.
Lands in the CRM
New companies, using whichever company type John picks. Each lead gets a "Buyer Route Companies" field, and each company gets "Related Project IDs." Once a job is sold, attach_company_to_project creates the real link.
How results come back: agents return one CSV/JSON per batch. Rex merges them, flags conflicts, and builds a before/after review for John. After John approves, the updates are written in batches, and each one goes through the CRM's own preview and confirm step.

5CRM redesign research

This is part of the research, and it gets reviewed after the project research comes back. The goal is a small redesign of how leads and pipeline work for a business that sells crews to GCs on large projects. These are the current CRM limits, checked read-only in the US Carpentry tenant.

Leads & pipeline UI

  • There's one lead pipeline today, "Sales" (New, Contacted, Qualified, Won, Lost). The proposed pipeline is "Industrial Crew Pursuit": Researched → Researching Buyer → Contacted → Prequalification → Bid Invited / Scope Defined → Quoted → Awarded, plus On Hold / Monitor and Closed – Lost / Not a fit.
  • What should a lead card show at a glance? For example priority, sector, state, GC verified, buyer route and next action.
  • Filtering by priority and sector: there's no tags tool, so this depends on select-type custom fields.
  • There's no lead value field. Investment is not deal value. Real value comes later from crew size × duration × rate.

Company-to-lead linking

  • Today a company can be linked only to a project (attach_company_to_project). There's no tool to link a company to a lead.
  • Until a job is sold, the contractor's name sits in a text field on the lead.
  • To research: a "companies on this lead" block with a role (GC, EPC, Owner, Specialty sub, Referral), so one company like Turner shows all its projects.

Company types

  • Only system types exist, and every one is payable: Vendor, Supplier, Subcontractor, Service provider, Attorney, Legal.
  • There's no "General Contractor" or "Owner / Developer" type (a buyer, not a vendor), and no tool was found to create one.
  • Options: Vendor + a "Relationship" custom field for now, or ask NokNok for GC / Owner types.

Custom fields

  • There are 0 custom fields today. The draft list in the plan is Project ID, Research Priority, Sector, Owner / Developer, Investment + Basis, Scale, Milestones, Current Status, Construction Team, GC Verified, Evidence, Crew Fit, Next Sales Action, Qualification Gate, Reviewed, Sources 1–4, Buyer Route Companies, and Raw Row (json).
  • This is under John's review. He may lay it out differently.
  • Fields can only be archived, never deleted, so the list should be settled before creating them.

6All 122 projects

From the Projects tab. "GC verified" is derived: it's "No" when the Construction team / role cell says "not verified." Click a column header to sort.

IDPriorityProjectStateLocationSectorOwnerCurrent statusGC verified