Melbourne · Victoria
AI consulting in Melbourne, for businesses that want it working rather than piloting.
I'm David Erenboim, a Melbourne-based AI consultant. I help small and mid-sized Victorian businesses put AI to work on the tasks that quietly eat their week — quoting, chasing, triaging, reporting, writing — and I stay until the thing runs without me.
Most Melbourne businesses I speak to have already tried AI. Someone has a ChatGPT tab open, a few staff use Copilot, and a manager is paying for a subscription nobody can explain. What's missing usually isn't tools. It's one person accountable for turning a vague interest into a workflow that saves hours every week.
What working together looks like
Every engagement starts with a free 15-minute review. You describe where the friction is; I tell you honestly whether AI is the right fix, and what the first step would be.
From there a typical project has three parts. First, a short diagnostic: I look at the actual work, the systems it touches, and the data involved. Second, one workflow built end to end — not a demo, a working process your team uses on Monday. Third, handover: written documentation, a short training session, and a clear owner inside your business.
Most first projects are scoped to four to six weeks. If you would rather test the water, hourly support and one-off workshops are available.
Where Melbourne businesses get stuck
The same three patterns show up in almost every business I work with. Tool sprawl: four subscriptions, none of them talking to each other, all of them billed monthly. Shadow usage: staff pasting client data into free chatbots because nobody gave them a safe option. And no owner: AI sits with whoever is curious, instead of with whoever owns the outcome.
Each of those is fixable, and none of them requires a new platform. Usually the fix is smaller than people expect — a clear policy, two integrations, and one workflow built properly.
Small enough to be accountable
You work directly with me. There is no account manager, no offshore delivery team, and no junior learning on your budget. I take a small number of engagements at a time so each one gets finished.
I work remotely across Melbourne and Australia, and on-site in the CBD, inner suburbs and south-east Melbourne when a workshop or a hands-on session is the better format.
What this looks like in practice
Quote turnaround
Supplier and subcontractor quotes read, compared and summarised into a draft proposal your estimator reviews instead of writes.
Enquiry triage
Inbound email and web enquiries classified by intent, routed to the right person, and answered from one approved knowledge source.
Knowledge retrieval
Your SOPs, policies and past proposals made searchable, so a new starter finds the answer in seconds instead of asking a senior.
Content and tenders
First drafts of case studies, capability statements and tender responses assembled from your own material, then edited by you.
Questions people ask
Do you work on-site in Melbourne?+
Yes. Workshops, training and hands-on build sessions are usually more effective in person, and I travel across Melbourne — the CBD, inner suburbs and the south-east. Ongoing work and support are handled remotely.
How much does AI consulting cost?+
Engagements are scoped and quoted before any work starts, so there are no surprise invoices. Small businesses typically begin with a single focused project or a block of hourly support rather than a large retainer. The initial 15-minute review is free.
Is this only for large companies?+
No. Most of my clients are small and mid-sized businesses, typically 5 to 100 staff, where one saved process is felt immediately. Larger organisations are welcome, but the value is highest where decisions are made quickly.
What industries do you work with?+
Professional services, trades and construction, wholesale and distribution, healthcare administration and technology resellers are the most common. The method is the same regardless: understand the work, then automate the repeated part.
How quickly will we see something working?+
The first working automation or assistant usually runs inside the first few weeks. Diagnostics and documentation come first, because automating a broken process only makes it faster to be wrong.
Do we need technical staff to maintain it?+
No. Everything I build is handed over with written runbooks and a short training session, and I stay available for support afterwards. A tool that needs a specialist to keep it alive is the wrong tool.