alex/rwo-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add Swiss hospitality tip ops pricing model

Browse Source
This commit is contained in:
alex wiesner
2026-04-10 01:35:39 +01:00
parent 30001e0654
commit b9450a027b
1 changed files with 582 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

582
reports/2026-04-10-switzerland-hospitality-tip-ops-pricing-model.md Normal file
View File

@@ -0,0 +1,582 @@
# Switzerland pricing model: hospitality tip ops + verified bank payouts
Date: 2026-04-10
## Executive summary
This memo prices the Swiss hospitality launch shape defined in `reports/2026-04-09-switzerland-hospitality-instant-tip-access-model-stress-test.md`.
The recommended model is a **site-led hybrid workflow pricing structure**:
- a monthly employer fee tied primarily to **sites**
- included usage tied to **active tipped workers**
- included usage tied to **standard payout capacity**
- one-time implementation fees
- an optional instant-payout premium
- group contracting for multi-site operators where appropriate
That is the right shape for Switzerland because it keeps the company positioned as **workflow + controls + reconciliation + payout orchestration**, not as a generic processor, bank account, or worker-fee-driven instant-access app.[3][4][5][7]
### Recommended commercial outcome
Use three public plans with site-led included usage:
| Plan | Monthly fee | One-time implementation | Intended customer shape |
|---|---:|---:|---|
| `Launch` | **CHF 990** | **CHF 3,000** | selective smaller groups, larger independents, and design-partner entry points |
| `Growth` | **CHF 2,250** | **CHF 6,000** | default offer for multi-site restaurant groups, hotel F&B groups, and stronger event/catering operators |
| `Enterprise` | **CHF 4,800** | **CHF 12,000+** | larger multi-site or multi-entity operators, sold selectively |
### Recommended Swiss early-stage ACV bands
Using the model below, the product should produce a plausible Swiss early-stage ACV band of roughly:
- **CHF 15k-18k** first-year value for selective smaller accounts
- **CHF 27k-40k** first-year value for default multi-site accounts
- **CHF 60k+** first-year value for enterprise accounts
Recurring ARR would sit below those numbers because implementation is one-time.
### Bottom line
The company should price Switzerland as a **site-led employer workflow product** for tip operations. It should **not** rely on float, interchange, lending, or worker-fee extraction to make the Swiss model work.[4][5][7][9]
---
## 1. Pricing objective
This pricing model is for **internal strategy / founder decision-making**, not a final external rate card.
### Objective
Set pricing that is:
1. **credible for Swiss hospitality operators**
2. **adoption-friendly for design partners without collapsing discipline**
3. **high enough to support implementation, support, and partner costs**
4. **aligned with the real product thesis**
5. **not dependent on stored balances, float, or lending economics**
### Product assumptions being priced
This memo assumes the Swiss V1 is:
- a digital tip ledger
- a rules engine for allocation, pools, and overrides
- a manager review and approval workflow
- an employee transparency product for earned and payable tips
- a bank-based payout orchestration product via a licensed partner
- a payroll / accounting export workflow
This memo does **not** assume:
- direct custody
- a wallet-first launch
- a processor-style take-rate model on tip volume
- worker-paid instant access as the default commercial posture
- literal per-transaction instant release of every tip
The strongest Swiss version is still:
`fast verified payout after the operational review step`
not:
`stream every tip in real time to a worker bank account`
That distinction matters commercially because the employer is buying trusted operations, not just a faster transfer.[7][9][10]
---
## 2. Benchmark anchors
Hospitality-specific public pricing for `tip ops` software is sparse. The best public anchors are therefore:
- hospitality software and terminal pricing
- Swiss payout-cost benchmarks
- Swiss hospitality labor and operating realities
- the behavioral findings from the hospitality stress test
Where the market lacks clean public tip-tech pricing, this memo separates **fact**, **inference**, and **recommendation**.
## 2.1 Public hospitality software and terminal anchors
| Product or anchor | Public pricing / capability signal | Why it matters |
|---|---|---|
| `Lightspeed Restaurant` Switzerland | Public restaurant POS pricing around **CHF 89 / 159 / 249 per month** for Basic, Core, and Pro tiers on the Swiss pricing page.[1] | Core hospitality software is usually sold in the low hundreds per site. A tip-ops system must justify a higher price through reconciliation, fairness controls, payout workflow, and payroll-adjacent exports. |
| `SumUp` Switzerland | Public POS software shown from **free** up to **CHF 39/month** on the Swiss POS comparison page.[2] | The low end of merchant software is cheap. That increases the need to explain why this product is not a generic terminal add-on. |
| `Worldline` Switzerland | Public merchant material highlights tip prompts, tip distribution, reporting, and payroll integration as part of professional payment systems.[3] | Terminal-layer tip capture is already partially commoditized. If the product only owns the prompt or the payout button, it will be easy to absorb. |
**Fact:** much of the visible hospitality software stack is cheap relative to the workflow pain being solved.[1][2][3]
**Inference:** the company must price and position above the terminal / POS layer, not inside it.
## 2.2 Swiss payout and labor anchors
| Anchor | Public signal | Implication |
|---|---|---|
| `moneyland.ch` | Swiss business-account and transfer comparisons note that local transfer fees can range from **free to around 50 centimes** depending on the bank.[4] | Standard Swiss payouts should be treated as low but non-zero cost. The model should not depend on large standard-payout margins. |
| `Stripe Connect` | Public platform pricing includes **0.25% + fixed fee per payout** and **1% instant payouts** in one reference configuration.[5] | Explicit payout pricing and explicit instant-payout premiums are commercially normal. |
| Swiss FSO wage data | Median gross monthly pay in `accommodation and food service activities` was **CHF 4,734** in 2024.[6] | Worker utility matters, but the product still needs employer ROI through admin reduction, trust, and cleaner close processes. |
**Fact:** standard payout economics are modest; hospitality labor economics are tighter than many other Swiss sectors.[4][5][6]
**Inference:** the business should monetize **software and workflow first**, with payout pricing as a meaningful but secondary lever.
## 2.3 Behavioral and operating anchors from the stress test
The stress test established four important realities:
1. Swiss guests still often prefer cash tips because many do not trust digital tips to reach staff cleanly.[7]
2. Swiss hospitality is a large employer base, but highly fragmented, with GastroSuisse reporting **20,000 members** and **250,000+ employees**.[8]
3. Swiss instant-payment receipt coverage is now broad, but company adoption is still early enough that the product should support same-day or next-day fallback and avoid promising universal instant payout on day one.[9]
4. GastroSuisse says there are **no generally valid rules** for sharing tips across staff.[10]
**Important implication:** the value is not `instant payout` alone.
The value is:
`trusted digital tip operations`
That is why pricing should be anchored on sites, rules, controls, and payout orchestration rather than on tip-event volume alone.
---
## 3. Pricing design principles
### Principle 1: price the site workflow, not the swipe
The product should primarily be sold as:
`site-level tip operations infrastructure`
The operational pain sits at site level:
- pool rules
- shift-close review
- manager approvals
- payout exceptions
- payroll export
- cash adjustments when needed
### Principle 2: keep site first, contract group-level when needed
The core unit should be **per site first**.
But multi-site groups should still be contracted at the **group level** where appropriate. Commercially, that means:
- site-led plan logic
- a single group contract
- pooled included usage where helpful
- one rollout and implementation scope per account
### Principle 3: avoid tip-volume-first pricing
Unlike the commission pricing memo, this memo should **not** use tip-event volume as a headline commercial lever in V1.
Why:
- it makes the product look like a processor
- it points the company toward the wrong identity
- it hides the actual employer value case
- Swiss tip behavior is too uneven to make tip volume the clean public story[7]
Tip-event volume can be monitored internally for margin analysis, but it should not be the main commercial story.
### Principle 4: keep the employer as the primary payer
The strongest Swiss thesis is employer ROI:
- fewer manual reconciliations
- less cash handling
- fewer fairness disputes
- faster shift-close operations
- cleaner payroll / accounting handoff
- higher staff trust in digital tips
That means the employer should remain the primary payer.
Worker-paid instant payout may exist as an optional pass-through mechanism in some accounts, but it should not be the default posture and should not carry the economics.
### Principle 5: standard payout should be cheap and predictable; instant should be explicit
Standard payout should be framed as the normal operating flow:
- scheduled bank payout
- same-day batch where possible
- next-day fallback where needed
Instant payout should be a **clear premium**, not something hidden inside the base plan.
### Principle 6: charge implementation separately
Swiss hospitality operators do not share one universal way to:
- split pools
- include or exclude roles
- handle overrides
- manage cash adjustments
- review and approve payouts
That work is real implementation work, and GastroSuisse explicitly notes that there are no generally valid rules for tip sharing.[10]
That work should not be hidden inside a low monthly price.
### Principle 7: later balance economics are upside only
If retained-balance behavior, stored balances, cards, or incentives are explored later, they should remain partner-led and secondary.
Swiss V1 pricing should work even if workers cash out quickly and retain no balance.
---
## 4. Recommended pricing architecture
## 4.1 Core formula
The recommended recurring price formula is:
```text
Monthly recurring price
= plan fee
+ extra sites
+ extra active tipped workers
+ standard payout overages
+ instant payout premium (if used)
```
This keeps the **site** as the anchor while still protecting margin against accounts with heavier staffing or payout intensity.
## 4.2 Recommended public plans
| Plan | Monthly fee | Includes | Best fit |
|---|---:|---|---|
| `Launch` | **CHF 990** | up to **2 sites**, **40** active tipped workers, **200** standard payouts, **4** manager/admin users | selective smaller groups, larger independents, paid pilots |
| `Growth` | **CHF 2,250** | up to **5 sites**, **150** active tipped workers, **800** standard payouts, **8** manager/admin users | the default Swiss mid-market hospitality offer |
| `Enterprise` | **CHF 4,800** | up to **12 sites**, **400** active tipped workers, **2,500** standard payouts, **20** manager/admin users | larger groups, more control complexity, sold selectively |
### Overage schedule
| Metric | Launch | Growth | Enterprise |
|---|---:|---:|---:|
| extra site | **CHF 450** | **CHF 400** | **CHF 350** |
| extra active tipped worker | **CHF 6** | **CHF 5** | **CHF 4** |
| extra standard payout | **CHF 0.50** | **CHF 0.40** | **CHF 0.30** |
### One-time implementation
| Plan | Recommended implementation fee |
|---|---:|
| `Launch` | **CHF 3,000** |
| `Growth` | **CHF 6,000** |
| `Enterprise` | **CHF 12,000+** |
### Instant payout premium
Model instant payout as:
- **0.75% of instant payout volume** in the base case
- stress test at **0.50%**, **0.75%**, and **1.00%**
Commercially, the employer can:
- absorb it
- pass it through to the worker
- split it
**Recommendation:** the employer should absorb it by default. Worker pass-through should be optional and selective, not the standard posture.
## 4.3 Contract structure
Recommended contract posture:
- **Pilot:** paid 3-month pilot
- **Standard:** 12-month agreement, billed monthly or annually
- **Enterprise:** annual commitment with implementation statement of work if needed
Additional guidance:
- single-site pilots should be taken only selectively
- a single-site account should still pay the full `Launch` minimum unless there is exceptional strategic value
- multi-site operators should still be papered at the group level even when site pricing is the headline logic
**Recommendation:** do not run free pilots. Paid pilots are the cleaner filter for design partners with real pain.
---
## 5. Example customer estimates
These are internal estimates, not quotes.
## 5.1 Example scenario table
| Scenario | Plan used | Monthly estimate | Recurring ARR | First-year value incl. implementation | Implied fee as % of monthly digital tip payouts* |
|---|---|---:|---:|---:|---:|
| 2-site brasserie / casual dining group: 30 tipped workers, 160 standard payouts | `Launch` | **CHF 990** | **CHF 11,880** | **CHF 14,880** | **3.3%** |
| 5-site restaurant group: 120 tipped workers, 700 standard payouts | `Growth` | **CHF 2,250** | **CHF 27,000** | **CHF 33,000** | **2.8%** |
| 6-site hotel F&B group: 180 tipped workers, 950 standard payouts | `Growth` + overages | **CHF 2,860** | **CHF 34,320** | **CHF 40,320** | **2.6%** |
| 4-site event / catering operator: 90 tipped workers, 1,100 standard payouts | `Growth` + overages | **CHF 2,370** | **CHF 28,440** | **CHF 34,440** | **2.6%** |
| 12-site hospitality group: 350 tipped workers, 2,200 standard payouts | `Enterprise` | **CHF 4,800** | **CHF 57,600** | **CHF 69,600** | **2.2%** |
| High-intensity enterprise: 15 sites, 500 tipped workers, 4,000 standard payouts | `Enterprise` + overages | **CHF 6,700** | **CHF 80,400** | **CHF 92,400** | **1.8%** |
\* Monthly digital tip payout-volume assumptions are internal estimates used for sanity checking, not sourced market facts.
## 5.2 Interpretation
### Selective smaller accounts
Selective smaller accounts can still make sense if they are:
- strong design partners
- operationally mature
- card-heavy enough to matter
- likely to expand to more sites
- strategically useful for partner distribution or category proof
But the model should not drift toward low-value single-site hospitality sales.
### Default multi-site accounts
This is the strongest early band.
Why:
- enough operational pain to justify workflow software
- enough site count to support real ACV
- enough staff and payout activity for the product to matter
- still small enough for disciplined founder-led selling
### Enterprise accounts
Enterprise should be sold selectively.
It can produce real ACV, but it also creates risks:
- longer sales cycles
- heavier implementation effort
- product distraction
- bad services economics if heavily customized
---
## 6. Full sensitivity tables
## 6.1 Assumptions for sensitivity modeling
These are directional internal assumptions:
| Usage level | Active tipped workers per site / month | Standard payouts per site / month | Assumed monthly digital tip payouts per site |
|---|---:|---:|---:|
| Low | 15 | 80 | CHF 7,500 |
| Base | 25 | 150 | CHF 15,000 |
| High | 35 | 250 | CHF 25,000 |
## 6.2 Price sensitivity by site pack and usage intensity
| Account size | Low usage | Base usage | High usage |
|---|---:|---:|---:|
| **2 sites** | **CHF 990 / month** | **CHF 990 / month** | **CHF 1,320 / month** |
| **5 sites** | **CHF 2,250 / month** | **CHF 2,250 / month** | **CHF 2,555 / month** |
| **12 sites** | **CHF 4,800 / month** | **CHF 4,800 / month** | **CHF 5,030 / month** |
## 6.3 Effective fee as % of monthly digital tip payout volume
This is not how the product should be sold, but it is a useful internal check.
| Account size | Low usage | Base usage | High usage |
|---|---:|---:|---:|
| **2 sites** | **6.6%** | **3.3%** | **2.6%** |
| **5 sites** | **6.0%** | **3.0%** | **2.0%** |
| **12 sites** | **5.3%** | **2.7%** | **1.7%** |
### Interpretation
- low-volume accounts are expensive on an effective take-rate basis
- that is acceptable because the product is **not** a commodity payout rail
- the model gets more attractive as site density, worker density, and payout intensity rise
- this supports focusing GTM on operators with real tip-ops pain, not on tiny low-complexity venues
---
## 7. Estimated unit economics and gross margin
## 7.1 Cost assumptions
Directional recurring-cost assumptions:
| Cost item | Bear | Base | Bull |
|---|---:|---:|---:|
| active tipped worker service / ledger cost | CHF 1.00 | CHF 0.75 | CHF 0.50 |
| standard payout cost | CHF 0.25 | CHF 0.15 | CHF 0.10 |
| monthly support / success / infra allocation: Launch | CHF 250 | CHF 200 | CHF 150 |
| monthly support / success / infra allocation: Growth | CHF 450 | CHF 350 | CHF 300 |
| monthly support / success / infra allocation: Enterprise | CHF 800 | CHF 600 | CHF 500 |
These are directional estimates, not vendor quotes.
Tip-event processing is assumed inside the support / infra allocation rather than priced publicly as a separate commercial lever.
## 7.2 Gross margin on included plan usage
| Plan | Bear case margin | Base case margin | Bull case margin |
|---|---:|---:|---:|
| `Launch` | **65.7%** | **73.7%** | **80.8%** |
| `Growth` | **64.4%** | **74.1%** | **79.8%** |
| `Enterprise` | **62.0%** | **73.4%** | **80.2%** |
### Interpretation
- the model can support a blended recurring gross margin in roughly the **70-80%** range if implementation is charged separately and standard payout costs stay reasonable
- this is lower than pure software, but healthy for a workflow product with payout orchestration inside it
- if standard payout costs land materially above the base case, the company should protect margin through plan minimums and explicit instant-payout pricing rather than by cutting software pricing
---
## 8. Discounting and design-partner rules
## 8.1 Recommended default posture
- discount **implementation** before discounting recurring fees
- preserve the **site minimums**
- keep standard-payout and instant-payout pricing mostly intact
- prefer short, explicit pilot concessions over permanent price erosion
- use single-site exceptions only where the account has clear rollout or partner value
## 8.2 Design-partner offer
Recommended default design-partner offer:
- paid 3-month pilot
- choose **one** of these:
- **50% off implementation**, or
- **20% off the first 3 months of platform fees**
- usage fees billed normally
- named operational stakeholder commitment
- monthly feedback sessions
- reference rights or case-study cooperation if successful
## 8.3 Floors and guardrails
### Do not do this
- no free pilots
- no worker-fee-led default pricing
- no tip-volume-first public pricing
- no deep site-fee erosion to win tiny venues
- no promise that future float, cards, or lending will subsidize the core product
### Suggested floor
Absent exceptional strategic value, avoid deals below roughly:
- **CHF 10k recurring ARR**, or
- **CHF 13k first-year value**
That floor matters because hospitality onboarding and rules configuration can become service-heavy quickly.
---
## 9. What not to optimize for in V1 pricing
## 9.1 Do not optimize for tip volume as the public story
Tip volume matters internally for margin analysis.
But the company should not sell the product as:
`we take a cut of tips`
That would point the business toward the wrong identity and weaken the employer workflow case.
## 9.2 Do not optimize for worker-fee extraction
The Swiss stress test points in the opposite direction:
- tip sizes are meaningful but not giant[7]
- trust and fairness matter a lot[7]
- employer pain around reconciliation and payout controls is what closes the sale[10]
So worker-paid instant payout should remain optional, not central.
## 9.3 Do not optimize for stored-balance monetization
If retained-balance or stored-value behavior is explored later, it should stay secondary and partner-led.
Swiss V1 pricing should work even if workers cash out quickly and retain no balance.
## 9.4 Do not optimize for processor identity
If pricing becomes mainly tip-volume-based or payout-fee-based, the company risks being perceived as:
- a processor
- a terminal add-on
- a generic payout tool
That would be strategically wrong for the Swiss hospitality launch.
---
## 10. Recommendation
### Recommended Swiss pricing posture
Sell the Swiss hospitality product as:
`site-led tip operations infrastructure priced as software + controls + payout orchestration`
### Recommended commercial stack
1. **Public plans:** `Launch`, `Growth`, `Enterprise`
2. **Headline unit:** sites first
3. **Secondary recurring levers:** active tipped workers and standard payout usage
4. **One-time fees:** implementation always charged
5. **Premium usage:** instant payout charged explicitly
6. **Design partners:** adoption-friendly, but still paid
7. **Enterprise:** sold selectively
### Why this is the best fit
It is the best fit because it:
- matches the actual hospitality product thesis
- keeps the employer as the economic center
- avoids drifting into worker-fee or processor identity
- produces plausible Swiss early ACVs
- protects margins without relying on float or balance retention
- remains comparable to the Swiss commission pricing memo while adapting the commercial logic where hospitality economics differ materially
### Final judgment
For Switzerland, the right early hospitality pricing model is **not**:
- tip-volume-first pricing
- worker-fee-led pricing
- wallet economics
- processor-style take rates
- free-pilot-led acquisition
It is a **site-led B2B workflow pricing model** with explicit minimums, clear implementation fees, and optional instant-payout premium.
---
## Sources
[1] Lightspeed Commerce, *Tarifs caisse enregistreuse Lightspeed Restaurant*. https://www.lightspeedhq.com/ch/caisse/restaurant/pricing/
[2] SumUp Switzerland, *Point of sale system: compare SumUp POS plans & hardware*. https://www.sumup.com/de-ch/kassensystem-uebersicht/
[3] Worldline Switzerland, *Portable payment terminals*. https://worldline.com/en-ch/home/main-navigation/solutions/merchants/solutions-and-services/terminals/mobile-payment-terminals
[4] moneyland.ch, *Swiss Business Account Comparison 2026* and related Swiss transfer-fee comparisons. https://www.moneyland.ch/en/business-accounts-comparison and https://www.moneyland.ch/en/transferwise-switzerland-questions-answers
[5] Stripe, *Pricing information | Stripe Connect*. https://stripe.com/connect/pricing and https://stripe.com/ae/connect/pricing
[6] Swiss Federal Statistical Office, *Earnings Structure by economic sections* (2024 data). https://www.bfs.admin.ch/bfs/en/home/statistics/work-income/wages-income-employment-labour-costs/earnings-structure/economic-sections.html
[7] Worldline Switzerland, *Majority of guests tip in restaurants* (study commissioned by Worldline, conducted by ZHAW School of Management and Law, survey of 1,179 people in Switzerland, September 2022). https://worldline.com/en-ch/home/main-navigation/resources/newsletters/bargeldloses-trinkgeld
[8] GastroSuisse, *Jahresbericht 2024*. https://jahresbericht.gastrosuisse.ch
[9] Swiss National Bank, *The Swiss National Bank in Brief* (2025) and *Payment Methods Survey of Companies 2025* (2026). https://www.snb.ch/public/asset/en/www-snb-ch/publications/communication/kurzportraet/kurzportraet_19/publications0_en/kurzportraet_19.en.pdf and https://www.snb.ch/dam/jcr:d9e199a4-fda2-4375-b69a-cc904d7e5b98/payment_survey_companies_report_2025.en.pdf
[10] GastroSuisse, *Trinkgeld*. https://gastrosuisse.ch/de/branchenwissen/wissenswertes/a-bis-z/trinkgeld