Revenue Plan: Clutch Solutions
The Baseline
New-logo motion against a named set of competing VARs — three national-scale, two regional — not a claim on total market competition. Clutch brings faster growth (Inc. 5000, CRN Triple Crown) and MBE certification as a structural edge the national players can't match, where supplier-diversity spend applies.
Historical account and vendor data exists for the territory. No opportunities are logged under this rep in Salesforce yet — this seat is new, the relationships and territory knowledge aren't.
OEM portals are accessible for margin and rebate reference. The strategic priority sits in The Quarters — rebates are a byproduct of vendor depth, not the target.
Account universe, incumbent VAR per account, vendor margin bands, and prior territory coverage history all need to be pulled before this baseline can carry real numbers — including how many active bidders are actually in play per account, since a two-bidder account and a five-bidder pile-on are not the same win-rate bet.
Capacity & Coverage
The Quarters
Named-account list finalized with incumbent-competitor tagged, and outbound sequencing live across the full account base. The opportunity-count gate begins at Q2, aligned with the month 4-6 ramp-to-productivity window — months 1-3 are mapping and relationship-building, not quota-bearing.
First real read on what's converting, correct list, message, or execution based on what that read shows. At least one deal reaches full documentation, not just verbal commitment.
Double down on whatever vertical or account type is actually converting — AI infrastructure is the first candidate worth testing, given where Clutch's own investment and vendor certifications run deepest — going deep on the top infrastructure and software vendors rather than chasing rebates account by account. Three or more new logos closed, with GP and cycle time now real numbers instead of ranges.
Rebuild every capacity and coverage number using a full year of actual data. Present the revised range to leadership as the basis for Year 2 targets.
The Rail
Outbound opens by naming the account's own operational reality — the incumbent VAR, the vendor gap — using RVP construction, not a generic intro.
Every touch is disposition-tagged in Salesforce from day one, so the read shows whether a list, message, or rep problem is constraining the funnel.
Five wins, each earned and documented, before an opportunity is allowed into forecast.
Terms shaped from vendor margin bands pulled off OEM portals, not concessions used to rescue a stalling deal.
A forecast that holds because every win has an artifact — closed-won GP and cycle time convert this plan's ranges into Sourced fact.
Origami and White Whale drive account and contact intelligence, backed by a disciplined dialer cadence run personally to keep outreach volume consistent — a 'whatever it takes' approach to the technology edge.
OEM account executives are engaged as active partners on my accounts, not treated as a rebate or spec resource. Success to validate in-seat: deal registration, MDF/co-op access, dedicated OEM SE time, and joint pipeline reviews — not just a strategic label.
Regional conferences and industry events put me in front of the CIOs, CTOs, and VPs of IT who own these decisions across Dallas/Ft. Worth, ahead of any cold outreach.
High-touch relationship-building — sponsored socials and other shared experiences — builds top-of-mind share with key accounts that a generic outbound cadence can't.
A named incumbent with an active relationship means this is priced and pursued as a displacement fight, targeting the 15-25% band. No real incumbent, or a genuine multi-bidder RFP, means it's pursued as greenfield, targeting 50-60%.
Estimate the price needed to beat the likely competitor and check it against the GP floor for this deal size. If winning requires pricing below the floor, this is a no-bid or a price-for-margin play, not a chase.
A five-minute requote and a full OEM sub-quote with dedicated SE time are not the same bet. Full pursuit effort is reserved for opportunities that clear the incumbency and margin checks first.
Technical evaluation criteria set with the prospect's own team, using whichever OEM specialist (HPE, Nutanix, or other) fits that account, not a generic checklist.
A champion inside the account is multi-threaded beyond one contact, especially critical where an incumbent VAR already has that relationship.
A named sponsor and a real decision date exist, with a stated cost if the date slips, not just a soft target.
Budget confirmed directly with the economic buyer, not assumed from a champion's read of the room.
Redlines cleared and a signature path confirmed with procurement before the deal is called closed.
KPI & Risk
fewer than 15 mapped by week 6
escalate the account pull, check territory data completeness
under 5 by end of Q1
check whether it's a list problem or a message problem before changing either
under 10% after 15 qualified opps
re-map the champion and check how deep the multi-threading actually goes
under 40%, or over 70%, after 15 qualified opps
under-band: check the bid gate isn't screening out winnable deals; over-band: price is too conservative, leaving margin or volume on the table
median cycle over 150 days by Q2
audit stalled deals stuck at verbal commitment, not yet documented
zero closes by end of Q2
pull the activity data and raise it in the next manager 1:1
can't compute coverage math without it
manager-assisted pull from an adjacent territory as an interim proxy
below floor at first read in Q2
fix the list before the message, the message before the rep
more than 2 still open entering Q4
force a mid-quarter data pull instead of waiting for year-end
technical support unavailable inside a deal's decision window, given known thin internal delivery capacity
pre-clear OEM SE relationships in Q1; escalate to manager if a live deal stalls waiting on support
real income lags the closed-won milestone by an unmodeled invoice-and-collection gap, with no base salary to bridge it
pull standard invoice/payment terms from Finance or the FY26 Commission Plan; if the gap threatens runway before it's known, raise it with Matt directly