How an outbound prospecting engagement runs, step by step.
What Ergon needs from you before outreach, what happens during the pilot, what the records look like, and how the common practical questions are answered.
Ergon executes within a framework you approve. Positioning and commercial decisions stay with you.
Discuss a pilotBefore outreach
What Ergon needs from you.
Outreach starts only after these are in place. After that, Ergon performs routine execution within the agreed framework; you are not asked to approve each individual action.
- 01A product or service briefing. What you sell, to whom, and what a good account looks like.
- 02Target criteria. Segment, size, geography, equipment or situation that makes a company worth contacting.
- 03Exclusions. Existing customers, active opportunities, competitors and any company you do not want contacted.
- 04Approval of the initial account list Ergon researches from the criteria.
- 05Approval of the messaging Ergon prepares from your briefing. Material changes are approved before use.
- 06A named person who will take interested conversations when Ergon hands them over.
Process
Responsibility and record produced at each step
01
Brief and target criteria
Client
You describe what you sell and to whom, set the target criteria and exclusions, and name the person who takes interested conversations. Ergon records the criteria as the framework for the engagement.
Record Agreed target criteria and exclusion list
02
Research accounts and contacts
Ergon
Ergon researches companies that meet the criteria in batches, records the reason each one fits, and identifies the relevant contact by role. Companies that fall outside the criteria or are ambiguous are flagged for your input rather than added.
Record Initial account list with fit rationale and contact research
03
Approve list and messaging
Client · approval point
You review the account list and remove or add companies. You approve the first-touch email, follow-up and call outline Ergon has prepared from your briefing. Nothing is sent before this approval, and each later batch of researched accounts is approved before it is contacted.
Record Approved account list and approved messaging
04
Run outbound and follow-up
Ergon
Ergon sends the approved email outreach, makes the calls and follows up according to the agreed outreach sequence, using the external representation agreed with you. Each account is recorded through to its outcome: a response, a wrong contact, a removal request, or a closed record once the sequence is complete.
Record Every action dated in the prospecting register
05
Record responses and review
Ergon · client participates at the review point
Responses are recorded as they arrive: no response, wrong contact, not a fit, removal requested, client input required, interested. At the review point you and Ergon go through the responses, target quality, messaging and practical issues, and adjust the criteria or messaging where appropriate.
Record Activity and response report; agreed adjustments
06
Hand off interested prospects
Ergon hands off · client takes the commercial conversation
When a prospect expresses interest, Ergon records the response, writes a handoff note with the relevant context and passes it to your named contact. Pricing, technical questions, proposals and everything after are yours.
Record Handoff note per interested prospect
At the end of the agreed period you receive the account list, contact research, complete register and all handoff notes produced during the engagement.
Prospecting register
The primary working record, as held by the client
Illustrative example — fictional data
Prospecting register — Example Automation Client
| Company | Segment | Contact role | Fit rationale | Last action | Outcome / note | Next action | Owner |
|---|---|---|---|---|---|---|---|
| Example Foods A | Food processing | Plant Engineering Manager | Two Ontario plants; line expansion announced on company site. In-house engineering per job postings. | Sep 15 Email 1 sent | No response | Follow-up email Sep 24 | Ergon |
| Example Packaging B | Packaging manufacturing | Operations Manager | Multiple packaging lines; recent posting for a controls technician indicates automation work in progress. | Sep 17 Call — voicemail | No response | Second call Sep 24 | Ergon |
| Example Beverage C | Beverage bottling | Maintenance Manager | Bottling plant within agreed region; public tender record shows use of third-party integrators. | Sep 16 Email 2 sent | Wrong contact Role has changed since research. | Identify current maintenance lead | Ergon |
| Example Dairy D | Dairy processing | Engineering Manager | Plant expansion announced publicly; within agreed segment and size range. | Sep 19 Short call at prospect’s request | Interested — handed to client Filler replacement planned for 2027. | Client to schedule conversation; see handoff note | Client |
| Example Snacks E | Snack manufacturing | Plant Manager | Within region and size range; multiple production lines listed on company site. | Sep 12 Reply received | Not a fit Outsources all automation to an existing integrator under contract. | None — record closed | No owner |
| Example Bakery F | Commercial bakery | Operations Director | Two Ontario facilities; new production line reported in trade press. | Sep 10 Email 1 sent | Removal requested — suppressed | None — no further contact | No owner |
| Example Meats G | Meat processing | Plant Engineer | Meets size and region. Unclear whether washdown-only environment is within the client’s scope. | — Research complete | Client input required Held until segment fit is confirmed. | Confirm inclusion in target list | Client |
| Example Brewery H | Brewing | Production Manager | Mid-size brewery with a canning line installed within the agreed equipment-age window. | Sep 19 Email 1 sent | No response | Follow-up email Sep 26 | Ergon |
Example Foods A
Food processing · Plant Engineering Manager
- Fit rationale
- Two Ontario plants; line expansion announced on company site. In-house engineering per job postings.
- Last action
- Sep 15 · Email 1 sent
- Outcome
No response
- Next action · owner
Follow-up email Sep 24
Ergon
Example Packaging B
Packaging manufacturing · Operations Manager
- Fit rationale
- Multiple packaging lines; recent posting for a controls technician indicates automation work in progress.
- Last action
- Sep 17 · Call — voicemail
- Outcome
No response
- Next action · owner
Second call Sep 24
Ergon
Example Beverage C
Beverage bottling · Maintenance Manager
- Fit rationale
- Bottling plant within agreed region; public tender record shows use of third-party integrators.
- Last action
- Sep 16 · Email 2 sent
- Outcome
Wrong contact
Role has changed since research.
- Next action · owner
Identify current maintenance lead
Ergon
Example Dairy D
Dairy processing · Engineering Manager
- Fit rationale
- Plant expansion announced publicly; within agreed segment and size range.
- Last action
- Sep 19 · Short call at prospect’s request
- Outcome
Interested — handed to client
Filler replacement planned for 2027.
- Next action · owner
Client to schedule conversation; see handoff note
Client
Example Snacks E
Snack manufacturing · Plant Manager
- Fit rationale
- Within region and size range; multiple production lines listed on company site.
- Last action
- Sep 12 · Reply received
- Outcome
Not a fit
Outsources all automation to an existing integrator under contract.
- Next action · owner
None — record closed
No owner
Example Bakery F
Commercial bakery · Operations Director
- Fit rationale
- Two Ontario facilities; new production line reported in trade press.
- Last action
- Sep 10 · Email 1 sent
- Outcome
Removal requested — suppressed
- Next action · owner
None — no further contact
No owner
Example Meats G
Meat processing · Plant Engineer
- Fit rationale
- Meets size and region. Unclear whether washdown-only environment is within the client’s scope.
- Last action
- — · Research complete
- Outcome
Client input required
Held until segment fit is confirmed.
- Next action · owner
Confirm inclusion in target list
Client
Example Brewery H
Brewing · Production Manager
- Fit rationale
- Mid-size brewery with a canning line installed within the agreed equipment-age window.
- Last action
- Sep 19 · Email 1 sent
- Outcome
No response
- Next action · owner
Follow-up email Sep 26
Ergon
Example Foods A
Plant Engineering Manager
- Outcome
- No response
- Next action
- Follow-up email Sep 24 Ergon
Details for Example Foods A
- Segment
- Food processing
- Fit rationale
- Two Ontario plants; line expansion announced on company site. In-house engineering per job postings.
- Last action
- Sep 15 · Email 1 sent
Example Packaging B
Operations Manager
- Outcome
- No response
- Next action
- Second call Sep 24 Ergon
Details for Example Packaging B
- Segment
- Packaging manufacturing
- Fit rationale
- Multiple packaging lines; recent posting for a controls technician indicates automation work in progress.
- Last action
- Sep 17 · Call — voicemail
Example Beverage C
Maintenance Manager
- Outcome
- Wrong contact Role has changed since research.
- Next action
- Identify current maintenance lead Ergon
Details for Example Beverage C
- Segment
- Beverage bottling
- Fit rationale
- Bottling plant within agreed region; public tender record shows use of third-party integrators.
- Last action
- Sep 16 · Email 2 sent
Example Dairy D
Engineering Manager
- Outcome
- Interested — handed to client Filler replacement planned for 2027.
- Next action
- Client to schedule conversation; see handoff note Client
Details for Example Dairy D
- Segment
- Dairy processing
- Fit rationale
- Plant expansion announced publicly; within agreed segment and size range.
- Last action
- Sep 19 · Short call at prospect’s request
Example Snacks E
Plant Manager
- Outcome
- Not a fit Outsources all automation to an existing integrator under contract.
- Next action
- None — record closed No owner
Details for Example Snacks E
- Segment
- Snack manufacturing
- Fit rationale
- Within region and size range; multiple production lines listed on company site.
- Last action
- Sep 12 · Reply received
Example Bakery F
Operations Director
- Outcome
- Removal requested — suppressed
- Next action
- None — no further contact No owner
Details for Example Bakery F
- Segment
- Commercial bakery
- Fit rationale
- Two Ontario facilities; new production line reported in trade press.
- Last action
- Sep 10 · Email 1 sent
Example Meats G
Plant Engineer
- Outcome
- Client input required Held until segment fit is confirmed.
- Next action
- Confirm inclusion in target list Client
Details for Example Meats G
- Segment
- Meat processing
- Fit rationale
- Meets size and region. Unclear whether washdown-only environment is within the client’s scope.
- Last action
- — · Research complete
Example Brewery H
Production Manager
- Outcome
- No response
- Next action
- Follow-up email Sep 26 Ergon
Details for Example Brewery H
- Segment
- Brewing
- Fit rationale
- Mid-size brewery with a canning line installed within the agreed equipment-age window.
- Last action
- Sep 19 · Email 1 sent
Handoff summary
What the client receives
Illustrative example — fictional data
Handoff note — Example Dairy D
- Company
- Example Dairy D — dairy processing, one Ontario plant with expansion announced publicly
- Contact role
- Engineering Manager
- Context
- Approved list, Sep 8. Email 1 sent Sep 11. Follow-up email Sep 18. Reply received Sep 18. Short call at the prospect’s request Sep 19.
- What happened
- Contact replied asking whether the client has built washdown-rated control panels for filling lines. On the call, confirmed that a filler replacement is being planned and that they want to understand build and integration scope before issuing an RFQ.
- Expressed interest
- Wants an introductory conversation with the client’s engineering or sales lead. Timing: planning stage, project expected in 2027.
- What was discussed
- The client’s general panel-building capability as described in the approved messaging. No pricing, lead times or technical claims were discussed.
- Open questions
- Experience with washdown-rated enclosures. Typical lead time for a panel of this type. Whether the client will work alongside the prospect’s existing integrator.
- Recommended next action
- Client engineering or sales lead to call the Engineering Manager the week of September 21 and reference the filler project. Contact details are in the register. Client
Sample outreach
First touch, as approved by the client
Illustrative example — fictional data
First-touch email
Subject: Control panels for the filling-line expansion — on behalf of Example Automation Client
Hello,
I am writing from Ergon Operations on behalf of Example Automation Client, an Ontario builder of custom control panels and automation cells for food and beverage plants.
Example Dairy D’s announced plant expansion is the reason for this note. If a filling-line or packaging upgrade is part of that work, Example Automation Client would be glad to describe how it has approached similar panel builds, including washdown-rated enclosures.
Would a fifteen-minute call with your engineering lead be useful? If this is not relevant, a one-line reply saying so is welcome and I will not follow up again.
View full example
Example Dairy D’s announced plant expansion is the reason for this note. If a filling-line or packaging upgrade is part of that work, Example Automation Client would be glad to describe how it has approached similar panel builds, including washdown-rated enclosures.
Would a fifteen-minute call with your engineering lead be useful? If this is not relevant, a one-line reply saying so is welcome and I will not follow up again.
Regards,
Vasily Nikulin
Ergon Operations
vasily.nikulin@ergonoperations.com
Illustrative example — fictional data
Call opener
“Good morning. This is Vasily Nikulin from Ergon Operations, calling on behalf of Example Automation Client, an Ontario control-panel and automation builder. I am trying to reach the person who looks after engineering for your filling lines. Is that you, or could you point me to the right person?”
“If this is not relevant to your plant, tell me and I will record that so we do not call again.”
Outreach standards
How prospects are contacted
- External representation is agreed before outreach and must be truthful. Ergon does not misrepresent its identity or its relationship to the client.
- Only approved messaging is used. Material changes are approved before use.
- Accounts are selected and researched against your approved criteria rather than supplied as an undifferentiated purchased lead list.
- Your exclusions are honoured for the full engagement.
- Removal requests are recorded and the contact is suppressed from further Ergon outreach for the engagement. Suppression information is included in your records.
- No pricing, technical claims or commitments are made on your behalf.
What reporting covers
Periodic reporting during the engagement summarizes the register:
- Accounts researched, approved and contacted
- Actions taken, by type and date
- Responses by outcome: no response, wrong contact, not a fit, removal requested, interested
- Handoffs made and their status
- Items waiting on client input
- Observations about target quality and messaging for the review point
Practical questions
Responsibility boundaries, stated plainly
Who approves target companies?
You do. You approve the criteria, the exclusions and the initial account list before outreach. Ergon researches further accounts in batches and you approve each batch before it is contacted. Borderline companies are recorded as “client input required” and held until you decide.
Who approves messaging?
You do. Ergon prepares the first-touch email, follow-up and call outline from your briefing. You approve them before use, and material changes are approved before use.
Who contacts prospects?
Ergon does, using the external representation agreed with you before outreach. Representation must be truthful: Ergon does not misrepresent its identity or its relationship to your company.
What does the client receive?
The researched account list, contact research, the prospecting register, a handoff note for each interested prospect and periodic reporting. Exact deliverables are set in the engagement scope.
What happens when someone is interested?
Ergon records the response, writes a handoff note with the relevant context and passes it to your named contact. Your team takes the conversation from there.
Who handles pricing?
You do. Ergon does not quote, propose, negotiate terms or take commission. If a prospect asks about price, the question is recorded in the handoff note.
Who handles technical questions?
You do. Ergon does not make technical claims or product-suitability judgments. Technical questions are recorded and passed to you with the handoff.
How is outreach recorded?
Every account, contact, action, response and next action is dated in the prospecting register. You hold the register at the end of the engagement.
How are removal requests handled?
The request is recorded and the contact is suppressed from further Ergon outreach associated with the engagement. Suppression information is included in the records handed to you.
What happens if a prospect is not a fit?
The reason is recorded and the record is closed. Reasons are summarized in reporting so the target criteria can be adjusted at the review point.
Contact Ergon Operations
Discuss a pilot.
Describe what you sell, who buys it and how new-account prospecting is handled today. Ergon replies by email to discuss target criteria and what a fixed-scope pilot would involve.
You work directly with
Vasily Nikulin
Founder
vasily.nikulin@ergonoperations.comToronto, Ontario, Canada