← Work/Case study
How a multi-location commercial landscaper turned scattered field notes into an operations workflow.
Account managers needed a field-friendly way to capture what they saw. Supervisors needed one place to review it, translate it, and turn it into follow-through.
At a glance
- Industry
- Commercial landscaping, multi-location
- Team
- Account managers in the field, an operations lead in the office, Spanish-speaking crew leads
- Workflow
- Account-manager site visits, captured structurally, reviewed centrally
- Status
- In production
The problem
Account managers spent the week driving between commercial properties, noticing issues and opportunities that mattered to crews, supervisors, and customers. But the observations did not land in one reliable place. Some notes lived on paper. Some lived in text messages. Some stayed in the account manager's head. Supervisors had no clean view of which properties had been visited, what was found, or what needed to happen next.
Why off-the-shelf software did not solve it
The company already had business systems, but none of them matched the field workflow. A CRM could hold records, but account managers needed something fast on a phone. A spreadsheet could be scanned, but it could not make field capture reliable. A task list could hold follow-ups, but only after someone translated the visit into tasks. The missing piece was a workflow layer between field observation and operational follow-through.
What shipped first
Botworks shipped a mobile-first web app account managers can open in the field on the phones they already carry. They pick the property, tap through structured visit categories, add notes and photos, and submit the visit before the details disappear. In the office, supervisors get a central review surface for every property visit, photo, issue, and enhancement opportunity.
The first system is capture and review. It gives the business a canonical record of what the field team saw, without forcing account managers to become software operators.
What became possible next
Once visits land structurally, the next workflows have something reliable to build on: translating English notes into Spanish for crew leads, creating operational tickets in the systems supervisors already use, drafting customer communications from real visit observations, and turning enhancement opportunities into proposals. Each next step reads from the same record instead of asking the office to re-enter the same facts again.
What the client owns
The capture app, the structured visit records, the photos, the review workflow, the deployment path, and the documentation needed to understand how the system works. Botworks maintains the workflow, but the operational record belongs to the business.
Have a workflow that should be easier?
Tell me where the work gets copied, chased, retyped, or remembered by one person. If software can make it cleaner, I'll tell you how — no commitment, no pitch.