XI — Companies, people, routes
Only now do we buy anything.
Every accepted Market Arm becomes a sourcing instruction, and candidate companies come back against it. A record returned by a database is a candidate. It is not yet a company worth writing to.
The company.
We check each candidate against the hypothesis that produced it:
- Does this company actually perform the target activity?
- Does it operate in the required geography?
- Does its scale fit the argument?
- Is the relevant facility or business unit real?
- Does it show the operational signal the hypothesis requires?
- Is it still trading?
- Is it a duplicate of a record already accepted under another name?
- Is it part of a larger group, and does that change who decides?
- Is it an operator, a vendor, an adviser, or a directory entry?
The company file records why the organisation was accepted or rejected, and which Market Arm produced it.
That last field matters more than it sounds. It is what allows a weak arm to be identified months later by its results rather than by somebody's opinion of it in a meeting.
Found in a database is not a reason to send a letter.
The person.
We do not send letters to markets. We send them to people, and not necessarily to the most senior person available.
The target is whoever sits closest to the decision. Who owns the problem. Who feels the cost when it happens. Who controls the relevant budget line. Who can approve a next step. Or who can carry the proposal to the person who will.
A title is evidence. It is not proof. Profiles go stale. Conference biographies describe jobs people have already left. A group executive can hold complete authority and no interest whatsoever in one site's problem. A site manager can feel that problem every single day and have no permission to change anything across the group. Where those signals conflict, the person stays unresolved until a current source closes it.
The record is strong when several signals agree at once: the person is current, the role is relevant, the geography makes sense, the operating scope matches the hypothesis, and the company context supports the argument the letter is going to make.
The physical route.
Here physical mail stops resembling email, and being wrong starts costing money.
A correct name and a headquarters address are not a delivery route.
The registered address often belongs to a formation agent. Headquarters can sit in a different country from the recipient. The person sometimes works from a regional office, a plant or a subsidiary trading under a different name. Companies move. People leave. A shared reception accepts a package and has no reason on earth to route it onward. Parent companies refuse mail addressed to employees of their own subsidiaries.
So we verify the route as one connected record: current company, current person, current role, the relevant receiving office, the physical mailing address, the sources supporting each of those, and anything that contradicts them.
- VERIFIED
- Every element agrees and is current. Cleared for production.
- NEEDS REVIEW
- Something is thin. A person looks at it before anything is printed.
- ROLE UNCERTAIN
- The individual is real and current. The responsibility is not confirmed.
- OFFICE UNCERTAIN
- The individual is confirmed. The receiving location is not.
- MOVED
- The record was correct and is no longer correct.
- REJECTED
- No route can be established. It stays out of production entirely.
A weak route is not tested with the client's postage.
That single sentence is most of the difference between physical outreach and email. A bad email address costs nothing, so it gets sent anyway, and the failure is invisible. Paper, an object, production, handling and postage all cost money, and every wasted send is a small physical monument to a decision that should have been made three steps earlier.
The constraint is not a disadvantage. It is the entire reason this system runs in the order it does.