Friday night deploy, Saturday morning phones
Your team ships a release late on Friday: a redesigned viewing calendar and some changes under the hood. Saturday is the busiest day of the week for sales branches, full of back-to-back viewings. By nine in the morning, negotiators at several agencies cannot see their afternoon appointments on the mobile app. Your developers are asleep or out. The founder answers support messages from a family event.
On the lettings side the timing can be worse. A change to how payments are grouped goes out on the last working day of the month, just as a letting agency runs its landlord statements and payments. The figures on screen do not match what the accounts person expects, and they stop the run until someone can explain it.
Why agencies feel every release
Agents use your product in the middle of live work, often in front of clients. A change that would be a mild annoyance in an office tool becomes a lost viewing or a delayed landlord payment. Most startups ship the way developers find easiest, and nobody has mapped the agency calendar onto the release plan.
- Releases go to every agency at once, so a fault reaches everyone at the same moment.
- There is no list of the journeys agents rely on most, so testing covers what the developer changed rather than what agents do.
- Rolling back means reverting code and redeploying, which takes a developer and time.
- Release timing ignores Saturdays, month end for lettings, and the spring and autumn peaks in the property market.
- Agencies hear about changes when they see them, with no notice or explanation.
What a bad release costs with agents
One bad Saturday can undo months of goodwill. Negotiators remember the morning they could not find their viewings, and branch managers start asking whether they should keep a paper diary as a backup, which is the start of using your product less. Month-end faults are more serious because they touch money: a delayed landlord payment is an agency's problem with its clients, and it becomes yours immediately.
Your team pays too. Developers learn to fear releases, so they batch changes into larger, riskier ones. The pace of improvement slows exactly when you need it to speed up.
How we build safer releases for agency software
What we build changes how code reaches agencies, without slowing your team down.
- A release calendar built from how agencies work: no releases on Friday afternoons or Saturdays, a freeze on anything touching lettings money in the last days of the month, and caution in peak listing weeks.
- Feature flags, so new features and risky changes are switched on per agency or per branch, starting with a small group who have agreed to see things early.
- Automated end-to-end tests on the journeys agents rely on most: booking a viewing and seeing it on mobile, recording an offer, publishing a listing, running landlord statements. These run before every release.
- Monitoring after release that compares error rates and key actions with normal levels, and alerts if something like viewings booked drops sharply.
- One-step rollback of a release or a flag, which your on-call person can do without a developer's help.
- Short release notes in plain language, shown in the product and sent to agency admins ahead of changes they will notice.
| Agency pressure point | Release rule |
|---|---|
| Saturday viewings | No releases Friday afternoon to Monday morning |
| Lettings month end | No changes to payments or statements in the final days |
| Spring and autumn peaks | Larger changes flagged to early-access agencies first |
| Portal feed changes | Tested against a sample of real listing shapes first |
| Visible screen redesigns | Notice to agency admins before switch-on |
None of this needs a large team. It needs the agency's calendar written into your process, and the ability to switch things off quickly.
A new calendar release, done differently
The redesigned calendar is finished on Wednesday. It goes out behind a flag, switched on for three agencies who asked to see new features early. Automated tests on booking viewings on mobile pass. On Thursday one early agency reports that recurring appointments look odd; the flag is switched off for them in a minute while the fix is made. The following Tuesday the calendar goes to everyone, with a short note to agency admins the day before. Saturday is quiet.
Is your release process risking agency Saturdays?
- You have released on a Friday and spent Saturday fixing it.
- Every release reaches every agency at the same moment.
- Rolling back needs a developer and a redeploy.
- Nobody has written down which agent journeys must never break.
- Agencies find out about changes by seeing them for the first time.