Why I built lawn care software for solo operators (and what I won't build)

I’m Geoff Shepard. I live in Kansas City, and I build MowNext mostly by myself. This post is the long version of why it exists — and, just as important, the list of things I’ve decided it will never do. If you’re going to trust your customer list and your invoicing to a small piece of software built by one guy, you deserve to know how that guy thinks. So here it is.

How I got here

I should say this up front: I’m not a lawn care operator. I’m a software engineer who’s spent years building tools for small businesses. The closest I’ve come to mowing professionally was a college summer cutting three neighbors’ lawns for $15 each. I’m not going to pretend otherwise, because the operators I’m building for can smell a fake from the next county over.

What I did do was research. Before I wrote a line of MowNext, I spent about six months reading. I joined every lawn care Facebook group I could find — the big national ones with tens of thousands of members, the regional ones, the communities built around the well-known lawn care YouTubers. I read every “what software do you use” thread on r/lawncare going back years. I went through Capterra and G2 reviews of every major lawn care tool, top to bottom, sorted by one star first. Then I bought five of those tools and ran each one for a month, pretending to be a 60-customer solo operation.

I went in expecting to find a crowded market with no room left. That’s not what I found. I found a market with a hole in the bottom of it. Every tool in the category had spent a decade climbing upmarket — bigger features, bigger price tags, bigger sales teams — and the solo operator with 80 customers and one truck had been quietly left behind. There’s a longer version of this argument on the Why MowNext page, but the short version is: the category got bloated, and nobody was building the antidote.

What I kept hearing from operators

When you read a few thousand forum threads, patterns stop being anecdotes. Three complaints came up so often I started keeping a tally.

The pricing felt punishing. This was the loudest one. Operators with 40 or 50 customers were looking at $120 to $169 a month for software, and the math offended them. They weren’t wrong to be offended. At that size, $169 a month is roughly four cuts of pure profit, every month, going to a software company. The same complaint kept coming up in slightly different words: I don’t need most of this, so why am I paying for all of it? And the per-user pricing made it worse. Hire one helper for the summer and your bill could jump by $100 or more. The software was charging you a tax for growing.

The mobile apps were broken. Not ugly — broken. Apps that froze in the driveway. Apps that lost a completed job when the signal dropped. Apps that logged operators out at random, in a truck, with gloves on, between stops. Most of these products were built desktop-first ten or fifteen years ago, and the phone app got bolted on later. But the actual job happens in a truck cab, often with one bar of signal. The desktop is where you sit on Sunday night doing the invoicing you resent. The phone is the business.

The products kept gaining weight. Operators asked for scheduling, invoicing, payments, and a way to text customers. What they got, quarter after quarter, was AI receptionists, marketing automation, sales pipelines, custom forms builders — and a new pricing tier to pay for each one. Every feature made the app slower, the dashboard busier, and the bill bigger. Nobody at these companies seemed to be saying no to anything.

None of these are my insights. They belong to the operators who typed them out, over and over, in public, for years. All I did was take them seriously.

Why I’m not building an “all-in-one” platform

The obvious move, looking at that research, was to build a cheaper all-in-one. Take the big platforms’ feature lists, rebuild them at $49 a month, undercut everyone. I thought about it for about a week.

Here’s why I didn’t. Every bloated platform in this category started as a lean tool. They didn’t set out to become 200-feature beasts with 90-minute onboarding calls. They got there one reasonable-sounding feature at a time. A big customer asks for inventory management. A board deck needs a growth story, so marketing automation ships. Each addition makes sense in the meeting where it’s approved. Ten years later, the solo operator opens the app and can’t find the schedule.

“All-in-one” isn’t a product strategy. It’s what happens when a company stops being able to say no. And the cost of every yes lands on the smallest customers — the ones who pay for the bloat in price, in load time, and in screens they have to scroll past to do their job.

So MowNext has a different thesis: figure out the small set of things a 1–8 person lawn care operation does every single day, build those really well for a phone in a truck, charge a flat honest price, and refuse everything else. The refusing is not a temporary stance until we get bigger. The refusing is the product.

That also means being honest about who we’re not for. If you’re running a shop with 10 or more employees, MowNext is the wrong tool, and I’ll say so to your face — go look at SingleOps, Service Autopilot, or Aspire. They’re built for that, and they’re good at it. I’d rather point you to a competitor by name than sell you something you’ll churn out of in six months.

The features that made the cut

Everything that shipped in MowNext had to clear the same bar: does a solo operator or small crew touch this every week? If yes, it had to work in a truck, on a phone, possibly offline. If no, it didn’t ship. Here’s what cleared the bar, and why.

The mobile app, which is actually the whole app. MowNext is a mobile-first PWA. You save it to your home screen, it loads fast, and it works offline — when you finish a job in a dead zone, the app records it and syncs when signal comes back. There’s no separate desktop product with a phone version bolted on. The phone version is the product. It works fine on a laptop too, but the truck cab came first in every design decision.

Scheduling built around recurrence. Weekly, biweekly, 3-week, monthly, custom. Skip a visit, pause a customer for vacation, shift a whole day forward — each one is a couple of taps, not a rescheduling project. Recurring routes are the spine of a mowing business, so they’re the spine of the app.

Weather-aware rescheduling. We watch the forecast for your route. If tomorrow looks rained out, MowNext asks you what you want to do the night before — push the day, skip it, or run it anyway — instead of letting you wake up to chaos and ten customer texts. Rain is the single biggest schedule-wrecker in this business, and almost no software treats it as a first-class problem. We do.

Invoicing and payments that chase the money for you. Job gets marked complete, invoice goes out. Payments run on Stripe: card on file, autopay, a customer-pays-the-fee toggle, tips. I built this part around a blunt fact from the research — cash flow kills more small lawn care businesses than competition does. The job isn’t done when the lawn is cut. It’s done when the money lands. (If pricing the work itself is your sticking point, I wrote a whole framework on how to charge for lawn care.)

A customer list that’s actually yours. Names, properties, gate codes, dog warnings, job history, and a full CSV export anytime, no fee, no retention dark patterns. Your data is not my leverage.

Plain customer communication. “On our way” texts, reschedule notices, payment receipts. Not a marketing suite. Just the messages an operator actually sends.

That’s the heart of it. Each piece earns its place by being used constantly, not by looking good on a comparison chart.

The features I said no to

This list matters more than the last one. Every item on it is something a competitor sells, something a prospect has asked me for, or both. The answer is no, and here’s the reasoning.

AI receptionists. Your customers call you because you’re a person who shows up. An AI answering your phone spends the trust you’ve built one awkward call at a time. If you’re big enough to need a receptionist, hire one — or use a platform built for that scale.

Marketing automation. Drip campaigns, email funnels, lead scoring. A solo operator’s marketing is door hangers, referrals, Nextdoor, and good work. A funnel builder inside your field software is a second job pretending to be a feature.

Sales pipelines and CRM funnels. You have customers, not “opportunities moving through stages.” A list with good notes beats a pipeline at this scale, every time.

Inventory, purchase orders, equipment fleet management, payroll, subcontractor management. All real needs — at 15+ employees. Building them would mean serving a customer who isn’t you, and you’d pay for it in price and clutter.

Custom form builders. Every drag-and-drop builder I tested added screens, settings, and confusion. We’d rather ship the three forms you need, already built.

Tiers above $49, annual contracts, setup fees, and sales calls. Pricing is a trust signal. Ours is $0, $19, or $49 a month — free up to 20 customers, no per-user games, no contracts, nobody on commission anywhere in the company.

Some of these noes will cost me customers. That’s fine. The ones it costs me were never a fit, and the ones it earns me are exactly who I built this for.

How you can hold me accountable

Every software company says this kind of thing early on. Then they raise a round, or get acquired, and the blog post quietly disappears. So instead of asking you to trust my intentions, here’s what you can check.

The pricing is public. $0, $19, $49 — it’s all on the pricing page, with no “contact sales” tier hiding above it. If it ever changes, it changes publicly, with 60 days notice and at least 12 months of grandfathering for existing customers.

The exit is open. Export everything as CSV, anytime, free. If leaving is easy, I have to earn your $19 every single month. That’s the deal I want.

This post is the record. If MowNext ever ships an AI receptionist or a marketing automation suite, link this post back at me. I’m writing it down precisely so it’s expensive to walk back.

I answer my own email. hello@mownext.com goes straight to my inbox. Feature requests, bug reports, “this post is wrong about X” — I read all of it, and I usually reply within a few hours during business hours. There’s more about me and the public commitments on the about page, and the full manifesto lives at Why MowNext.

That’s the whole story. No funding round, no founder myth. A guy in Kansas City who read the forums, believed what operators were saying, and built the small, sharp tool they kept describing. I intend to keep it that way — and now you have it in writing.