mh studio Book a free call
← All work
HR and payrollHospitalityFictional client

crewday

Rotas, payroll and tips for small hospitality teams. A manager web app, a staff mobile app and a website, all working.

Role
Solo designer, end to end
Deliverables
Web app, mobile app, website
Benchmarks
Gusto, Deel
Style
Soft and friendly
01

The brief

Crewday helps cafés, bars and restaurants with 8 to 40 staff run their week. In the brief, managers juggle a spreadsheet rota, a payroll provider and a group chat. Staff have no single place to see shifts or pay.

The goal: one product where the rota, clock-ins, tips and payroll feed each other, and a staff app people actually want to open.

Business problem (assumed): small venues trial scheduling tools, then churn when payroll still lives somewhere else and hours get re-typed. Design goal: a published rota becomes clock-ins, and clock-ins become payroll, with no re-typing in between.

Assumptions in the brief, not measured
~5 hrs
a week on rotas and payroll (assumed)
3 tools
spreadsheet, payroll, chat
1 in 4
shifts changed after publishing (assumed)

These figures frame the brief. A real engagement would replace them with interview and rota data before any design decision leaned on them.

Constraints

  • Shared, older phonesStaff use their own phones, often older Android, often with weak signal in basements and kitchens.
  • Payroll must reconcileHours, unpaid breaks, overtime and tips have to add up to the cent on every surface.
  • Concept scopeOne venue, EUR, sample data. No real payroll provider, tax engine or users behind it.
02

What I owned

A self-initiated concept, framed as a client brief so the decisions have real stakes. I worked solo, so everything below is mine, including the parts a real team would share.

Owned
  • Problem framing and the assumptions list
  • Information architecture for three surfaces
  • All UI: manager web app, staff app, website
  • Design system: colour roles, type, components
  • Working prototypes, built in code
  • Success metrics and targets
In a real team, shared
  • Metrics and pilot design, with the PM and founders
  • Payroll rules, with a payroll specialist
  • Notification and offline sync, with engineering
Not done yet
  • User interviews or usability tests
  • Legal and labour-law review per country
  • Backend, integrations and real payroll runs

Team: solo concept. In a real engagement I would expect a PM, two engineers and a payroll specialist.

Planned timeline for this concept

About 7 weeks, split into five phases. This is how I would plan the work as a real engagement, not a record of time spent.

  1. Week 1
    Discover
    Rota and payroll pain points, personas and the assumptions list
  2. Weeks 2 to 3
    Design
    Shift board, staff app and the rota to payroll flow
  3. Weeks 4 to 5
    Prototype
    Working prototypes of the manager web app, staff app and website
  4. Week 6
    Build
    Design system, offline states and developer handoff
  5. Week 7
    Test and launch
    Usability tests with a manager and staff, then a one-venue pilot plan
03

Two people, two very different days

🧑‍🍳
Sam Carter
Manager, Maple & Co. Café

Persona voice“I just want next week done before Sunday dinner.”

  • Build and publish the rota
  • Keep labour under 30% of sales
  • Run payroll without re-typing hours
☕
Sofia Martinez
Barista, 40 hours a week

Persona voice“Tell me when I work and what I earned. That’s it.”

  • See shifts at a glance
  • Swap shifts without chasing people in the chat
  • Understand tips on her payslip

Personas are assumptions built from the brief, not interview subjects.

04

The manager web app

A floating dock and a full-width weekly shift board, like a wall planner on screen. Try it below.

app.crewday.co
Maple & Co. Café
Schedule
Nov 16 to 22
Wages this week28.2% of sales
€5,493of €5,800 budget
Scheduled hours
322h
Open shifts
3
Overtime alerts
1
TeamMon 16Tue 17Wed 18Thu 19Fri 20Sat 21Sun 22
Open shiftsTap one, then a teammate
Sofia MartinezBarista · 40h
Jake TurnerBarista · 40h
Aisha BrownFloor lead · 40h
Leo KimFloor · 40h
Hannah LeeFloor · 32h
Maya PatelKitchen lead · 50hOvertime
Diego RamosKitchen · 40h
Sam CarterManager · 40h
Hours per day40h48h48h48h56h50h32h
  • 👉 Tap a shift, then an empty day to move it
  • 👉 Tap an empty day to add a shift
  • 👉 Approve Leo’s time off and watch his shifts move to open shifts
  • 👉 Run payroll end to end
Open full screen ↗
05

The staff mobile app

Monday, Nov 16
Hi Sofia 👋
Today's shift
07:00 to 15:00
Barista · Maple & Co. Café

This week

40h scheduled
Mon 16, 7:00 to 15:00
Barista · 8 hours
On with you
MPABSCLK
Maya, Aisha, Sam and Leo

Sofia, a barista, opens the app twice a day: to clock in and to see what she earned. Everything else is one tap away.

  1. 1Drag the knob on Slide to clock in all the way. The shift timer starts.
  2. 2Start a break, then Clock out to see paid time and today’s pay, with the unpaid break taken off.
  3. 3In Shifts, swap Friday with Jake, or open Wednesday to see a swap conflict. You can also pick up the open Saturday shift.
  4. 4Pick two days in Time off and send the request.
  5. 5Open a payslip in Pay: hours, tips and taxes add up to the take-home line.
06

When shifts go wrong

Frontline work happens in basements, on old phones and at 23:00. The happy path is the easy part, so these are the states I designed for first.

Staff app

Offline clock-in

The clock-in is stored on the device with the device time, then synced. Sam sees a small “synced late” tag on the board, not an error, so nobody is marked late for a basement with no signal.

Staff app

Clocking in away from the venue

A soft check, not a block. Hard geofences fail on bad GPS and push people back to paper. An honest “clock in anyway” keeps the record complete and puts the decision with the manager.

Staff app, live in the prototype

Swap conflict

Availability comes from the same rota the manager edits, so the app never offers someone who is already on shift. Picking a busy person explains why and points to who is free, instead of failing after Sam approves.

Manager web app

Payroll mismatch

Payroll cannot be confirmed while a shift has a missing or edited time. The manager fixes it in the row, and every edit is logged with who changed it and why, which is what an accountant asks for later.

The swap conflict is interactive in the staff app above. The other three are designed states, not yet wired into the prototypes.

07

The website

Owners are not software buyers. The site leads with warmth and shows the product working: stickers of everyday moments, an auto-filling rota, a tips splitter and a savings calculator. Proof is framed as pilot goals, not invented testimonials.

crewdayTry it free
Rotas, payroll and tips, sorted before the coffee’s cold.
Open the full website ↗
08

Key decisions

1A floating dock instead of a sidebar

Managers live in one screen, the week. A small dock on the left gives the shift board the whole width, and it reads like a wall planner.

Rejected: A standard left sidebar, as in Gusto and Deel. It costs over 200 px of the width a seven-day board needs, for navigation managers use a few times a week.

2Tap to pick, tap to drop

Dragging is fiddly on a laptop trackpad during service. Picking a shift and tapping a free day is faster and works the same on a tablet.

Rejected: Drag and drop as the only way to move shifts. It is fiddly on a trackpad and unusable with a keyboard or switch access. Drag can come later as a shortcut on top.

3Labour cost always in view

Every change updates the cost bar and the percent of sales, so managers see the effect before they publish the rota.

Rejected: A separate labour report. Managers would see the cost after publishing, when it is too late to change. Known gap: the figure is wages only; an “include employer costs” toggle is next.

4Slide to clock in

A slide gesture avoids accidental clock-ins from a pocket and feels like a small ritual at the start of a shift.

Rejected: A plain tap button. Faster, but pocket taps create false clock-ins that a manager then fixes in payroll. The slide is a native range control, so keyboards and screen readers can operate it (see Accessibility).

5Payroll as three short steps

Review hours, check pay, confirm. Each step answers one question, then ends in a celebration because payday should feel good.

Rejected: One long payroll table with a Pay button. Fast for experts, but it hides the two questions that cause mistakes: are the hours right, and is the pay right.

6Publish with a diff

The brief’s sharpest problem is late changes. Publishing a changed rota first shows who is affected. Each person gets one notification per change and taps Got it, so the manager knows it was seen. Designed, not yet in the prototype.

Rejected: Saving edits straight to everyone’s phone. It feels fast, but silent changes are how a moved shift becomes a missed one.

09

Accessibility decisions

Frontline staff are every age, use whatever phone they own and often read in a second language. These decisions are in the prototypes unless marked as spec.

Slide to clock in has a non-gesture path

It is a native range control with a label, so a keyboard (End key) or a screen reader’s adjust gesture can complete it. The spec adds a tap-and-confirm button when VoiceOver or TalkBack is on.

Colour is never the only signal

Role colours always come with the role name and the shift times on the chip, so the board works in greyscale and for colour-blind managers.

Targets sized for gloves and wet hands

Every control in the staff app is at least 48 px tall, and the main actions sit in the bottom half of the screen.

Motion can be switched off

Confetti, bouncing stickers and sheet animations stop when the system asks for reduced motion. Nothing important is only shown through animation.

Numbers you can check

Payslips and the clock-out sheet show the sum as rows (hours, break, tips, taxes) so people can verify pay without doing maths in their head.

Known issue to fix in v1

White text on the Peach buttons measures about 2.4:1, below WCAG AA. The fix is Ink text on Peach (about 7:1), which keeps the brand colour.

10

Design system

Soft and friendly: warm cream instead of white, round shapes everywhere, one colour per role so a shift is recognisable from across the kitchen. Every colour has one job.

Ink
#2B2118
Text, primary
Peach
#FF8A5B
Staff actions, kitchen
Sunny
#FFC24B
Barista, highlights
Mint
#3CC9A0
Success, floor
Lilac
#B9A6FF
Manager, swaps
Sky
#7CC4FF
Pay and info
Cream
#FFF8EE
Background
Aa
Nunito, 400 to 900. Rounded terminals, friendly at every size.
07:00 to 15:00 · BaristaFloor · 8hKitchen neededManagerPrimary buttonRun payroll
11

What I left out of v1

Scope is a design decision. Each cut keeps v1 focused on one loop: rota, clock-in, payroll.

Multi-venue reporting

The brief is single venues. Roll-ups and head-office permissions would slow the core loop for the people it is for.

Auto-scheduling

v1 copies last week and lets the manager edit. Auto-filling needs real availability and sales data first, and trust comes from seeing the week.

Labour-law guardrails beyond overtime

v1 flags overtime only. Rest periods, maximum hours and under-18 rules vary by country, so they come next with legal review.

Tax filing

Crewday prepares the monthly file for the accountant. Filing itself needs per-country compliance work.

Employer costs in the labour %

The board shows wages as a share of sales. Employer contributions add a lot in EUR markets, so a toggle is first on the v1.1 list.

In-app chat

Swaps, notifications and time off cover what clogs group chats today. A full chat is a product of its own.

12

Success targets

Concept project, not measured. No pilot was run. These are the targets I would agree with a client for a 6-week pilot in three venues.

Target
under 4 min
to build next week’s rota
Baseline (assumed)
About 2 hrs in a spreadsheet
How measured
Rota editor opened to published, median over the pilot
Target
0
missed clock-ins in the pilot
Baseline (assumed)
Paper sign-in, gaps unknown
How measured
Scheduled shifts with no clock-in, per week
Target
3 steps
from approved hours to payday, no re-typing
Baseline (assumed)
Hours re-typed into a payroll provider
How measured
Re-typed fields per payroll run, target none
Target
9 in 10
staff open the app weekly
Baseline (assumed)
Group chat only
How measured
Weekly active staff divided by staff on the rota

Counter-metric: manual edits to clock-in times per payroll run. If edits go up while missed clock-ins stay at zero, the clock-in flow is failing quietly and managers are patching it.

13

Reflection

What I’d change

The slide to clock in. It protects against pocket taps, but it is the one gesture every new starter must learn on day one. I would test it against a press-and-hold button with five baristas before committing.

What was hard

Making the numbers agree across three surfaces. Hours, breaks, tips and take home have to match from the rota to the payslip. An early version of the staff payslips did not add up, which is the first thing a payroll buyer checks.

What I’d test first

The riskiest assumption: staff will open a work app weekly without being told to. Cheapest test: a clickable staff app with one venue’s team for two weeks. Success means 6 of 8 open it unprompted each week.

Hiring a product design lead, or fixing a scheduling product?

I can walk you through the prototypes and the decisions behind them on a short call.

Next project
Draftboard

An AI app builder where every change is a reviewable diff.

View case study →