Public Footprint Reconnaissance: How SEs Research Prospects Before the First Call

Most first calls with a prospect are spent on questions the Solution Engineer could have answered before the meeting started. What cloud are you on? Which compliance regime applies to you? How big is the engineering team? Every minute spent on these basics is a minute not spent on the questions that actually move a deal. Public footprint reconnaissance is the discipline of doing that homework in advance, so that discovery starts at the level of real problems instead of introductions.

This skill sits in the pre-engagement stage of the SE Ignite skills inventory, and it is entirely vendor-neutral. Whatever you sell, the prospect leaves the same kind of public trail, and the same method reads it.

What “public technical footprint” actually means

A company’s public footprint is everything it reveals about its technology, organisation and constraints without you having to ask. For a Solution Engineer, four sources matter most:

• Job postings. A requisition for a platform engineer lists the tools the team already runs, the ones it wants to adopt, and often the pain behind the hire (“migrate legacy workloads”, “build observability from scratch”).
• Tech stack dependencies. Engineering blogs, conference talks, open-source repositories, developer documentation and integration pages show which platforms the prospect depends on and how they connect.
• Industry compliance requirements. The prospect’s sector and the regions it operates in tell you which regulations shape its architecture: data privacy, financial reporting, data residency, sector-specific security standards.
• Company communications. Annual reports, press releases, investor updates and leadership interviews reveal strategic priorities, such as expansion, consolidation or cost control, that your technical conversation must connect to.

A four-step reconnaissance routine

1. Set a time box

Reconnaissance can swallow an afternoon. Decide in advance how long the account deserves: a short block for a smaller opportunity, a longer one for a strategic account. The goal is a sharper first conversation, not a research paper.

2. Collect signals, not facts

Write down what you find as signals with a source next to each: “Hiring three data engineers with streaming experience (careers page)”, “Announced expansion into a new region (press release)”. A signal is something that suggests a need; it is not yet a confirmed problem.

3. Turn signals into questions

This is the step most SEs skip. Every signal should become a discovery question you can ask with credibility:

• “I noticed you are hiring for streaming data skills. Is that tied to a specific initiative, or is it a gap in the current platform?”
• “With the move into a new region, how are you thinking about data residency for customer records?”

Questions like these show the prospect you did your work, and they invite them to correct or confirm your reading, which is far more productive than asking them to describe their environment from scratch.

4. Feed the hypothesis

Reconnaissance is the raw material for a technical hypothesis: a short, testable statement about where the prospect’s architectural pain probably sits. Keep the hypothesis to two or three sentences and bring it to the call as something to test, never as a conclusion.

A simple reconnaissance template

Area	What I found	Source	Question it raises
Hiring
Stack and integrations
Compliance and regions
Strategic priorities

Fill one per account and attach it to the opportunity record so the Account Executive and anyone else joining the deal start from the same picture.

Common mistakes

• Presenting guesses as facts. “You run X” sounds presumptuous if it is wrong. “It looks like you might run X” invites a correction and keeps trust intact.
• Showing off the research. Reconnaissance should shape your questions, not become a monologue about everything you found.
• Stopping at technology. A stack list without the business priority behind it leads to a feature conversation. Always connect a technical signal to a strategic one.
• Using only stale sources. Old conference talks and archived blog posts may describe an architecture that no longer exists. Note the date of each source.
• Crossing ethical lines. Use public information only. Never try to obtain internal documents or access you have not been given.

How to practise it

Pick one company you know well and one you do not. Spend a fixed block on each, fill the template, and write three discovery questions per account. Then compare: the questions for the unfamiliar company are usually vaguer, which shows you exactly where your research process needs tightening. Repeat weekly with a real target account and the routine becomes automatic.

Why this skill lasts

Products change; the habit of arriving prepared does not. Public footprint reconnaissance is part of the “80% of Solution Engineering” that SE Ignite focuses on: tech-agnostic mechanics that work whether you sell infrastructure, security, service management or SaaS. The SE Ignite curriculum covers pre-engagement skills like this alongside discovery and narrative mechanics, and it is free to access for anyone who wants to build the foundation.