The design story behind the mobile app — from problem to personas to screens. A 5-minute read.
Field teams in vacation-rental operations run their day on WhatsApp, paper checklists, and spreadsheets. Competitor apps (Breezeway, Turno) treat cleaning in isolation — disconnected from reservations, devices, and revenue. The result:
The #1 operational cost. Bad tools drive people out.
Units not ready at check-in. Nobody tracked progress.
Managers stitch together who-did-what across 5 tools.
"Make executing a shift a joy for the field, and running a portfolio effortless for the office."
SuiteOp mobile is the operational nervous system — the tool everyone uses to run the day. Not a web companion. The primary work surface.
Every task on SuiteOp is born knowing four things Breezeway and Turno don't own:
Who's arriving, when, how many, what they paid for. Reservation context inline.
Smart lock unlock inline — from a task, property, or reservation. No app-switching.
Upsells and VIP flags drive prioritization. Managers see dollars; taskers see smart sort order.
1000+ tasks, 100+ requirements, 500+ units. Speed doesn't change.
Two primary personas. One app, two very different experiences inside it.
Housekeeper · Spanish-primary · Budget phone · Gloves on · Mobile-only
50/50 iOS/Android · 25-75 items/task (100+ on tail) · Batch-completes at end of room
220 units · Team of 8 · Desktop AM, field PM · On-call 24/7 · Plans 4 days ahead
Supervisor (Marcos) = same persona, department-scoped, field-tilted
Profile and settings live in a top-right avatar menu — not a tab. Four tabs, forever, both personas, both platforms.
Maria opens the app and knows her whole day. Priority strip shows 0-3 urgent cards (access code changed, new dispatch) — invisible when nothing needs her. Timeline below shows tasks in order with drive times and guest-arrival markers.
Why timeline over a feed? Shows the shape of the day — order, drive time, guest urgency. A flat list can't. Priority strip gives feed-like urgency without dominating.
Revenue-silent. "Early check-in (upsell)" on the task card tells Maria why speed matters — without showing the dollar amount.
James answers "anything I need to act on?" in under 3 seconds. Pulse counts arrivals (guest check-ins), not tasks.
Below the pulse: critical feed (0-5 P0 cards, one-tap actionable), at-risk arrivals with turnover context, collapsed on-track count, departures summary, and aggregate batches (approvals, AI flags).
4-day rolling window. Managers plan in short horizons (validated). Spot Thursday's gap on Tuesday. No "yesterday" on the home.
Exception-based. At 100+ units, on-track collapses to a count. Only problems are shown. Calm when nothing's wrong.
Department-scoped for supervisors. Marcos sees Cleans by default; James sees everything. Same UI, different filter.
The highest-value surface. Every interaction optimized for gloves, one hand, patchy signal, budget phone.
Batch verify is validated behavior. Taskers do the physical work, then click through at the end. We respect this instead of forcing per-item discipline.
Report Issue = bottom sheet. Maria is on item 23 of 75. Navigating away loses her spot. The sheet preserves everything. 35 seconds, zero context loss.
When two options compete, the one that better serves these wins.
% tasks closed within SLA. The operational heartbeat.
In-app prompt + retention. If this drops, nothing else matters.
% work in-app vs. Slack/text
Issue → accepted
Productivity leverage
We've mapped 42 screens across both personas. Open the Screen Atlas, scroll through, type feedback below any screen, then click "Copy all feedback" and paste it in Slack.