MowSeason
  1. Home
  2. Author

Jimenez Julien

Founder and product lead of MowSeason. He writes the software, answers the support email, and takes the call when a route rebuild goes sideways at 5 in the morning.

Portrait of Jimenez Julien

Why this product exists

The first lawn care owner I ever worked with ran 96 properties out of a single garage in the suburbs and kept his entire book in a spiral notebook with a rubber band around it. I was there to help him move his bookkeeping off paper. What I found instead was a business that made almost all of its yearly decisions in a six week window in late winter, then spent the next eight months absorbing the consequences. He priced the season in February by memory, sold it by text message, and every rainy Tuesday after that quietly cost him a half day he never billed anyone for.

That notebook is the reason MowSeason exists. Software for this trade tends to be built by people who think of a lawn as a work order. It is not. A lawn is a subscription that the customer forgets they bought, delivered by a crew that has forty minutes to be somewhere else, on a schedule set by rainfall and soil temperature rather than by anybody in the office. Once you accept that, the design problem changes shape. You stop building a ticket queue and start building a season: a package that is sold once, a rotation that holds it, and a routing engine that knows what to do when Thursday is underwater.

I spent two winters riding along and sitting in on renewal calls before I wrote the first line of the scheduler. I watched an owner in Ohio lose eleven properties because his renewal texts went out in the third week of March, after a competitor had already knocked on those doors in January. I watched a crew leader in Georgia carry a laminated card of gate codes because the office system did not have a field for them. I watched a bookkeeper reconcile mulch deliveries against invoices by hand, in April, at a kitchen table. None of those are exotic problems. They are the daily texture of a green industry company between one and eight crews, and almost none of them were addressed by the tools those owners were already paying for.

So the rules I set myself were narrow on purpose. MowSeason will not try to be a full field service platform, it will not chase commercial property management, and it will never charge per property, because charging per property punishes the exact growth the product is supposed to create. It prices per crew, because a crew is the unit that costs an owner real money. Everything else follows from that: the package builder, the seven, ten and fourteen day rotations, the growth curve pacing through the May flush, the weather shift that moves a day and tells the customer before the phone rings.

What I am accountable for is simple to say and harder to do. The route rebuild has to be correct, because a missed visit is a lost customer and a double cut is a refund. The agreement has to be plain enough that a homeowner reads it on a phone in a driveway and understands what they are buying. The export has to work, every time, because your customer list is yours and no vendor should be able to hold it. And when something breaks in the middle of a spring flush, the person answering is the same person who wrote the code.

Experience and expertise

  • Eleven years building operational software for small service businesses, the last four spent entirely inside the green industry.
  • Two full seasons of ride alongs with mowing crews in Indiana, Georgia and Wisconsin, plus renewal call shadowing with 14 owners.
  • Designed the visit rotation engine that now schedules more than 240,000 recurring lawn visits per season.
  • Built the weather shift model against ten years of county level precipitation records so the thresholds match how crews actually decide to stand down.
  • Regular reader of NALP and state landscape association material, and a persistent nuisance in three regional lawn care operator forums.
  • Publishes annual pricing benchmarks drawn from anonymized package data, shared with every customer before they set the next season price.

How this product is built and maintained

MowSeason ships small changes weekly and never during the first three weeks of the spring flush, because nobody wants a new interface the week their calendar is fullest. Every scheduling change is tested against a library of real season shapes: a 118 property Indiana book on seven day cycles, a Texas book that goes dormant in July, a Wisconsin book that ends abruptly with a hard frost in the first week of November. If a change would move a single visit in any of those books without being asked to, it does not go out.

The written material on this site follows the same standard as the software. Numbers come from customer accounts with permission, not from a marketing spreadsheet, and every figure quoted on the home page is a median rather than a best case. Testimonials are published with the owner's full name, company and city, and each one was read back to the person who said it before it went live. When a claim stops being true, it gets edited or removed rather than quietly softened. Corrections are made in place, and material changes to the pricing or the terms are announced by email before they take effect.

Published articles

These nine reports were written for The Cut List, the magazine this site publishes on the working lawn care season, and all of them went live on September 3, 2026.

Contact the author

The fastest way to reach me is email. Support questions, feature arguments, pricing disagreements and bug reports all land in the same inbox, and I read them myself. If you run crews and you think one of the numbers on this site is wrong, tell me and bring your book, that is a conversation I always want to have.

Email jimenezjulien42@gmail.com

Published by MLJ, SASU

MowSeason is a product of MLJ, SASU, registered in Paris. Company details, hosting information and the publication director are listed on the legal notice, and data handling is described in the privacy policy.

Written by Jimenez Julien, last reviewed on March 2, 2026. Questions about anything on this page go to jimenezjulien42@gmail.com.