Questions worth asking a development partner before you start
20 August 2026 · 1 min read · ZiyaCore Technologies
A capabilities page can be rewritten in an afternoon. The way a team answers a few specific questions is harder to costume. You are not looking for bravado. You are looking for whether they can describe the work in a way your own team could hold them to.
What is not in the first release?
Ask them to cut your idea down. A serious partner will remove scope and say why. A weak one will accept the whole list and discover the cuts after the schedule has already been promised to someone else.
Where do the business rules live?
If pricing, permissions, or validation live only in the interface, the next client — a second app, a script, a new hire — will get them wrong. The rules belong on the server. Ask them to point at the module, not the slogan.
What do we receive besides the screens?
A handover is the repository, the environments, the accounts, and a short explanation of how to run and deploy the product. If the answer is “we will hop on a call,” you do not yet have a handover. Calls disappear. Notes do not.
What happens when an integration fails?
Payments, email, and model APIs fail. Ask what the user sees, what is logged, and whether the action can be retried. A team that has not thought about this will discover it in production, with your customers.
Who maintains it, and under what agreement?
Launch is not the end of the work. Ask whether support is included, extra, or simply hoped for. A defined engagement is healthier than a vague promise to “be around.” The same people who built the product should be able to explain how a change gets made three months later.
None of these questions require you to be an engineer. They require the partner to be specific. Specific is what you can manage.
