Systems that shipped. Numbers that held.

An internal AI platform,
allowed to touch the CRM safely.

The tangle

An internally engineered AI workbench with connectors into Slack, email, and HubSpot through an OAuth app. The question nobody had verified: when the AI acts on a user's behalf, does it inherit that user's permissions, or the app's? Nobody wanted to learn the answer in production.

What got wired

• Deterministic regression suite: user personas (view-only, team-scoped, admin) × read and write operations, tested against what each persona can actually do in the UI
• Proved the critical mismatch: view-only users could complete writes through the app, because OAuth scopes authorize the application at the portal level while user permissions govern the UI. Escalated with reproducible evidence to HubSpot solutions architecture
• Diagnosed the token layer underneath: a shared app token acts regardless of who is asking, so permission parity requires per-user, session-initiated tokens with minimized scopes
• The permission-parity suite now runs as the regression gate as the platform adds connectors

Fifteen hours of routing latency,
engineered down to six minutes.

The tangle

Two CRMs that disagreed with each other, duplicate accounts everywhere, and a patchwork of legacy workflow automation stacked over years. Inherited architecture → degraded performance → 15-hour routing latency, with high-intent trial signups sitting unowned at the end of it.

What got wired

• Full dedupe across Salesforce + HubSpot — accounts, contacts, hierarchies
• Lead grading hierarchy (fit + intent) computed on entry, synced to CRM in seconds
• Round-robin routing to reps with re-enrollment — nothing falls through twice
• AI agent workflows (Claude) running the dedupe, enrichment, and grading passes, governed with dry runs, backups, and human review on every batch
• Governed deployments: changes built and QA'd in sandbox with Claude Code, shipped through peer reviewed pull requests and automated deploy tooling

An assessment funnel,
wired end to end.

The tangle

A founder launching a scored self-assessment as her growth engine — with no marketing infrastructure behind it. Results needed to segment into three buyer paths, each with its own branched nurture, before a hard launch date.

What got wired

• Assessment platform → HubSpot integration: field mapping, exact-value contracts, QA'd with a full test cohort
• 22 marketing emails + 4 branched journeys segmented by role, timing, and readiness
• Compliance, sending domain, and handover docs — the team runs it without me

Buyer intent, routed to
the rep the same day.

The tangle

Nine-figure pipeline concentrated in a handful of enterprise accounts — and buying-committee research happening on the website that nobody saw until the next QBR. Intent data existed; it just never reached a human in time to act.

What got wired

• Intent monitoring scoped to the accounts behind the top 20 open deals
• Signal-triggered workflow: intent spike on an open-deal account → same-day internal alert to the deal owner
• ABM target structure built for the expansion motion behind it

A CRM the leadership team
could finally forecast from.

The tangle

A growing MSSP whose CRM had drifted: pipeline stages that didn't match how deals actually closed, lifecycle data years stale, and no automation carrying deals forward — every report started with an apology.

What got wired

• Sales pipeline redesigned in place — no downtime, no lost history
• 13 live workflows: stage hygiene, stuck-deal alerts, closed-won handoff, lifecycle sync
• Lifecycle cleanup across the whole customer base + forecasting enabled for leadership