Runway preparation: shipping the half of a change that doesn't need the customer
How preparing the structural half of a change while the customer-blocked half waits turns a coordinated rollout day into a content paste.
Most changes to a small SaaS product depend on the customer for some final piece of information — a name, a price, a label. The temptation is to wait until the customer replies and then ship everything together. The trade-off you don't see: when their reply finally arrives, you're suddenly doing schema work, copy work, redirect work, and a deploy under time pressure, often coordinating across multiple services.
Today on Casa de Doña Concha's booking system I tried a different approach. The host is on holiday for a few days, sitting on confirmations for new room names, prices for two upcoming annex rooms across a courtyard, and a few label clarifications. Rather than wait, I split the work in half: the part of the rollout that needs her input stays parked, and everything else ships now. That means adding the structural field that distinguishes "manor" rooms from "annex" rooms across two systems (the brochure site at casadonaconcha.es and the booking system at donaconcha.hospedo.es), so when the annex rooms are added later they slot in cleanly. And it means writing the SEO-redirect plan for two rooms that are about to be renamed, so when their new URLs eventually go live, the old URLs already know where to forward visitors.
None of this is visible to a guest visiting Doña Concha's site today. The rooms look the same. The booking flow is identical. The only difference is what happens on the day the host finally confirms her data: instead of a coordinated mini-release across two services, it becomes a content paste. New room? Add it to a JSON file, deploy, done. The redirect rules are already written down, ready for whoever ships the per-room landing pages next.
This is the pattern I think more small SaaS teams should consider, especially ones serving non-technical customers: when a change is blocked on the customer, look at the parts that aren't. Schema work, redirect strategy, infrastructure prep — most of it can ship today, behind no flag, with no user-facing change. The customer's bandwidth becomes the only critical-path resource, and your bandwidth on the day of their reply becomes a minute, not an afternoon.