Explicit acknowledgment checkboxes for workshop dates, scope change costs, and more.

Terms & Boundary Enhancements

Priority: Could Have

Add explicit acknowledgment checkboxes for specific terms that are currently buried in the general T&Cs. Each gets its own confirmation so the client engages with each boundary individually — not one blanket "I accept."

Why This Matters

Deep Work's onboarding had separate acceptance steps for each major term. The current Research Tech flow has a general terms acceptance but doesn't surface specific items like date change fees or scope change costs as individual acknowledgments.

Separate checkboxes force engagement: a client who checks "I understand scope changes cost €1,000+" is harder to negotiate with mid-sprint than one who accepted generic T&Cs.

What to Build

Five enhancements to the agreements page. Each is independent — implement any combination based on the client relationship.

1. Workshop Date Acknowledgment

What: Separate checkbox confirming the workshop date works for the client and all attendees.

Why: Currently just shown in the engagement summary. An explicit checkbox prevents "I didn't realise it was that date" conversations.

Implementation: Add checkbox to agreements page: "I confirm [DATE] works for our team for the workshop."

Deep Work reference: Step 4 — locked collaboration dates with $3,000/day change fee if dates move.

2. Scope Change Acknowledgment

What: Explicit checkbox for scope change terms — changes beyond agreed scope cost €1,000+ per change.

Why: Currently in T&Cs but not highlighted. Surfacing it prevents mid-sprint "can we just add..." requests. The structure says no.

Implementation: Checkbox: "I understand that changes to the agreed scope may incur additional costs of €1,000 or more per change."

Deep Work reference: Section c (Change Requests) — unlimited changes but requotable at $4,000/day workshops, $2,000/day design.

3. Workshop Participant Minimum

What: Require 3+ attendees from the client side. Validation if fewer are listed.

Why: Workshops with 1-2 people lack the diverse perspectives needed for good decisions. Deep Work required this explicitly in their assumptions.

Implementation: In the prep/onboarding flow: "Please confirm at least 3 team members for workshops. We recommend 3+ people to get diverse perspectives on the user journey."

Deep Work reference: Step 3, Assumption 1 — "You'll provide at least three people on the workshop sessions."

Note: May waive for very small teams (2-person startup) — but document the waiver in the engagement summary.

4. Date Change Fee

What: Acknowledgment that changing booked dates after confirmation incurs a fee.

Why: Protects sprint week availability. Once a week is booked, other clients are turned away. Deep Work charged $3,000/day.

Implementation: Checkbox: "I understand that changing confirmed sprint dates may incur a fee of €500-1,000 per day."

Deep Work reference: Step 4 — "$3,000 per day if there is an impact on team's availability or other projects timescales."

Zebra adaptation: €500 for an €8k sprint, €1,000 for €15k+. Proportional to engagement value.

5. Late Payment Penalty

What: 10% late charge for payments past due date.

Why: Ensures timely payment without awkward chasing conversations. Deep Work included this as standard and it prevented most late payment issues.

Implementation: Include in payment terms section: "Payment is due within 10 working days. A 10% late charge applies to overdue payments."

Deep Work reference: Section 9 — "A 10% late charge can be charged for late payments."

Client-Specific Adaptation

Date change fee amount: Scale proportional to sprint cost
Participant minimum: Waive for 2-person startups, but note it in the engagement
Scope change cost: Keep at €1,000+ regardless of sprint price — this is a boundary, not a revenue source
Late payment: Standard across all clients — no exceptions
Workshop date: Always include — this is zero-effort to add and prevents real problems

How It Connects

Deferred features: next-client.md items #2, #3, #4, #5, #6
Deep Work reference: deep-work-upfront-admin-reference.md Steps 3-6 and T&Cs
Current terms: sprint.zebradesign.io agreements page
Methodology principle: "The structure says no" — explicit boundaries protect both parties

These are Could Have because the general T&Cs already cover the legal ground. Surfacing them as individual checkboxes is better practice but not blocking for the next engagement.