Crewtide

Giving schedulers back the week they spend rebuilding the week.

Crewtide builds next week from a recurring master list, optimizes routes around real-world constraints and tells customers when their visit moves. I led it from the first conversations with schedulers through product design to an early-access launch.

Status

In early access, with a live interactive demo and a waitlist for recurring field-service teams.

Try the Crewtide demo

Crewtide launch page: “Plan the week, not the spreadsheet,” beside a glowing route map, with the top of the weekly scheduling board below. — Launch site The launch site leads with the product itself: a live board you can drag.

Role: Product lead, start to finish
Stage: Discovery → early access
Platform: Web app · technician mobile view · Google OR-Tools
Contribution: Research · scope · UX/UI · launch site

Challenge

Recurring service teams rebuild next week by hand, every week. They copy last week’s spreadsheet, flip every-other-week customers on and off, chase time off across texts and calendars, then call every customer whose visit moved. Most of it lives in one person’s head, and moving one stop quietly bumps three others.

What I did

Started with how a scheduler’s week actually goes. One told us about 60% of theirs went to four tasks, and about a quarter went to a single question: where can this customer go, and who does it bump? That question became the center of the product.
Defined who it’s for: commercial teams of roughly 5 to 100 technicians running the same routes every week, such as commercial kitchen services, pest control, cleaning and HVAC maintenance.
Shaped the week into four steps (build, fix, notify, publish) on a single board.
Designed Find a spot, which ranks every open slot in plain language (fits as is, pushes later stops back, bumps another stop, runs past clock-out) before anyone commits.
Made problems hard to miss: 20+ live checks flag conflicts in red or amber, and every day gets a backup plan for call-offs.
Kept the automation honest. Route optimization runs on Google OR-Tools, anything it can’t place is listed with the reason, and a person approves the plan.
Closed the loop for everyone else: a To notify list for customers, a phone route for each technician and sync back to the system of record.
Built the launch site around a working demo with invented crews, plus an early-access waitlist.