Prepared for Hittle Landscaping · Westfield, Indiana

We didn't write a pitch.
We built the demos.

Working builds for the way a commercial grounds operation actually runs: a console that knows where every truck and every crew member is, how long each site visit should take, and how many crew-hours it burned against the bid. Plus a client app your property managers will open every morning, and a commercial-first rebuild of hittlelandscape.com. All live right now. Open them on your phone.

03working builds, live today
340crew members tracked live
312vehicles in the fleet sim
00slides in this deck

Don't take our word for it. Try them.

Everything below is a working build seeded with a realistic day of Hittle's commercial operations: 96 crews, 340 people, four branch yards, a live clock. Nothing is a screenshot of a slide. Tap any frame and it opens the real thing.

01
Fleet + crew intelligence console · The flagship

Groundspeed

hittle.hoosai.dev/groundspeed

All 312 of Hittle's vehicles, across four regional yards, on one console. Groundspeed watches the GPS feed and turns it into the number your ops team actually argues about: how long did we sit on that site, and how long did the estimate say? When a crew runs past its estimated duration — one truck or ninety, running at once — Groundspeed doesn't wait for the Friday recap. It flags it while the trailer is still on the property.

hittle.hoosai.dev/groundspeed Groundspeed live fleet map
  • I
    Fleet-wide live map, on real roads. Actual Indianapolis-metro geography — real highways, real interchanges, real reservoirs — not a stylized mockup. Four regional yards on one console: zoom out to see every branch's load at a glance, zoom into a region to watch individual trucks move along the same roads your crews actually drive. Crews sharing a property cluster into a single badge instead of stacking labels.
  • II
    Site timers vs. estimate. Every active truck ticks against its estimated duration — a searchable, sortable board across all 96 trucks working today, not just a glance at a handful.
  • III
    Overage reporting, live. The moment any crew crosses its estimate, an alert fires with minutes-over counting up — plus arrival, departure, and long-idle events across the whole fleet, with acknowledgements.
  • IV
    Drive time vs. site time. A day report computed from the same feed: splits of site, drive, and yard minutes by branch and crew type, an estimate-accuracy leaderboard, fleet-wide utilization.
  • V
    Crew tracking, built in. A new Crews tab tracks the people, not just the trucks: who's on the clock, punches, timesheets, and crew-hours against the bid. Details in the next section.
  • VI
    Production pass. The real build plugs into your actual GPS hardware (Samsara, Verizon Connect, or in-cab phones), draws geofences from true property boundaries, syncs estimates from your bid and job-costing system, and pushes alerts to text or Teams.
One truck's day, the way Groundspeed sees it
7:12a
The Yard at Fishers Districtest 1h 30m · actual 1h 22m −8m
8:51a
Drive · 14 minSR-37 → I-69 S
9:05a
Fort Ben Commerce Parkest 1h 00m · actual 1h 09m +9m
10:14a
Drive · 24 minI-69 N → Saxony
10:38a
Saxony Corporate Campusest 1h 45m · on site now
Seeded demo data — in production this strip is your telematics feed.
Open the live demo →
02
New · Crew tracking inside Groundspeed

Crews

hittle.hoosai.dev/groundspeed/#crews

A truck on a map doesn't tell you who's on it. The Crews tab tracks all 340 people on 96 crews: punches captured automatically at the yard and property geofences, who's on site, driving or on lunch, and the number that decides margin on commercial work: crew-hours used against crew-hours bid. When a crew runs over, Groundspeed tells you whether it's a productivity problem or a staffing gap, and which nearby crew can send help.

hittle.hoosai.dev/groundspeed/#crews Groundspeed Crews tab: every crew, who is on the clock, and crew-hours against the bid
  • I
    Every person, live. Each crew shows who's on the clock, who's on site, driving or at lunch, and who never showed. Search by name, crew or property.
  • II
    Crew-hours vs. bid. Every visit is budgeted as estimate × planned crew size. Groundspeed compares that to the people-minutes actually spent on site, visit by visit, crew by crew.
  • III
    Staffing gap or slow crew? A crew that's a person short runs long on the clock but can still be under on crew-hours. Groundspeed says which one it is, so you don't chase the wrong problem.
  • IV
    Send help. When a crew runs over, it lists the nearest crews in the same branch that are about to finish, with distance, and dispatches them in one tap.
  • V
    Timesheets that build themselves. Geofence punches, lunches and projected clock-outs roll into a timesheet for every person. Approve the clean ones in one click, export CSV for payroll, and see who is heading into overtime by Wednesday.
  • VI
    Exceptions, not paperwork. Late punches, punches from outside the yard, skipped lunches and no-shows surface on their own, each with a one-tap fix.
One crew's morning, from the punches
5:48a
No-show · HL-206one crew member calls off by text · crew runs 3 of 4
6:33a
Crew punches in at the East yardcaptured by the yard geofence, no app tap needed
8:50a
Arrives at Hamilton Town Centerbid at 9.0 crew-hours (2h 15m × 4 people)
11:05a
Over on time, under on crew-hours6.9 of 9.0 crew-hours used staffing gap
11:08a
Help, one tapa crew on the same property wraps in 14 min
Every timestamp above matches the live demo's seeded day.
Crews · Timesheets Auto-built timesheets with flagged punches and overtime watch Open crew tracking →
03
Client-facing app · The relationship layer

Greenline

hittle.hoosai.dev/greenline

The same GPS feed, pointed at the client. Greenline gives every property manager their own Hittle app: this week's schedule, a live map of the crew heading their way with a real ETA, a chat line to their account manager, and photo-backed service reports with one-tap proposal approvals. In the demo you're Dana, the property manager at a Fishers corporate campus — and truck HL-07 is 23 minutes out.

  • I
    Today, at a glance. Next visit with a live ETA counting down, weather that affects the work, and anything waiting on the client's signature — one screen, zero phone tag.
  • II
    Schedule they can trust. Three weeks of visits with scope details a tap away — mowing, irrigation, enhancements, fertilization — each tied to a named crew.
  • III
    Live crew tracking. Watch the truck come down US-31, get a notification at the gate, then follow the visit checklist item by item while the crew is on site.
  • IV
    Chat with the account team. A direct line to the account manager with AI-drafted replies the team reviews — plus quick actions for quotes, issues, and schedule changes.
  • V
    Reports & approvals. Photo-backed visit reports with time-on-site, and enhancement proposals the client can approve in one tap — straight onto the schedule.
  • VI
    Production pass. The real build adds per-client logins across whole portfolios, push notifications, e-sign on approvals, and a feed straight from Groundspeed — one system, two audiences.
The visit, from your client's side
1
7:00 AMVisit appears on today's schedule — crew and window confirmed.
2
10:15 AMTruck HL-07 goes en route — live ETA starts counting.
3
10:38 AMArrival notification. On-site timer and checklist go live.
4
12:23 PMVisit report lands: photos, tasks, time on site vs. estimate.
5
AnytimeQuestions go to chat. Proposals get approved in one tap.
Every timestamp above matches the live demo's seeded day.
Open the live demo →

One feed. Every audience.

Groundspeed and Greenline run on the same feed. The GPS ping that tells your ops team a crew is 40 minutes over estimate is the same ping that punches that crew in on site and tells your client the truck is 5 minutes out. Build the spine once — every audience gets its own view of the truth.

Why HoosAI builds like this

We invest in the teams we want to build with.

HoosAI is an Indiana software shop, and Hittle is the kind of company we built it for — fifty years of family operation, the biggest independent book of commercial grounds in the state, and an operations problem that software actually solves. We build working demos first because it's the honest way to sell: you judge the product, not the promise. If it's a fit, we co-brand the case study, you get a reference build your industry hasn't seen, and the specifics land in the walkthrough — no fine print.

04
Full marketing site rebuild · Commercial first

hittlelandscape.com

hittle.hoosai.dev/website

We rebuilt the whole website too, and pointed it at the buyers Hittle actually serves: property managers, developers, general contractors and homebuilders. Commercial leads the navigation, the homepage and every call to action ("Request a commercial bid"). Residential is still there, one link deep. Same real photography, the same fifty-year story, every page the current site has.

hittle.hoosai.dev/website Hittle Landscaping website rebuild: commercial-first hero
  • I
    Commercial first, everywhere. Bid Build, Maintenance and Production Homes lead the nav and the homepage, with the commercial bid form one tap away. Residential stays live but no longer sets the tone.
  • II
    Every real page, not a landing page. 25 pages: commercial services, project gallery, bilingual careers, education center, and working bid and contact forms.
  • III
    Your real work, not stock photos. 88 real project photos pulled from actual job sites, in a proper masonry gallery with a lightbox.
  • IV
    Forms that actually send. Commercial bid, builder bid, general contact and consultation forms, wired to real email delivery, live today.
  • V
    Built mobile-first. Every page, form, and animation checked on a real 375px viewport before anything shipped.
By the numbers
25pages, live
88real project photos
4working lead forms
100%mobile-optimized
Same content strategy as the current site — rebuilt, not reinvented.
Open the site rebuild →

Next steps

Step 1
The walkthrough

Forty-five minutes, your team and ours. We drive the demos, you poke holes, we map them to how your crews and clients actually work.

Step 2
Scope lock

We agree on what the production build includes — GPS hardware, integrations, properties, users — and put it in writing.

Step 3
Build to launch

HoosAI builds, you review live builds as they land — the same way you saw these — until your crews and clients are on it.

The demos are live.
The conversation is one email away.

nehemiah@hoosai.biz