The problem
The project could easily have become a spreadsheet that sent emails. The business needed company and contact records, suppression, review, source evidence, campaign history and a safe way to decide whether a message was ready.
Built, activation pending · Ontario, Canada commercial-services provider
Building controlled prospect research and outreach for Ontario businesses
I designed a reusable lead-management system and built importable workflows for Ontario business discovery, enrichment, evidence-based research, review and measured email outreach.
The working context
What I was solving and what I owned.
My contribution
I designed the wider lead-engine architecture and built or specified the discovery, queue, research, review and email workflows. The retained version was not a proven live campaign, so I keep the activation boundary explicit.
I have kept the organisation, product and people private. I also left out exact figures and internal details that could identify the work. The status above tells you how far the implementation actually went.
How I worked through it
The choices behind the implementation.
If you are working on a similar system, these are the decisions I would examine before choosing tools or adding more automation.
- 01
Separate discovery from permission to send
Finding a company did not make it outreach-ready. I kept discovery, enrichment, fit review, contact validation and sending as separate states.
- 02
Use public evidence without inventing a problem
The research workflow could identify relevant services from the prospect's own public information. It could not claim that a facility had a fault, a compliance issue or overdue work without evidence.
- 03
Claim queued work atomically
The send queue was designed so two workers could not claim the same record. Uncertain send outcomes went to review instead of being retried blindly.
Expert insights from the work
What I learned and what I'd ask you to consider.
These are the lessons I took from the work. I would use them as questions for your own implementation, not as a universal recipe.
A lead database needs lifecycle rules
If your system cannot explain why a prospect is queued, suppressed, under review or complete, it is not ready to automate outreach.
Personalization must be checkable
Store the source behind every personalized claim. Your reviewer should be able to see what the workflow read and why it considered the detail relevant.
Uncertain delivery is its own status
A timeout does not prove that an email failed. Mark the outcome as uncertain and check the sending system before another attempt.
Where the evidence stops
Activation and campaign outcomes still need to be proven.
The architecture and workflows were built, but credentials, activation and live campaign evidence were not complete in the retained snapshot. I would run a small reviewed batch before making any claim about outreach performance.
Connected disciplines
- Lead operations
- Prospecting
- Workflow automation
- Email systems
- Review controls
Continue through the work
Related experience and perspective.
If this overlaps with a system you are thinking through, start a relevant conversation.