--- title: "Brilliant and buried: signs your only developer is overloaded | Fluff Software" description: "Seven signs your only developer is overloaded, why that's a business risk, and practical ways to take the pressure off." url: https://www.fluff.software/guides/brilliant-and-buried/ updated: 2026-10-23 publisher: Fluff Software --- # Brilliant and buried. Seven signs your sole developer is overloaded, why it’s a business risk as well as a people problem, and practical ways to take the pressure off before they burn out or leave. By **Scott Gulliver**, founder of Fluff Software Published 23 October 2026 _Image: A developer working at a desk_ ## Short answer If your one developer is the only person who understands the system, works through a backlog that never shrinks, and never gets to the hard problems, they’re overloaded. That’s a risk to the business as much as to them. The fix is to move well-defined work off their plate and give them a second senior opinion. ## Seven signs 1. **The backlog only grows.** More goes in each month than comes out. 2. **Everything routes through them.** Features, bugs, “quick questions” and access requests. 3. **Holidays are tense.** Something always breaks the week they’re away. 4. **Estimates keep slipping.** Not because they’re slow, but because urgent work keeps interrupting. 5. **The important improvements never happen.** Upgrades, tests and refactoring are permanently “next month”. 6. **They’ve stopped pushing back.** Saying yes to everything is often a sign someone’s too tired to argue. 7. **Nobody else could explain how it works.** If they left tomorrow, you’d be starting from scratch. ## Why it’s a business risk When one person holds all the knowledge, the business depends on their health, their goodwill and their next job offer. A resignation becomes a crisis, and a long illness becomes a frozen product. That’s before you count the features that never ship. ## What helps **Protect their focus.** Agree which work only they should do: architecture, the hardest problems, the parts that need deep context. Everything else is a candidate to move. **Move the well-defined work.** Features with a clear “done”, bug fixes, integrations and design changes can go to another team without your developer losing control of the product. **Get knowledge out of one head.** A second team working in the same codebase spreads understanding naturally, and makes the business less fragile. **Give them a second senior opinion.** Sole developers rarely get their work reviewed. A senior peer to sanity-check decisions is a relief as much as a safeguard. ## Hire, or bring in a team? A second hire takes months and adds one more person to manage. A subscription can take the queue off their plate within a week or two of signing, with senior review included. Many teams do both: the subscription now, a hire later if the workload proves permanent. [How we work with one-developer teams](https://www.fluff.software/for/one-developer-teams/). ## Questions Will our developer lose control of the product? No. They keep ownership of the product and the architecture. We take well-defined work from the queue and every release is reviewed before it reaches you. Can you work alongside our existing developer? Yes. We work in your codebase and repositories, and review it properly before changing anything. ## Keep reading [The real cost of hiring a developer in 2026 Salary, 15% employer NI, pension, recruiter fees and months of hiring time, plus the January 2027 dismissal changes: what a senior UK developer really costs.](https://www.fluff.software/guides/real-cost-of-hiring-a-developer-uk/) [How to clear a software backlog A practical method for getting a software backlog under control: delete ruthlessly, sort by value and risk, break big items down, and protect a steady release rhythm.](https://www.fluff.software/guides/how-to-clear-a-software-backlog/) [How to write a request that ships quickly A simple template for writing feature requests and bug reports your development team can ship fast: the problem, who it’s for, what done looks like, and what to leave out.](https://www.fluff.software/guides/how-to-write-a-good-request/) --- Fluff Software, a senior product team embedded in your business. Book a call: https://www.fluff.software/contact/ or email contact@fluff.software. Agents: see https://www.fluff.software/llms.txt and https://www.fluff.software/AGENTS.md.