GTM Systems Builder · San Francisco Bay Area

I turn GTM operations into pipeline.

Sales, RevOps, automation, and software in one seat. I carry a quota by day and ship the systems underneath it at night.

UC Santa Barbara · Salesforce · HubSpot · APIs · Claude Code

Daniel Gonzalez
Daniel GonzalezUCSB ’26 · LinkedIn
Proof, not promises

Numbers I can back up.

0Products shippedAcross insurance, home services, mortgage, legal, and education.
0Live platforms right nowDeployed and reachable, not screenshots.
0Automated tests behind themUnit, database, and end-to-end coverage.
0Industries shipped intoEach one has its own compliance and trust rules.

Every number on this page is real and verifiable. Ask me about any of them.

★ Start here

How a GTM machine is actually wired.

Two teardowns I wrote and built. The workflows that run without anyone touching them, and what each of 35 connectors actually does. Tool names are easy. This is the machine.

Open the teardown
GTM workflow diagram: scored list routed to Outreach, Instantly, HeyReach and Nooks
Selected work

Insurance, home services, mortgage, legal, and education. Same job every time: find what is slowing the business down, build the system that fixes it, then put it in front of the people doing the work.

Twelve products shipped. See everything →

What I bring

What I bring.

01

Revenue Operations

Salesforce · HubSpot · pipeline management · CRM architecture · attribution. I operate these on a real quota every day.

02

GTM Engineering

APIs · workflow automation · data pipelines · integrations · Claude Code. I build around the stack, not inside its limits.

03

Growth

Intent signals · segmentation · automated outreach · lead routing · experimentation.

04

Commercial

Sales · discovery · pipeline generation · unit economics · ROI. Licensed CA P&C and Life & Health.

How I think

Systems as investments, not automation projects.

01

Instrument before automating

If you cannot explain where a lead came from, why it was prioritized, and what happened next, automation just makes the confusion faster.

So I log every state change with a timestamp and an actor, and I separate our delay from the customer's before I optimize anything.
02

Compliance as schema

Consent, suppression, and sequence caps live in the database, not in a checklist. The system physically cannot send a bad message.

Every send writes to an append-only log first, and Postgres triggers reject anything that breaks a rule. The app layer is just a client.
03

Economics decide

Acquisition cost, conversion, deal value, scale, feedback. A system only matters if the numbers work.

If more spend does not produce proportionally more revenue, the automation is decoration. I would rather kill it than ship it.

Active brains win, and they bring the change companies need to grow.

What I want next: a GTM team with real scale behind it. Every system on this page I specified, built, and shipped end to end. Put me against a bigger surface and harder problems and I will do the same thing faster, with people who make the work better.

Tell me straight

What did I miss?

If you hire for GTM, you see this page from an angle I cannot. I’d love to hear from you.

Feedback is how I get better. If you see something wrong, let me know.

Sends straight to my inbox. Nothing is stored on this page.

San Francisco Bay Area

I look forward to connecting.

Open to GTM Engineer, Growth Engineer, and Revenue Operations roles in the Bay Area. You do not need an open role to reach out. I am happy to walk through any of these systems live.

Email me LinkedIn ↗ Resume →