Find the roles. Read what they ask. Answer with evidence.
The engine runs a complete executive search end to end. It was built by running one, and every rule in it exists because it was learned the expensive way. Here is what it does, stage by stage, and what each stage hands you.
How it works · the stages, the files they produce, and the two ways to run them.
The sequence.
-
Observe the market
An intake interview sets the level, the target markets, the salary floor, and the verified facts about you. Then the engine scans the live boards that actually work, keeps only postings it has read off a real page, and tiers what is there against your floor and fit. The result is one living workbook, updated in place from then on.
-
Map the evidence
The shortlisted postings are read for what they state as minimums, what recurs across the set, and the unusual asks most candidates miss. Each requirement is mapped to your real history. Where the evidence is not there, that is recorded as a gap, and a gap never becomes resume text.
-
Brief the next move
Tailored resume versions are built from one shared fact bank, so they look general and are quietly built for a specific kind of role. Every version passes two gates before it reaches you. Then a weekly refresh reports what changed — new roles, verified closures, salary moves, your own application movement — and asks for a decision.
What the engine produces.
The four operating layers, each with its plain function and the real file it is in the career offer.
| Name | Layer | Plain function | In a search | Status |
|---|---|---|---|---|
| Recon View | Interface | Shared operating picture | The living workbook: every verified role, per-market views, top matches, lifecycle dates, refresh log | Live |
| Field Map | Context model | Facts, constraints, and dependencies | The fact bank. Nothing reaches a resume unless it is here; contested claims stay in a register that never ships | Live |
| Recon Kits | Tools | Reusable diagnostic and implementation tools | The kit itself: nine skills, the resume builder, the workbook updater, the two delivery gates | Live |
| Briefing Cycles | Workflows | Assessment, decision, and follow-through | The weekly refresh and the decision it asks of you | Live |
Live means the software exists and is what is sold. It does not mean an outcome: no placement, interview rate, or salary result is claimed here.
Approved ExecRecon imagery. Nothing here was photographed or generated for this site.
The rules the engine will not break.
They are why the output can be trusted, and they hold whether you run it or we do.
- Never fabricate a link
- Every apply link is read off a page that was actually fetched. A posting that cannot be verified is left out, and the workbook says so.
- Never infer closure from absence
- A role changes to closed only after direct verification. A partial scan, a blocked board, or an empty result page is not evidence that a job went away.
- Check eligibility before tailoring
- Stated minimums first: years, licence, location, work authorization, degree. A polished resume cannot rescue a disqualifying answer, and the hour is better spent elsewhere.
- Do not add or imply
- Where evidence for a requirement does not exist, that is a gap. It never becomes resume text, a skills-line entry, or an implication. Every claim has to survive a conversation with someone who does this for a living.
One more true thing, said even though it undersells the tooling: the single biggest lever in a search is moving an application from a cold board into a referral. No document does that. The engine says so where it matters.
Start with the search in front of you.
Leave an email and we will tell you the day it opens. Nothing else is sent.