Before hiring a software development agency, ask about code ownership, realistic timelines, what happens after launch, who you will actually communicate with day to day, where the team is based, and what happens if the project overruns. A vendor that cannot answer these clearly, before a contract is signed, is a real signal worth weighing.

Who owns the code when the project ends?

Ask explicitly whether you receive full source code and repository access on delivery, or only a licence to use the finished product. Some agencies retain ownership or charge separately for source access, which matters enormously if you ever want to switch development partners or bring maintenance in-house later. Get the answer in writing before signing anything, not as a verbal assurance.

This question matters even if you have no current plan to leave the agency you hire. Circumstances change, budgets shift, a relationship that works well today may not work in three years, and a business without access to its own code is genuinely locked into one vendor regardless of how that relationship develops.

What is the realistic timeline, and what could change it?

A credible agency gives a timeline tied to a specific, agreed feature scope, and explains what would extend it, added features, third-party API delays, slow feedback on design reviews, rather than a single fixed number presented as unconditional. If a vendor gives a confident date without first understanding your actual requirements in detail, that confidence is not grounded in anything real yet.

What happens after launch?

Ask specifically what maintenance is included, for how long, and what happens when that period ends: is there a support retainer, an hourly rate for fixes, or nothing at all. Also ask how bugs discovered shortly after launch are handled, since a small number of post-launch issues is normal for any software project, and the answer to who fixes them, and at what cost, should be agreed before launch, not negotiated afterward.

Who will you actually talk to during the project?

Ask whether you get direct access to the developers working on your project, or only a project manager relaying information, and how often you can expect updates. A pattern of vague or infrequent communication during the sales process is a reasonable predictor of communication during the actual build.

Ask specifically what tools communication happens through, a shared chat channel, weekly calls, a project management board you can see directly, and whether that access continues for the full duration of the project or tapers off after the initial kickoff enthusiasm. The gap between how a vendor communicates during the pitch and how they communicate three months into a live build is where a lot of client frustration actually originates.

Where is the team based, and does that matter to you?

Ask directly rather than assuming. Team location affects time zone overlap for calls, and sometimes cost, but a well-run team delivering from anywhere can be a genuinely strong choice. What matters is the agency being upfront about it rather than being vague, since vagueness on a simple factual question is a worse signal than the location itself.

What happens if the project overruns?

Ask how scope changes are priced, whether overruns are billed at the same rate as the original quote or at a different rate, and who decides whether a delay is due to a scope change you requested versus the agency's own estimation being wrong. Getting this answer before signing prevents a difficult conversation happening for the first time under pressure, partway through a live project.

A genuinely fair agency will distinguish clearly between a delay caused by their own underestimation, which is reasonably their cost to absorb, and a delay caused by scope you added mid-project, which is reasonably billable. If a vendor cannot articulate that distinction when asked directly, assume every delay will default to being billed to you.

Checklist

QuestionWhat a good answer sounds like Who owns the code after delivery?Full source and repository access transfers to you on delivery What is the timeline, and what could extend it?A specific range tied to agreed scope, with named risk factors What support exists after launch?A defined period or retainer, clearly priced, agreed upfront Who will I communicate with?Named contact, direct access to the team, agreed update cadence Where is the team based?A direct, specific answer, not a vague or evasive one How are overruns priced and decided?A clear process agreed before the contract is signed How Sheraian answers these

Sheraian is a UK-registered software studio delivering from Pakistan, stated plainly rather than left for a client to discover later. Clients get full source code and repository ownership on delivery, a scoped timeline agreed during discovery with named risk factors, and direct access to the development team rather than only a relayed project manager. Ask Sheraian these exact questions before signing anything, and expect a specific answer to each one, not a general reassurance.

Frequently asked questions

Is it reasonable to ask for references from an agency's past clients?

Yes, and a credible agency should be able to provide them, or explain clearly if a specific client relationship is under a confidentiality agreement that prevents it.

Should I be concerned if an agency is based overseas from me?

Not inherently. What matters is time zone overlap for the communication you actually need, and the agency being upfront about location rather than vague about it. Many strong development teams deliver from a different country than their clients.

How much detail should a timeline estimate include before I sign a contract?

Enough that you understand which specific features are included in the quoted timeline, and what would count as a scope change that could extend it. A single date with no feature breakdown behind it is not a real estimate.

What is a reasonable amount of post-launch support to expect included by default?

This varies by agency and project size, but a short defined period, commonly a number of weeks, covering bug fixes from the original build is a common baseline. Anything beyond that is reasonably a separate, clearly priced arrangement.

Should I be able to speak directly to developers, or is a project manager normal?

Both models exist and can work well. What matters is that the agency is clear about which model they use and that you get enough direct visibility to feel confident in progress, not that one specific structure is inherently correct.

What is a red flag during the sales process itself?

Vague or evasive answers to any of the questions above, pressure to sign quickly before questions are fully answered, or a quoted timeline given before your requirements have been discussed in any real detail.

Can I negotiate code ownership if an agency initially says they retain it?

Sometimes, though it is worth treating a default retained-ownership policy as a signal about how the agency generally operates, not just a single negotiable line item.

Ready to ask these questions of a real agency? Sheraian expects to be asked all six and will answer specifically, not generally. Get in touch and put these questions to us directly.