Landscape Revenue Intelligence is a category. Naming it changes everything.

In 2010, HVAC software was a junk drawer. Dispatch boards from the 90s. Paper invoices stapled to clipboards. A QuickBooks file the office manager guarded like a wedding ring. Then ServiceTitan walked into that mess and did one thing nobody else had done: they named the layer. They called it the operating system for the trades, and the moment that phrase had a name, every dollar of trade-software venture money in the country lined up to fund it. Fifteen years later, the category they invented is worth nine billion dollars.

Landscape software in 2026 looks exactly like HVAC software in 2010. We have dispatch boards. We have invoicing modules. We have QuickBooks integrations and a thousand point tools that don't talk. And we have the same hole in the middle of the P&L — the layer between the truck and the books, where the money actually leaks. That layer doesn't have a name yet. So we're naming it.

Landscape Revenue Intelligence

Three words. They mean exactly what they sound like. The work of catching, keeping, and compounding the revenue your shop already touches — and turning every property, every quote, every call into a number the owner can see before payroll prints. It is not a CRM. A CRM is a rolodex with a calendar bolted on. It is not field service. Field service is what happens after the truck pulls onto the property. Landscape Revenue Intelligence is the layer that decides which truck goes to which property, what gets quoted on the way out, what gets followed up the next morning, and what gets re-walked in February when the customer almost canceled.

Naming a category is not a tagline exercise. It is a thesis about where the value sits. The thesis is this: in landscape, the value does not sit in dispatch software, because routing a truck is a solved problem. The value does not sit in accounting software, because every shop already has QuickBooks and is not switching. The value sits in the layer between them — the layer that catches the leaks. The forgotten quote. The customer drifting toward cancel. The half-pallet of sod nobody logged. The crew chief who quit because the office punished him for the field. That layer is the largest single line item on every shop's missed revenue, and no software company has ever built for it as a category.

The HVAC parallel — and why it matters more than people think

HVAC in 2009 had the same complaint landscape has now. Owners said the software was made by people who'd never sat in a service truck. Crews said the dispatch app punished them for the field. The office said the books didn't tie out. ServiceTitan's answer was not a better version of any of those things. It was a new layer that watched all of them at once — a system that knew the truck, the technician, the customer, the call, the part on the shelf, and the dollar at risk on every job, in one place, at the same time. Once that layer existed, it was no longer a tool. It was the operating system. Owners did not buy it because it was cheaper. They bought it because the company that didn't have it was running blind.

Landscape is sitting in 2009 right now. The shops are growing — two and a half million workers, $115 billion of annual revenue, margins that should be healthy and rarely are. The shops are also bleeding — six figures a year per shop in forgotten quotes, slipped renewals, off-the-truck upsells nobody asked for, and good crew chiefs who left for $2 an hour more because the software treated them like a barcode. The software hole is real. The category is open. Whoever names it owns it.

The five layers of Landscape Revenue Intelligence

We organize the work the way an owner thinks about the year. Bid season. Mow days. Fall apps. Snow contracts. The layoff. The rehire. The first quote of spring. Every one of those moments has a different revenue job to do, and every one of them has a software layer that should be doing it. We named the layers the way the trade names them, not the way a software architect would.

1. Win the work. Catching the inbound quote before it dies in voicemail. Walking the property with the right pricing. Beating the office to the callback by a Monday morning.
2. Keep the work. Catching the customer before the cancel. Reading the tone of the email that says 'we'll think about it.' Saving the renewal in February when the storm cleanup left a bad taste.
3. Get smarter. The system that learns YOUR shop — your won bids, your urgency patterns, your tone shifts — and is more useful on day 1,000 than day 1.
4. Run the crew. The Field Crew App, Operator Score, Foreman's Notebook. Making excellence portable so the foreman who quit in October doesn't take the gate codes with him.
5. Build the network. The Surplus Yard. Find a Crew. Property Hunter. The trade compounding on itself instead of subsidizing big-box returns desks.

Each layer is a P&L line. Each layer has engines that own it — Quote Intercept and InstantText in Win the Work, Save Play and Customer Worth in Keep the Work, WinPlaybook and RedFlag and ToneRadar in Get Smarter. We don't ship modules. We ship engines, named for what they do, organized by the layer of the year they show up in. That is what the category looks like from the inside.

What changes the day landscape has a category name

The first thing that changes is how owners shop. Right now an owner shopping for software gets pitched a dispatch board, a CRM, a chemical app, a field service tool, and a books integration — and is told to assemble those into something that closes the gaps. With a category name, the owner asks one question: who runs the revenue intelligence layer? The conversation collapses from ten vendors to one or two. That is what a category does. It collapses the buying decision.

The second thing that changes is how investors price the trade. Software for $3M-revenue landscape shops gets valued at SMB-tools multiples right now, because the software lives in a category called field service or CRM and those categories trade at SMB multiples. Software for the layer above field service — the layer that compounds revenue across a year, across a renewal cycle, across a referral chain — trades at operating-system multiples. That re-rating is what funded ServiceTitan to a nine-figure round. It is also what will fund the company that owns Landscape Revenue Intelligence.

The third thing that changes is how the trade talks about itself. Bid season conversations between owners stop being about which dispatch board has nicer drag-and-drop. They start being about which shop's revenue intelligence is sharper. Which one's WinPlaybook is teaching the crew chief better questions on the walk. Which one's RedFlag flagged the brewing cancel two weeks out instead of the day-of. The conversation moves up a layer, and the layer is where the money is.

We're not asking for permission

We're naming the layer. We're shipping the thirty-three engines. We're standing up the five layers as the architecture every landscape software company should have built, and didn't. The category is Landscape Revenue Intelligence. The thesis is that the layer between dispatch and accounting is where the trade actually makes — and loses — its money. Every post we put out from here is going to push on that thesis from a different angle. Forgotten quotes. The labor crisis as a software problem. Why most software is the same on day 1,000 as day 1. Why thirty-three engines, not eight. Five posts in, you'll be able to feel the shape of the layer we're building. Then we'll keep going.

If the thesis lands for you, the rest of this site is the product. Run your shop's numbers on the ROI page. Read the manifesto if you want to know what we'll never do. Or pull up The Council application if you want a Signal thread with the founders and locked-in founder pricing for the life of the account. Either way — once you've read this far, you've already read the longest sales pitch we'll ever write. The shorter version is on the homepage.