Mansoor Ali
RevOps & CRM Architect

I fix the CRM your team outgrew.

Somewhere in your company, someone keeps a spreadsheet open next to the CRM. That spreadsheet is a quiet vote of no confidence. I rebuild the CRM until it has nothing left to do: the pipeline stages, the data model under them, the automation that holds the line, and reporting a forecast can stand on. Real work inside HubSpot, not slides. Built with Clay, Claude Code, n8n, Supabase and HubSpot, and shown below with the wiring exposed.

SOURCE → ENRICH → DEDUP → PIPELINE → REPORT
Selected work

Five systems, with the wiring exposed.

01

Harness: a CRM cleanup pipeline, in build.

Point it at a messy CRM export and it hands back a clean one. The working slice runs five gates: intake and column mapping, enrichment review, dedup key selection, dedup pair review, then delivery. A person reviews enrichment and duplicate pairs before anything ships. Enrichment runs on Qwen2.5-72B, so you are not paying frontier prices to lowercase an email. Routing the hard calls to Claude or GPT-4o, and writing back to the CRM, are designed but not built yet.

Underneath sits the Brain, a shared enrichment cache on Supabase, so the pipeline reuses what it already knows instead of looking it up again every run. First real run: 99 rows in, 96 out, 2 duplicates collapsed, 1 junk row removed.

Claude CodeQwen2.5-72B Supabase
Five-gate buildFirst real run logged
In progressStatus page ↗
02

A revenue engine, designed end to end for HubSpot.

Where the data discipline meets strategy. A Bootprint cohort project built on Zinier's public footprint, not a client engagement. I designed a CRM operating model from a blank page: market sizing and segmentation, 7 lifecycle stages with entry and exit rules, a lead-source taxonomy that survives reporting, 7 deal stages with required fields, and 7 cross-team handoffs with SLAs, where pipeline usually leaks. Documented as a 20-page build handbook and a one-page revenue-engine blueprint, not a slide about one.

HubSpotRevOpsLifecycleData modeling
Revenue-engine blueprintBuild handbook
03

Clay to HubSpot sync, without the duplicates.

Paid client work. Enriched Clay records land in HubSpot without duplicates. It matches contacts on email and companies on domain before it writes, and it only updates records it created itself. Anything else is skipped and flagged for a person. Deployed to production on a 15-minute schedule. Client name withheld.

Clay HubSpot Claude Code Supabase Trigger.dev Vercel
04

Twenty thousand messy contacts, one clean list.

A client had the same company showing up three ways across job boards and no way to tell one real lead from a duplicate. I built the pipeline that fixes it. n8n scrapes the sources, Clay normalizes the names so "Avery Dennison Corporation" and "Avery Dennison" become one company, fuzzy matching kills the duplicates across roughly 20,000 contacts, then enrichment and outreach take over. Shipped, with recorded walkthroughs.

n8n Clay GPT-4o mini Apollo Instantly
Blueprint
Live
05

The same data discipline, rebuilt for construction.

Proof the skill travels outside SaaS. I took a construction firm's legacy accounting system and rebuilt it from scratch into a working web app with Claude Code. Messy real-world records, hard consistency rules, an industry that never gets this treatment. Same instincts as the CRM work, different vertical.

Claude CodeWeb appData modeling
Shipped
About

Fix the system. Trust the forecast.

A CRM is supposed to be the one place a company agrees on what is true. Most are not. Fields fight each other, two reports give two answers, and leadership quietly goes back to trusting their gut over the dashboard. I put the truth back, so the number on the screen is the number you would bet on.

I learned this where a wrong number is not a typo, it is a dry hole. Geophysics and Fortune 500 drilling data, where bad numbers cost real money. The same instinct runs my RevOps and CRM work now: lifecycle, pipeline, enrichment, dedup, and a sync a revenue team can actually trust. I also own a piece of Quadron Builders, where I rebuilt the accounting system from scratch. Clean systems travel.

The interesting frontier is not models that answer questions. It is systems that model, predict, and simulate. That is the direction I build toward.

No decks. I would rather show you a system that runs than talk about one. Open to full-time or freelance, remote, any timezone.

Get in touch

You should not have to double-check your own CRM.