Skip to content

Case study · Technical Safety Services

Technician Opportunity Program

Took over a field-sourced lead program after a failed launch and rebuilt it into a net-new revenue channel that technicians actually use.

Period
2023 – present
Role
Program owner · rebuilt flows, integrations, reporting
Results

2,226

opportunities submitted

436

opportunities won

$2.8M

net-new revenue

Figures are those published in my resume. Architecture is described at the pattern level: no confidential configuration, pricing logic, or customer data appears on this site.

Field technicians are inside customer facilities every day and see expansion opportunities that sales never would. The original program meant to capture those leads launched and failed: the submission flow did not fit how technicians work, the handoff into sales was unreliable, and there was no reporting to show whether anything was converting.

A program like this fails quietly. Technicians stop submitting, sales stops trusting the leads, and the channel disappears without anyone deciding to end it.

  1. Started from the technician side, which I knew firsthand from two and a half years in the field. Rebuilt the submission flow around what a technician can realistically capture on site, in the time they have.

  2. Rebuilt the Salesforce flows and integrations so a submission becomes a properly routed opportunity with the context sales needs to act on it, and the outcome flows back so technicians can see what happened to their leads.

  3. Built the reporting layer in Power BI to track submissions, conversion, and revenue by the dimensions the business cares about, so the program could be managed instead of hoped for.

  4. Delivered enablement to both sides: technicians on how and when to submit, sales on how to work a technician-sourced lead.

A field observation becomes a won opportunity
  1. Technician spots an opportunity Inside the customer facility, during a scheduled visit.
  2. Submits in minutes A flow rebuilt around what can be captured on site, on a phone.
  3. Salesforce routes it A properly owned opportunity with the context sales needs.
  4. Sales works the lead Enabled on how a technician-sourced lead differs.
  5. Power BI reports it Submissions, conversion, and revenue by the dimensions that matter.

The outcome flows back to the technician who submitted it

The rebuilt program has produced 2,226 submitted opportunities, 436 won, and $2.8M in revenue that did not exist as a channel before.

Because conversion and revenue are reported, the program is managed on evidence and continues to run as a standing part of the sales motion.

Share of technician submissions won

19.6%

436 won of 2,226 submitted

19.6% · 436 of 2,226
won submitted

Technician-sourced opportunities since the rebuild, and the share that closed won: $2.8M in net-new revenue.

Where it sits

The highlighted nodes are the systems and people this project touched.

works opportunities submits field leads creates opportunities change requests scope · validation two-way sync price books pricing rules closed-won data CRM + quote data history forecast + intervals models analytics Sales team national org · 3 divisions Field technicians on-site at customer facilities IT & external consultants change control I govern Salesforce CRM system of record Tech Opportunity Program field leads into the pipeline Pricebook automation Python · 48 modules DealHub CPQ quoting backbone Commissions automation closed-won to payout Snowflake · MS SQL Server analytics data layer Revenue forecasting ensemble · ETS · LightGBM · foundation models Power BI executive dashboards CEO · CFO · VP Sales Ops decisions in, rules out