← Back to proof of work

Turning owner-held knowledge into a system the team could run

Not a real client

Simulated case study. Greenfield Grounds LLC and Patty Sorensen are fictional. This project was built to test and demonstrate my workflow-audit process. The numbers and recommendations below are projections, not verified results.

A workflow audit on a fictional 22-person landscaping company, run end to end the same way I'd run a real one. Here's what the process found, what I recommended, and where the honest limits of the work are.

  • Commercial landscaping
  • 22 employees
  • ~$1.8M revenue
  • 14 years in business

The business

Greenfield Grounds was a 14-year-old commercial landscaping company with 22 employees and about $1.8 million in annual revenue. The business had grown, but its systems hadn't kept up. Scheduling lived on a shop whiteboard and in group texts. Job details, hours, and change orders arrived through scattered messages. Client records were split across Google Sheets, QuickBooks Desktop, and phone contacts. Invoices could go out two to three weeks late, straining cash flow right before payroll.

The pivotal finding

The real constraint wasn't the calendar. The logic for matching crews to accounts lived entirely in the owner's head: which teams could handle municipal work, which clients needed extra care, which leads she trusted with bigger properties. A generic scheduling tool could show the plan. It couldn't make that call.

So I split the fix in two: shared schedule visibility, solved fast with an off-the-shelf tool, and crew-to-account decisions, which needed documented rules and a carefully scoped custom build.

Current State

Where the workflow breaks

Seven steps from first phone call to invoice, and every handoff depends on somebody remembering something.

1

Lead or referral

Phone call starts the process

2

Estimate

Loose Google Sheet, completed differently each time

3

Proposal + contract

Word or email, with manual back-and-forth

4

Crew assignment

Critical matching logic lives only in Patty's head

Continues

5

Schedule changes

Whiteboard + group text create conflicting versions

6

Field completion

Hours, extras and job status arrive by text or memory

7

Invoice + payroll

Patty reconstructs details and re-enters everything

Root cause

One owner is acting as the integration layer.

Visible impact

Late billing • crew conflicts • missed revenue

Simulated scenario. Greenfield Grounds LLC and Patty Sorensen are fictional, and this workflow was reconstructed from a practice discovery call, not a real client engagement.

What I recommended

  • A shared mobile schedule to replace the whiteboard and group texts
  • Short field forms for hours, job completion, and change orders
  • One client record for contacts, contract terms, renewals, and follow-ups
  • Automatic arrival notifications and renewal reminders
  • A weekly bookkeeping cadence and a plan to catch up the QuickBooks backlog
  • Down the road, a custom tool that drafts crew assignments from skill, trust, and account sensitivity, with the owner approving every match

Future State

A system that carries the work

The same job, running through tools that hold the details so nobody has to remember them.

1

Client record

Airtable becomes the operational source of truth

2

Draft assignment

Custom tool applies crew skills, trust and account sensitivity

3

Owner approval

Patty reviews the draft instead of rebuilding it

4

Shared schedule

Trello gives every crew lead the same live plan

5

Field capture

Mobile forms log hours, completion and change orders

6

Invoice-ready log

Clean records reach Patty for final review and QuickBooks entry

Automated follow-through

Client arrival notifications and renewal reminders reduce routine calls and memory-based follow-up.

Controls that remain human

Invoices, contracts, hiring, purchasing and final crew assignments still require Patty's approval.

Simulated scenario. Greenfield Grounds LLC and Patty Sorensen are fictional. This is a recommended workflow from a practice audit, not a system in production at a real client.

Projected impact

The audit found 9.25 hours of weekly time savings, worth about $15,031 a year at a conservative $31.25 hourly rate. A simulator evaluation was more conservative near-term: 7 to 9 hours a week, climbing to the full number once the custom assignment tool ships.

Past the hours, the roadmap was built to speed up invoicing, protect change-order and renewal revenue, cut crew misdirections, and free up enough capacity for two more commercial contracts without adding office staff.

Projected Business Impact

What the roadmap makes possible

Four numbers from the audit, and what they add up to for the owner.

9.25

Hours / Week

identified in the audit

$15,031

Annual Time Value

at a conservative $31.25/hour

7–9

Hours / Week

evaluator's realistic savings band

2–3

Months

estimated project payback

The owner-level outcome

Faster invoicing, fewer crew misdirections, and enough operating capacity to pursue two additional commercial contracts without adding office headcount.

Projected outcomes based on a simulated discovery call, not verified client results. Greenfield Grounds LLC and Patty Sorensen are fictional.

What this means if you're the client

The interview surfaced Greenfield Grounds' core bottleneck inside a single 45-minute call, not weeks of open-ended discovery. The turning point came from two specific questions: what information already lives in more than one place, and what lives only in the owner's head. That second question is usually where the real constraint hides.

The resulting roadmap was built to be usable by a technically cautious owner and a field crew, not just a tech-savvy office team. It also didn't call for a rip-and-replace. Low-risk fixes came first, like the shared schedule and field forms. The more sensitive custom decision tool came later, once the basics were already working and the crew-matching rules were fully documented.

The simulated client responded well to the report and was likely to move forward with implementation if the payment structure eased her cash-flow concern. That's also where the honest edges of this audit show up: a real engagement would go further, digging into job-level profitability, equipment-maintenance costs, a formal sales-to-crew handoff, onboarding and adoption planning, and a firmer timeline for the QuickBooks Online migration. Naming what's still open is part of what makes the roadmap trustworthy.

The lesson

The most valuable insight wasn't a tool recommendation. It was recognizing that "I just remember it" is a process gap. The roadmap turned owner-only knowledge into a system the team could actually run, while keeping the approvals that genuinely protected the business.

Curious what's hiding in your week?

A real audit starts with a free 15-minute call. No pressure, no obligation, just an honest look at where your time is going.

Book a Free Intro Call