Revenue Operations · GTM Systems · AI Automation

I turn messy GTM work into working systems.

CRM, sales process, enablement, AI workflows, dashboards, and field adoption — built for cleaner data, clearer handoffs, and tools people actually use.

Revenue Operations
GTM Systems
Sales Enablement
AI Workflow / Sales Ops

Proof points

A few simple signals that show the kind of work I have done and the scale I have worked around.

400+ sellers supported through a national Salesforce FSC rollout and sales process launch.
$2B division supported through Salesforce rollout, field enablement, and process adoption.
250K visits generated by a sales technology support hub I created and scaled.
0→1 HubSpot CRM built from historical Gmail relationship data as a solo builder.

What I build

I am strongest where the work is messy, cross-functional, and close to how revenue teams operate every day.

Revenue systems

CRM structure, pipeline stages, handoffs, dashboards, data hygiene, and operating routines.

AI workflows

Prompt standards, meeting prep, follow-up, lead routing, and manager visibility.

Enablement that sticks

Training, playbooks, manager routines, support hubs, and field feedback loops.

Messy data cleanup

Turning inboxes, CRM records, notes, and relationship history into usable systems.

Where I fit your team

Pick the problem closest to what you are hiring for. This shows where I would start, what I would build first, what I would measure, and why my background fits.

Where I would start
Cleaner CRM data

Cleaner CRM data

A practical plan for turning scattered records into a system the team can trust.

    Short case studies

    No long story. Just the problem, what I did, and what changed.

    Salesforce rollout and sales process

    Scale: 400+ sellers Focus: rollout + sustainment
    Problem

    Large sales team moving into a new Salesforce environment with new process, new routines, and adoption risk.

    What I did

    In-person and virtual training, playbooks, manager routines, dashboards, and field support.

    Outcome

    Successful rollout and sustainment across 400+ sellers.

    AI workflow adoption

    Focus: practical sales use cases Teams: Sales Ops · Product · Data
    Problem

    Leaders needed practical AI workflows tied to real sales work, not scattered experiments.

    What I did

    Defined use cases, prompt standards, guardrails, feedback loops, and Salesforce-connected workflow needs.

    Outcome

    Practical workflows for prep, follow-up, prioritization, retention, manager visibility, and daily execution.

    Q Stories CRM build

    Build type: solo 0→1 HubSpot CRM Source: Gmail relationship data
    Problem

    Years of useful relationship history lived in Gmail, but there was no working CRM to manage it.

    What I did

    Built a HubSpot CRM from scratch, cleaned contacts and companies, removed duplicates, and organized notes and opportunities.

    Outcome

    Turned old email history into a usable system for relationship tracking, follow-up, and pipeline.

    Best-fit work

    I fit roles where the company needs someone who can sit between leadership, sales, operations, data, product, and the field — then turn messy work into a clear operating rhythm.

    Revenue Operations / GTM Systems

    Owning the process, CRM structure, dashboards, stage discipline, handoffs, and operating cadence behind a revenue team.

    Sales Enablement / Field Adoption

    Building the training, playbooks, manager routines, and support needed to make process and technology stick.

    AI Workflow / Sales Ops

    Taking practical AI ideas from rough concept to usable workflows with guardrails, testing, and field feedback.

    CRM Builder / Systems Operator

    Cleaning up messy data, building usable CRM workflows, and creating reporting that helps people act.

    The short version

    I know how to take scattered information, unclear process, and uneven adoption and turn it into a working revenue system. I am hands-on, comfortable with ambiguity, and strong at the point where business needs become tools, workflows, training, and reporting.