{
  "id": 8139606,
  "title": "Why We Banned Hourly Retainers: 4 Engineering Rules That Changed How We Ship Software",
  "url": "https://urgent.news/2026/09/18/why-we-banned-hourly-retainers-4-engineering-rules-that-changed-how",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-09-18T00:59:34.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/shruti-mehta/why-we-banned-hourly-retainers-4-engineering-rules-that-changed-how-we-ship-software-i3b"
  },
  "original_language": "en",
  "account": "In the early days of my career as a software architect, I observed a common problem in the industry. Clients would hire software agencies, only to find themselves frustrated after months of work, having spent most of their budget with little to show for it. This led me to ban hourly retainers and ambiguous retainers at AnyPlace, replacing them with four engineering rules that have improved our delivery speed and client trust.\n\nRule 1: Every 7 days, the client must have working software in their own repository. We enforce a hard checkpoint where the sprint ends with tested pull requests merged directly into the client's private repository. A 20-minute live demo is scheduled to showcase the functionality, ensuring that engineers write modular, deployable code rather than hoarding monolithic code until the deadline. This approach promotes continuous integration of business value.\n\nRule 2: We prioritize fixed scope over open-ended retainers. In the discovery phase, we map data flows, authentication boundaries, and third-party API dependencies. We draft a written architectural specification with strict milestones. Changes to the scope become conscious business trade-offs, rather than passive-aggressive budget creep. This approach ensures that any changes are deliberate and cost-effective.\n\nRule 3: We give the client full custody of all code and assets from day one. We build in the client's GitHub/GitLab organization and provision cloud environments directly inside their accounts. This approach eliminates vendor lock-in and ensures that the client can leave the project at any time, knowing they own everything.\n\nRule 4: We communicate architectural honesty in plain language. When a client asks for complex solutions, we ask if their current traffic volume justifies the operational overhead. We promote resilient, maintainable systems over complex architectures, focusing on finding the most effective path to business value.",
  "summary": "Early in my career as a software architect and technology founder, I noticed a painful pattern recurring across our industry: A client hires a software agency or dev shop. The sales team promises the moon with an estimated \"hourly bucket.\" Two months in, the client has spent 70% of their budget, attended dozens of Jira status calls, and has yet to see a single line of working software running in…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}