Checking
The business grew.The systems behind it didn’t.
Someone’s checking three systems, copying the same details and chasing the next step.I fix the process, connect the tools and automate the repeated parts that don’t need a person. Better systems for the work behind the scenes.
Bring the messy version. No polished brief. No obligation.
The work behind the work
Still doing the work
your setup should handle?
Copying
Can you add it there too?
Chasing
Just following up...
Remembering
I forgot to follow that up.
HOW I WORK
First, I look at the whole mess.

The whole picture
- What’s happening now?
- What are you using?
- Who’s involved?
- Where’s the work supposed to end up?
What’s doing what?
- What happens by hand?
- What already happens automatically?
- What talks to what?
- What only happens because somebody remembers?


Why’s it like this?
- Why does that spreadsheet exist?
- Why are you entering this twice?
- Why does someone have to keep checking it?
- Why are you paying for two tools doing almost the same job?
What actually needs changing?
- Keep it
- Fix it
- Connect it
- Replace it
- Consolidate it
- Automate it

Robot Army
Ever caught yourself thinking,
“I need another me”?
Good news. We can skip the cloning.I build the repeated job into a workflow that handles the normal stuff and sends the unusual case back with what you need to check it.
Meet the Robot ArmyROBOT 03 · SHIFT REPORT
Clocked inThings handled while you were somewhere else.
FOLLOW-UP SENT
While the enquiry was still warm.
RECORD UPDATED
Once, in the right place.
REMINDER SCHEDULED
Nobody had to remember.
ODD CASE RETURNED
With context, not a vague cry for help.
3 jobs moved · 0 tabs reopened · 1 human left alone
Different businesses. Same work getting stuck.
"Amanda at Lunaris is an absolute Make.com whiz! Her automation work simplified our operations completely. She’s incredibly friendly, down-to-earth, and excels at thinking outside the box to solve complex workflow challenges."
"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."
Start with the annoying job.
Show me the job that keeps making a nuisance of itself. I’ll tell you whether it needs a proper look, one contained fix, a Robot Army or ongoing support.
A Proper Look
Not sure what needs changing?
A focused Zoom review of one problem, with written findings and a practical next-step plan.
Build It
One job or a whole Robot Army?
One contained setup or fix, through to a multi-step workflow that handles the repeated work.
Ongoing or Custom
Need me to stick around, or is the job particularly weird?
Ongoing support for agreed workflows, plus migrations, custom tools and multi-system builds.
Halaxy Setup
Need Halaxy set up properly?
New, half-built or inherited accounts configured, tested and handed over.
Surely there’s a
better way to do this.
Five quick questions to find the jobs worth fixing.
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
What’s taking more work than it should?
Answer five quick questions.
I’ll show you the first place I’d look.
No PDF gate. No fake savings promise.

Hello hello 👋
Don’t ask. It’s a saga.
Twenty years working inside government systems gave me a sharp eye for process, compliance and practical problem-solving.
These days, I work across workflow automation, business systems and complex data migration, helping teams connect systems, reduce manual handling and make complicated work safer and easier to manage.
My projects have included Halaxy workflows, API automation, OCR-supported review, reporting dashboards and migration platforms built to move thousands of records without quietly setting fire to anything important.
If it has an API, I can usually make it talk to something it was never meant to meet.
I’m nosy about systems. I want to know why something takes six steps, why two tools refuse to speak and why everyone has accepted that Thursday afternoon now belongs to the spreadsheet.
That curiosity is basically Lunaris.
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 usually 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.
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 a chilli bean over the zombie base wall are adorable.
Also, a special mention to Sunflower and her
✨ iconic Gingersun skin ✨.
And if I start humming a completely unrelated song during a Zoom call, apparently that’s also part of the service.

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
HowIGot Here
Government was where this particular habit started.
I worked 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.
That work eventually pulled me further into workflows, automation, systems, data and APIs, until 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.
All these years later, I’m still asking the same question:
Why are we still doing it this way?
The bits I care about
Ask the obvious questions
Make it usable
Connect the bits
Leave some things alone
The practical questions are usually the useful ones.
Useful things for awkward workflows.

I already pay for the software. Why am I still doing all the admin?
Buying software does not remove admin by itself. The work only gets easier when the tools, handoffs and exceptions are set up around the way the business actually operates.
Read more about I already pay for the software. Why am I still doing all the admin?
Do I need automation, or is my process the actual problem?
Automation helps when a task is repetitive and rule-based. If responsibilities, inputs or exceptions are unclear, fix the process first or the automation will reproduce the confusion faster.
Read more about Do I need automation, or is my process the actual problem?
How do I know what is actually worth automating?
The best automation candidates are frequent, predictable and rule-based. Start with a contained task where the inputs, outcome and exception path are clear.
Read more about How do I know what is actually worth automating?What job keeps costing time, creating mistakes or pissing everyone off?
Show me what’s happening.
You don’t need to know the answer.
That’s my job.
Leave your details and I'll get back to you within 24 hours.
