Should I hire an AI agency, a freelancer, or build in-house?

Question

VX-N · Accepted Answer

Hire in-house only once the system works and you know what it needs to do — before that you are paying a salary to discover requirements. A freelancer is the cheapest route to a prototype and the wrong call the moment the work touches customer data, payments, or anything that must keep running after they move on. An agency buys continuity and oversight, and you pay for the layers between you and whoever writes the code. The risk nobody prices properly is continuity. When a freelancer finishes, the institutional knowledge leaves with them. If an API changes six months later, there is no support line. That is fine for a prototype and expensive for anything load-bearing. The test is simple: if this system going down for a week would cost you real money, the person who built it cannot be someone whose availability you cannot count on. The agency premium buys real things — coverage when someone is sick, a second set of eyes, a process that survives staff turnover — but it also buys an account manager translating your problem to a developer you never meet, and translation is where requirements die. The tell is who shows up on the sales call. If the person who scopes the work will never touch the code, every decision you make together gets re-decided later by someone who was not in the room. In-house is the right end state for a system that has become core to how you operate, and the wrong starting point. A full-time developer is $180,000+ a year loaded before anything ships, and the first months of an undefined project burn that salary on discovering what should be built — work a scoped external engagement does faster and with a defined end. The sequence that works: have the system built externally, run it long enough to know what it actually needs, then hire the person to own it, with documentation and account ownership already in your name so the handover is real. Whichever shape you pick, three questions filter most of the bad outcomes: who exactly writes the code and can I talk to them; who owns the code and the accounts from day one; and what is the smallest first milestone we can judge you on. A vendor who resists any of the three is telling you how the engagement will go. VX-N is deliberately none of the three shapes: a small team where the person on the call is the person who builds. There is no account manager relaying your problem to a developer you never meet. If your problem genuinely needs a twelve-person agency, we will say so on the first call.