Widenet across mid-market discrete manufacturers, narrowed by three signals that name the buyer.
6,000 emails a month across the eight verticals OpGate serves. Three signals overlay every send so the message names the vertical, the ERP, and the pain the recipient is already living. €2,000 a month plus a 5% success fee on any deal that closes through this engine within a 12 month window, with full attribution visible in your CRM.
What you get.
One engine, two motions running together. Widenet covers the market. Signals sharpen the timing. You see both in your CRM.
Electronics, automotive, machinery, precision metal, aerospace and defense, medical devices, clean energy, specialty materials. Discrete manufacturers, 50 to 500 employees. Wide enough to discover which vertical converts, tight enough to skip everyone who is not the ICP.
A procurement hire. An ERP project. An audit or compliance trigger. When one of these fires, the account jumps to the front of the queue that week with a message that names the specific event. When none fire, the widenet base keeps OpGate in front of the market.
Every account we touch is created as a lead in your CRM with the source and signal tagged. Every reply, meeting, and closed deal is attributed against those tags. The 5% success fee is only ever charged on deals your CRM confirms as sourced through this engine.
Who we write to.
The eight verticals from the strategy, plus which two lead. The rest run in parallel underneath.
| Vertical | Why it is on the list | Order |
|---|---|---|
| Aerospace and defense | Audit-forced demand. AS9100 and ITAR requirements map one to one to OpGate’s audit-ready logging. | Lead |
| Medical devices | Audit-forced demand. ISO 13485 traceability requirements map to the same audit-log wedge. | Lead |
| Electronics | Volatile categories (semis, boards), high supplier count. De-Risk value lands. | Parallel |
| Precision metal | Volatile categories (steel, copper, alloys), high supplier count. Same De-Risk story. | Parallel |
| Machinery | Long BOMs, many suppliers, tendering pain. Fits the “too complex for Excel” line. | Widen |
| Automotive | Supplier compliance and cost pressure. Consolidation moment when M&A fires. | Widen |
| Clean energy | New builds, growth-stage procurement, scaling supplier base. | Widen |
| Specialty materials | Category-specialist manufacturers with volatile inputs. | Widen |
Personas per account: procurement or purchasing manager, head of supply chain / COO, CFO on the savings angle, quality or compliance lead on the audit angle. One to two contacts per account, so the widenet stays personal.
The three signals.
Three trigger types, each a public event at a named account on a real date. When one fires, that account is written to that week. When none fire, the widenet base keeps steady rhythm.
A manufacturer is hiring a procurement, purchasing, strategic sourcing or buyer role. Or the job post names the exact pain OpGate replaces: manual, Excel, RFQ, spend analysis, supplier management. Either way, the account has just admitted procurement is a live problem and named the person who will own it. Reach them the same week.
Dynamics, SAP, or Odoo project surfaced through partner press, implementer job posts, or case announcements. Procurement-tool decisions happen alongside ERP because that is when the wiring gets rebuilt. OpGate integrates natively with all three, so the timing and the fit line up in the same message.
Aerospace and defense pursuing or renewing AS9100. Medical device firms in an ISO 13485 cycle. ITAR-adjacent quality hires. Each one needs a traceable sourcing trail, and OpGate’s audit-ready logging maps directly to the requirement. Compliance turns "someday" into "by this quarter." Verify the specific cert requirements before copy ships.
Why three and not twelve: the strategy doc lists twelve, and all twelve work, but three is the smallest set that covers OpGate’s three distinct buying moments (a hire, a system change, an external mandate). We can add signals four through twelve as the engagement scales without renegotiating the base package.
Package and pricing.
One package, two components: a monthly base that covers the whole engine, and a success fee only on deals your CRM confirms as ours.
| Component | Price | What it covers |
|---|---|---|
| Monthly base Smallest widenet pack + three-signal overlay. |
€2,000 / mo | 6,000 emails a month across the eight verticals, ICP-tight (50 to 500 employees, compatible ERP where identifiable). Three-signal overlay so signal accounts get written to the same week the trigger fires. Copy per vertical, one ask per touch. Reply routing to your team same day. Weekly report. |
| Success fee Only on deals attributed to this engine. |
5% for 12 mo | 5% of recognized revenue from any deal your CRM attributes to a lead we sourced, over the 12 months following the deal-close date. If no attributed deal closes, no fee is due. Attribution is visible to both sides in the CRM before any invoice is raised (see section 06). |
Term: 90 day initial engagement on the monthly base, then month to month. The 12 month success-fee window runs per deal, starting the day that deal closes. Success-fee eligibility ends the day the base engagement ends, on any new deals. Deals already attributed and closed before that date continue to pay through their own 12 month tail.
What is not included: paid ads spend, gifting, or events. Anything beyond the smallest widenet pack and the three signals is a separate scope quote. Adding signals four through twelve, or scaling above 6,000 emails a month, is a base-package uplift, quoted transparently.
What is included.
The line above says "widenet with three-signal overlay." Here is what that actually means, so €2,000/mo reads as a full engine, not a fee.
Dedicated sending domains and mailboxes, warmed to send safely at 6,000/mo. SPF, DKIM, DMARC set correctly. Weekly deliverability scan against the same industry gate we use for other prospect work. Any mailbox that drifts is pulled and replaced without you needing to notice.
Discrete manufacturers, 50 to 500 employees, in the eight verticals. Compatible ERP flagged where identifiable. Procurement, ops, finance, and (aero/med) quality seats enriched per account. Every list row includes the account, the seat, and any active signal event with its date. Verified before every send (catch-all, invalid, disposable removed).
One base sequence per vertical. Three signal-triggered variants: procurement hire, ERP project, audit or compliance. Each variant leads with the specific event and names the vertical and the ERP. Numbers used are OpGate’s own published figures, attributed to OpGate, never inflated. Three to four touches per contact.
Base widenet sends run every week to keep the funnel moving across all eight verticals. Signal-triggered sends fire the same week the trigger event surfaces, so the message lands while the hire is still onboarding, the ERP project is still being scoped, or the audit is still fresh.
Positive replies tagged by vertical and signal, forwarded to the OpGate reply owner you nominate. Meeting requests routed straight to that person’s calendar link. Objections and negatives suppressed automatically so nobody gets a second unwanted touch.
Weekly report on deliverability, replies, meetings booked, and which vertical and signal drove each. Every account touched is already a lead in your CRM with source and signal tagged, so the weekly numbers reconcile to the CRM in one click. That reconciliation is what feeds the success-fee calculation in section 06.
Attribution to CRM, transparent.
The 5% success fee only works if both sides see the same source of truth. Here is how attribution is wired so no invoice ever surprises either side.
Every account on the widenet list is created as a lead in your CRM with three tags: source = revsculpt-outbound, vertical, and signal (if any). Tags are visible on the lead record, filterable, and immutable once written. If the lead already exists, we do not overwrite; we add the tag and stop.
A meeting booked from a reply is logged as a CRM activity on the source lead. The activity carries the same source and signal tags. Every meeting flows into the standard opportunity pipeline OpGate already runs, no separate workflow.
When a lead converts to an opportunity, the source and signal tags flow through automatically via CRM inheritance. If an opportunity later gets renamed, merged, or reassigned, the tag stays with the record. Any attribution dispute is settled by what the CRM shows, not by what either side remembers.
A shared CRM dashboard filters on source = revsculpt-outbound across leads, meetings, opportunities, and closed-won revenue. RevSculpt has read access, OpGate has full access. Neither side can alter the filter. Monthly, the closed-won number on that dashboard is the number the 5% is applied to.
Base €2,000 invoiced monthly in advance. Success fee invoiced monthly in arrears, at 5% of new attributed revenue recognized that month, per the dashboard. Each success invoice cites the specific deals and CRM record IDs, so both sides can trace every euro back to a named account.
The 12 month success-fee window is applied per deal from its close date. Attributed expansion within that window (upsell, renewal add-on, cross-sell into the same account) counts. Renewals of the base contract past month 12 do not. This keeps the fee tied to the initial win, not to the account’s lifetime.
CRM in scope: the CRM OpGate already uses. If OpGate switches CRMs mid-engagement, the source tags are migrated with the records and the dashboard is rebuilt against the new system, no re-attribution debate.
The 90 day plan.
Build in week 1, send in week 2, hit rhythm by week 4. Same shape as every engagement we run, adapted to widenet-plus-signals.
Widenet list built across all eight verticals, aero/med first. Three signal sources wired (ATS + ERP-partner press + cert registries). CRM lead-source tags created and tested. Sending domains bought and warmed in parallel. Copy drafted per vertical plus three signal variants. You approve the final copy before anything sends.
Widenet base goes live at ~1,500/wk to hit 6,000/mo. Signal overlay live: any account matching signal 1, 2, or 3 is boosted that same week. Every touched account appears as a tagged lead in the CRM. Week 4 review: which verticals answered, which signal drove the reply.
Volume rebalanced across verticals based on which ones are answering. Aero/med typically pulls disproportionately in this window because the audit trigger is unusually specific. Signal variants tuned based on which variant is winning. First meetings booking into OpGate calendars. Shared dashboard live.
Engine at rhythm across the widenet plus the three signals. Early opportunities landing in the CRM with source tags intact. First deal or two may close inside 90 days on faster-cycle accounts. Day 85: 90 day report presented, and you decide to continue month to month, expand the package, or stop. Every asset stays yours.
Sign and start.
Four decisions and we start the list build the same week.
| Decision | What we need from you |
|---|---|
| 01 · Package | Smallest widenet pack (6,000 emails/mo) + three-signal overlay at €2,000/mo + 5% success fee (12 month window per deal). Confirm. |
| 02 · Beachhead verticals | Aerospace/defense + medical devices as recommended, or override with two other verticals you want first. The other six run in parallel underneath either way. |
| 03 · CRM & access | Which CRM (HubSpot, Salesforce, Pipedrive, other). Grant read access to the shared dashboard filter. Nominate the reply owner who takes meetings. |
| 04 · Geography | Europe-first as the strategy doc suggests, or a specific country priority (DACH, Nordics, UK, Benelux). We time sends to the local business day. |
Countersign: reply to the thread with "confirmed" and the four answers above. We send a one-page order form back the same day, list build starts day 1.