conduithq.it.com

Information should flow to the right people.
I build the systems that make that happen.

I build revenue systems, automation pipelines, and tools that move information to the right people — fast.

The story behind Conduit

I grew up in New Orleans. At some point I got tired of waiting for life to come to me, so I packed up and moved to the Bay Area — first one in my circle to do it. My whole family eventually followed. That's probably the most Troy thing I've ever done.

I graduated from San Jose State in 2020, right in the middle of COVID. No ceremony, no real transition — just suddenly out in the world during the strangest possible moment. My degree was in Organizational Studies, not CS or engineering. I learned the technical side by building things until they worked. I figured out the rest as I went.

The instinct that drives my work — noticing what's broken and fixing it — didn't start with any system or org. It started with me. I turned it on myself first. Then I realized I could point it at anything, and it worked the same way. I spent months charting live basketball games for a data analytics firm — tracking plays, verifying data, catching errors in real time. Then I built Courtside. That's usually how it goes.

The midnight builds aren't about hustle culture. I'm not trying to impress anyone with my hours. I'm building toward something real — a stable life for me and my wife. A garden. Farmer's market Saturdays. Barbecue competitions on the weekends. Enough freedom that work is something I choose, not something I have to do.

Conduit is the vehicle. The name means something — a strong, powerful connection between two points. Every system I ship, every tool I build, every problem I solve before anyone asks — it's all pointed at the same thing.

From New Orleans · Based in the Bay Area

Revenue systems that stick

Selected work from client engagements at CModel Data, Inc

Case Study 01

Building a Revenue System from the Foundation Up

Salesforce HubSpot Flows RevOps
First since 2014
Successful lead process
90 days
Built in full
5 flows
Coordinated & live

Walked into an org untouched for years. No lead process, no attribution, no routing. Built the full system from scratch — five flows, HubSpot integration, contact attribution, engagement scoring, and a 200+ entry change log. Nobody asked for most of it.

Read Case Study

Case Study 02

Listening to a Non-Technical Stakeholder and Building Exactly What They Described

HubSpot Calendly Riverside Slack
65.91%
Open rate
30.68%
Click-through rate
8 flows
Coordinated workflows

Started as a broken email sequence. Diagnosed the root cause, expanded scope after spotting a larger opportunity, and built an 8-workflow automation system across four platforms. Lead gen brought in-house. Outsourced vendor replaced.

Read Case Study

Case Study 03

The Sales Team Never Changed Their Behavior. The Data Structure Changed Around Them.

Salesforce Flow Automation Change Management RevOps
Zero
Rep behavior change required
2 weeks
Silent validation before surfacing
3 fields
Auto-calculating in real time

Built a bridge flow that mapped the existing Amount field to a new data structure automatically on every update. Reps kept doing exactly what they'd always done. The new structure populated silently around them. When they finally saw it, the section header read "Auto Populates — For Open Stages Only." It felt like a feature.

Read Case Study

Case Study 04

The Instructions Were Flawed. I Built It Anyway. Then I Fixed It.

Salesforce Flow Architecture Dashboard Build RevOps
45.17s
Governor limit — documented
7
Dashboards delivered
42
Reports built and configured

Built a loop-over-loop flow exactly as instructed. It hit Salesforce's Apex CPU governor limit at 45.17 seconds — every time. Flagged it. No response. So I stopped forcing a broken solution, put quarterly quota directly on the User object — unconventional, nobody does this — and built a projected amount formula field instead. Seven dashboards. 42 reports. No developer required.

Read Case Study

Case Study 05

The CRM Had the Contacts. It Didn't Know Which Ones Were Worth Calling. Now It Does.

Python HubSpot Claude API Serper RevOps
3
Outputs written per record
2
Pipelines — EDO + podcast
4
Signal categories scored

CModel had hundreds of EDOs in HubSpot with no signal layer — every record looked the same. Built an end-to-end Python pipeline: HubSpot CRM list in, Serper web signal enrichment, Claude ICP scoring, automated write-back. Every scored record now has a 0–100 fit score, a lane classification, a rep-ready signal note, and a personalized outreach hook. No manual research required.

Read Case Study

Case Study 06

No Territory Object. No Regions. No Rep Assignments. I Built the Structure — Then Cleaned Up What Was Under It.

Salesforce Custom Objects Territory Management RevOps
6
Regions defined and AE-mapped
4
Custom fields on Territory object
Zero
Duplicate assignments remaining

No territory structure existed in Salesforce — no object, no regions, no rep assignments. Built a custom Territory object, defined six regions, mapped every AE, audited account ownership against the new structure, and ran a bulk ownership transfer. Caught two edge cases mid-audit: a duplicate state in two reps' lists and an unassigned inside-sales rep. Both resolved. Fully governed, validated, user-accepted.

Read Case Study

Case Study 07

The ROI Story Was Already There. She Was Looking for It in the Wrong System.

HubSpot Salesforce Marketing Attribution Stakeholder Alignment
1
Reframe — HubSpot as marketing-quality layer
3
Deliverables — ROI report, sync decision, identity layer
Zero
Formal training sessions — built through the work

The Head of Marketing was chasing deal-close data in HubSpot — a system that was never built to give it to her. Reframed HubSpot as the marketing-quality layer and Salesforce as the deal layer, then built the tooling to match: a marketing ROI report, a formal sync-direction decision with Salesforce as source of truth, and a HubSpot identity layer with full source attribution. Built over time through the working relationship, not a training session.

Read Case Study

Case Study 08

Diagnosing a Dead-End Integration: From "Which Reps Are Tracked?" to a Root-Cause Fix

Salesforce Einstein Activity Capture Microsoft Exchange Root-Cause Analysis
2
Root causes diagnosed — license/config, then dead auth method
11
Users — first org-wide working email/calendar sync
Zero
Rep behavior change required — fix was infrastructure, not adoption

Leadership wanted to know if reps' emails were being consistently captured in Salesforce — a months-old, unresolved request. Diagnosed the wrong tool being measured, then found Einstein Activity Capture had 7 licenses and 0 configuration, all tied to employees who'd left years earlier. Fixed the licensing — then it broke again a day later, this time from a Microsoft-retired auth method underneath. Migrated to the current supported auth, coordinated the Microsoft-side consent, and confirmed a live, working sync across all 11 current users.

Read Case Study

Case Study 09

Four Systems, One Word: Untangling a Rollout Before It Confused Everyone

Salesforce Outreach Microsoft 365 Stakeholder Communication
4
Systems disambiguated — one word had been covering four different tools
1
Live customer email — personally verified before training anyone
Zero
Reported issues — first wave of rep sign-ups

With email capture finally working end to end, the project shifted to rollout — and hit a communication problem, not a technical one. Leadership had told a stakeholder an integration was "connected." It wasn't the one they meant — four separate systems had been getting called by the same word. Untangled all four, diagnosed the real license bottleneck, personally verified a live customer email before training anyone, and shipped individually tested, individually delivered instructions to each rep.

Read Case Study

Case Study 10

Solving the "Is This a New Customer?" Problem in Salesforce

Salesforce Flow HubSpot Data Architecture Lead Deduplication
2
Record-triggered flows — live in production
3
Sandbox test scenarios — before a single demo
Zero
False "Net New" results shipped — blank-email bug caught pre-production

Leads landed in Salesforce the same way whether the company was a total stranger or a five-year customer — nothing distinguished the two at creation. Built a Salesforce Flow that turns a lead's email domain into a verifiable match against every existing Account, routing real matches to a RevOps review queue and stamping everything else "Net New – Verified." Caught a blank-email edge case and an environment-specific queue ID, both before they could reach production.

Read Case Study
Salesforce Administration HubSpot Revenue Operations Salesforce Flow CRM Implementation Pipeline Management Marketing Automation Stakeholder Management AI Automation VS Code Claude Code Python Node.js

The Think Tank

Personal builds. Real problems. Built solo.

AI Content Pipeline

Snack Fax

AI Content Pipeline

Built a fully automated YouTube content pipeline. Scrapes trends, scores scripts against my content strategy, gates on human approval, generates voiceover, sources matching video clips from Pexels, and assembles the final video. Built for myself. Adopted by my employer. Growing channel with 1.5K weekly views.

Watch on YouTube

Full Stack App

Relocate

Full Stack App

A relocation planning app with real cost calculations, housing delta comparisons, peak season data, and an auto-generated 28-task moving checklist with timelines. Built because spreadsheets aren't good enough for a decision this big.

View Project

Scout Intelligence Tool

Courtside

Prospect Tracker Bias Mitigation

A full-featured basketball prospect tracker built for scouts who take accuracy seriously. 44 data fields, 11 evaluation sliders, analytics dashboard, CSV import/export, and printable scouting reports. The differentiator: a bias mitigation system most tools don't think about — blind eval mode hides player identity while scoring, a second-opinion engine flags high-discrepancy evals, and extreme scores require written justification before saving. Built because scouts have blind spots. This catches them.

View Project

More builds in progress. Deal Hunter coming soon.

Let's build something

Available for project-based Salesforce and RevOps engagements. Currently consulting at CModel.