Operations architect · Sydney · US East Coast hours
Set out before you build.
I design the system a service business runs on, then build it. Usually HubSpot, because that is where you already are.
Eight things I built. Move them around.
01 / The idea
Set out before you build
On a construction site the set-out comes first. Get it wrong and every wall after it is wrong.
You do not patch that. You demolish.
A surveyor marks where every footing, wall and service goes before anything is built. It is slow, it produces nothing you can photograph, and it is the most consequential day on the job.
Your CRM is the same. The data model, the pipelines, the definition of a qualified lead. That is the set-out. Almost nobody does it. Everybody builds on top of it anyway.
What I find instead, 121 times over: someone needed it live by Monday, so it went live by Monday. Then the workarounds started. Then the workarounds became the process. Then the process became how we do things here.
Nobody decided any of it. It accumulated. That is the thing I am hired to undo.
02 / The work
The index
Everything on the table above, in the order I would show it to you. Open any one of them.
Client work
3 entries
Built for myself
5 entries
03 / Engagements
Four ways in
Architecture first, everything else follows. Most people start at the top of this list because it is the only honest way to find out what they actually need.
The Set-Out
Portal audit and architecture review
A scored read on your data model, pipelines, automation and adoption, with a prioritised roadmap. Two or three quick wins built while I am in there, not just written into a document.
You get the scorecard whether or not you hire me for anything after it.
The Build
Implementation and onboarding
A new portal, or a real one after a rushed setup. Designed as one system: objects, properties, pipelines, automation and reporting that agree with each other.
The Clean-Out
Optimisation and remediation
Duplicates, dead properties, workflows nobody remembers building. Cleared out, then rebuilt so it stays clean without anyone policing it.
Standing By
Ongoing support retainer
A few hours a month instead of a full-time hire. Most portals need architecture once, then a steady hand.
04 / About
About
I have onboarded, implemented and optimised 121 HubSpot portals over two years. That number is the point.
My credibility is volume and pattern recognition, not theory. The same mistakes repeat across industries, and I know which ones cost you deals. That is a claim only someone who has worked across a lot of industries can make.
The businesses I am useful to are not defined by their sector. They are defined by how they sell. Deals take weeks or months. They are won on trust and follow-through, not price. A small number of important deals rather than a large number of small ones. Somebody has to hold context across a timeline long enough for people to forget things.
That pattern turns up in construction and trades, where I came up and where I can skip the explaining. It turns up just as often in professional services, engineering, education, healthcare and manufacturing. A CRM should protect the way you win work. Most are built as though that does not matter.
The personal projects are not a side hustle. They are how I stay sharp. I learn a tool by building something real and slightly excessive with it, then bring what survives into client work. Retrieval design, automated QA and browser automation all arrived that way.
- Based
- Sydney, Australia
- Hours
- US East Coast, from a 5am window
- Platform
- HubSpot, every hub
- Also
- Cloudflare Workers, Playwright, retrieval systems
- Works with
- Long sales cycles won on trust, in any sector
- Portals
- 121 over two years
- semih@asaroglu.com
- semih-asaroglu
05 / Start here
15 minutes. No pitch. Clarity either way.
Tell me what is broken and I will tell you what I would fix first, whether you hire me or not. Worst case you leave with a clearer read on your portal than you have today.