Liam W.

I build HubSpot revenue systems for fast-scaling teams: a forecast you can stand behind when the board pushes on it, deals that don't quietly die, and reps who know what the next move is and why. 𝐃𝐨 𝐭𝐡𝐞𝐬𝐞 𝐬𝐨𝐮𝐧𝐝 𝐟𝐚𝐦𝐢𝐥𝐢𝐚𝐫? 1. "𝘞𝘦'𝘷𝘦 𝘨𝘰𝘵 𝘮𝘰𝘳𝘦 𝘴𝘪𝘨𝘯𝘢𝘭𝘴 𝘢𝘯𝘥 𝘪𝘯𝘵𝘦𝘯𝘵 𝘥𝘢𝘵𝘢 𝘵𝘩𝘢𝘯 𝘦𝘷𝘦𝘳, 𝘣𝘶𝘵 𝘵𝘩𝘦 𝘳𝘦𝘱𝘴 𝘥𝘰𝘯'𝘵 𝘬𝘯𝘰𝘸 𝘸𝘩𝘢𝘵 𝘵𝘰 𝘥𝘰 𝘸𝘪𝘵𝘩 𝘪𝘵." 2. "𝘐 𝘬𝘯𝘰𝘸 𝘦𝘹𝘢𝘤𝘵𝘭𝘺 𝘸𝘩𝘢𝘵 𝘨𝘰𝘰𝘥 𝘴𝘩𝘰𝘶𝘭𝘥 𝘭𝘰𝘰𝘬 𝘭𝘪𝘬𝘦. 𝘉𝘶𝘵 𝘸𝘩𝘢𝘵𝘦𝘷𝘦𝘳 𝘸𝘦 𝘥𝘰, 𝘪𝘵 𝘯𝘦𝘷𝘦𝘳 𝘭𝘰𝘰𝘬𝘴 𝘭𝘪𝘬𝘦 𝘵𝘩𝘢𝘵 𝘪𝘯 𝘱𝘳𝘢𝘤𝘵𝘪𝘤𝘦. 3. "𝘛𝘩𝘦 𝘯𝘶𝘮𝘣𝘦𝘳 𝘐 𝘱𝘳𝘦𝘴𝘦𝘯𝘵 𝘶𝘱𝘸𝘢𝘳𝘥 𝘢𝘯𝘥 𝘵𝘩𝘦 𝘱𝘪𝘱𝘦𝘭𝘪𝘯𝘦 𝘮𝘺 𝘳𝘦𝘱𝘴 𝘣𝘦𝘭𝘪𝘦𝘷𝘦 𝘪𝘯 𝘢𝘳𝘦 𝘵𝘸𝘰 𝘥𝘪𝘧𝘧𝘦𝘳𝘦𝘯𝘵 𝘯𝘶𝘮𝘣𝘦𝘳𝘴." 4. "𝘞𝘦'𝘷𝘦 𝘨𝘳𝘰𝘸𝘯 𝘧𝘢𝘴𝘵 𝘢𝘯𝘥 𝘏𝘶𝘣𝘚𝘱𝘰𝘵 𝘩𝘢𝘴𝘯'𝘵 𝘬𝘦𝘱𝘵 𝘶𝘱 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘤𝘰𝘮𝘱𝘢𝘯𝘺." The people I do my best work with are revenue and RevOps leaders who already know their craft. You're not blind to any of this. You've got ideas, possibly too many, and a stack full of tools promising more signals and more intent. The hard part is turning all of it into something a rep can act on, and that's the job I get hired to do. I sit at the table with commercial leaders, bring my own ideas, and then build it. 𝐖𝐡𝐚𝐭 𝐲𝐨𝐮 𝐠𝐞𝐭: ✅ Reporting and a forecast you can trust. Lifecycle, deal stages with real exit criteria, and numbers that hold up when someone senior leans on them. ✅ A pipeline where nothing slips silently. Risk you can actually see, stalled deals surfaced in real time, closed-lost put back to work. ✅ Reps with buyer context. You've probably already got signal and intent tools firing. The gap is what happens between a signal firing and a rep knowing what to do with it, and that gap is what I build. The system reads each signal in the context of the account and your sales process, works out whether it changes anything, and puts a recommended move on the record. Your reps open an account and see why it matters now and what to do about it. On the third one: I've built my own engine for this from the ground up. Collectors sweeping public sources for buying signals, an operational data store underneath, and a Claude reasoning layer working out what each signal means for a specific account before anything reaches a rep. For client builds, it runs on HubSpot and Clay at the core, custom code where it earns its place. I'm a builder and operator as much as a strategist. Took one client's 46,600-company universe from 3 buying signals to 184 in a single build.. The open-source half of my tooling is public on GitHub (𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗹𝗲 𝗼𝗻 𝗺𝘆 𝗽𝗿𝗼𝗳𝗶𝗹𝗲) and PyPI if you want to see how I work. 𝐈'𝐯𝐞 𝐰𝐨𝐫𝐤𝐞𝐝 𝐰𝐢𝐭𝐡 𝐨𝐯𝐞𝐫 60 𝐜𝐨𝐦𝐩𝐚𝐧𝐢𝐞𝐬. 𝐇𝐮𝐛𝐒𝐩𝐨𝐭 𝐏𝐚𝐫𝐭𝐧𝐞𝐫, 𝐚𝐧𝐝 𝐑𝐞𝐯𝐞𝐧𝐮𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐜𝐞𝐫𝐭𝐢𝐟𝐢𝐞𝐝 𝐛𝐲 𝐖𝐢𝐧𝐧𝐢𝐧𝐠 𝐛𝐲 𝐃𝐞𝐬𝐢𝐠𝐧. 𝐔𝐒 𝐰𝐨𝐫𝐤𝐢𝐧𝐠 𝐡𝐨𝐮𝐫𝐬. ❌ 𝙄'𝙢 𝙣𝙤𝙩 𝙮𝙤𝙪𝙧 𝙥𝙚𝙧𝙨𝙤𝙣 𝙞𝙛 𝙮𝙤𝙪'𝙧𝙚 on Salesforce or another CRM, and staying there (HubSpot is where I'm the expert), if you're B2C or primarily product-led (my work assumes a sales team working enterprise or mid-market deals), if you need day-to-day CRM admin. ❗𝗪𝗼𝗿𝘁𝗵 𝗸𝗻𝗼𝘄𝗶𝗻𝗴 𝗯𝗲𝗳𝗼𝗿𝗲 𝘆𝗼𝘂 𝘀𝗽𝗲𝗻𝗱 𝗮𝗻𝘆𝘁𝗵𝗶𝗻𝗴: 𝗜 𝗿𝘂𝗻 𝗮 𝗳𝗿𝗲𝗲 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 𝗟𝗲𝗮𝗸 𝗦𝗰𝗮𝗻 𝗼𝗻 𝘆𝗼𝘂𝗿 𝗛𝘂𝗯𝗦𝗽𝗼𝘁 ❗ It reads your portal and shows you, in your own numbers, where revenue is leaking. On one live portal it surfaced about $3.5M sitting in closed-lost with no recycling logic and 40% of deals carrying no value. Ten minutes of your time, and you keep the findings either way. ↪️ 𝗦𝘁𝗮𝗿𝘁 𝗵𝗲𝗿𝗲: send me the question you can't answer quickly, or the number nobody trusts. I'll come back with a straight read on what's probably behind it and what I'd build. - - - 🛠️ 𝗧𝗼𝗼𝗹𝘀 𝗮𝗻𝗱 𝘀𝗽𝗲𝗰𝗶𝗮𝗹𝗶𝘀𝗺𝘀: HubSpot CRM implementation, revenue operations, RevOps, deal pipeline architecture, lifecycle stage automation, lead routing, lead scoring,, CRM migration,, sales operations, marketing operations, workflow automation, dashboards and reporting, signal-based prospecting, buyer intent signals, target account list building, cold email deliverability, outbound systems, Clay, n8n, Make, Apollo, Instantly, Smartlead, Cargo, Supabase, revenue architecture, GTM engineering, B2B SaaS.