Why does Varstatt use weekly retainers instead of sprint-based contracts?

Weekly billing changes how work actually flows. Instead of planning two-week or three-week sprints, work comes in, gets prioritized, gets executed, then ships. There's no artificial boundary where you're waiting for the next sprint to start or cramming things into an arbitrary cycle. The rhythm matches reality instead of a calendar.

This matters for responsiveness. Something urgent mid-week doesn't wait for sprint planning next Monday—it gets added to the queue and surfaces based on priority. Clients see faster iteration and I see clearer signal about what actually matters. You're not negotiating scope within a time box; you're managing a continuous queue of ranked work.

It also makes pausing honest. Since billing is weekly and work is continuous, a client can pause for a month or cancel entirely without renegotiating contracts. Billing stops immediately. This removes the awkwardness of "we want to pause but you'll charge us through the sprint end," and it means clients don't pad scope to feel like they got their money's worth.

The trade-off is accountability on both sides. The client has to maintain the queue and prioritize clearly. I have to be ready to shift context if priorities move. It's not great for teams that need planning certainty or "predict and deliver" contracts, but for ownership and rapid iteration, it's cleaner than sprints.