I turned my husband's lawn app into a business. Here's the story from outside the code.

I'm Kirralea. I run a small Australian software company called McPherson Solutions, and I'm the person responsible for LawnSuite existing as a product instead of as a personal project gathering dust on my husband's phone. This is the story of how that happened, because people keep asking and I figured I'd write it down once, properly, in one place.

My husband is a medically retired army veteran. He got into gardening as therapy after he got out of service. The short version is that the army ends and you still need something physical to do with your hands, something outdoors, something with visible progress week to week. For him it was the lawn.

We had moved into a 1900s Queenslander on a 1,200m² block of Coalfalls clay in Ipswich, and the Couch grass that came with the house was dying in slow motion. I watched him fight it for two years. Most of what he learnt came the hard way.

I was not paying attention at first

For the first twelve months I thought he was just obsessed with grass. He would come inside with dirty knees and tell me about curl grubs, root systems, rain events, BOM forecasts, and what he had sprayed on which zone. I mostly nodded and kept working. I run the business side of a few different small operations, so my evenings tend to be spreadsheets and invoices, not garden chats.

Then one night he showed me his phone.

He had lawn notes in five different places. A notebook he kept losing on the back deck. Two AI chatbots he was asking questions to, with histories he could not search. A Google Sheet he had set up and then forgotten about. Product rates scribbled on the back of fertiliser bags in the shed. Photos in his camera roll with no labels on what zone they were of or what the problem had been.

I asked him how he was supposed to remember what he had applied last month, at what rate, and whether it worked. He said he was not. He was just guessing most of the time and hoping for the best.

That was the moment I realised the system was the problem, not him.

Why he was in that situation

My husband has some cognitive decline from service. Keeping track of things across multiple places is genuinely hard for him. It is not a criticism, it is just how his brain works after injury. The scattered-notes situation was not laziness, it was him trying every tool he could find and none of them fitting how he needed to work.

So he started building his own. He had a background in software from before his service years, and he figured if nobody else had built what he needed, he could write it himself. At first it was a single screen. Just a zone tracker with a note field. Then he added a dosage calculator because he was tired of Googling "mL per 100 square metres" every time he mixed a product. Then treatment logging because he needed to look back and see what had worked. Then weather integration because the spray window for his fertiliser kept getting ruined by rain he had not seen coming.

Over a few months of nights and weekends it turned into something that actually helped him. He stopped losing his notes. He stopped double-applying products. He stopped forgetting what rate he had mixed at last time. His lawn started improving. The tool was working.

The moment I knew it was a business

He showed me the zone detail screen one evening. It had his TestZone with the turf type, the area in square metres, the soil profile, the last treatment, the next scheduled task, and an analytics summary showing health scores over time. Real structured data that meant something.

I said "this is not just for you".

He said "it is rough, nobody else would use it".

I said "everyone I know who gardens would use it. My mum would use it. Your mate John at Beg Your Garden would use it. Every person in those Facebook gardening groups you read would use it."

He was not convinced. He kept saying the UI was rough, the code needed cleanup, there were bugs, he was not ready to show anyone. I told him that is what beta testing is for. I told him I would set up the business side if he kept building the product side. He eventually said yes.

What I did next

I set up McPherson Solutions Pty Ltd as the trading entity. I registered the company ABN. I bought the domain at lawnsuite.com.au. I briefed the first version of the privacy policy and terms of service (we have since rewritten both to be properly compliant with Australian Consumer Law and the Privacy Act, which was its own whole project). I got the LawnSuite logo designed. I set up the beta signup system. I built the first version of this website so we had a place to point people.

My husband kept writing code. He added the AI assistant that knows your specific lawn. He added photo diagnosis for plant diseases and pests. He added weather-intelligent scheduling that pulls from the Bureau of Meteorology. He added the flow calibration tool that calculates how long you need to water based on your actual hose flow rate. He added 35 turf varieties, 60 David Austin roses, 18 fruit trees, and 111 Australian products with real label rates.

The whole time he was also doing the actual lawn renovation on our own block. The Barricade mistake that killed his couch grass recovery. The Acelepryn grub treatment. The Sir Walter Buffalo laying. The cyclone that hit three days after we finished laying. Every feature in the app traces back to a problem he hit on our own 1,200m² of Coalfalls clay. The app is not theoretical. It is built by someone who needed it to work for his own turf first.

If you want to read the lawn renovation story from his perspective, he wrote it up with photos.

Why Australia specifically

The existing lawn care apps are almost all US focused. They ask you for a zip code. They recommend Scotts products you cannot buy here. They suggest treatment windows based on American climate zones. They do not know what Kikuyu is. They do not know what Coalfalls clay means. They have never heard of Sir Walter Buffalo, let alone the seven or eight Buffalo cultivars we actually have in Australia.

Australian gardeners have been making do with spreadsheets, notebooks, and generic Northern Hemisphere advice for years because nobody has built the tool for us. We decided to fix that. It was not a grand mission statement, it was just that my husband needed it and I realised other people needed it too.

We have written up a comparison of the main lawn care apps Australians can use if you want to see how the landscape looks.

The co-founder dynamic

People sometimes assume one of us is the "real" founder and the other is a helper. That is not how it works. He is the one with the lawn obsession, the product intuition, and the engineering skills to build what he needed. I am the one who saw the product in the tool, set up the business to carry it, handles the customer side, and does all the work that is not code.

Neither of us could do this alone. The app is his. The business is mine. LawnSuite is both of us.

If that sounds domestic, it is. We run it from home. We do not have an office. We do not have investors. We do not have employees. We have a single product, a beta tester group that is growing, and a backyard that is still dirt and weeds because the front yard took everything we had last summer.

Where we are heading

Android closed beta is running now. Free during beta while we fix the bugs. Pro subscription will be $9.99 per month or $89.99 per year (AUD) when we open it to the public. The first 50 beta testers who subscribe lock in our Founding Member rate of $4.99 per month or $49.99 per year for life, as long as the subscription stays continuous. Once the 50 spots are gone, Founding Member pricing closes permanently.

iOS is on the roadmap for later this year. A web dashboard is on the roadmap after that for people who want to review their lawn history from a computer.

The backyard will probably be turfed when Stampede Buffalo is officially released for sale, because my husband is very specific about what grass he wants for the shade and he refuses to commit until the variety is on the market. I have given up trying to rush him.

The business side is just me, for now. If LawnSuite grows we will hire. If it stays small, it will still have been worth it, because it has already made my husband's own lawn care easier, and that was the original goal.

If you want to try it

The app is in Android closed beta. Join the waitlist here and we will send you an install invite.

The blog (the one you are reading) is where we are going to write honestly about what is working, what is not, and what we are building next. My husband writes the lawn content from the ground-level obsessive perspective. I will write the business and product decision side from the outside looking in. If you are interested in watching a tiny Australian software company get built in real time, this is where we will be writing about it.