Product Strategy

Questions to ask a software agency before you sign, and the answers that should worry you

Questions to ask a software agency before you sign, and the answers that should worry you

Short answer: before you sign with a software agency, ask seven things: can I see a written scope before the price, who owns the code and the accounts, who will actually build it, what happens when the scope changes, how will I see progress, what does support look like in month two, and what happens if we part ways. A good agency answers all seven plainly and in writing.

Most proposals look the same on the surface: a price, a timeline, a list of features. The difference shows up in how an agency answers questions it would rather not be asked. These are the seven we would ask if we were the ones buying, and what a worrying answer sounds like.

1. Can I see a written scope before I see the price?

A scope says what will be built, what will not, and what "done" means for each part. Without it, a price is just a number someone chose. Worrying answer: a fixed price on the first call, with "we will work out the details as we go."

2. Who owns the code, the hosting accounts and the domain?

The answer should be you, in writing, from day one. That covers the source code, the cloud and hosting accounts, and the domain name. Worrying answer: accounts opened in the agency's name, or ownership that only passes to you after a final payment, with no detail on what you get when it does.

3. Who will actually build it, and will I meet them?

The people in the sales call are not always the people writing the code. Ask for the names and roles of the team, and ask to speak with the person who will lead the build. Worrying answer: a team that "will be assigned after signing."

4. What happens when the scope changes?

It will change. Learning something once real people use the product is normal. What matters is how the agency handles it: a written change request with a clear effect on cost and time, agreed before the work starts. Worrying answer: no process, or a promise that everything is "included" that you cannot find in the scope.

5. How will I see progress along the way?

You should be able to see working software early and often, not only at the end. Ask how often you get a demo and whether you can try the product yourself between demos. Worrying answer: weeks of silence followed by a big reveal.

6. What does support look like in month two?

Launch is the part everyone plans for. Month two, when the team's attention has moved to the next client, is where the gaps appear. Ask who answers when something breaks, how fast, and what it costs. Worrying answer: "we will sort that out after launch." If you want the longer version of this one, it is point three in our checklist before hiring an offshore dev team.

7. What happens if we part ways?

Ask this one calmly, before anything goes wrong. A good agency can describe exactly what you receive if the relationship ends: the repository, the documentation, the credentials and the accounts. Worrying answer: any hesitation, or a handover that depends on their goodwill at the time.

How to use these questions

Send them in writing before the next call and compare the answers side by side. The agencies worth hiring tend to answer the same way in writing as they do on a call, and they do not mind being asked. If you already have a proposal and want a second opinion, send it to us. We will tell you what we would ask before signing, even if you decide to go with someone else.

Frequently asked questions

Seven things: a written scope before the price, who owns the code and the accounts, who will actually build it, what happens when the scope changes, how you will see progress, what support looks like in month two, and what you receive if you part ways.

Not by itself. A fixed price before there is a written scope is. The scope says what the price covers; without it the number is only a guess about a project nobody has defined yet.

Ask for the names and roles of the team and ask to speak with the person who will lead the build. If the team will only be assigned after you sign, treat that as a reason to pause.