Built by a small business owner
for small business owners

I’m not a developer. I’ve never written a line of code in my life.

Indeed, I never set out to build a SaaS app. For the past eleven years, my wife, Pai, and I have run Water Lily House, a traditional Thai massage clinic in Warrnambool, Victoria.

Pai is the face of the clinic, handling the hands-on work and day-to-day client care. I’m her administrative assistant, handling the systems, admin, websites, records, and all the strange little back-office problems that small businesses somehow collect. We met in Thailand, where I was living after spending a decade at the Australian Tax Office (ATO).

I wasn’t working in GST or compliance at the ATO, but you don’t spend ten years inside the ATO without absorbing how the system works. You learn what “compliant” actually means in practice. You see what gets flagged, what gets missed, and what kind of records hold up when questions get asked.

Four years after leaving the ATO, and now living back in Warrnambool, my hometown, Pai and I opened our clinic. While setting it up, I was looking for a way for Pai to track appointments and came across Cliniko. Cliniko is excellent practice management software - appointment scheduling, patient records, invoicing, and our favourite feature: online booking. We like it so much that we’re still using it eleven years later. But back in 2015, it had one obvious gap for our business: no built-in gift voucher support.

So, like many business owners, I built my own system inside Cliniko - tracking voucher sales, recording balances, noting expiry dates, updating records when clients redeemed part of a voucher. The team at Water Lily House couldn’t figure out the process, so it relied on one person understanding the system well enough to keep it running: me. It was manual, convoluted, time-consuming, and fragile, but it worked - until it didn’t.

I developed a chronic illness in 2021 that left me unable to work, and the system fell apart.

Pai went back to a handwritten notebook, and voucher tracking slipped back into exactly the kind of fragile process I had spent six years trying to avoid.

By mid-2025, I had recovered enough to resume some of the administrative tasks in the business. I was finally able to build a proper website, and tackle years of neglected admin.

Then, in December 2025, while catching up on several hundred voucher records, I asked an AI one simple question: “How difficult would it be to write a script that uses the Cliniko API to enter vouchers automatically?” Within three hours, a working system was tracking vouchers, syncing with Cliniko, and - crucially - letting anyone on the team use it, not just me.

That’s how Water Lily Vouchers was born.

Water Lily Vouchers was originally intended to solve one problem for one clinic: automate the voucher system we had been trying to manage for years. It handled the Christmas 2025 gift voucher peak so well, that I started thinking that other Cliniko users - who I knew were looking for a gift voucher solution - might like to use it.

So with no idea what I was getting myself into, the build started. Over the first few weeks, the same realisation kept appearing in different forms: a gift voucher system needs to be the system of record, not a field bolted onto someone else’s database. Partial redemptions need a proper balance ledger with full history, not a value that gets overwritten. GST classification needs to live with the voucher from the moment it is created, not be inferred later from a product code. The ACCC three-year minimum expiry needs to be enforced at issue, not remembered as a policy.

None of that belonged inside Cliniko’s product records - not because Cliniko had failed, but because that is not what product records are for.

By the end of that month, Water Lily Vouchers had been renamed VoucherGrid.

It was then that the product stopped being a Cliniko add-on in any meaningful sense. The integration was no longer the product. The voucher system was the product.

With the core in place, online voucher sales were the next unplanned feature. We added a branded storefront, connected Stripe, generated proper voucher codes and delivery emails, and let customers buy vouchers without calling, messaging, or walking through the door.

The surprise was not the technology. It was where the sales came from. Once vouchers were available online, many buyers came from outside our local area - people buying gifts for friends and family who lived near us, while they were interstate or even overseas. One gift voucher was even purchased from France.

That was the moment the product’s purpose changed. VoucherGrid was no longer just about tracking vouchers properly. It was about helping local businesses reach gift buyers they were previously invisible to.

With sales running, the next logical layer was compliance. I worked through ACCC expiry rules, ATO GST treatment, deferred revenue, breakage, and voucher reporting using our own voucher data as the test case. My background at the ATO meant I understood what “getting it right”looked like from the regulator’s perspective - even if I’d never personally written the rules.

VoucherGrid translates those requirements into an almost invisible workflow a small business can actually use every day: clear voucher types, balances, redemptions, expiry dates, audit trails, and reports your accountant can work with. No fragile spreadsheet, no one-person workaround, and no guessing what happened six months later.

VoucherGrid has changed how we run Water Lily House.

The Christmas voucher peak that used to consume weeks of admin now runs quietly in the background.

Pai can sell a voucher over the phone in under a minute. Our team can issue, redeem, and balance vouchers without anyone needing to ask me how it works. We have records that hold up, and we reach buyers we would never have reached. For the first time in eleven years, the voucher process is not the fragile part of the business.

I’m proud of what VoucherGrid has become - and I’d be lying if I said I expected any of it when I asked one question to an AI in December 2025.

The response from early users has been warmer than I had any right to expect. Beta testers have caught edge cases I’d missed, suggested features I hadn’t thought of, and - more than once - told me they couldn’t imagine going back to spreadsheets and paper.

I opened this page by saying I’m not a developer. I think that’s why VoucherGrid works. It wasn’t built to capture a market - it was built because it’s what Pai and I needed. The fact that other businesses needed the same thing is the reason it kept growing, not the reason it started. If you’re trying VoucherGrid, I hope it works for your business as well as it has for ours.