RAMOS LAWN CARE

The site came first. Then the P&L system the business now runs on.

Role: Operations & Financial Systems Lead
Year: 2026
Discipline: Software Engineering · Operations & Financial Systems
Stack: React · TypeScript · Vite · Tailwind CSS

Started as a client site build, then grew into an operating role. Architected an automated financial reporting system tracking recurring vs. project revenue across 19 properties — managing $10.7K+ in monthly gross revenue and a 21.7% net operating cash reserve — and streamlined 4-day crew workflows across 18 accounts with automated billing reconciliation, eliminating paper invoicing and unbilled visits.

System notes

Financial systems
Automated P&L reporting distinguishing recurring vs. project revenue across 19 properties — the reporting layer the business now uses for cash-flow decisions.
Process digitization
Digitized 4-day crew workflows across 18 accounts and automated billing reconciliation, eliminating paper invoicing and previously-unbilled visits.

Ramos Lawn Care & Services website homepage

PRD-02 · Shipped

Product requirements

Operations & financial reporting system for a working lawn care business

Problem

Ramos Lawn Care ran on paper: invoices written by hand, visits tracked from memory, and no reporting layer separating recurring revenue from one-off project work. That made it impossible to answer basic operating questions — what's this month's actual cash position, which accounts are behind on billing, is the crew's 4-day route actually profitable — without manually reconstructing the numbers.

Goals

Eliminate paper invoicing and unbilled visits by digitizing the crew's billing workflow end-to-end.
Give the business owner an automated P&L view that separates recurring revenue from project revenue, instead of one blended number.
Make the 4-day crew route across 18 accounts auditable — every visit tied to a billing record, not tracked from memory.
Ship a public-facing site first, establishing enough trust in the engagement to take on the financial-systems work next.

Target users

Business owner: Needs a real-time read on cash position and which revenue is recurring vs. one-off, to make hiring and pricing decisions.
Crew / field operations: Runs a fixed 4-day route across accounts and needs billing to follow automatically from completed visits, not a separate paperwork step.
Prospective clients: Land on the public site to evaluate and request service — the original scope before the engagement expanded.

User stories

As the owner, I can see monthly gross revenue and net operating cash reserve broken out by recurring vs. project work.
As the owner, I no longer reconcile invoices by hand — completed visits generate billing records automatically.
As the crew, I follow the same 4-day route across 18 accounts and every visit is logged against its account without extra paperwork.
As a prospective client, I can find the business online, see the service offering, and request work.

Scope

Public marketing site (the original engagement scope)
Automated financial reporting: recurring vs. project revenue across 19 properties
Automated billing reconciliation tied to the crew's visit schedule
Digitization of the 4-day, 18-account crew workflow

Out

Client-facing self-service scheduling or online payments
Multi-crew / multi-route support (single crew, single route at this stage)
A packaged product for other lawn care businesses (built specifically for this operation)

Success metrics

Monthly gross revenue tracked: $10.7K+ visible in the automated reporting layer
Net operating cash reserve: 21.7%, now a reportable figure instead of a manual estimate
Unbilled visits: Eliminated — every completed visit produces a billing record
Accounts on the digitized route: 18 accounts across a 4-day crew cycle

Risks & open questions

The reporting and billing system was purpose-built for one business's workflow, so extending it to a second crew or route would need real rework, not just configuration.
Single points of ownership (one owner, one crew) meant scope could shift mid-engagement — the project itself started as a site build and grew into the financial-systems work.