Joseph D.

I build the revenue systems that sit between marketing, sales and product data: CRM architecture, lead routing, enrichment, scoring, workflow automation, and the API integrations native connectors do not reach. The test I hold myself to is whether the system still runs after I leave. At 1up.ai, Ignyte, Cortex and Anchor Browser, those teams still operate what I built, in house. CERTIFICATIONS Salesforce Certified Platform Administrator HubSpot Revenue Operations Administrator Clay Automated Outbound Certification WHAT I HAVE SHIPPED Cut lead response from 48 hours to same hour on 500+ leads a week, by assigning ownership at record creation instead of negotiating it afterward. Reduced lead-to-opportunity time from 14 days to 4 days for a $5M ARR SaaS company. Built enrichment pipelines processing 10,000+ leads a month, still running. Built a 63,000 record enriched contact base as the data layer a go-to-market motion ran on, with Salesforce as the system of record. Brought one client's CRM health to 82% with a mapped plan to 92%. WHERE I WORK HubSpot and Salesforce RevOps. Four years hands-on in HubSpot: lifecycle stages, pipeline and object architecture, property and data model design, workflow automation, lead scoring and routing, list logic, reporting. Salesforce operations including SOAP authentication and sync to surrounding systems. Lead scoring, enrichment and routing. Pipelines that decide who enters a sequence and when, with dedupe and exclusion tables, retry logic on every API write, and a human review checkpoint before any record is touched. Clay. End to end implementations: signal-stacked prospecting, waterfall enrichment, scoring, territory routing, CRM sync. Outbound infrastructure. Cold email deliverability, sending domain separation, SPF, DKIM and DMARC, warm-up and suppression. Apollo and Instantly for sequences, Sendblue and FrontSpin for SMS. AI agents and workflow automation. Custom agents built with Claude Code for GTM workflows, plus Zapier, Make and n8n where native connectors fall short. API and application development. React, Node.js and Python for internal tools, integrations and customer-facing applications. HOW I WORK I explain what I am building while I build it, on a shared screen, with whoever is going to own it. A system nobody on your team can explain is a system nobody will maintain. What you get at the end is a working build plus written reasoning for each decision, so the next person is not guessing. Based in Louisiana, US Central time, covering Eastern business hours. Available up to 40 hours a week. Happy to spend 30 minutes looking at where your revenue systems leak before you commit to anything. Clay Works of Art