AI freelancer or AI studio.

How do an AI freelancer and an AI studio compare?

Levy Street is an AI studio, so we have a side in this question. A capable freelancer is still the right answer for plenty of AI work, and this page says which. A freelancer here is one person contracting on their own account; a studio is a small firm whose specialists design, build and run AI systems together. If you are weighing a permanent hire instead, see AI agency versus internal hire.

Which jobs suit a freelancer, and which suit a studio?

Ask what happens after the work is delivered, and who will own it.

If you are not sure the idea works yet, a short AI proof of concept with go/no-go numbers agreed first costs less than either full build. For a system that already struggles, see AI system rescue.

What does each cost over three years?

Day rates favour the freelancer. The studio’s case rests on breadth and continuity, so price those. Worked example with illustrative assumptions, not market rates: D is the studio’s day rate, the freelancer charges 0.6D, and the build is the same 30 engineering days either way.

Here the freelancer is about 21 studio days cheaper. The decision rule: pay the studio’s premium when the value lost during a gap (say, a month with the system down or degraded) plus your own project management time exceeds the difference. For a back-office automation that staff can cover by hand for a month, it rarely does. For a customer-facing system, it often does.

What happens after launch, and if the builder leaves?

An AI system needs maintenance even when nobody touches it. Anthropic’s model deprecations page shows seven Claude models retired from its API between January and August 2026, and promises at least 60 days’ notice for publicly released models. Sixty days is ample for a team and tight for a freelancer deep in another contract. MBIE’s responsible AI guidance asks buyers to check “what support arrangements with the provider would be in place should something go wrong”.

Key-person risk is the chance that the one person who understands your system becomes unavailable. With a freelancer it is the main risk; with a studio, check it has not simply moved to one engineer inside the studio.

• Code, prompts and the evaluation set sit in a repository your organisation owns
• You hold the admin login for every account the system uses, and can remove the builder’s access in minutes
• A runbook covers weekly checks and what to do on failure (documenting an AI workflow for handover)
• The evaluation set runs on every change, and a pass mark blocks releases
• Someone besides the builder has run the system from the runbook
• The contract states response times, notice periods and what happens if the freelancer stops trading

Managed AI operations is how a studio such as Levy Street covers this; a freelancer can cover it with a written retainer and a named backup.

Contracts, IP and contractor status

General information, not legal advice:

• Contractor or employee. Since 21 February 2026, the gateway test treats a worker as a contractor if all five criteria hold: a written agreement saying they are an independent contractor or not an employee; freedom to work for others; no set times, or a right to subcontract; no termination for declining extra work; and a reasonable chance to get independent advice before signing. If any fails, the common law tests of intention, control, integration and economic reality apply. A freelancer working set hours, only for you, for years, starts to look like an employee.
• Tax and GST. Employment New Zealand says contractors pay their own tax and ACC levies and must register for GST once earning over $60,000, so check whether quotes include GST.
• Ownership. Under section 21(3) of the Copyright Act 1994, whoever commissions and pays for a computer program owns it first, unless the parties agree otherwise. Freelancer and marketplace terms may agree otherwise, so get a written, signed assignment. Our offshore versus New Zealand developers comparison covers the extra steps when the person is overseas.
• Insurance and liability. Ask whether the freelancer carries professional indemnity insurance and what liability cap their terms set. Ask a studio the same.

How do you test either with a paid work sample?

Pay for a small first milestone, five to ten days, that produces something you would need anyway. Give freelancers and studios the same brief, written with the AI project brief template.

1. Pick a slice of the real job. For example, extract fields from 40 anonymised supplier quotes into a spreadsheet, with a confidence flag on each.
2. Ask for measurement, not a demo. The deliverable includes results on all 40 and a list of the ones it got wrong.
3. Work in your accounts from day one. A repository and model account you own.
4. Run a handover test. Give the runbook to someone who did not build it and see whether they can run it within an hour.
5. Ask the support question. “If our model is retired with 60 days’ notice, who migrates it, and when?”

Good signs: questions about your data and privacy before starting, failures reported plainly, and a suggestion to keep some step manual. If the brief itself is unclear, you may need advice first; see AI consultant versus software developer. To find freelancers, use referrals, LinkedIn and marketplaces: Freelancer.com runs a New Zealand site, and Twine lists freelance AI developers in Auckland (as listed on 20 October 2026). A platform’s vetting is a starting point, not a test.

Which should you choose?

Choose a freelancer if

• The job is small and bounded: one automation, one prototype, one review.
• Someone in your business, or your own developers, will own it afterwards.
• A month without the system would be an inconvenience, not a loss.
• You have time to run the project yourself.

Choose a studio if

• The system faces customers, handles personal information at volume or informs decisions.
• It needs several skills: data, integration, evaluation, security, interface.
• You want support, monitoring and model migrations under contract.
• You need cover when any one person is away.

Where this goes wrong

• The freelancer becomes the system. Everything lives in one person’s head and accounts.
• A studio that is really one person. Ask who else has worked on your system, and meet them.
• A prototype promoted to production. Two weeks of code goes live without review queues, monitoring or a security review.
• Hourly billing without deliverables. Fix what each milestone delivers, whoever you hire.

Written by the Levy Street team in Wellington. Last updated 19 October 2026.