# Message test — https://www.shiftbase.com/ After reading your page, only 9 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.shiftbase.com/ - **Audience tested against:** Who we are for A business that can only run when the right people are physically on site. Restaurants, shops, hotels, gyms, dental practices. The work is planned in whole shifts, meaning a morning, an afternoon or a full day, and the admin is created by those shifts. They come to us when they professionalise. That can be an ambition to grow, a process that has become too big to run by hand, or a new law that forces the change. At that point the way they work today, spreadsheets and WhatsApp in a small business or a stack of disconnected tools in a bigger one, stops keeping every shift covered and every hour correct. They need one place to plan shifts, track the hours worked, manage time off, and get those hours ready for payroll. The person who feels the pain is whoever owns the schedule and the pay prep. In a small business that is usually the owner. As the business grows, it becomes an operations manager together with HR. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/workforce-software-for-shift-based-businesses-ckoI4eU > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 14/15 | 99% | 14 without hesitation, 1 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 94% | 11 without hesitation, 4 with reservations | | 3. Value | Do they actually want it? | 14/15 | 74% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 9/15 | 56% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 12/15, 67% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Differentiation.** Earliest failing layer, walking the sequence in order — not simply the lowest score. ### What they thought you sell 1 of the personas who named a category got it wrong: - 1× “Shift-based workforce management software” --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Add a multi-site customer story near the case studies naming locations and employee count** Every case study is a single Dutch site, so an operator running twenty locations cannot tell the product holds up at their size. Add one story that states how many sites and employees the customer runs. *effort medium · impact high · tested against Proof next to the claim* **Replace the Blokker reporting quote with a result carrying a number and timeframe** "In the old system it was very difficult to create the right reports yourself" names the old problem but no outcome, so the reader learns nothing about what changed. Say what the customer now gets and how much faster. *effort low · impact high · tested against Specifics beat superlatives* **Add a line under the hero explaining why swaps reach payroll without an export step** "All shift teams need a digital home. This is it." is a claim any scheduling tool makes. Say what Shiftbase does that a scheduling app plus a payroll tool cannot, using the Tuesday-swap-to-Friday-payroll flow as the reason. *effort low · impact high · tested against Give a reason to choose you* ### Clarity **Replace the tab labels "Communicate" and "Analyse" with the job each one does** The tab row reads as navigation, not capability, so a scanner passes it without learning anything. Label each tab with the outcome, as the payroll export line already does. *effort low · impact medium · tested against Front-load the meaning* ### Value **Add a source and sample size under "-30%" and "Avg. satisfaction with Shiftbase"** Both figures float with no basis, so readers treat them as marketing rounding. State who was measured, how many, and when. *effort low · impact high · tested against Proof next to the claim* ### Brand alignment (side metric) **Name the payroll systems Shiftbase exports to beside "Payroll integrations"** "Payroll integrations" is unnamed, and every logo and location on the page is Dutch, so a US or UK reader assumes their payroll provider is not supported. List the actual named integrations under the payroll prep list. *effort low · impact high · tested against Proof next to the claim* **Replace "8,9" and "-30%" with locale-correct formatting and a source line** "8,9" uses a decimal comma and "got their Spark back" reads as translated copy, which makes English-language readers think the page was not written for them. Fix the number format and the phrasing. *effort low · impact medium · tested against Plain language* --- ## 03 · What is working ### The swap-Tuesday-updates-Friday-payroll-export example is the line that makes the… Eight respondents singled out the specific scheduling-to-payroll data flow example as what made the value prop legible, calling it better than a feature list and a concrete demonstration of the integration mechanism. > The line "a swap on Tuesday still shows up in Friday's payroll export" actually tells me what it does better than the feature list does. > > — Restaurant Manager, Hospitality, 11-50 > Scheduling, worked hours, time off, and pay prep sit in one place, so a swap on Tuesday still shows up in Friday's payroll export > > — Business Owner, Hospitality, 11-50 > a swap on Tuesday still shows up in Friday's payroll export > > — Restaurant Manager, Health and Wellness, 201-500 > a swap on Tuesday still shows up in Friday's payroll export > > — Shift Supervisor, Food and Beverage, 1-10 ### The hero line names the problem and the buyer fast enough to be understood before… Six respondents said the headline stated problem and solution in one sentence and identified shift-based operators and their pain points plainly, without requiring inference. > That "swap on Tuesday still shows up in Friday's payroll export" line right up top nails the problem — spreadsheets and WhatsApp groups for shift teams that don't talk to payroll > > — Restaurant Manager, Hospitality, 11-50 > the hero line "Scheduling, worked hours, time off, and pay prep sit in one place, so a swap on Tuesday still shows up in Friday's payroll export" tells you the problem (payroll errors from messy scheduling/swaps) and "Get your team off WhatsApp" tells you exactly what they're replacing > > — HR Manager, Food and Beverage, 1-10 > the row of icons (Schedule, Track time, Absences, HR, Communicate, Payroll prep) tells you this is shift-scheduling software for shift-based operations before you've even scrolled > > — Restaurant Manager, Health and Wellness, 201-500 > the hero line "All shift teams need a digital home" plus "Get your team off WhatsApp" told me the problem (scattered scheduling via spreadsheets/WhatsApp, hours not reaching payroll cleanly) and the buyer (shift-based businesses) within seconds > > — HR Manager, Retail, 51-200 > "Get your team off WhatsApp" and "Spreadsheets aren't built for scheduling. Shiftbase is." tell you the problem in seconds, and the industry tiles (Restaurant, Hotel, Retail, Healthcare, Transport, Production) spell out exactly who it's for without me having to infer it. > > — Business Owner, Health and Wellness, 201-500 > Obvious fast — headline "get your team off WhatsApp," scheduling/payroll for shift teams. > > — Restaurant Manager, Hospitality, 11-50 --- ## 04 · What the personas said ### Feature tabs and surrounding copy read as generic SaaS navigation until the payroll… Two respondents said the feature list and tab labels used generic language and read like navigation before the copy explained anything, with the payroll export detail the first concrete item. > the only soft spot is the feature list itself ("Communicate," "Analyse") which is generic SaaS-speak until you hit the concrete lines like the payroll export sentence > > — HR Manager, Food and Beverage, 1-10 > the only friction was the feature-tab labels up top (Schedule, Track time, Absences, HR, Communicate, Analyse, Payroll prep) reading like a nav bar before the copy underneath explained what each one actually did > > — HR Manager, Retail, 51-200 ### Advertising auto-scheduling and chat as beta or early access turns them into liabilities Four respondents discounted auto-scheduling as unproven against complex multi-site operations, and one said they would not beta-test a chat feature against WhatsApp, which already works. > auto-scheduling (still "early access") actually run against our real shift complexity — without that it's a maybe, not a yes. > > — Operations Manager, Health and Wellness, 201-500 > the "-30% less time on time tracking" and "8.9 avg satisfaction" numbers have no source or sample size attached, and the auto-scheduling feature is explicitly "in early access," > > — Shift Supervisor, Food and Beverage, 1-10 ### Statistics on time savings and satisfaction are not believed because no source or sample… Four respondents flagged the proof points as unsourced and lacking sample-size transparency, which undercut their credibility. > the only hard numbers on the page — "-30% less time on time tracking" and "8,9 avg satisfaction" — have no source, sample size, or methodology attached, so I can't tell if that's from three customers or three hundred. > > — Operations Manager, Health and Wellness, 201-500 > I'd want the -30% time-on-time-tracking and 8.9 satisfaction numbers sourced — sample size, whether it's self-reported, whether it's from businesses my size — before I believed them > > — Business Owner, Hospitality, 11-50 > the "-30% less time on time tracking" and "8.9 avg satisfaction" numbers have no source or sample size attached, and the auto-scheduling feature is explicitly "in early access," > > — Shift Supervisor, Food and Beverage, 1-10 ### The proof shown is single-site and metric-free, so larger and multi-site prospects… Two respondents said the case studies skew to single-site owners and the retail case study lacks metrics and sizing comparable to their own operation. > the customer stories skew toward single-site owners ("Head Chef and Co-Owner," "Franchise Owner") rather than someone managing multi-site headcount like mine > > — Operations Manager, Health and Wellness, 201-500 > the quote itself, "In the old system it was very difficult to create the right reports yourself," is too thin to close the deal on its own; there's no number, no team size, no before/after > > — Shift Manager, Retail, 51-200 ### The page reads as a Dutch or European company reaching into English-language markets Three respondents read the brand as European-anchored, one noting incomplete localization; separately one said US payroll integrations like ADP, Gusto and QuickBooks would be needed to read as built for the US. > the Dutch names everywhere (Blokker, Alpha Logistiek, Aards Eetbar, Nmbrs, Loket, AFAS) give that away immediately, and it reads like a company that's grown by selling into hospitality, retail and small logistics operations rather than enterprise > > — Shift Manager, Retail, 51-200 > I picture a mid-size European SaaS company, probably Dutch-founded and maybe 10-15 years old, that's grown a solid book of business in hospitality and retail across the Netherlands and is now trying to push into English-speaking markets without fully localizing yet > > — HR Manager, Retail, 51-200 > I'd want a US-specific payroll integration named outright, not just Exact Online lumped in with Nmbrs, Loket and AFAS — if I saw ADP, Gusto, or QuickBooks Payroll listed, that's the line that would make me stop treating this as a European product I have to vet and start treating it as built for me. > > — Shift Manager, Food and Beverage, 1-10 ### Who the product is for is inferred from context rather than stated One respondent said the target audience had to be picked up from context clues instead of being named outright, and another wanted export screenshots to back the integration claim. > The named payroll integrations — "Nmbrs, Loket, AFAS, and Exact Online" — are the one concrete thing that'd move it up the shortlist, because that's specific and checkable against my actual provider, not a vague "integrates with payroll" claim. Everything else that would rule it in or out is missing: no pricing, no named error-handling for a failed sync, and "auto-scheduling is in early access" is a flag against > > — HR Manager, Food and Beverage, 1-10 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **One sentence is carrying the entire page; strip the swap-Tuesday example and nothing else proves the integration works.** *(high)* Eight respondents named that single data-flow line as what made the value prop legible, while feature tabs read as generic navigation until the payroll export detail appeared and two more wanted export screenshots. The page has one asset, not a message. - **Every proof element on the page is dismissible, so the claims rest on assertion alone.** *(high)* Four respondents rejected the time-savings and satisfaction statistics as unsourced with no sample size, and two said the case studies skew single-site and lack metrics. Nothing survives to substantiate the hero promise. - **The page disqualifies itself from the larger accounts it needs, evidencing only the smallest deployments.** *(high)* Two respondents said proof skews to single-site owners with no comparable sizing, and four discounted auto-scheduling as unproven against complex multi-site operations. Scale buyers read two separate signals that this product has not handled their situation. - **Labelling features beta actively subtracts value rather than signalling momentum.** *(high)* Four respondents treated auto-scheduling as unproven and one refused to beta-test chat against WhatsApp, which already works. Unfinished features benchmarked against free incumbents make the paid product look riskier than the status quo. - **US prospects are told, through omission, that this product was not built for them.** *(medium)* Three respondents read the brand as European-anchored with incomplete localization, and one specified that ADP, Gusto and QuickBooks integrations would be required to read as US-built. The payroll export hook is precisely where the gap shows. - **A strong hero is wasted because the page never confirms the reader it attracted is the intended buyer.** *(medium)* Six respondents said the headline named problem and buyer plainly, yet one had to infer the target audience from context clues and feature tabs read as generic SaaS navigation. The opening promise is not held past the first screen. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Restaurant Manager | Hospitality | 11-50 | | 2 | Shift Supervisor | Retail | 51-200 | | 3 | Operations Manager | Health and Wellness | 201-500 | | 4 | HR Manager | Food and Beverage | 1-10 | | 5 | Business Owner | Hospitality | 11-50 | | 6 | Shift Manager | Retail | 51-200 | | 7 | Restaurant Manager | Health and Wellness | 201-500 | | 8 | Shift Supervisor | Food and Beverage | 1-10 | | 9 | Operations Manager | Hospitality | 11-50 | | 10 | HR Manager | Retail | 51-200 | | 11 | Business Owner | Health and Wellness | 201-500 | | 12 | Shift Manager | Food and Beverage | 1-10 | | 13 | Restaurant Manager | Hospitality | 11-50 | | 14 | Shift Supervisor | Retail | 51-200 | | 15 | Operations Manager | Health and Wellness | 201-500 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-09-24, then deleted along with the personas and their answers.