Sales Operations
I build the systems behind sales teams. CRM architecture, automations, reporting, and the custom tools that don't come out of the box. If it doesn't exist yet, I build it.
Remote. Available for full-time or project work.
jt@jtylerray.com · jtylerray.com/resume
Most of what I build replaces one of two things: nothing at all, or something that quietly stopped working. Reps who don't log their calls. Dispositions that never sync. Leads that sit for hours before anyone touches them. A tag list nobody has pruned in two years. The work usually starts by making the invisible visible, then making sure it stays that way without anyone babysitting it.
I work across the whole stack rather than inside a single tool. The problem decides the tool, not the other way around — sometimes that's a CRM rebuild, sometimes an automation, sometimes a dashboard, and sometimes a piece of custom software that didn't exist until it needed to.
When the no-code tools run out of road, I write code. That's the line most operators can't cross, and it's where the durable systems get built — the ones that hold up under real volume instead of breaking the first busy week.
I'm not a coach or a sales trainer — I build the systems the people doing that job run on.
GoHighLevel, HubSpot
Zapier, Make, n8n, custom code
Airtable, Supabase, BigQuery, Looker Studio
Slack, Calendly
JavaScript, Claude & Claude Code, most documented APIs
The specific tools matter less than the fact that I learn whatever the company already runs.
High-ticket coaching offers across:
A working sample of what I've built, grouped by what it does.
Remote. Available for full-time or project work.