Andrew Ramos
  • The welcome screen, with team cards over a map

    Welcome

  • Onboarding: creating more teams

    Creating teams

  • Home: the map with each team’s route and remaining properties

    Home

  • Choosing a start date and team, with each team’s properties and time to complete

    Picking a route

  • A property card over the map, on a team’s route

    Property on the route

  • A property’s page: request payment, last service, and its services

    Property details

  • Setting a service’s frequency, month by month through the season

    Service frequency

  • A Deck Install project: its schedule and the teams on site

    Project schedule

  • The project’s tasks, with due dates

    Project tasks

  • Adding notes for a day on the project

    Project notes

Overall concept

Background. In early 2023, some friends and I were looking to build a startup and quickly latched onto the idea of a scheduling and routing product for the lawn care space. Operators run their day from a truck, but the software built for them was built for the office. Terratory started as a bet that a crew-first product could carve out space for itself with small and medium-sized businesses. I came on as co-founder and led design of the product across three platforms, as well as the brand, and the marketing site.

What problem are we solving? Early conversations with owners showed us they reached for their devices throughout the day, not to manage anything, but to simply answer: where are the crews right now, how much have they finished, and is something going to roll over to tomorrow.

Beyond that, there was the challenge of scheduling. Most told us they stayed up Sunday evenings planning the week ahead to ensure all properties were being scheduled.

  • Home: the map with each team’s route and remaining properties

    Home

  • Setting a service’s frequency, month by month through the season

    Service frequency

  • A property’s page: request payment, last service, and its services

    Property details

Process

Those two problems shaped the product. To replace the Sunday-night planning session, we gave each service a season and a set cadence, so work schedules itself. And because owners mostly wanted to know where things stood, we made the map the base layer of the main screen, with routes and remaining properties sitting right on top. Owners can tell at a glance whether anything will roll over to tomorrow.

Sketching let us explore directions quickly and work out which controls users would need. In Figma we refined the look and feel, then took it back to users. After a few rounds of that we started building: a web app for v1, then React Native for v2 so we could offer native apps.

Terratory shipped on iOS, Android, and web, with real operators running their days on it.

Pencil sketches of the app: the map with routes, a property card rising from the bottom, and the Teams screen, with notes in the margins
Early sketches of the map, routes, and property cards
The payments page: from completed job to paid invoice
Payments
An ad: “Work smarter. Grow faster.” with App Store and Google Play badges
Ad

Tech stack

  • FigmaDesign
  • ElixirBackend
  • PhoenixWeb app (v1)
  • React Native and ExpoiOS and Android apps (v2)
  • GitHubCode
  • Claude Code and Intent by AugmentCoding with AI agents
  • VercelWeb app hosting
  • SentryCrash and bug reports
  • MixpanelProduct analytics
  • LinearTickets and organizing work
  • FramerMarketing site
  • Customer.ioNewsletters

How can I help?

andrew@andrewramos.com