Jonathan S.

Most HubSpot work stalls in the same place: the drag-and-drop editor runs out of road, and there's no engineer around to take it further. That's usually when I get the call. I'm a software engineer who works in HubSpot — not a portal configurator. I write HubL, JavaScript, and Python. I build custom objects, real API integrations, and dynamic sites off HubDB. And when HubSpot genuinely can't do something, I build the thing next to it that can — one client brought me in to stand up an application portal for their AI startup from scratch in Django. That wasn't a HubSpot job at all. I was just the person who could do it. Where I usually end up: - CRM and lifecycle process — lead, deal, onboarding, and support pipelines built properly and automated, not duct-taped together - Integrations and automation — Zapier, Make, n8n, or custom API work for when the no-code tools hit their ceiling - AI wired into the actual workflow — the model doing real work where your data already lives, not a chatbot bolted onto the side - Portal audits and cleanup — you inherited a mess from the last agency and need someone to find what's actually running - Custom builds — Python and Next.js apps that pick up where HubSpot leaves off A lot of my work is repeat work. People keep me on the bench and come back for the second and third project — that tells you more than any single review does. How I operate: you tell me what's broken or what you're trying to build, and I tell you what it'll actually take — including when the answer is "that's simpler than you think" or "HubSpot is the wrong tool for this." I'd rather lose the contract than sell you six weeks of work you don't need. Send me a message or book a consultation. Bring specifics.