Skip to main content

Account Executive turned RevOps Builder

I build revenue infrastructure that scales GTM teams

Six years carrying quota at Toast, Dutchie, Shipday, and GigFinesse. 110-267% attainment. $200M+ ARR generated. Now building the operations systems I needed when I was selling.

About

The gap between sales execution and operations infrastructure

Most RevOps builders have never carried quota. They build theoretical systems that look good in Lucidchart but break when reps actually use them. I've spent six years closing restaurant operators while building the automation that made me more effective.

6 Years Carrying Quota
$200M+ ARR Generated
267% Peak Quota Attainment

I understand what actually moves deals forward because I've been in the seat. When I build lead enrichment platforms, workflow automation, or customer health monitoring systems, I'm solving problems I've experienced firsthand. Not theoretical bottlenecks from a backlog grooming session.

My technical background (Python, SQL, Make.com, n8n, Claude API integrations) means I can architect and implement complete systems. No handoffs to engineering. No waiting quarters for implementation. I spec it, build it, deploy it, and train your team on it.

Restaurant tech specialists: I've sold to thousands of restaurant operators across QSR, fast casual, and full service segments. I know the workflows, pain points, and what actually closes deals in this vertical.

Projects

Real systems that drove measurable revenue impact at restaurant tech companies

What I Built

Multi-platform enrichment workflow that processes restaurant leads and generates sales intelligence for territory targeting.

System captures:

  • POS systems (Toast, Square, Clover)
  • Third-party delivery platforms (DoorDash, Uber Eats, Grubhub)
  • Driver operations and delivery volume estimates
  • Contact information (emails, phone numbers)
  • Lead scoring (0-150 points based on fit criteria)

What Happened

  • 1,000 restaurants processed across CT and MA markets
  • 600+ verified contact emails extracted
  • Built to scale - can process additional markets by adjusting geography
  • Used to create call blocks and multi-touch outreach campaigns

How It Works

Feed restaurant names and addresses into Google Sheets. Workflow automatically searches Google Maps/Places APIs for business details, analyzes operations using Claude API, extracts contact information via n8n, scores leads, and writes enriched data back to the sheet.

n8n
Make.com
Claude API
Google Maps

What I Built

Automated campaign system that identifies expansion opportunities in existing customer base and executes outreach sequences.

System monitors:

  • Customer usage patterns
  • Feature adoption signals
  • Lifecycle stage and contract timing
  • Engagement activity

What Happened

  • 15%+ of monthly closed revenue came from automated campaigns
  • Higher conversion rates during winter months compared to peak season
  • Consistent expansion activity throughout the year
  • Account team could focus on strategic deals while automation handled standard upsells

Key Finding

Winter months (traditionally slower for new business) showed higher conversion rates for expansion campaigns. Customers had more time to evaluate, there was less competitive noise, and it aligned with annual planning cycles.

How It Works

Salesforce queries segment customers based on usage and engagement criteria. Gmass triggers personalized email sequences when expansion signals are detected. System tracks responses and updates CRM automatically.

Gmass
Salesforce

What I Built

Dual calculator system serving different stakeholders:

Spreadsheet Version:

  • Detailed cost breakdowns with assumption visibility
  • Scenario modeling capabilities
  • Used by owners, accountants, key stakeholders who need to see the math

HTML Version:

  • Browser-based calculator for live demonstrations
  • Real-time calculations during remote Zoom calls
  • Restaurant economics: commission costs, labor per delivery, payback period

What Happened

  • Adopted org-wide by sales team for product demos
  • Standardized value conversations across reps
  • Two distinct versions for different use cases (internal analysis vs. customer-facing demos)

How It Works

Input restaurant's delivery volume, average ticket size, current platform costs, and labor expenses. Calculator shows current total costs, projected costs with new platform, and payback period in months. Spreadsheet version allows detailed scenario testing. HTML version provides instant calculations during conversations.

JavaScript
HTML/CSS
Google Sheets
Apps Script

What I Built

Automated research system that triggers when restaurant demos are booked via Calendly. Takes restaurant name and website as input, runs operational analysis across multiple data sources, and delivers comprehensive discovery brief via email.

System generates:

  • ROI calculator with estimated savings based on restaurant profile
  • Third-party services identified (delivery platforms, POS systems)
  • Google ratings and review analysis
  • Local competitor landscape
  • Potential pain points based on operational signals
  • Positioning strategy recommendations

How It Works

Calendly booking webhook fires when demo is scheduled. System captures restaurant name and website URL, runs Google Maps API lookup for ratings and reviews, analyzes operational profile for pain points using Claude API, identifies competitor landscape, generates ROI estimates, and delivers complete discovery brief via automated email.

Infrastructure

Built on self-hosted n8n server running on DigitalOcean infrastructure (automation.mikegrowsgreens.com). Docker containerization with Caddy reverse proxy for SSL management. Self-hosting provides unlimited operation execution for high-volume discovery analysis without per-operation cost constraints.

Why self-host: Make.com works for simple workflows but becomes cost-prohibitive at scale. Self-hosted n8n provides full control over deployment environment, unlimited operations, and ability to build custom integrations.

What Gets Included

ROI Calculations: Estimated savings based on delivery volume, average ticket size, and current platform costs. Shows payback period and annual savings projections.

Third-Party Services: Identifies which delivery platforms they use (DoorDash, Uber Eats, Grubhub), current POS system, and other tech integrations.

Google Intelligence: Star rating, review count, recent review sentiment, operational hours. Review analysis for operational signals.

Competitor Context: Local competitors within radius, their ratings, market positioning opportunities.

Pain Point Analysis: Based on review text, operational profile, and tech stack. Identifies likely friction points with current setup.

Positioning Strategy: Recommended approach for demo based on their specific operational profile. Tailored talking points.

Why This Matters

Discovery and demo happen in same Zoom call (typical for restaurant sales). Having intelligence upfront allows tailoring demo to specific operational context rather than spending first 10-15 minutes asking basic research questions.

Calendly
n8n
Claude API
Google Maps

Why Restaurant Tech Companies Hire Me

Six years at Toast, Dutchie, Shipday, and GigFinesse taught me that selling to restaurants is fundamentally different than typical SaaS sales

Buyer Behavior

Restaurant operators are busy, skeptical of tech, and need ROI proven in dollars, not percentages. They make decisions during rare quiet moments and need solutions that work immediately.

Sales Cycle

Longer evaluation periods, multiple stakeholder involvement (owner, manager, accountant), and operational disruption concerns. Every new system means retraining staff during service.

Data Requirements

POS systems, delivery platform dependencies, labor cost structures, operational maturity indicators. Generic B2B data enrichment doesn't capture what matters to restaurants.

Competitive Landscape

Crowded market, strong incumbent systems, high switching costs. Restaurant operators have seen hundreds of "game-changing" solutions. Credibility is everything.

The revenue infrastructure I build accounts for these realities. My lead enrichment systems pull restaurant-specific data. My ROI calculators speak the language of food cost and labor efficiency. My upsell automation understands seasonal buying patterns in hospitality.

If you're a Series A-B restaurant tech company, I don't need to learn your market. I've been selling into it for six years.

Services

I help revenue teams build the infrastructure they're missing

RevOps Audit

I'll assess your current GTM infrastructure, identify bottlenecks, and deliver a prioritized roadmap for what to build first.

Includes:

  • Current state assessment
  • Data flow analysis
  • Bottleneck identification
  • Implementation roadmap with effort estimates
  • Tool stack recommendations

Timeline: 1-2 weeks

What makes this different: I've carried quota while building these systems for restaurant tech companies. I know what actually works when selling to restaurant operators: which data points close deals, which integrations matter, and how to structure workflows that account for busy operators who won't respond to typical SaaS outreach.

If you're selling to restaurants, I've been in your reps' shoes for six years. Contact me to discuss your specific needs and get a scope estimate.

Contact

Let's talk about what you're building

Schedule a Call

30-minute discovery call to discuss your needs

Book on Calendly
Book a Call