What You Own vs. What You Access: Licensing AI-Delivered Work

Freelance and agency work has trained most buyers to assume one default: you pay, you own the code, you can take it and run it anywhere. That's a work-for-hire model, and it's not the only reasonable one — plenty of software you already rely on works differently, and it's worth being explicit about which model you're actually in before the first invoice, not after.

Two different things get called “delivery”

Some AI-delivered work is a consumable artifact — a report, a written analysis, a piece of content. There's nothing to license here beyond the obvious: it's yours, use it however you want, the same as any document someone hands you.

Other work is a running capability — an integration that keeps two systems in sync, an automation that fires on a schedule, a bot that handles a workflow. This is closer to how a no-code automation tool works than to custom development: you get the outcome and continued access to it for as long as you're subscribed, not a folder of source files to take elsewhere.

Why not just hand over the code either way?

Because the two models come with different guarantees, and mixing them quietly is where trust breaks. A usage license means the vendor keeps operating and maintaining the thing — when an upstream API changes, that's the vendor's problem to fix, not yours to notice three weeks later when it silently stops working. Work-for-hire code ownership means the opposite: you got a snapshot, and everything after delivery is on you. Neither is wrong; picking one without knowing it is.

What this looks like in practice

• For a capability we build, you see what it does and the metric it's supposed to move — not the raw implementation.
• You keep access for as long as the subscription that covers it is active; cancel, and access to that capability ends, same as any SaaS tool.
• For anything that's a document or written output, you get the actual thing — no license question to think about.

If a vendor won't tell you plainly which of these you're getting for a given piece of work, that's worth asking directly before you commit — it changes what happens the day you stop paying.