Tech Stack Consolidation Recommendation

What it tests

Vendor evaluation skills, total cost of ownership thinking, and ability to build consensus for a tech decision across Sales, Marketing, and Finance stakeholders

Format

1. 1Candidate receives a scenario: the company has grown from 10 to 60 reps and now has 14 GTM tools across CRM, sales engagement, intent data, conversation intelligence, and revenue intelligence — with $380K annual spend and significant overlap
2. 2Task 1: audit the stack — categorize tools by function, identify redundant capabilities, and flag integration gaps
3. 3Task 2: build a consolidation recommendation reducing spend by at least 20% — show the before/after stack, estimated savings, and migration risk for each cut
4. 4Task 3: write a 3-slide executive summary (can be a doc outline) for a CEO/CFO audience explaining the recommendation, the tradeoffs, and the implementation sequence

What to look for

• Does the audit identify functional overlap with specifics ('Outreach and Salesloft are both being used for sequencing by different teams') rather than vague observations?
• Is the consolidation recommendation sequenced — cutting low-risk, low-usage tools first — or does it arbitrarily combine everything at once?
• Does the exec summary lead with the business case (ROI, risk reduction) — or get lost in vendor feature comparisons?
• Do they account for migration costs and rep disruption in the savings calculation — or is it naive gross savings?

Adaptation guide

Provide your actual GTM tool list (anonymized if needed) — candidates who audit a real stack give more actionable output. For earlier-stage companies with smaller stacks, focus the exercise on a greenfield stack design: 'You have $60K/year — build the ideal RevOps stack from scratch.'

Full description