For a deep tech company, a GTM engineer builds a list of a few hundred named sites instead of thousands of contacts. The data comes from permits, procurement portals, capex announcements, grant awards and job posts for technical roles. The CRM then tracks each site's buying committee and paid pilot across a cycle that often runs past a year.
Why start with a short named account list?
Start there because an industrial market can be counted. A company selling a monitoring system for cement kilns can list every kiln in its target countries, and the buyer is the site that runs it. A SaaS GTM engineer builds for volume: thousands of contacts, subject line tests, and reply rates read across large samples. A deep tech GTM engineer builds for coverage: every relevant site known, ranked by evidence of an active project, and owned by one person.
In practice the list holds a few hundred sites, each with a reason to be there. A site earns a place when it runs the process your product changes. It moves up when a public record shows money or people moving toward that process. The general role, and the point at which a startup should hire one, is covered in what a GTM engineer is and when to hire one.
We have worked this way in crypto infrastructure. At FastLane, we took market share from 10% to 75% by working from a short list of named accounts.
Which data sources find industrial buyers?
Public records find them, because industrial buyers file paperwork months before they buy, and those filings show what a site plans to do next.
| Source | Where to look | What it tells you |
|---|---|---|
| Environmental permits | EPA's ECHO database and state permit portals | A new or modified air or water permit often means a new line or a process change. ECHO covers over one million regulated facilities (EPA, checked Oct 2026). |
| Procurement portals | SAM.gov for US federal buyers, TED for EU public buyers, state and utility portals | Pre-solicitation and sources-sought notices give months of warning before a tender closes. |
| Capex announcements | Company press releases, earnings calls, state economic development awards | Names the site, the budget and the start date. US manufacturing construction ran at $170.7 billion a year in August 2026, down 19.2% from $211.1 billion in August 2025 (Census Bureau, Oct 2026). Fewer new projects make each announced one worth more. |
| Trade show exhibitor lists | Public exhibitor directories on show websites | Shows which integrators, OEMs and competitors sell into your category, and who partners with whom. |
| Grant awards | SBIR.gov, DOE and EU program award lists | Awardees are often buyers or partners, and the abstract states the technical problem. SBIR.gov holds 219,770 SBIR and STTR awards (checked Oct 2026). |
| Technical job posts | Company career pages and job boards | A post for a controls engineer or a battery test technician names the equipment and often the project. |
Job posts show the gap between the two markets most clearly. Our signal monitor scored 92 signals as a strong fit between 14 September and 14 October 2026, and 48 of those were go-to-market hires (our data, Oct 2026; we score each public signal against a fit model from 1 to 10). For a SaaS seller, a new sales leader is a good trigger. For a deep tech seller, the trigger is the engineer who will own your product on site.
Why does enrichment fail for plant and operations roles?
Contact data is thin for the people who run plants. Many contact databases build their records from public professional profiles, and plant roles use those profiles less. Pew found that 53% of US adults with a bachelor's degree or more use LinkedIn, against 28% with some college and 10% with a high school education or less (survey May to September 2023, published January 2024). Plant roles that do not require a degree fall into the groups with lower use.
Site structure adds a second gap. Databases tie people to a head office domain, while the buyer sits at a plant that may trade under a subsidiary name. Name matching fails here first. In our own data we caught a hiring signal for one company matched to a different company with the same name (our data, Oct 2026), and plant subsidiaries create more of these collisions.
A GTM engineer fills the gaps with sources tied to the site:
- Read permit filings. A Title V air permit application must be certified by a responsible official at the facility, so the filing often names a senior person on site.
- Map the organization by site address, then by title.
- Call the plant switchboard to confirm names before any email goes out.
- Use association member lists and conference speaker lists for engineering roles.
- Mark every contact with a source and a check date.
How do you run a sales cycle that lasts more than a year?
Track the account, and treat each contact as temporary. An industrial purchase usually involves the plant manager, a process or controls engineer, environmental health and safety, procurement, and a corporate capex committee. The GTM engineer builds an account map with a slot for each role, flags empty slots, and records the last touch per person.
Contacts go stale inside one cycle. We re-verified 520 B2B contacts that a verifier had marked deliverable about 10 weeks earlier: 23% were invalid and 10% were catch-all (our data, Oct 2026; two verification tools, fintech and B2B lists). Over a cycle longer than a year, re-verify every quarter and watch for job changes. When the champion leaves, the account moves to at risk the same week, and the GTM engineer finds the replacement before the next touch is due.
Aim for at least three named people per site, with at least one at corporate level, so one job change does not stall the deal.
How should the CRM track pilots?
Track each pilot as its own record with a decision date, because pilots stall. A SaaS deal stage called "trial" cannot hold the data a hardware pilot needs.
Create these fields on the pilot record:
- Site, line or asset under test
- Signed success criteria, with the metric and threshold
- Technical owner and executive sponsor, as two separate contacts
- Start date, end date and the scale-up decision date
- Who pays for the pilot, and which budget pays for the rollout
- Number of units or sites in the rollout if the pilot passes
- Status: proposed, signed, installed, measuring, passed, failed, stalled
Report pilots that pass their end date without a decision every week. A pilot with no signed success criteria counts as a free demo and gets no forecast value.
SaaS GTM engineering versus deep tech GTM engineering
| Dimension | SaaS GTM engineering | Deep tech GTM engineering |
|---|---|---|
| Account list | Thousands of companies from a database filter | A few hundred named sites from public records |
| Unit of account | Company domain | Site, line or asset |
| Main signals | Funding, sales hires, tool installs, web visits | Permits, tenders, capex, grants, technical hires |
| Enrichment | Vendor data covers most roles | Plant roles need manual and public record sources |
| Outreach | Sequences tested on volume | Few touches per person, several people per site |
| Stakeholders | Often one buying team | Site, engineering, safety, procurement, corporate |
| Cycle | Weeks to a few months | Often more than a year, with a paid pilot |
| CRM objects | Lead, contact, opportunity | Site, account map, pilot record, opportunity |
| Main metric | Meetings and pipeline per month | Sites covered, threads per site, pilots converted |
When should a deep tech company set this up?
Set it up before the first pilot ends. A founder can track a handful of accounts from memory, but parallel pilots and procurement deadlines need a system. Build the site list and the pilot record first, then add signals. To test the list on real buyers, our free trial books the first 3 qualified meetings at no cost.
If you want the site list, data sources and pilot fields mapped for your market before you hire, start with The Diagnostic.