Frequently asked questions

No. I'm a senior software engineer and technical strategist, not a design studio. I build to designs you or your designer supply, and I can help find or coordinate design help when you need it — but visual design itself isn't a service I sell.

I'm based in Sydney and prefer local work for discovery and handover, because meeting in person is the best way to understand how your business actually runs. That said, I work with clients right across Australia — audits, builds, automation, hosting, and ongoing support all run perfectly well remotely. Travel outside Sydney is quoted separately when it genuinely adds value.

Most start small — a free website check, a presence review, or a single well-defined fix. From there we scope the larger build or automation work once we both understand what's needed. I give fixed quotes wherever the scope is clear, so you're not signing up for open-ended hours.

Start with a free website audit, or email [email protected] with your URL and a sentence about what's going wrong. I respond within 24 hours on business days, and I'll tell you honestly whether I'm the right person to help.

Fixed scope wherever possible — you know the price before work starts. For discovery, advisory, or evolving work I bill hourly. Standard rate is $165/hr, with a $145/hr partner rate for agencies and referrers. All prices are in Australian dollars and exclude GST.

WordPress isn't the problem — overkill is. For a small brochure site, a WordPress install means hosting, plugins, and security updates you pay for twice over. I recommend the simplest stack that does the job, which is often fast static hosting. If your content workflow genuinely needs WordPress, I'll build and support it — priced for the real maintenance involved.

Often a targeted fix is all you need — a speed pass, a broken form, or a content update. Sometimes the foundation is the problem and a rebuild is cheaper over time. The free audit tells you which, with a rough cost for each path so you can decide.

Accessible, responsive markup is just how I build — semantic HTML, keyboard navigation, sensible colour contrast, and readable structure. I don't sell standalone accessibility audits as a content-marketing product, but the sites I deliver are built to be used by everyone.

Technical SEO is whether Google can find, crawl, understand, and load your site — speed, structure, metadata, redirects, and indexation. Content SEO is the writing, keywords, and link building. I handle the technical side and can recommend trusted partners for content when you need it.

No, and you should be wary of anyone who does. Rankings depend on factors no one controls. What I can do is fix the measurable technical problems holding you back and show you clear before-and-after evidence of the improvement.

Yes — it's a real review by a senior engineer, not an automated score widget. For many small businesses it's enough to know exactly what to fix and roughly what it costs. Deeper presence research or hands-on fixes are scoped separately if you want them.

Automation is reliable, rule-based plumbing — "when this happens, do that." AI tooling adds judgement inside those workflows, like drafting, classifying, or summarising. They often ship together, but automation doesn't require AI to be useful, and most quick wins are pure automation.

Whatever fits your existing stack — commonly automation platforms, serverless functions, and direct API connections. I don't lock you into a product or resell you a subscription; I solve the workflow and document how it works so you're never stuck.

It can be, with the right boundaries. We agree upfront what data can leave your systems, what stays private, and what needs a human to review before it reaches a customer. I build AI into workflows deliberately — not as a black box you have to trust blindly.

The model is one component, not the product. Useful AI tooling wraps it in your data, your templates, and review steps — retrieval over your documents, drafting from your formats, and checks before anything goes out. That's the part that actually saves you time.

Small and well-defined is ideal — a single integration, a script, or one internal tool. What I avoid is vague "build me an app" work without clear requirements, because that's where budgets disappear.

Yes. Contracting and collaboration are part of what I do — clear scope and good communication matter far more than who owns the relationship. I'm happy to slot in on performance, integrations, or overflow work.

You own the client relationship; I deliver the technical work and invoice you B2B at the partner rate. Reports and builds can carry your branding by arrangement. A warm intro and early scoping make it run smoothly — don't wait until the night before launch.

No — that's your strength, not mine. Send me mockups, Figma files, or specs and I'll build them properly, flagging implementation issues early rather than quietly changing your design.