Choose an AI developer arrangement by the work, support and usable handover it provides.
What you'll learn
- Compare a defined project with a continuing technical function.
- Keep quoted fees, salary and employer costs distinct.
- Check documentation, access and actual cover with every route.
- Agree acceptance, changes and support before signing.
Choose the hiring arrangement alongside the shortlist. The contract, handover and actual backup determine what support you can expect when the person who built the system is unavailable. Check those arrangements with an individual or a team.
What are the four ways a small business can hire an AI developer?
Compare a freelancer, an employee, an agency and a provider that takes responsibility for a defined implementation. These are useful buying arrangements rather than mutually exclusive categories: an agency may offer a managed service or use subcontractors. Choose against the continuing work and the responsibility you need, not the label alone.
| Hiring route | Cost basis to compare | Possible fit | Continuity question |
|---|---|---|---|
| Freelance marketplace | Agreed hourly rate or project price, plus applicable fees | Defined work with an owner on your side | Who can maintain the result if the freelancer is unavailable? |
| In-house employee | Local salary plus employer costs, recruitment and supervision | Continuing technical work and internal ownership | Who shares access and knowledge during absence or departure? |
| Boutique agency | Scoped project, support or retainer terms | Related builds with access to different skills | Who actually works on your system and provides cover? |
| Done-for-you implementation | Defined deliverables, acceptance and ongoing support terms | A bounded workflow with agreed operating responsibility | What is included after launch, and how can you hand over? |
Decide whether the need is a project, an ongoing function or both before searching profiles. Write down the outcome, connected tools, required review and likely maintenance. A single workflow may still be commercially important enough to need internal expertise; many workflows do not automatically require an employee if a suitable external arrangement covers them.
What does each hiring route actually cost?
Compare a quote for the same defined work and support, keeping salary, contract fees and total employer costs separate. As of October 2026, goLance's September rate page shows a US$20 hourly median across 369 listed AI developers. Its broader guide quotes US$93–US$160 for experienced freelance AI developers.[1] Those are different populations and publisher estimates, not interchangeable market averages or a price for your project.
Indeed's October 5, 2026 US listing reports US$185,152 average annual base salary for machine-learning engineers, based on about 5,300 salaries from job postings over the preceding 36 months.[2] It is a US occupational posting statistic, not total compensation, a European salary or the cost of maintaining one agent. Obtain local role-specific evidence and add applicable employer and recruitment costs.
Ask agencies and implementation providers for the actual scoped price. Identify discovery, connections, acceptance tests, documentation, review setup and support. A project fee does not automatically include maintenance, nor does an hourly contract necessarily leave the scope uncontrolled. Compare exclusions, change terms, budget limits and responsibility for a failed acceptance test.
For a source-based illustration of hourly arithmetic, goLance's guide uses 100 hours at US$93 an hour: 100×93=US$9,300 before applicable fees.[1] The 100 hours are that publisher's chosen example workload, not a measured duration for an agent build. Replace both hours and rate with a scoped estimate and written quote; add expected changes and support before comparing with a fixed-price offer.
A lower initial total does not settle continuity or quality. Ask what happens if the build needs repair, acceptance fails or another person takes over. Keep uncertain future work visible rather than applying a universal percentage for the cost of a bad hire.
Why is a single developer a single point of failure?
Dependence arises when only one person can access, understand or maintain the system. It can occur with a freelancer, employee or agency. Check documentation, business-controlled accounts, available cover and a usable handover rather than assuming an employment or agency contract removes the risk.
A demo cannot show future availability. Ask for concrete delivery evidence, written support terms, accessible documentation and a named handover route. Where technical review is needed, arrange an independent qualified reviewer for the proposed build.
If the developer is unavailable, another maintainer needs more than the source files. They need access through your approved accounts, a description of the workflow and connections, deployment and recovery instructions, known limitations and acceptance cases. Test that the handover is usable without exposing a former client's confidential material.
Compare the price with the support and handover you can actually use.
An employee can share knowledge with colleagues or a support provider. A freelancer can supply documentation and an agreed backup. An agency can still concentrate all knowledge in a single assigned person. Ask who has actually reviewed the build and what happens during absence, termination or a dispute about scope.
A team can provide cover when more than one person has relevant knowledge and authorized access. Get that arrangement in writing and check it against the work. The provider's headcount alone does not establish that anyone else can operate your particular system.
What should you vet before signing with an individual developer?
Check documentation, availability, a bounded paid assessment where useful and a handover route. Use these alongside relevant work examples and references. Ask the candidate to explain the proposed workflow, failure handling and acceptance evidence in language your task owner can evaluate.
Request a permitted handover example. Ask for a redacted or public example of operational documentation, not confidential client access. Review whether it explains the connections, setup, known limitations, tests and recovery. A sample helps you assess the proposed deliverable; inability to disclose a former client's files alone does not prove poor documentation habits.
Confirm availability and support terms in writing. State expected response arrangements, hours of coverage, rates, limits and what counts as an urgent failure. Ask how changes are requested after launch and who can provide cover. A future promise remains a commitment to assess, not proof that the person will always be available.
Use a small paid assessment before a larger commitment where appropriate. Define a useful deliverable such as a task map, access investigation or acceptance plan. Agree its price, scope, ownership and decision point. Inspect how the candidate resolves uncertain requirements; a short exercise cannot eliminate all delivery risk.
Ask who else could take over. Look for usable documentation, authorized account access and a named person or handover process. Confirm the permissions and responsibilities involved. An individual need not employ a team to supply a workable handover, and a team should demonstrate actual cover.
For an agency, see how to choose an AI implementation partner. For the procedure and decisions to prepare on your side, see before you hire.
Which red flags show up before the contract?
Investigate unclear deliverables, missing acceptance rules, unexplained access demands and undefined support. Rate alone cannot establish competence or honesty. Ask for the reasoning and evidence behind the proposal before deciding whether the risk fits the task.
A low rate may reflect location, experience, scope or commercial choice. A high rate does not guarantee delivery. Compare the candidate's relevant examples and their explanation of the actual work, including unfamiliar tools or business rules. Ask what discovery remains rather than assuming missing sector examples make the engagement unsuitable.
Hourly billing can fit exploratory work when priorities and spend are controlled. Fixed pricing can fit agreed deliverables when exclusions and changes are clear. Neither contract form substitutes for acceptance tests and an escalation route when results are wrong. Resolve those terms before relying on the build for client-facing actions.
Define the workflow first
Match the route to the need
Run the four vetting checks
Get scope and price in writing
Frequently asked questions
How do I hire an AI developer for my small business? Define the work, acceptance conditions and continuing responsibility, then compare freelancer, employee, agency and scoped implementation arrangements. Check relevant examples, documentation, support and handover. The route alone cannot determine continuity or delivery quality.
How much does it cost to hire an AI developer? Obtain a quote for your scope and location. The article distinguishes goLance’s platform rate data and guide estimates from Indeed’s US machine-learning-engineer base-salary statistic. Neither supplies a universal project price or total employer cost. Include fees, support, changes and handover.
What is the biggest risk when hiring a freelance AI developer? Dependence on one person is an important risk when nobody else has the knowledge or authorized access to take over. Check documentation, account control, support and handover. The same dependency can occur with an employee or an agency.
Should a small business hire an AI developer or use an implementation service? Compare the ongoing technical function, internal supervision, scope and support you need. A defined project may fit an external provider; continuing internal work may support an employee. Verify actual responsibilities and cover instead of assuming a service automatically supplies a team.
Notes
- AI Developer Hourly Rate Guide. Updated September2026. Accessed October 15, 2026.
- Machine learning engineer salary in United States. Updated October 5, 2026. Accessed October 15, 2026.
