Insights · Buying guide

Who actually writes the code, written scopes and fixed quotes, code and IP ownership, demos, communication and the red flags to walk away from. A practical checklist for hiring a development partner.

5 min readBy FocusCode Solutions

Choosing a development partner is hard because most proposals look alike. Every company says it is experienced, agile, transparent and quality-focused. The differences only show up months later, in missed deadlines, surprise invoices or code nobody else can work on. This checklist is designed to surface those differences before you sign.

Use it on every shortlisted company, including us. A good partner will be happy to answer all twelve.

1. Who will actually write the code?

The people on the sales call are often not the people who build your product. Ask directly: who will work on this, what is their experience, and how much of their week will they spend on your project? Senior engineers cost more per hour but typically need far less rework and supervision. Juniors are fine as part of a team, as long as a senior engineer designs the architecture and reviews their work. Ask to speak to the lead engineer before you commit.

2. Can you see and click their past work?

Screenshots and logo walls are easy to assemble. Ask for live products or demos you can actually use, ideally similar in type to yours. Ask what exactly they built on each one, since many projects involve several vendors.

3. Is there a written scope before the price?

A quote without a scope is just a number. A useful scope document lists the user roles, the screens or features, integrations, assumptions, what is explicitly out of scope, and what you are responsible for providing (content, access, approvals). If a company quotes after a ten-minute call without writing anything down, the real price will show up later as change requests.

4. Fixed quote or time and materials, and what happens on change?

Both models are legitimate. A fixed quote suits a well-defined scope and gives you budget certainty. Time and materials suits evolving products where you expect to change direction. What matters is that you know which one you're signing and how changes are handled: how they're estimated, approved in writing, and billed.

5. Are payments tied to working software?

Milestones should be things you can see and test, such as “login and dashboard working on staging”, not “design phase 60% complete”. Be cautious of very large upfront payments. A reasonable advance is normal; paying most of the project before seeing anything removes your leverage.

6. Who owns the code and the accounts?

The contract should assign intellectual property in the code and designs to you on payment. Beyond the contract, make ownership practical:

  • The code lives in a repository under your organisation's account (GitHub, GitLab or similar), with the vendor added as collaborators.
  • The domain, hosting, cloud, email, analytics and app store accounts are registered in your company's name.
  • Credentials and deployment instructions are documented and handed over.
  • Any third-party or pre-existing components the vendor reuses are disclosed, with their licences.

7. Will you see regular demos?

You should be able to click through progress on a staging environment every week or two. Regular demos catch misunderstandings early, when they are cheap to fix. A vendor that goes quiet for six weeks and then reveals everything at once is taking a risk with your money.

8. How will communication work?

  • Who is your single point of contact, and are they technical enough to answer real questions?
  • Which channels (email, Slack, WhatsApp) and expected response times?
  • Which hours overlap with your working day?
  • Will you get written progress updates, and a shared view of tasks?

9. What are their quality practices?

You don't need to be technical to ask. Do they use version control and code review? Do they have a separate staging environment? Do they write automated tests for critical paths such as payments and authentication? How do they handle backups, secrets and security updates? Clear, specific answers are a good sign. Vague ones are not.

10. Are technology choices explained in plain language?

A good team can explain why they chose a stack, and what the trade-offs are, without jargon. Prefer mainstream, well-supported technologies that other developers can pick up later. Be careful with proprietary platforms or in-house frameworks that only the vendor understands; they tie you to that vendor indefinitely.

11. What happens after launch?

Ask about a warranty period for fixing bugs in delivered work, ongoing maintenance options, response times for urgent issues, and who handles hosting, monitoring and dependency updates. Get this in writing before launch, not after something breaks.

12. How do they handle things going wrong?

Every project hits problems. Ask about a project that went off track and what they did. A thoughtful, specific answer tells you more than any portfolio. If possible, speak to a past client, and ask what working with the team was like, not just whether the product shipped.

Red flags to walk away from

  • A price given before anyone has asked detailed questions about your project.
  • No written scope, or a scope with no “out of scope” section.
  • Reluctance to let you meet the engineers.
  • Code, domain or hosting kept in the vendor's accounts “for convenience”.
  • Pressure to sign quickly with limited-time discounts.
  • Promises that everything is possible, on any timeline, at any budget.
  • Most of the payment due before any working software is delivered.
  • No staging environment and no plan for demos.

Questions to ask on the first call

  1. 01Who exactly will build this, and can I speak to them?
  2. 02Can you show me something similar you built that I can use?
  3. 03Will I get a written scope with assumptions and exclusions?
  4. 04Is the quote fixed, and how are changes priced and approved?
  5. 05Will the repository and all accounts be in my company's name?
  6. 06How often will I see working software?
  7. 07What does support look like after launch?

If you're comparing options, we're happy to be on your list. Get in touch and ask us any of the questions above, or use our project estimator to put your requirements in writing first.

Hiring developersOutsourcingSoftware developmentContractsChecklist

Planning something similar?

Tell us what you're building — you'll get a written scope and a fixed quote within 24 hours.

Estimate your project
Taking on new projects this month


Tell us what you're building. You'll get a written scope, timeline and fixed quote within 24 hours — free, with no obligation.

WhatsApp usfocuscode.in.official@gmail.com