AI-Enabled Operations, Revenue Growth & Platform Modernization
Prepared for Chris Beutz and Arc Outdoors Team
Green Horizons, Inc.
February 2026
Confidential — Client Strategy Document
Six workstreams to transform operations before the fall platform transition.
6 Months to Build the Future
March–August 2026: a strategic window to deploy AI-native operations, grow revenue per customer, and create capabilities that compound over time
Green Horizons sits on 25 years of operational data across 5,600+ service locations—a proprietary asset no competitor can replicate. With Pistachio launching April 1 and a major platform evaluation in October, the next 6 months represent a unique opportunity to build AI-powered capabilities that drive efficiency, revenue, and customer experience regardless of which platform powers operations long-term.
Route automation saves 400+ hours/year of manual scheduling and reduces windshield time by clustering stops geographically
Ordering upgrades—bundling, upsell prompts, and auto-renewal—can drive 15–25% more revenue per customer
Route density marketing turns geographic concentration into a customer acquisition engine targeting high-value neighborhoods
AI-native operations—morning briefings, after-hours call handling, smart dashboards—create a compounding advantage no off-the-shelf platform provides
Primary Recommendation
Prioritize route automation and ordering improvements for immediate spring impact, while building the intelligence layer (dashboards, AI briefing, marketing segmentation) that makes every future capability smarter.
Six parallel initiatives, sequenced by impact and dependency.
| # | Workstream | Priority | Timeline | Key Outcome | Status | Effort |
|---|---|---|---|---|---|---|
| 1 | Route Automation | Critical | Mar–May 2026 | AI-optimized daily routes, crew dispatch, weather handling | Active | 35% |
| 2 | Ordering & Revenue | Critical | Mar–Apr 2026 | Bundling, upsell, auto-renewal, mulch quantities | Planned | 20% |
| 3 | Business Intelligence | High | Mar–Jun 2026 | AI Command Center, morning briefing, executive dashboards | Planned | 15% |
| 4 | Marketing & Density | High | Mar–May 2026 | SEO, geo-targeted campaigns, route density acquisition | Active | 10% |
| 5 | AI Customer Experience | High | Apr–Jun 2026 | After-hours AI phone, website chatbot, smart responses | Planned | 10% |
| 6 | Platform Evolution | Moderate | Ongoing | Pistachio integration, incremental portal improvements | Active | 10% |
The single highest-impact opportunity: transform manual daily scheduling into AI-assisted route generation.
Today
19 preset routes per day, each manually assembled through the management portal
60+ minutes of daily “click-click-click” to build and assign crew routes
Excel cheat sheet tracks crew availability, route preferences, and scheduling rules
Weather disruptions require complete manual re-routing
Service rules (e.g., no fertilizer day-of/after mowing) tracked mentally
Vision
“Optimize Route” button: AI generates the full day's routes in seconds
Geographic clustering minimizes drive time between stops within each route
Auto-assign crews based on preferences, equipment, and availability
Weather-responsive: automatically reschedule and re-cluster when storms hit
ASAP priority queue with deadline management for urgent requests
Service conflict rules enforced automatically (fertilizer/mowing spacing)
19
routes built daily
400+
hours/year saved
60+
min/day scheduling
5,600+
service locations
Four phases from proof-of-concept to full weather-responsive autonomy.
| Phase | Deliverable | Timeline | What Changes |
|---|---|---|---|
| Phase 1 | Cheat sheet digitization | Weeks 1–2 | Crew data, route rules, and preferences move from Excel to database. Foundation for all automation. |
| Phase 2 | “Optimize Route” button | Weeks 3–6 | One-click route generation. AI clusters stops geographically, assigns crews, respects service rules. Human reviews & approves. |
| Phase 3 | Crew dispatch & notifications | Weeks 7–8 | Approved routes auto-text to crew leads. Real-time status updates. ~$0.01/msg all-in via Twilio SMS. |
| Phase 4 | Weather intelligence | Weeks 9–12 | Weather.gov integration (free, reliable). Auto-detect disruptions, suggest re-routes, handle ASAP carryover. |
Optimization Engine
Google OR-Tools
Open-source vehicle routing. Apache 2.0 license. Handles 80+ stops with time windows and capacity constraints. $0 cost.
Road Distance
GraphHopper (existing)
Already integrated in mobile crew app. Provides real road-distance matrices for accurate clustering.
Weather Data
Weather.gov API
Free, reliable NWS data. No API key required. Hourly forecasts for Minneapolis metro area.
Anchor Deliverable
The “Optimize Route” button is the centerpiece. It transforms a 60-minute daily task into a 5-minute review. Critical dependency: digitizing the crew cheat sheet (Chris's Excel) is the gate — everything else builds on it.
Four pillars to increase revenue per customer without acquiring a single new account.
Smart Ordering
Today: mulch orders are locked to 1 yard. Customers cannot change the quantity at all.
Vision: Auto-calculate recommended quantities based on property square footage and DeepLawn measurements. “Your 8,200 sq ft property typically needs 4 yards of mulch.”
Service Bundling
Today: customers order services individually. No incentive for multi-service commitment.
Vision: Pre-built packages — Spring Essential (mow + cleanup), Full Season (mow + fert + cleanup), Premium (all services). 5% discount for 3+ services drives commitment.
Intelligent Upsell
Today: no cross-sell prompts. Customer orders mowing, sees nothing else.
Vision: Contextual prompts during checkout: “Customers who order weekly mowing typically add spring cleanup” — powered by 25 years of service history data.
Auto-Renewal
Today: every spring, customers must re-order everything from scratch.
Vision: “Renew All Services” one-click campaign. Pre-populate last year's services with updated pricing. Email in February, lock in revenue before the first mow.
Conservative
+8%
revenue/customer
Moderate
+15%
revenue/customer
Aggressive
+25%
revenue/customer
Turn 25 years of data into daily decisions with conversational AI and executive dashboards.
Imagine This at 6 AM
“Good morning Chris. Today you have 19 routes scheduled across 4 crews. Rain is expected after 2 PM — I've flagged 3 fertilizer routes that should be moved to tomorrow. Revenue is tracking 12% above last February. Two renewal reminder emails went out overnight to 47 customers who haven't re-ordered spring mowing yet.”
Automated daily email combining weather, scheduling, revenue, and customer activity into one actionable summary.
Executive Dashboard KPIs
Revenue
Daily/weekly/monthly vs. prior year, by service type
Crew Efficiency
Stops per hour, drive time ratio, completion rate
Customer Retention
Renewal rate, churn risk, lifetime value trends
Route Profitability
Revenue per route, cost per stop, density score
Service Mix
Bundle adoption, upsell conversion, seasonal patterns
Natural Language Queries
Ask “What was our best month for fertilizer revenue?” and get an answer from 25 years of data instantly.
Dashboard Tooling
Metabase (free self-hosted) or Looker Studio (free, Google-hosted) connecting directly to existing MySQL database.
Proactive Alerts
Revenue dips, crew efficiency changes, or unusual customer patterns surface automatically before they become problems.
Densify existing service areas instead of expanding territory. Every new neighbor on a route increases profitability.
The Density Thesis
Your top 20 cities represent ~80–85% of all customers. Premium markets like Edina, Wayzata, Plymouth, and Eden Prairie have the highest revenue per customer. Adding one more customer on an existing route costs almost nothing in additional drive time — it's nearly pure margin.
Radius-Based Campaigns
“Your neighbor at [street] uses Green Horizons” — targeted mailers and digital ads within 0.5 miles of existing customers. Google Ads local campaigns start at ~$10/day for neighborhood-level targeting.
Weather-Triggered Campaigns
Automated email/SMS after significant weather events: “Heavy rain this week? Perfect time for fertilizer application” or “Storm damage? We handle cleanup.” Triggered by Weather.gov data, sent to segmented customer lists.
SEO Before Spring
Google Business Profile optimization, local keyword targeting (“lawn care Minneapolis,” “lawn service Edina”), and review generation strategy. Organic search is the highest-ROI acquisition channel for local services. Target: complete by March 1.
Premium
~$1,200+/yr
Top 20% by revenue. Full-service bundles, priority scheduling.
Growth
~$500-1,200/yr
Mid-tier, 2-3 services. Upsell candidates for bundling.
Starter
~$200-500/yr
Single-service. Cross-sell through seasonal prompts.
At-Risk
Lapsed
Haven't re-ordered. Renewal campaign targets.
Extend customer service to 24/7 with AI-powered phone and chat that captures every opportunity.
The 8 PM Call
A homeowner calls at 8 PM about a fallen branch blocking their driveway. The AI phone agent captures the details, confirms the address from the customer database, and logs an ASAP service request. At 6 AM, Chris's morning briefing flags the priority item. By 9 AM, a crew is dispatched. The customer receives an automated text: “Your crew is on the way.” No call was missed. No sticky note was lost.
AI Phone Agent
After-hours and overflow call handling via CallRail's AI agent or similar platform. Answers FAQs, captures service requests, routes urgent calls to on-call staff.
Estimated Investment
$95–$280/mo depending on plan and volume
Website AI Chatbot
Trained on GH service catalog, pricing, and service area. Handles “Do you serve Wayzata?”, “How much is weekly mowing?”, and converts browsing visitors to estimate requests.
Options Range
Tidio ($29/mo) to Intercom Fin ($0.99/resolution)
The Integration Flywheel
AI phone and chat don't just answer questions — they feed the intelligence layer. Every interaction becomes data: what customers ask about most, when they call, which services generate the most inquiries. This data improves routing, marketing targeting, and service offerings over time.
A pragmatic approach: build capabilities that transfer to any platform, not features tied to one.
Current Architecture
Management portal (Green Solution) built on ColdFusion — 20+ years of operational logic
Customer-facing website with Stripe payments and DeepLawn instant estimates
MySQL database: 25 years of customer, service, and financial data
Mobile crew app with GraphHopper routing integration
Build Portable Capabilities
Every feature we build (route optimization, AI briefing, customer segmentation) operates on data, not on a specific UI. Whether the front door is ColdFusion, Pistachio, or any future platform, these capabilities plug in via API.
Pistachio Integration
Customer-facing website target: April 1. Meeting with Jack & Andy scheduled to clarify backend integration. Key question: how does Pistachio sync with the existing MySQL data layer that powers all of our AI features?
Decision Framework: When to Build vs. Wait
Build Now
Features that work at the data layer (routing, intelligence, segmentation), deliver immediate spring value, and transfer to any future platform.
Evaluate After Pistachio
UI-heavy features tied to a specific portal experience. Let Pistachio's capabilities clarify what needs custom building vs. what ships out-of-the-box.
Month-by-month priorities with dependencies and key milestones.
March 2026
Foundation & Spring Prep
Digitize crew cheat sheet
Build route optimization engine
Launch bundle packages on website
Auto-renewal email campaign
SEO & Google Business Profile
Set up Metabase dashboards
April 2026
Launch & Iterate
Pistachio goes live (Apr 1)
"Optimize Route" button live
Crew SMS dispatch system
Upsell prompts in checkout
AI Morning Briefing v1
Deploy website AI chatbot
PISTACHIO WEBSITE LAUNCH
May 2026
Optimize & Expand
Weather-responsive re-routing
AI Command Center queries
Density marketing campaigns
AI phone agent (after-hours)
Customer segmentation analysis
Smart quantity recommendations
Critical Dependencies
Cheat sheet data gates all route automation. This is the #1 input needed from Chris.
Pistachio integration clarity (Jack/Andy meeting) determines what we build custom vs. what ships with Pistachio.
Spring bandwidth: March is the busiest planning month. Feature rollouts must not disrupt operations.
Key risks with mitigation strategies to keep the roadmap on track.
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| Cheat sheet data delayed | Medium | High | Schedule dedicated 30-min session with Chris to walk through the Excel. Build template for easy data entry. Can start with partial data for 5 routes. |
| Pistachio integration conflicts | Medium | Medium | Design all features at the data/API layer, not the UI layer. Monday meeting with Jack & Andy will clarify integration points early. |
| Spring operational bandwidth | High | Medium | Stagger feature launches. Route automation first (saves time). No disruptive changes during peak weeks. “Parallel run” approach: new system generates suggestions, old process still available. |
| Data quality gaps | Medium | Medium | 25-year database has known inconsistencies. Build validation layer, handle edge cases gracefully, and use AI to flag anomalies rather than fail silently. |
| Crew adoption resistance | Low | Medium | Phase in gradually: AI suggests, humans approve. SMS dispatch is familiar. Early crews become champions. No change to field workflow until crew leads are comfortable. |
| Platform evaluation timeline shifts | Low | Low | All capabilities built as portable data services. If timeline accelerates, features transfer. If it extends, current system gets more capable. |
Risk Philosophy
Every feature uses a “parallel run” approach: the AI generates recommendations, a human reviews and approves, and the old process remains available as fallback. This means zero operational disruption during rollout — the worst case is that we keep doing things the current way.
A before-and-after view of Green Horizons operations by June 2026.
Today — February 2026
Chris spends 60+ minutes building routes every morning
Customers order one service at a time, no bundles
Weather disruptions require manual re-routing
After-hours calls go to voicemail
Business questions require pulling reports manually
Marketing is general, not geographic
Spring renewals happen customer-by-customer
June 2026 — The Vision
One click generates optimized routes for every crew
Customers choose bundles, quantities auto-calculated
Weather triggers automatic schedule adjustments
AI captures after-hours calls, morning briefing flags priorities
"What was our best month for mulch?" answered instantly
Neighbors of existing customers receive targeted outreach
Auto-renewal locks in spring revenue before March
Scheduling Time
60+ min/day
5 min/day
90% reduction
Revenue/Customer
Baseline
+15-25%
via bundles & upsell
After-Hours Capture
Voicemail
100% captured
AI phone + chat
Decision Speed
Report pulling
Instant answers
AI Command Center
Data sources, technology references, and recommended immediate actions.
Data Sources
| Source | Data Used |
|---|---|
| GH MySQL Database | 5,600+ locations, 25 years of service history, pricing, routes |
| Management Portal | Route structure, crew assignments, service scheduling rules |
| Stakeholder Meetings | Chris Beutz operational workflow, pain points, priorities |
| Linear Project Tracker | 25+ tracked issues, statuses, and dependencies |
| GraphHopper Integration | Existing routing engine in mobile crew app |
Technology References
| Technology | Cost |
|---|---|
| Google OR-Tools (VRP) | Free — Apache 2.0 |
| GraphHopper (routing) | Existing integration |
| Weather.gov API | Free — NWS public data |
| Metabase (dashboards) | Free self-hosted / $500/mo cloud |
| Twilio SMS (dispatch) | ~$0.01/msg all-in (~$330/yr) |
| CallRail AI Agent | $95–$280/mo |
| Tidio / Intercom (chat) | $29/mo – $0.99/resolution |
Recommended Immediate Actions
Share the crew cheat sheet. This single input unlocks the entire route automation workstream.
Clarify Pistachio backend scope in Monday meeting with Jack & Andy to align build priorities.
Schedule the deep brainstorm session (Tue/Wed, 8–9 AM CT) to prioritize which 3–4 features matter most for spring.
Approve the bundle packages (Spring Essential, Full Season, Premium) for website launch before March 1.
Prepared by Walter Vambrace, Chief of Staff • February 18, 2026 • For internal use
Methodology: Operational analysis, stakeholder interviews, technology benchmarking