About
One person. Real systems. Straight answers.
I'm Elliot Stenson. I build for one kind of client: SME manufacturers and industrial B2B — websites, trade and ERP-integrated portals, and AI visibility you can measure. Founder-led: the same person quotes you, builds it, and answers the phone months later. And you own everything I make.
The short version
Four years in UK B2B marketing. Then I moved to Melbourne to start something solo.
I've been doing digital marketing for four years — most of that spent building and managing websites for UK businesses in the Indutrade group. Industrial, technical, B2B work: machining, components, engineered products. The kind of marketing where you have to actually move pipeline, not just generate traffic.
That's the part that matters here. I've sat on the inside of manufacturing businesses long enough to know how the work actually gets won — a technical buyer with a spec, a drawing, a tolerance and a lead time, quietly building a shortlist before anyone picks up the phone. I don't need the tolerance explained to me, and I won't write your capabilities page like a brochure.
Studied Marketing as part of my BA at Sheffield. Moved to Melbourne in 2026 to start something solo — the part of the job I always liked best was the strategic + craft work directly with clients, not the agency layer above it.
The thing I keep coming back to: most manufacturers don't need a "digital transformation". They need to be findable and credible at the moment a buyer is shortlisting — capability content in the buyer's own language, a site fast and structured enough that Google and the AI assistants your buyers now ask first can actually read it, and where it earns its place, the systems work behind it: a trade portal, live stock, orders flowing into your ERP. That's what I build.
Deliberately one kind of client, too. A studio that works across cafés, clinics and machine shops learns none of them properly. Staying narrow is what makes the case studies, the ERP depth and the AI-visibility work compound instead of scatter.
The point of view
Three things worth being clear about up front.
The launch is the easy part.
The pattern I see most often in manufacturing: a site gets built, gets shipped, and then nobody touches it again. Two years later the design feels dated, the search rankings have plateaued, and the analytics nobody opens are showing traffic that never enquired. The hard part isn't the build — it's making the site earn its price tag over the 18 months of enquiries that follow.
A website without a marketing plan is decoration.
Websites get framed as deliverables, but they're really infrastructure for a marketing programme. If the programme doesn't exist, the site can be beautifully made and still produce nothing. Plenty of manufacturers have a good-looking site and no idea which pages a buyer actually reads before enquiring. I start with the plan — who your buyers are and how they shortlist — and build the site to serve it, rather than the other way around.
Transparent pricing is a feature, not a risk.
A lot of agencies hide pricing behind a discovery call. The argument for that is reasonable — it lets the conversation focus on fit before money. The trade-off is that you can't self-qualify before booking. So the bands are published: rebuilds from A$8k, retainers by level, portal and ERP work quoted to scope. What I won't do is put a calculator on it and pretend a range that runs from A$8k to well past A$100k can be settled by a form — that isn't transparency, it's a guess with a confident font. Bands in the open, then a firm number once I understand the job.
How I work
Modern, fast, low-maintenance.
The exact platforms and tools vary depending on the project — we land on the right fit during discovery. The principles below apply to every build I do.
Performance-first foundation
Modern static frameworks where the site doesn't need a CMS dashboard. Lighthouse 95+ on mobile as a measurable baseline, not a marketing claim.
Commerce and ERP where it earns its place
When you're genuinely selling or taking trade orders online, that's a systems job — NetSuite, Global Shop or Epicor connected to the site so stock, contract pricing and orders stay in sync. Not a plugin bolted onto a brochure.
Found by Google and AI from day one
Schema markup, clean structure, analytics and Search Console baked into the build — so the assistants your buyers ask first can read what you actually make, rather than guessing.
Capability content, not brochure copy
A page per real capability — process, material, tolerance, application — written in the buyer's terms, and an authoring approach matched to how you want to maintain it.
Measured, not claimed
Proper rank tracking, plus AI visibility measured with my own tool, Periscope — so we know what's actually moving rather than guessing.
Reporting people will actually read
Monthly reports that summarise what's working, what's not, and one specific recommendation for the coming month — not a 40-page PDF nobody opens.
Where I'm probably not the right fit
Honest filter, not false modesty.
A few situations where another setup would serve you better than I would. Saying so up front saves us both an hour.
Businesses outside manufacturing and industrial B2B
This is the deliberate one. Cafés, clinics, retail, generic small business — someone else will serve you better and cheaper. Everything here is built around one buyer: the technical person specifying and shortlisting suppliers.
Migrations off a working platform
If your current site is doing its job — even on a platform I wouldn't pick from scratch — my view is don't migrate for the sake of migration. The lift has to clearly outweigh the disruption.
Enterprise platform replatforms
I'm a solo operation. If the project needs six months, a Jira board and a five-person team, a larger agency is the right home for it.
Marketplaces with multiple sellers
Out of scope. Happy to refer to specialists who do this work.
Default AI chatbots, intrusive popups, gamified quizzes
I'll usually push back on these. On a technical B2B site the conversion lift rarely justifies the cost to trust and performance — an engineer looking for a tolerance does not want a chat bubble. Not a hard rule; we'll talk it through in discovery if your situation genuinely calls for one.
Budgets under about A$8k
Not a judgement — there are decent template-based options that deliver a working site well below what I can. A rebuild here starts around A$8k because of the capability content and search work underneath it. If the budget isn't there yet, go template, and talk to me when the site needs to start winning work.