# How to hire an AI agent developer: a guide with a brief to paste

For the business owner who has decided to pay someone to build an AI agent and is afraid of paying the wrong person. Read it and you can put every candidate through the same three tests, send them all one brief, and finish the fifteen steps owning the code and the data.

[Freelancer or agency?](#freelancer-or-agency-three-tests)

## In short

- Write what the agent does, not the tools it uses.
- Ask every candidate for the same evidence, in the same order.
- Pay for a small discovery first, and own the code from day one.

## Freelancer or agency: three tests

Apply the same three tests to every candidate. 18F, the US government's digital service, says most vendors "will not have enough people 'on the bench'" to commit named staff, and treats turnover of key personnel as a standing risk [1] [2].

| Test | Freelancer | Agency |
|---|---|---|
| Capacity: can they deliver while sick or busy? | One person. If they are ill or busy, the work waits. | An agency can swap people in. |
| Continuity: who can change the agent in a year? | Ask for the repository, a handover document and a second person who has read the code. | The same ask. Make sure the people who know it are named. |
| Dependence on one person | Certain. | Ask who exactly is named and what happens if they leave. 18F caps named staff at two or three. |

## Which fits you

- **A freelancer fits when** you need one narrow, well-specified agent, you start with a short discovery, and the handover is met: the repository is yours and a second person reviews the code.
- **An agency fits when** the agent has to be kept running, or no one on your side is technical enough to judge it. Name the key people in the contract.

## The brief to paste

Everything above comes down to this paragraph. It names what the agent does, not the tools it uses, and it ends with the ask that turns a claim into evidence: one agent they have shipped, and its eval results.

Fill the three brackets and the test, then paste it into a message or a job post. The test comes from step 2 below.

```
We need someone to build one agent that [does X] using [our inputs]. It may [allowed actions] and may not [forbidden actions]. You will build tool calls, orchestration, retrieval if needed, tracing, an evaluation set and guardrails. Done means [the test from step 2]. Show us one agent you have shipped, its repository or a running copy, and its eval results.
```

## The fifteen steps

### Decide

1. **Decide that you need an agent.** Write what a plain automation or a person would do instead. Ask each candidate later: when would you not build an agent? Stop here if a rule-based tool does the job. Anthropic's own advice is to find the simplest solution, which "might mean not building agentic systems at all" [3].
2. **Write the work package.** One page: the inputs the agent reads, the actions it may take and may not take, what done looks like as a test you can run (for example, 8 of 10 sample cases handled acceptably), your data and who owns it, the timeline, the budget, and who on your side takes part each week. Carnegie Mellon's course on managing outsourcing teaches this as the work package [4].
3. **Write the brief by the agent and its actions, not by frameworks.** Duties to paste if it is a hire: tool calling, orchestration, retrieval, tracing, evaluation and guardrails. Those are the duties a published job description lists for the role [5]. The brief is above.
4. **Set your criteria and weights before you look at anyone.** Include a running system you can inspect, an eval set, a failure story, and a straight answer to step 1. A decision matrix, as taught in Georgia Tech's vendor selection course, keeps you from reweighing after you meet someone you like [6].

### Find

5. **Collect candidates from at least three places.** A marketplace, an agency list, a referral. Treat every skills list and agency page as a claim: marketplace profiles can say "77% better RAG accuracy" with no evidence beside it [7].
6. **Ask each for evidence, in this order.** First, links to two or three source code repositories, or a running system they can show [1]. Second, the eval set and pass rate for one shipped agent. Third, one agent that failed in use and what they changed. Fourth, a one-to-two page plan; 18F caps proposals at 5 to 10 pages.
7. **Have them explain one shipped system, then change it with you watching.** Ask them to walk you through a system they shipped, then ask for one small change to it while you watch [8].
8. **Check the vendor is real.** Gartner estimates that only about 130 of the thousands of agentic AI vendors are real, and calls the rest "agent washing" [9].

### Choose

9. **Pay for a short discovery first.** Award it to one or two candidates and continue only with the one that shows it can deliver. This is the UK government's guidance for buying agile work [10].
10. **Choose the contract by how well you can specify the work.** Well-specified, repeatable work suits a fixed price or fixed-price sprints; exploratory work suits time and materials with a ceiling and a demo every cycle [4].

### Contract and pay

11. **Own the code and the data from day one.** Put delivered code in a repository you own. Get the rights assigned to you in writing before the first payment, and have a lawyer read the wording. In Canada the author is the first owner of a work, only an employee's work in the course of employment goes to the employer, and "no assignment or grant is valid unless it is in writing signed by the owner" [11]. So a contractor owns what they write until they assign it.
12. **Pay against deliverables, not process.** GOV.UK says to "avoid basing payment milestones on the delivery of the agile process itself" [10].

### Run and close

13. **Manage by demonstration.** A working demo each cycle rather than a written report, your own named person in the loop, and handover documents [2].
14. **Close out or correct.** If the supplier is not performing, act early, and do not wait for the end of a cycle [4].
15. **After delivery, monitor the agent.** Someone on your side owns watching it. Brown University's course on buying AI adds ongoing monitoring as a step [12].

## Look at your own plan

Private. There is no score.

- ☐ I can say in one sentence what the agent would do for me.
- ☐ I know what I would do if a plain tool did the job.
- ☐ I have a test I could run to know it is done.
- ☐ I know who on my side would watch it each week.
- ☐ I would own the code and the data.
- ☐ I have three candidates to ask.

## A second pair of eyes on your brief

Two ways to use the brief you just wrote. The first costs an email: send it to Mackenzie for a second pair of eyes before any stranger sees it. The second is to notice that the job in your first bracket may be one a [sprint](/offers/ai-setup-sprint) takes on - booking replies, meeting notes, receipts, scheduling - in which case there is no hiring process to run. Mackenzie builds the one job end to end on your own accounts within a week, with about two hours of your time, and you finish with the handbook, the client-data sheet and the fix-it guide. If the job isn't running on your real work by the end of the week, you don't pay the balance.

[Email Mackenzie your brief](mailto:mackenzie@mackenziebowes.com?subject=My%20agent%20brief)

Or write to mackenzie@mackenziebowes.com and say what you want the agent to do.

## Sources

1. 18F (US General Services Administration), "Buying development services", archived 20 January 2025. <https://guides.18f.org/derisking-government-tech/buying-development-services/>
2. 18F (US General Services Administration), "Vendor management", archived 20 January 2025. <https://guides.18f.org/derisking-government-tech/vendor-management/>
3. Anthropic, "Building effective agents", 19 December 2024. <https://www.anthropic.com/research/building-effective-agents>
4. Carnegie Mellon University, Software and Societal Systems Department, "Managing Software Outsourcing" executive course page, read 5 November 2026. <https://execed.s3d.cmu.edu/courses/mso.html>
5. jobdescription.org, "AI Agent Developer" job description, last updated 16 May 2026. <https://jobdescription.org/jobs/artificial-intelligence/ai-agent-developer>
6. Georgia Tech Professional Education, "Supply Chain Project Management: Vendor Selection and Management", page read 5 November 2026. <https://pe.gatech.edu/courses/supply-chain-project-management-vendor-selection-and-management>
7. Upwork, "How to hire AI developers", page read 5 November 2026 (a marketplace selling the service). <https://www.upwork.com/hire/ai-developers/how-to-hire/>
8. Hacker News discussion on hiring for AI-assisted coding, item 47722081, read 5 November 2026 (commenters' opinions). <https://news.ycombinator.com/item?id=47722081>
9. Gartner, press release "Gartner Predicts Over 40% of Agentic AI Projects Will Be Canceled by End of 2027", 25 June 2025. <https://www.gartner.com/en/newsroom/press-releases/2025-06-25-gartner-predicts-over-40-percent-of-agentic-ai-projects-will-be-canceled-by-end-of-2027>
10. UK Government, "Contracting for agile: guidance note", Digital, Data and Technology Playbook, updated 20 June 2023. <https://www.gov.uk/government/publications/the-digital-data-and-technology-playbook/contracting-for-agile-guidance-note-html>
11. Government of Canada, Copyright Act, section 13 (ownership of copyright), current to 19 October 2026. <https://laws-lois.justice.gc.ca/eng/acts/C-42/section-13.html>
12. Brown University, "AI Procurement: How to Evaluate and Adopt AI Vendors and Solutions" course page, read 5 November 2026. <https://masterscareers.brown.edu/classes/ai-procurement-how-to-evaluate-and-adopt-ai-vendors-and-solutions/>

---

Published 2026-11-06. Web page: https://www.mackenziebowes.com/hire-an-ai-agent-developer
