Skip to content
ADVIQ LABS
All insights

Guides3 min read

12 questions to ask before you hire a development partner

Portfolios all look good. These questions reveal how an agency actually works: who writes the code, who owns it, and what happens when things change.

ALBy the Adviqlabs team

Choosing a development partner is one of the most expensive decisions an early-stage company makes. Websites and portfolios tend to look alike. The differences show up in how a team works week to week, and you can uncover most of them with the right questions.

Here are the twelve we'd ask if we were on your side of the table. (We're happy to answer every one of them ourselves.)

About the people

1. Who will actually write the code?

Ask for the roles of the people on your project and whether they're employees, contractors or subcontracted to another company. You want to know who is responsible and whether the people on the sales call are the people doing the work.

2. Will I talk directly to the developers?

Layers of account managers slow everything down and distort requirements. Direct access to the people building your product saves time and misunderstandings.

3. What happens if someone leaves mid-project?

People change jobs. A good partner has code reviews, documentation and shared knowledge so one departure doesn't stall your product.

About ownership and access

4. Who owns the code and the accounts?

The answer should be "you, from day one". Your code should live in a repository under your organisation, and cloud, domain and third-party accounts should be in your name. Be wary of anyone who hosts everything under their own accounts "for convenience".

5. Can I see the repository at any time?

If the answer is anything other than yes, ask why.

About how work happens

6. How often will I see working software?

Weekly demos on a live staging link are a good standard. Monthly updates with screenshots are a warning sign.

7. How do you handle changes to scope?

Scope changes are normal. What matters is the process: are changes written down, estimated and agreed before work starts, or do you find out at invoice time?

8. How do you estimate, and how often are you wrong?

Every estimate is uncertain. Look for a partner who breaks work into small pieces, explains assumptions and tells you early when something is taking longer.

About quality

9. What does "done" mean for a feature?

A good answer includes code review, automated tests for important logic, working on staging, and your approval. "It works on my machine" is not done.

10. How do you handle security and credentials?

Ask how secrets are stored, who has production access, and how access is removed when the project ends. Least privilege and a password manager are the minimum.

About the long run

11. What does handover look like?

Even if you plan to keep working together, ask what you'd receive if you stopped: documentation, architecture notes, deployment instructions and a walkthrough. A partner confident in their work makes leaving easy.

12. What happens after launch?

Launch is the start. Ask about bug fixing, monitoring, dependency updates and how ongoing work is priced.

A few red flags

  • A fixed price quoted before anyone has asked detailed questions about your product
  • Reluctance to share a sample of code or a technical walkthrough of past work
  • No written scope, just a call and an invoice
  • Everything hosted on the agency's accounts
  • Promises of timelines that sound too good to be true

Talking to development partners? Ask us all twelve questions. Book a free call.

Start a project

Have a product in mind? Let's scope it together.

Book a free call. We'll talk through your idea, suggest the leanest path to launch and follow up with a written proposal.