How we work
Diagnose. Architect. Build. Operate.
The same four steps on every engagement, whether it is a two week audit or a four month implementation. The order matters more than the labels: nothing gets configured before the architecture is written down, and nothing is called finished before somebody checks it is being used.
A named specialist replies within one working day. No sales sequence.
How does Muloo run a HubSpot project?
Four steps. Diagnose the portal, process and data before proposing anything. Architect the data model and integrations in writing, signed off before build. Build in stages with a working portal at each checkpoint. Operate it, with training, governance and a thirty-day adoption review against real usage.
The four steps
What actually happens, in order.
-
01
Diagnose
We look at the portal, the process and the data before proposing anything. Half of what people ask us for turns out to be a symptom of something else, and finding that out costs two weeks rather than two months.
-
02
Architect
The data model, integration map and automation design get written down and signed off before a single property is created. This is the step most builds skip, and it is why their reporting breaks a year later.
-
03
Build
Delivered in stages with a working portal at the end of each one, sequenced around your sales cycle. Nothing is a big-bang cutover, and there is a rollback point before anything risky.
-
04
Operate
Training, documentation and a governance model, then a thirty-day adoption review against real usage data. We fix what people are avoiding rather than reminding them to use it.
What is different about it
Four things we do that most do not.
None of these are clever. They are just the parts that get dropped when a project runs late.
-
01
A named engineer, not an account manager
You talk to the person doing the work. Nobody relays your question to a delivery team and relays an answer back three days later with the detail sanded off.
-
02
Architecture before configuration
A written design you approve first. It is slower for a fortnight and cheaper for years, because the expensive failures in HubSpot are structural, not cosmetic.
-
03
Measured on adoption, not delivery
A build nobody uses is a failed build, whatever the project plan says. We review real usage at thirty days and remove whatever is not earning its keep.
-
04
AI-first internally
We use our own tooling on every engagement, which is why builds move faster and depend less on any one consultant. You get the benefit without buying the tooling.
Free, and yours to keep
Find out what is actually wrong with your portal.
An automated audit of data quality, workflows, unused licences and automation nobody owns. The findings are yours whether you engage us or not.
- Portal health
- Workflow audit
- Data hygiene
10,000 credits buys one of
- HubSpot-sent emails
- 666
- Workflow actions
- 3,333
- AI service conversations
- 200
- AI content pieces
- 10
Who you deal with
A small team, deliberately.
You get the person who did the work, not a summary of it.
-
Jarrud van der Merwe on LinkedIn, opens in a new tab
Lead architect and engineer. Sales engineer and HubSpot specialist who scopes the work and stays on it
-
Grant Watt on LinkedIn, opens in a new tab
Client director. Runs the programme office and delivery operations
-
Jhani Coetzee on LinkedIn, opens in a new tab
Client director. Owns the relationship and keeps the work pointed at the outcome
-
Candice Lloyd on LinkedIn, opens in a new tab
HubSpot delivery expert. Builds it properly and hands it over documented
What it looks like in practice
What changed, and what it was worth.
-
Build · integrations
Rescued and rebuilt across 20+ product lines
A fragmented portal consolidated into one data model with documented integrations and a pipeline people use.
EPI-USE
-
Grow · RevOps
An underused portal becomes a growth platform
Cleaned the CRM, rebuilt lifecycle stages and gave leadership a forecast they could defend.
W.consulting
-
Build · website
A client portal and a theme-based website
Migrated off a legacy stack onto HubSpot with a modular theme the marketing team runs themselves.
Phillips Law
Already know what you need?
Seen enough? Book 45 minutes.
Tell us what is going on and we come to the call having already looked at it. If we are not the right fit, we say so.
Before you ask
The questions people ask about working with us.
How long does the diagnose step take?
Two to three weeks for most portals, and it is mostly read-only access plus three conversations. If you have not had the free audit yet, start there, because it is the first part of this anyway.
Can we skip straight to the build?
You can, and we will say so if the architecture is genuinely clear. What we will not do is configure a process that two teams have not agreed on, because that cost is paid later with interest.
What happens after go-live?
Thirty days of fixes are included, then either your team runs it with the documentation and governance model, or we run it on a retainer. Both are fine. Handing over an undocumented portal is not.
Do you work with our internal team?
Often, and it is the best version of this. They keep the context and we bring the pattern library and the capacity.
What if we already have an agency?
Then an independent architecture review is usually the right first step. It is written so you can take it to them without us in the room, and plenty of reviews end with us saying the current setup is fine.
Talk to us
Tell us what is going on.
One form, one reply, from the person who would do the work. No sequence, no SDR, no chasing.
- A reply within one working day
- From a dedicated specialist, not an account manager
- No sales sequence unless you ask for one
Rather pick a time now?
Book a callProtected by reCAPTCHA. We do not sell, share or rent your details.