As a software development agency, we see a wide variety of projects. Many are inherited from other developers — sometimes another agency, sometimes a freelancer, and increasingly the client's own attempts using "vibe coding." Some even originate from our own team, from a previous iteration delivered months or years earlier.

A surprising (and frustrating) amount of time is often spent just getting started: setting up a local development environment, figuring out how deployment works, and understanding how the application is wired together. Which third-party services are in use? How does code move from a developer's IDE into production?

Change is the one constant in software development. It will happen — and usually when you need it, you need it now. But if an agency has to spend days reverse-engineering the deployment process and local setup, you lose valuable time (and pay for it).

So what should you demand from your software development agency? What is the minimum acceptable project deliverable?

1. A real, non-generic README

It should clearly specify the third-party services in use, the core technologies involved, which environment variables are required, and how to set up a local development environment. We still see far too many projects that ship with a generic, auto-generated "React" README, which is practically useless.

2. Automated, documented deployment

This is not a high bar today — and frankly, it hasn't been for over a decade. It's not something reserved for startup-land; most modern, developer-friendly tooling supports it out of the box. And just as important: the deployment automation must be documented.

A professional team will often go further — adding automated testing in continuous integration, documentation for AI agents, and more. But the two points above are the bare minimum. In today's software landscape, they should not be negotiable.

If you want software that's built to evolve, not stall, we can help.