Vision Field Notes

Freelancing in Computer Vision: Winning Your First Jobs

Computer vision looks like a good freelance skill. Many businesses have cameras and images, and few have someone who can turn them into something useful. But the work is risky for freelancers. Clients often misunderstand what is possible, data is poor, and "just detect the thing" can hide weeks of difficulty.

This article covers how to position yourself, how to scope work so you do not lose money, and how to avoid projects that go badly. It is general guidance. Rates, platforms and market conditions change, so treat any specifics as things to check yourself.

Start with what you can honestly deliver

Clients do not buy "computer vision". They buy a result: fewer missed safety violations, an automatic count, a faster inspection, a way to search images. Describe what you can deliver in those terms, and only claim what you have done.

Good areas to define for yourself:

A narrow, clear statement such as "I build and deploy object detection for camera feeds" is easier to hire than "AI developer, anything". Specialising does not stop you taking other work. It makes your pitch believable.

If you are new, build proof first. A few finished, honestly described projects are worth more than a long list of skills. See build a computer vision portfolio that gets clients.

Where first clients come from

There is no secret. The usual sources are:

Expect slow early weeks. Treat the first few jobs as a way to build references, but do not work for free on large pieces.

Scope before you price

Most freelance losses come from unclear scope. Computer vision has a special trap: the same sentence can describe a one-day task or a six-month research problem.

Before quoting, ask:

  1. What decision or action will the output drive? This tells you which errors matter.
  2. What data exists? Images, video, labels, camera types, and how many sites. Can you see samples before you quote?
  3. What does success look like, in numbers? For example, an agreed error rate on a test set that you both approve. Without this, "it does not work well enough" can never be answered.
  4. Where does it run? Cloud, an on-site server, or small devices. Hardware limits change the model choice.
  5. Who labels data, and who provides test footage? Labelling is often the largest cost.
  6. What are the privacy and legal constraints? Footage of people raises extra requirements.
  7. Who maintains it afterwards? Models drift when conditions change.

Be honest about unknowns. If the data quality is unknown, say the first step is to assess it, and price that step separately.

Split the work into phases

A common structure that protects both sides:

Phase What it covers Why
Discovery Look at data, define success, test feasibility on a small sample Removes the biggest unknowns cheaply
Prototype Train a first model, report honest metrics on held-out data Client sees real evidence before committing
Build Full pipeline, integration, alerts, testing Larger spend only after feasibility is shown
Handover or support Documentation, deployment, monitoring, fixes Sets expectations for after delivery

If the feasibility check fails, you and the client both learn that early, which is a good outcome for them and for your reputation.

Schematic bar diagram of four project phases on a baseline. Discovery, a short box, covers looking at data and defining success. A yellow go/no-go diamond follows. Prototype, a taller box, covers a first model and honest metrics. A second go/no-go diamond follows. Build, the tallest box, covers the full pipeline, alerts and testing. Handover and support, a medium box, covers docs, deployment and monitoring. A note says box height shows relative client spend and is schematic.
Caption: The cheap phases come first and each ends in a decision, so the client only commits to the expensive build once the data and a prototype have been seen. Heights are schematic, not real costs.

Pricing models

Each model has strengths and risks.

Conceptual map with two axes. The horizontal axis is how clear the scope is, from unclear to clear; the vertical axis is how long the work is, from one project to ongoing. Bottom left: hourly or daily rate, safer while unknowns remain, send estimates and updates. Bottom right: fixed price per phase, only with written scope, exclusions and a change process. Middle right: value-based, needs clear, measurable savings and trust. Top centre: retainer, ongoing monitoring and improvement.
Caption: A rough guide rather than a rule. The less you know about the data and the scope, the further left you are, and the more an hourly rate or a small fixed discovery phase protects both sides.

I will not quote rates here, since they vary widely by region, experience and client. Look at current listings and ask peers. Do not price so low that you cannot afford to do careful work, because that leads to rushed, unreliable systems.

Whatever model you use, include in the quote: who supplies data, how many revision rounds are included, cost of cloud or GPU services (who pays), and what happens if the data turns out to be unusable.

Writing a proposal that stands out

Short and specific beats long and generic.

Avoid promising a specific accuracy before seeing data. A confident promise without evidence is a warning sign to experienced clients.

Projects to be careful with

Delivering well

What keeps clients and brings referrals is usually not the model. It is the reliability and communication:

Checklist

Next steps: build a computer vision portfolio that gets clients, computer vision engineer roadmap.