
The whole picture
- What’s happening now?
- What are you using?
- Who’s involved?
- Where does the work go?
Still checking, chasing, copying or working around software that should be doing more?I find where the work is getting stuck, then fix the process, connect the tools or automate the repetitive parts.
Chasing leads. Checking things got done. Copying information. Remembering the next step.
You’ve got enough to remember already.




Different businesses. Same chasing, copying and workarounds.
"Amanda sorted out my custom GPT using Make when I couldn't get it to work myself. She went way beyond what I expected and gave me clear, practical instructions. Save yourself the time and just give Amanda a call. It is absolutely worth it."
Good news. We can skip the cloning.I can build you a robot army to handle the stuff that doesn’t need you every bloody time.
Follow-up sent
While it was still warm
Records synced
Once, in the right places
Reminder sent
Nobody had to remember
Odd one out?
Back to you, with context
A quick, practical check for the repeated admin, software workarounds and “we just do it this way” jobs worth questioning.
Spot the work your team keeps repeating, chasing or re-entering
See where the software you already pay for could be doing more
Work out what’s worth changing before adding another tool
No PDF gate. No fake savings promise.
Answer five quick questions.
I’ll show you the first place I’d look.
No PDF gate. Definitely no fake savings promise.
No more tools for the sake of more tools. Just a setup that does more of the work for you.
Keep what works.
Get rid of what doesn’t.
Make the tools you already pay for earn their keep.
Get the right things talking to each other.
Hand the repetitive stuff to your robot army.
If you’ve outgrown something, I’ll find something better and set it up properly.

About me
(Don't ask, it's a saga.)
I’m the person who wants to know why we’re doing it this way, why we’re entering the same thing again, why these systems can’t talk to each other and, occasionally, who the fuck designed this?
That curiosity is basically Lunaris.
I work in the gaps between people, processes and software, the places where information gets lost, work gets repeated and everyone quietly invents their own workaround.
I get into the processes, software, admin and data behind a business and look for the better way hiding in what people already do.
Sometimes I redesign the workflow. Sometimes I automate it. Sometimes I connect systems that were apparently never emotionally prepared to meet.
And sometimes I build a small digital Franken-monster because the sensible solution does not exist yet.
What matters to me is that the result makes sense to the people using it.
No mystery boxes. No technology theatre. No giant handover document everyone politely saves and never opens again.
And yes, Lunaris comes from my love of the moon, with a little nod to my boys too. Love you guys 💜
When I'm not fixing workflow problems, you'll find me escaping the city lights with my Canon R7, chasing galaxies and fumbling my way through astrophotography. Still learning, still swearing (and occasionally yelling at clouds), but that's half the fun.
And when I’m not out of Perth chasing galaxies, I’m usually curled up playing Plants vs. Zombies: Battle for Neighborville with the kids. They squeal and I squeal louder.
Yes, Peashooter has a weird face, but the noises he makes after lobbing out a chilli bean (over the zombie base wall I might add 😂) are adorable.
Also a special mention to Sunflower and her
✨ iconic Gingersun skin ✨.

Like, come on. Just look at her 😍

Always reminds me of Marvin the Martian.
Favourite Colour
Purple (obviously)
Coffee Order
Flat white with a sweetener
Favourite Animal
Cats
Music Genre
Yes
Love Language
Not having to repeat myself
Secret Weapon
Cert IV Accounting and Bookkeeping
I spent twenty years in government working with software that looked like it hadn’t been updated since dial-up.
There were endless forms, pointless reports, meetings about meetings and plenty of “that’s not my job” energy.
While everyone else worked around the limitations, I kept wanting to know whether there was a better way.
So I started making one.
I built registers so information could be found again. I tracked things people were relying on memory for. I pushed existing software further, linked information together and built processes that made considerably more sense than the ones I inherited.
Somewhere along the way I realised the bit I loved wasn’t administration itself.
It was figuring out how the whole thing worked and making it work better.
That eventually pulled me further into workflows, automation, systems, data and APIs, until apparently building things that software vendors never intended their products to do became a perfectly reasonable way to spend a Tuesday.
Make.com became one of my favourite tools because its capabilities are genuinely wild. I build advanced custom scenarios, work with APIs, handle messy data and connect systems that would otherwise continue pretending the other one doesn’t exist.
I’m also a Make Partner, because naturally I went far enough down the rabbit hole to acquire credentials.
But the tool has never been the point.
The point is still the same question I was asking twenty years ago:
Why are we still doing it this way?

The principles behind every build, decision, and late-night fix.
Why twice? Why this tool? Why does one person have to remember it?
If the people doing the work can’t use it, it isn’t finished.
People, information and systems need to hand work over cleanly.
Not everything needs automating. Sometimes the answer is to stop doing it.
Start with what you know: what needs fixing, what needs taking off your plate, or simply that the current setup could work better.
Not sure what needs changing?
I’ll trace one problem or workflow and show you where I’d start.
Know exactly what needs sorting?
One clearly scoped setup, fix or connection.
Want the repeat jobs off your plate?
A multi-step workflow that handles the routine work and flags the weird stuff.
Got more moving parts?
Migrations, custom tools, complex integrations and the weird projects.
Ongoing support for maintenance, troubleshooting and continued improvement.
3-month minimum
The practical questions are usually the useful ones.
If your business runs on too many tools, too many handoffs, and too much manual admin, here’s why I keep reaching for Make.com to build workflow automation that actually fits real business processes.
Read more about Why I Keep Reaching for Make.com in Business WorkflowsYou need the work to run better.
Sometimes that means automation. Sometimes integration. Sometimes a cleaner process. And sometimes the smartest thing I can tell you is: leave that alone.
If something behind the scenes is costing you time, creating mistakes or just pissing everyone off, show me what’s happening.
You don't need to know the solution. That’s my job. Drop me a message and I'll get back to you within 24 hours.