First 90 Days Running Tinylawn at a 4-Crew Landscape Company
An honest walkthrough of what running Tinylawn looks like over 90 days at a 4-crew landscape operation — the wins, the friction, and the numbers that surprised us.
Table of Contents
If you’ve made it to this post, you already know what an AI receptionist is. You probably already know what Tinylawn does. What you don’t know — and what the marketing copy on the product page can’t honestly answer — is what running it actually feels like across the first 90 days at a real landscape operation.
This is that walkthrough. Composite picture from operators running 3–5 crew landscape operations in the $600K–$1.5M revenue range. Where the numbers landed. Where the friction was. What we’d do differently.
If you want to know whether this is worth your time before signing up, this is the honest version.
The Baseline (Before Tinylawn)
Before turning Tinylawn on, the typical 4-crew landscape company looks like:
- Inbound call volume: 80–140 calls per week during peak season (March–October), 20–40 per week off-season
- Calls answered live: Maybe 35–55% during business hours — the rest go to voicemail
- Voicemail return time: 4–18 hours during peak season, 1–4 hours during off-season
- Estimated lost leads: 8–15 leads per month going to voicemail and never calling back
- Owner phone time: 60–120 minutes per day on inbound calls and callbacks
The owner’s typical pattern: drive between job sites with the phone on the dash, return missed calls during traffic, lose half the calls anyway, work the inbox at 8pm to catch up.
Setup was about 12 minutes including configuring services, FAQs, business hours, and the call forwarding from the existing business number.
Week 1: Mostly Quiet Friction
The first week is calibration. Three things became immediately obvious:
1. The AI was answering calls within 3 seconds. Every call. Including the ones the team would’ve missed.
2. About 30% of “calls” turned out to be sales pitches, telemarketers, and spam. Tinylawn handled them without escalating to the team. That was an unexpected win — those calls used to interrupt the owner’s day for nothing.
3. The first few real leads sounded slightly different on the call summaries than the team was used to. Tinylawn captured the structured data fields cleanly, but didn’t always pick up the conversational nuance the owner would’ve heard if they’d taken the call themselves.
The first week’s data point: 12 lead summaries in 7 days. Three of them were leads the team would have missed entirely (after-hours calls, midday calls during a meeting, calls during a job site).
Friction: The owner kept second-guessing whether the AI was handling calls “right.” Listening back to the first 5 call recordings settled that pretty fast.
Weeks 2–4: Operational Adjustments
By the second week, the team started building a workflow around Tinylawn’s output instead of trying to mimic the old phone behavior.
Adjustment 1: Stopped checking the phone constantly. The team had been conditioned to glance at their phone every time it rang, even when they couldn’t answer. Once they trusted the AI was capturing the call, they stopped. The crews reported being able to focus longer on actual work.
Adjustment 2: Built a call-summary triage routine. First thing in the morning and once at lunch, the owner reviewed new lead summaries from the dashboard. About 15 minutes total per day. Replaced the old habit of returning missed calls at random throughout the day.
Adjustment 3: Added 4 new FAQs. Listening to the first 20 call recordings, the team noticed certain customer questions kept coming up that hadn’t been pre-configured. Adding the FAQs took 5 minutes and reduced “follow-up needed” tags by half.
Adjustment 4: Set up the call forwarding for after-hours only initially. The team wanted to keep answering calls themselves during business hours for the first month. By week 3, they switched to “all calls” forwarding. The volume of “did the team know about this call?” confusion dropped to zero.
The Week 4 numbers:
- Total calls handled by Tinylawn: 287
- Spam/sales calls filtered: 78 (27%)
- Lead summaries generated: 142
- Appointments booked directly by AI: 38
- “Needs follow-up” flagged: 24
- Estimated new revenue captured that would’ve gone to voicemail: $11,000–$18,000 over the first month
Month 2: The Habits Settle
By month 2, Tinylawn was just “how the phone works.” The team didn’t talk about it much. A few specific dynamics emerged:
Property managers noticed the response time. Three commercial accounts mentioned during routine conversations that “you’re easier to reach now.” One specifically said it was a factor in renewing for the next year.
The owner started using the call recordings. Not to babysit the AI — to coach the sales team. Hearing exactly what callers were asking for, in their own words, surfaced two service areas the company was under-offering: irrigation troubleshooting and small drainage projects. They expanded the pitch on both.
Two unusual cases came up. A customer called demanding to “speak to a real person.” The AI handled it gracefully — “Of course, I’ll have someone call you back within the hour” — but the customer was still annoyed. The owner called back, smoothed it over, and added a note to the team to watch for that. About 1 in 80 callers had that reaction in months 1–2.
The free trial limit (5 calls or 7 days) became irrelevant. The math had paid for the subscription roughly 6x over in the first 30 days based on captured leads that would have been lost. Nobody was thinking about cost anymore.
Month 2 numbers:
- Total calls handled: 312
- Lead summaries generated: 168
- Appointments booked: 51
- Conversion rate on captured leads to booked work: 31%
- Direct hours saved on phones across the team: ~25 hours/week
- Customer complaints about AI receptionist: 1 (the “speak to a real person” caller)
Month 3: What We’d Do Differently in Hindsight
By the end of month 3, the team had enough data to know what they’d recommend a similar-sized landscape operation do differently from the start.
1. Don’t try to write perfect FAQs at setup. Configure the basics, go live, then listen to the first 20 call recordings and add FAQs based on what callers actually ask. The pre-configured FAQs from setup were maybe 70% of what callers asked. The remaining 30% was unknowable until the calls came in.
2. Set the AI’s intake question list to capture more than the basics. Tinylawn allows custom intake questions. The default name/address/service captures the core, but adding things like “How did you hear about us?” and “What’s the urgency on this?” generated useful operational data the team didn’t have before.
3. Switch to “forward all calls” earlier than feels comfortable. Most operators try to keep answering business-hours calls themselves at first. The data shows this is suboptimal — even during business hours, you miss 30–50% of calls because you’re on a job, in a meeting, or driving. Forwarding everything to the AI within the first 2 weeks gets the math working faster.
4. Brief commercial accounts and property managers proactively. “We’ve added an AI receptionist to make sure your calls get answered fast” pre-empts the “wait, am I talking to a robot?” moment. Almost universal positive reaction when framed that way.
5. Use the transcripts for sales coaching. This was the unexpected use case. Three months of call transcripts showed the team where leads were leaking out of the funnel — and pointed at specific phrases the sales team should be using more (and less). Call transcript review became a weekly 30-minute team habit.
The 90-Day Numbers
Across the first 90 days at a representative 4-crew landscape company:
- Total calls handled: 891
- Spam/sales calls filtered (never escalated): 218 (24%)
- Real lead summaries generated: 478
- Appointments booked directly by AI: 142
- Leads that converted to booked jobs: ~165 (some after follow-up by the team)
- Estimated incremental revenue (calls that would’ve gone to voicemail): $58,000–$74,000
- Owner hours freed up per week: 12–18 hours
- Cost of Tinylawn for the period: Under $600
The ROI ratio isn’t worth printing in big numbers — it’s silly. The cost is small enough that the question isn’t “is this worth it?” The question is “why didn’t we do this earlier?”
What Tinylawn Didn’t Solve
Honest about what stayed broken:
- The CRM is still a separate problem. Tinylawn captures lead data well, but transferring it to whatever CRM the team uses requires a workflow — manual export, integration setup, or workflow tools. The team set up a simple flow but it took a couple of weeks to dial in.
- Estimate scheduling is only partly automatic. The AI books site visits and consultations, but the actual estimating still requires the owner or estimator to do the visit and quote. Tinylawn handles the front of the funnel, not the middle.
- Customer disputes still need a person. Three calls in 90 days involved customers who were upset about billing or a service issue. The AI handled them politely and escalated immediately, but the resolution required the owner.
- Bilingual edge cases. Most Spanish-speaking callers had decent experiences, but a few callers in regional dialects had moments of confusion. The team noted these and adjusted their service area FAQs accordingly. Most callers got through without issue.
These aren’t dealbreakers — they’re just the boundaries of what the product does well. Same conversation as any other tool.
Who This Setup Actually Works For
Based on the first 90 days, the AI receptionist setup is strongest for:
- Landscape operations with 2+ crews that can’t justify a full-time office hire
- Owners who are still spending 60+ minutes a day on inbound calls
- Operations with significant commercial or property manager accounts (where response time matters)
- Businesses with after-hours call volume that’s currently going to voicemail
- Owners who want to be in the field, not on the phone
It works less well for:
- Solo operators with low call volume (under 10 calls per week — the math gets thinner)
- Operations where the owner genuinely wants every call to be a personal touchpoint (lifestyle businesses, very high-end residential)
- Businesses where most calls are highly nuanced consultative conversations (high-end design-build with $50K+ projects — though even there, lead intake works fine)
The Bottom Line After 90 Days
If you’ve been on the fence about whether an AI receptionist is “real” or whether it’ll feel weird to your customers, here’s the honest summary: it’s real, it works, your customers mostly don’t notice, and your business gets meaningfully more efficient without you having to change how you operate.
The first 90 days has some friction — you’ll second-guess the AI, you’ll wish you’d set up FAQs differently, you’ll have one or two awkward calls. The friction goes away by week 4. By month 3, the AI is just how the phone works.
The hardest part is committing. The setup is 10–12 minutes. The free trial is 5 calls or 7 days. Most landscape operators know whether it’s right for them after the first 2–3 calls land in their inbox.
If you want to see what your business sounds like through Tinylawn before committing to anything, the demo is the fastest path. For more detail on the setup itself, see Everything You Need to Know Before Setting Up Tinylawn.