Drivant  /  How I work

How I workBy Luis GarcíaUpdated October 2026

One operator, written decisions, 21 days.

How the build runs, what you receive, what I need from you, and who you'd be working with.

01

Who does the work.

I'm Luis García. I have about four years in GTM engineering and RevOps. I have built GTM systems for B2B SaaS, fintech, HR-tech and staffing companies, from early-stage startups to established teams: prospecting systems, sales pipelines, CRM architecture and custom fields, and outbound campaigns.

Drivant is founder-led on purpose. The person on the first call is the person inside your CRM. There are no account managers and no handoffs to juniors.

02

The 21 days.

Days 1–2

Audit

Access agreed in writing, full export, then the checks listed on each problem page.

Week 1

Data foundation

Duplicate matching, merge rules, checks wherever new records get created.

Week 2

Pipeline truth

Signed definitions, stamped stage dates, one leadership dashboard.

Week 3

Lead engine

Custom signals, fit model, sequences on warmed inboxes.

Day 21

Handoff

Operating guide, decision log, access removed if you don't continue.

03

What you receive.

Decision logEvery rule and definition we chose, who signed it and why, in plain language.
Weekly written summaryWhat changed, what's next, and anything that needs your sign-off.
Operating guideHow to keep the data clean, read the reports and run the engine.
Everything in your accountsCRM changes, signal setup, lists and sequences live in accounts in your company's name.
04

What I need from you.

  1. One person who knows how you sell, about an hour a week
  2. A CRM user with permissions we agree in writing, plus a sandbox if you have one
  3. Quick written sign-offs on definitions and rules
  4. A decision on day 21: run it yourselves, or keep me on the monthly retainer

If a change isn't written down and signed, it doesn't ship.

Luis García

Want to see how this would run on your CRM?

Get the Pipeline Leak Teardownor book 20 minutes