# Ten questions to ask an engineering partner before you sign.

Every vendor says senior, agile and AI-enabled. These are the ten questions that separate them, with what a good answer sounds like and what should worry you.

By Precision Code Studios. Published October 6, 2026. Category: Hiring. https://www.precisioncodestudios.com/insights/questions-to-ask-an-engineering-partner

Hiring an outside engineering team is an odd purchase. You are buying work that does not exist yet, from people you have met twice, at a price set by a proposal written before anyone has looked at your code. The sales calls all sound alike, because every vendor has learned the same vocabulary: senior, agile, AI-enabled, partnership.

Proposals will not separate one firm from another. Questions will. What follows is the list we would use if we sat on your side of the table, with a note on what a good answer sounds like. Put them to every firm you are considering, including us.

## Who will actually do the work

- **Who, by name, will be on my project?** The people on the sales call are rarely the people who write the code. Ask to meet the engineers before you sign, and ask how long each of them has been doing this. A firm that cannot name them has not staffed your project yet, whatever the proposal says.
- **What happens when one of them leaves?** People change jobs, on your team and on theirs. A good answer describes a handover: weeks of overlap, documentation that is kept current, a replacement you get to speak to. A poor answer is that it never happens.
- **How much of the team is learning on this project?** A mix of experience levels is normal and can work well. What matters is that you are told the mix, and that the rate reflects it. You should not discover it from the quality of the first pull request.

## How the work will run

- **When will I first see working software?** Not a design document and not a status report: something you can click. Weeks is a healthy answer. A date several months away means you will find out late whether the project is in trouble.
- **How will I know where things stand on any given day?** You should be able to open the backlog, the code and the test results yourself, in tools you have access to. If the only window into the project is a weekly slide deck, you are seeing what someone chose to show you.
- **Who decides what gets built next?** It should be you, or someone you name. When the vendor sets the priorities, their interest in hours and your interest in outcomes begin to drift apart, slowly and politely.
- **How do you use AI, and who checks its output?** Nearly every team now writes code with AI assistance, and the good ones are faster for it. The question is review: who reads what the tools produce, how it is tested, and whether your code or your data is sent to services you have not approved.

*Figure: A table of the ten questions. For each one, a strong answer is shown beside a warning sign, such as named engineers you can meet versus a promise of "our best people". Print it, take it to the call, and keep score.*

## What you own and what it costs

- **Who owns the code, and where does it live?** Your repository, your cloud accounts and your name on the licences, from the first day. If the work sits in the vendor's accounts until the final payment, leaving becomes a negotiation.
- **What is not included in this price?** Hosting, third-party licences, testing, project management, fixes after launch. None of these is a scandal as an extra, but each one should be visible before you sign and not on the third invoice.
- **What does it cost me to stop?** Ask about the notice period, any minimum commitment, and the handover you receive on the way out. A partner who is confident in the work makes leaving easy, because they do not expect you to.

> **The tell:** Vendors who are good at the work are relaxed about being checked. Reluctance to answer is itself an answer.

## How to read the answers

You are not looking for ten perfect replies. Every firm has a weak spot, and a team that admits one is telling you something useful about how it will behave when the project hits trouble, which every project does. What you are listening for is detail. "We have a rigorous process" is not an answer. "You will have read access to the repository on the first day, and here is how last sprint was reported on another project" is one.

Notice which answers the firm is willing to put in writing. Staffing, ownership and exit terms belong in the contract, not in the memory of a pleasant call. If something was promised out loud and is missing from the paperwork, ask for it to be added, and watch how the request is received.

Notice, too, how the questions themselves land. Some firms welcome them, because a careful buyer usually makes a good client: clear about what they want, quick with decisions, hard to disappoint by surprise. Others become vague, or hand you back to the sales deck. Both reactions are information you could not have had from the proposal.

## When the answers are close

Sometimes two firms answer well and the choice is still hard. Then the cheapest test available is a small one. Agree a first piece of work that is short, useful on its own and paid for: a few weeks, one clear outcome, the real team. You will learn more from how that fortnight goes than from any number of reference calls, and so will they. If the firm resists starting small, add that to the scorecard.

## Our own answers, briefly

It would be strange to publish this list and not answer it. We staff senior engineers only, vetted for how they communicate as well as for technical depth. They join your stand-ups and your channels, work in your tools and in your hours, and you direct the work. Staffing is billed at a flat rate, and an inquiry gets a tailored plan back within 24 hours. The longer answers are a conversation, and we would sooner have it with someone holding this list than with someone who is not.

The best time to learn how a partner behaves under scrutiny is before anything depends on it.

## The short film: transcript

Ten questions before you sign: the short version (0:27).

Ten questions before you sign

Who, by name, does the work? The team on the sales call is rarely the team that writes your code. Ask to meet them.

When do I see working software? Weeks is a healthy answer. Months means you learn late that something is wrong.

Who checks what the AI writes? Every team uses AI now. What matters is who reviews it and where your code is sent.

What does it cost me to stop? A partner who is confident in the work makes leaving easy.

Good vendors are relaxed about being checked.
