I'd quote a fixed pilot after seeing the workflow, with the input, output, integrations and acceptance checks written down.
Price the work around your delivery estimate and the value of the task, then make hosting, usage costs and ongoing support separate line items.
Take on 1 pilot at a time until you know how much support it needs.
Your first clients are probably closer than you think.
I'd try these routes in this order, starting with people who can explain a real workflow to you.
01
Warm introductions
Ask people you know for an introduction to an agency owner, bookkeeper or service-business manager who still organises a repeated task by hand.
Ask to understand the task before offering a build.
02
Agency partnerships
Approach small web, design, CRM or consulting businesses that already have client relationships.
You can become their specialist for a defined integration project, with ownership and support agreed up front.
03
Targeted LinkedIn conversations
Choose 1 type of buyer, show a relevant example and ask whether the task matters to them.
Use business websites, introductions and normal platform search to understand each business.
04
People already buying help
Look for narrowly matched integration or workflow briefs on a freelance marketplace.
Jono's video gives you an alternative when your own network's light on suitable buyers.
The free-demo idea we discussed
For context, my current setup's SendPilot with LinkedIn Premium, sending 30 invitations a day and offering a free homepage prototype.
For you, I'd keep the same clear invitation and change the demonstration to a small workflow example for a specific type of business.
Build 1 reusable demo with sample data, then adapt the explanation when someone shows interest.
I'd make your first test 10 personal approaches and learn from the replies before choosing a daily volume.
LinkedIn's published rules prohibit unauthorised tools that automate invitations or messages, and the policy doesn't give Premium accounts an exemption, so check the approach against LinkedIn's own guidance ↗.
A first message you can make your own
Hi [name], I noticed [specific detail about their business].
I'm speaking with [type of business] owners about how they move a new client from an accepted proposal into their project system.
I've put together a small example that turns an intake form into a project checklist, folders and a welcome draft.
Is that a step you still organise by hand, and would it be useful if I sent you the example?
A gentle follow-up
Hi [name], following up on the onboarding example I mentioned.
I've used sample data so you can see the workflow without sharing client information.
If this is a task you're looking at improving, I'm happy to send the short walkthrough.
A message for an agency owner
Hi [name], I'm a software engineer in Adelaide, and I'm starting a small side practice helping agencies connect the tools they already use.
I've built an example that turns client intake into project setup, folders and a welcome draft.
Do your clients ask for this sort of integration work, and would it be useful to see an example?
When someone says, "Yes, that's useful"
Ask them to show you the last time they did the task.
Find out how often it happens, who's involved and how long each step takes.
Ask what a correct result looks like, including the awkward cases.
Agree what data you can use and which person approves the output.
Offer a bounded paid pilot with acceptance checks and a handover.
For the first demonstration, use fictional examples or information they've specifically approved.
Once it's running, compare the work against the starting process using actual timings, accuracy and staff feedback.
15 creators worth a look.
I've split these by what you'll get from them: business ideas, practical builds and deeper engineering.
How I chose these
The 19 video links and creators were checked against YouTube metadata, with descriptions, chapter lists and creator articles or code used to check the topics.
This is a researched shortlist, rather than a claim that I've watched every recording from beginning to end.
Some creators sell courses or communities, and the income figures in their titles are their claims rather than evidence of what you'll earn.
The older tutorials can still help with structure, but check current tools, pricing and licences before using them in a client project.
15 creators shown · 0 of 19 videos marked as watched
I'd start with Dave because he connects practical AI engineering with finding clients, scoping projects and handing over useful software.
What I'd take from this
I'd borrow his approach of defining a clear deliverable, speaking with people who already know you and separating a feasibility demo from a working product.
I'd adapt his delivery process to your own capacity, because his larger projects and sprint prices aren't a starting target.
I'd put Jason near the top for understanding how a technical specialist turns useful expertise into a consulting offer.
What I'd take from this
I'd copy his discovery questions about what success looks like, then write the proposal around that outcome and a few clearly scoped options.
I'd treat this as an archive of his consulting methods, because he's closed his consulting and training offerings and his example prices aren't a forecast.
I'd start with Liam for a clear introduction to packaging AI knowledge into consulting and implementation services.
What I'd take from this
I'd borrow the small consulting offer: understand 1 business workflow, recommend suitable tools and turn the most useful improvement into a defined implementation project.
I'd use the free material first and treat the client-acquisition video as a menu of options, since the channel also promotes a paid accelerator and doesn't establish that every method will work for you.
I'd use Michele for the practical steps between choosing a niche, making an offer and starting conversations with potential clients.
What I'd take from this
I'd publish a useful demonstration for 1 type of business, make your LinkedIn profile explain that offer and start personal conversations with people who engage with it.
I'd judge the ideas by the steps you can apply, with the earnings and 30-day language treated as the creator's marketing rather than your expected result.
I'd use Mark for the connection between practical AI implementation and helping a business learn to use what you've built.
What I'd take from this
I'd borrow his build-and-teach approach by packaging a working improvement with a short handover, clear instructions and a way for the client to run it confidently.
I'd use this 2025 roadmap for the business-adoption discussion and check current tool details before choosing a platform.
I'd use Nate when you've picked a useful workflow and want a practical n8n build to work through.
What I'd take from this
I'd start with a small support or document-processing workflow, then use his handover guide to decide who owns the accounts, what gets tested and how the client takes over.
He promotes a paid community and affiliate tools, so I'd judge each lesson by the working system and delivery detail rather than its headline earnings.
I'd keep this as a reference for n8n foundations, APIs, support workflows, invoice processing and agents rather than make finishing the whole course your first milestone.
I'd use Nick for the mechanics of connecting business tools and building workflows that have a clear commercial purpose.
What I'd take from this
I'd borrow the pattern of a booking triggering a CRM update and a response, then adapt it to a business whose owner can tell you exactly what that saves them.
The course dates from April 2025 and promotes paid training, so I'd check current tool instructions and treat its sales claims as marketing.
I'd put Jono on your list for concrete client acquisition alongside the build tutorials.
What I'd take from this
I'd test a small number of tailored Upwork proposals against jobs asking for a specific integration or workflow, with a short relevant demonstration.
His $100 starting-budget premise isn't a verified acquisition cost for your business, and his descriptions include affiliate links and paid consulting.
I'd use Greg for offer ideas, particularly this conversation with Corey Ganim about a small, repeatable AI assessment service.
What I'd take from this
I'd explore a structured interview, a short recommendations report and a review conversation that leads naturally into a separately priced implementation.
I'd treat the earnings and conversion figures as the guest's claims, and judge the assessment by whether its recommendations are useful to a real customer.
I'd follow Claire for practical demonstrations of how people use AI in real work, with this Hamel Husain episode offering a useful consulting angle.
What I'd take from this
I'd consider a focused quality review for a business that already has an AI assistant, using real conversations to identify and prioritise improvements.
I'd keep the client involved in judging good answers, because this work depends on understanding their customers and product.
I'd use Peter's interviews for approachable demonstrations of product work, especially this explanation of testing AI with Hamel Husain.
What I'd take from this
I'd learn the simple spreadsheet approach before choosing an evaluation platform, then turn observed issues into checks the client can understand.
I'd treat this as delivery training rather than customer acquisition advice, and you can learn from the free recording without buying the promoted course.
I'd follow Dan for advanced coding workflows that combine agents with ordinary code, tests and review steps.
What I'd take from this
I'd borrow a small part of his workflow for your own delivery process, then consider a repository setup service once you've proved it works consistently.
I'd keep this behind the business videos in your queue, because it's advanced engineering with a course funnel and little direct customer acquisition guidance.
I'd try a 6-8 hour weekly budget if that fits alongside your job and existing business.
For example, 2 hours on Tuesday, 2 on Thursday and a 2-4 hour weekend block, with the first customer conversations arranged at a time you can genuinely offer.
These are targets for a small experiment, rather than a promise of a client in 4 weeks.
Your choices and ticks stay in this browser.
Week 1
Choose a useful starting point
Aim for 1 clear offer and 5 useful conversations.
Week 2
Build something you can show
Aim for 1 reusable demonstration.
Week 3
Put it in front of buyers
Aim for 10 relevant, personal approaches.
Week 4
Offer a paid pilot
Aim for 1 decision on a bounded project.
0 of 16 steps ticked.
Give it a clear space alongside the day job.
I've kept the offer examples outside freight, logistics, customs and supply-chain software, given WiseTech's business ↗.
I'm not an employment lawyer, so I can't tell you what your contract allows.
From what I know, I'd get an Adelaide employment lawyer to check the outside-work, IP, confidentiality and conflict provisions before taking a client, and get any approval your contract requires.
Working in another industry is a useful starting point for the discussion, rather than confirmation that a project's clear.
Keep your own equipment, accounts, repositories, data and working time separate, and keep employer code, internal methods and customer relationships with your employer.
My suggestion for tonight: watch Dave's first-project video, choose 1 of the offers above and write down 5 people who could tell you how that task works.
Send me the offer you like and I'll give you an honest opinion.