Running a Startup on a Four-Day Week
A four-day week sounds like a perk only big, profitable companies can afford. In practice, small startups are often better placed to try it, because they can change how they work in a single meeting. This guide shows you how to choose a model, protect your customers, run an honest pilot and decide, with real evidence, whether a shorter week makes your startup stronger.
Key takeaways
- There is no single four-day week. Reduced hours, compressed hours and staggered days each suit different startups.
- Run a time-boxed pilot with clear success measures agreed before you start, not after.
- Protect customers first: publish coverage rules, response times and an on-call plan for urgent issues.
- Cut wasted work before you cut days. Meetings, handoffs and unclear priorities are where the time usually goes.
- Employment rules on hours, pay and leave vary by country and state, so put the change in writing and check local law.
Founders usually come to the four-day week to fight burnout or to win candidates from larger, better-funded rivals. Both reasons are valid, but a shorter week that quietly hurts customers or slows the roadmap will be reversed within months, and that reversal costs more trust than never trying. The good news is that you can test it carefully, with a clear design and a few honest metrics. A quick note before we start: this article is general information about working patterns, not legal or employment advice. Rules on working time, pay and contracts differ between the US, the UK and European countries, so talk to an employment lawyer or HR adviser before you change anyone's terms.
What a four-day week can mean
When people say "four-day week," they can mean very different arrangements. Pick your model on purpose, because each one changes cost, coverage and contracts in its own way.
Reduced hours, same pay
Everyone works four normal-length days and keeps their full salary. This is the version most people picture, and the one that asks the most of your productivity. It only works if the team genuinely gets the same results in less time, which usually means removing work rather than squeezing it.
Compressed hours
People work their usual weekly hours across four longer days. It costs nothing in salary, but long days can be tiring, and in some places rules on daily hours, breaks and overtime may apply. It suits teams with deep, focused work more than teams handling a steady flow of customer requests.
Staggered or rotating days off
Each person works four days, but the day off varies, so the company stays open five days a week. Half the team might take Monday and half Friday. This is often the most practical choice for startups with customers who expect replies every weekday.
Seasonal or partial versions
Some teams try a shorter week only in summer, or every other Friday off. If you are planning in May, a June to August pilot is a natural, low-risk start.
Pro tip
Write your chosen model in one sentence and share it before anything else, for example: "From 7 June, everyone works Monday to Thursday, full pay, with a rotating Friday support shift." Most confusion in four-day week trials comes from people imagining different versions of the same idea.
Is your startup ready for a shorter week?
A shorter week magnifies whatever is already true about how your team works. Clear priorities make it easier; constant urgency makes it harder. Weigh the pros and cons honestly.
Why it can work
- A strong reason for candidates to choose you over larger employers
- More rest, which can mean fewer mistakes and better decisions
- Forces you to drop low-value meetings and busywork
- Small teams can change habits quickly and see results fast
Why it can struggle
- Customer-facing roles need cover, which is hard with a tiny team
- Deadlines from customers or investors do not shrink with your week
- Founders often keep working the fifth day, which undermines the culture
- Hard to reverse without disappointing people
Three questions help you decide. Can you name the work that would stop if everyone had one less day? Do you have at least two people who can cover each critical function, such as support or production systems? And is the company stable right now, rather than mid-fundraise or mid-launch? Founders should also agree whether they take the day off too, because if they keep working five days, the team will feel pressure to do the same.
Cut the waste before you cut the day
The teams that make a shorter week work rarely do it by typing faster. They do it by removing work that never needed doing. Spend two weeks before your pilot auditing time.
- Meetings. Cancel recurring meetings that exist only for status updates and replace them with a short written update.
- Handoffs. Notice where work waits for someone else, and fix it with clear ownership.
- Interruptions. Agree on focus blocks and a clear route for anything truly urgent.
- Priorities. Work that does not move a current goal is the first candidate to drop.
- Tools. A couple of weeks of time tracking with Toggl Track, Harvest or Clockify can reveal surprises; check current features, pricing and privacy policies, and tell the team why you are doing it.
Common mistake
Announcing the four-day week first and figuring out the work later. When the team has not agreed what to stop doing, people quietly work on their day off to keep up, and you end up with a five-day workload squeezed into four days plus resentment. Do the audit first.
How to run a four-day week pilot
A pilot gives everyone permission to experiment without promising forever. It also gives you clean data for the decision at the end. Here is a straightforward way to run one.
- Set the length. Choose a fixed period long enough to get past the novelty, often around three months. Put the start and end dates in writing.
- Choose your success measures. Pick a small set of numbers from three areas: output (such as features shipped or deals closed), customers (such as response times and satisfaction) and people (such as a short wellbeing survey).
- Record a baseline. Measure the same numbers for the months before the pilot so you have something to compare against.
- Design coverage. Decide who is reachable on each weekday, how urgent issues reach someone and what customers will be told.
- Agree the ground rules. Is the day off truly off? Can people swap days? What happens in a week with a public holiday? Write it down.
- Check in midway. Hold a short review halfway through. Fix coverage gaps and workload problems rather than waiting for the end.
- Decide together. At the end, review the numbers and the team's feedback, then choose to continue, adjust or stop. Share the reasoning openly.
Hypothetical example
Imagine Lena runs a nine-person software startup selling to small accounting firms. She picks staggered Fridays and Mondays off, keeping support open five days. She cancels two weekly status meetings first. Her success measures are the number of releases per month, first reply time on support tickets and a five-question monthly team survey. After three months, releases hold steady, first reply time is unchanged and survey scores rise. Two engineers admit they still checked messages on their day off, so she adds a clear "no replies needed" rule and continues the arrangement for another quarter.
Keeping customers happy with fewer days
Customers do not care what your week looks like. They care whether you answer, deliver and fix things when they break. Plan coverage before the first short week, not after the first complaint.
List every customer touchpoint, from the support inbox to production alerts, and decide who covers each one on each weekday. If you sell to businesses, check any service-level commitments in your contracts too.
A simple coverage plan template
Copy this table into a shared document and fill in one row per function. The names and times below are made-up examples.
| Function | Covered Mon to Thu by | Covered Fri by | Target response (example) | Urgent route |
|---|---|---|---|---|
| Customer support inbox | Priya, Sam | Rotating support shift | Same business day | On-call phone for outages |
| Sales demos | Jordan | No demos booked | Within 1 business day | Founder by email |
| Production systems | Engineering team | On-call engineer | Within 1 hour for outages | Alerting tool to on-call |
Then tell customers what to expect with a short note on your support page, such as "We reply Monday to Friday, and urgent issues are always covered." Block days off in booking calendars so demos never land on them.
Measuring whether it is working
Feelings matter, but they should not be your only evidence. Decide on your measures before the pilot so nobody can be accused of choosing numbers to fit a preferred answer.
- Output measures. Track the work that matters to the business, such as releases, qualified leads, closed deals or projects delivered. Compare with the same period before the pilot, allowing for seasonal swings.
- Customer measures. First reply time, resolution time, satisfaction scores and churn. A rise in complaints is an early warning.
- People measures. A short anonymous survey on energy, stress and focus, plus sick days and any resignations.
- Hidden work. Ask directly how often people worked on their day off. If the honest answer is "most weeks," the workload has not really shrunk.
If your startup sets OKRs, typically quarterly, a pilot lines up neatly with one quarter. When you report to investors, frame it as an operating experiment with measures and a review date, and share the results either way.
Contracts, pay and policy basics
A change to working days is a change to how people are employed, so treat it with the same care as any other policy. The details depend heavily on where your team is based.
- Put it in writing. Whether the arrangement is a trial or permanent, write down the model, the dates, the pay and the review point. In many places, changing contractual hours or pay needs agreement and proper notice.
- Pay and overtime. Compressed hours can raise overtime and break questions for hourly or non-exempt US staff. Check federal and state rules first.
- Holiday and leave. In the UK and much of Europe, leave is often counted in days or hours, so a shorter week may change the math. Set a rule for bank holidays, such as the UK spring bank holiday on 31 May 2027.
- Remote and hybrid rules. If people work remotely, a good remote work policy should already cover hours, equipment, data security and expenses. Update it so it reflects the new pattern.
- Contractors. Freelancers and contractors set their own hours, so be careful not to dictate their schedule in a way that blurs the line with employment.
Employment law varies by country and sometimes by state or region, so treat this list as a starting point and check the official guidance where your people work.
Your four-day week action checklist
- Choose one model and describe it in a single sentence
- Audit meetings, handoffs and interruptions for two weeks
- Agree on what work will stop or shrink
- Pick output, customer and people measures and record a baseline
- Build a coverage plan for every customer touchpoint
- Write the pilot rules, dates and pay terms and check local employment law
- Tell customers what to expect and update booking calendars
- Hold a midway review and fix problems quickly
- Decide to continue, adjust or stop, and share the reasons with the team
Frequently asked questions
Is a four-day week realistic for a very early startup?
It can be, especially with staggered days that keep you open five days a week. The bigger risk is the stage of the company. During a launch, a fundraise or a crunch with a key customer, it is usually wiser to wait until things settle and then run a pilot.
Should salaries drop with a shorter week?
That depends on the model you choose. Many trials keep pay the same and expect the same results, while compressed hours keep both pay and total hours unchanged. If you plan to reduce pay or hours, take legal advice, because that is a significant change to employment terms.
What if one role cannot work four days?
Some roles, such as solo support or operations, may need a different arrangement, like a rotating day off, time off in lieu or a later start. Fairness matters, so explain the reasons and look for an equivalent benefit rather than leaving that person out entirely.
How do we end the pilot if it is not working?
Share the data honestly, thank the team for trying and explain what you learned. You might keep some of the improvements, such as fewer meetings, even if you return to five days. Because the pilot had a fixed end date, stopping is a planned outcome, not a broken promise.
Related reading
The bottom line
Running a startup on a four-day week is less about the calendar and more about how clearly your team works. Choose a model on purpose, remove wasted work first, protect customers with a written coverage plan and measure results against an honest baseline. Then let the evidence, not enthusiasm, decide what happens next.
If the timing is right, block an hour this week to draft your one-sentence model and your success measures. A summer pilot could give you clear answers by early autumn, and either way your team will learn something useful about how it spends its time.
