Freelancing Gives You Authority. Contracting Gives You Access.

A designer gets an email from someone he hasn't talked to in years. They worked together once, long ago, before their careers went in different directions.

The message is straightforward:

"Hey—hope all is well with you. We're in the middle of a product project that's grown larger than we expected. We're looking to contract out 1–2 additional designers to help the team keep things moving. Would you be interested?"

The request makes sense. The project expanded. They need more hands. But one word gives him pause: contract.

He's been freelancing for years. That model is familiar. Contracting, though, is something he's never had to think too deeply about. He realizes he doesn't actually know how it would change his role or what would be expected of him on a day-to-day basis.

That evening, he goes to his regular networking meetup. He ends up talking with designers working across agencies, product teams, freelance roles, and contract positions. When someone asks how work is going, he mentions the email.

"I might take on a contract role," he says. "I've always freelanced, so I'm trying to understand what the difference really is."

One person speaks up. "I'm a contract designer."

They explain that contracting usually means being brought in because a team needs additional capacity. The direction is already set. The roadmap exists. Their role is to step into the work, execute clearly defined tasks, and contribute to the project's progress.

"I'm not there to reshape the work," they say. "I'm there to support it."

"So you're basically an employee?" he asks.

"No," they reply. "That's the part people often misunderstand. I'm not on the payroll the way an employee is. I'm there for a fixed period of time. When the contract ends, either we set up another one, or I'm back out looking for my next project."

They pause, then add, "There's no staying until I quit or they let me go. My time with the team is defined by the contract."

The conversation shifts as someone else describes freelancing. When they freelance, clients come to them for their experience and judgment. They help clarify problems, make recommendations, and influence direction. The expectation is different.

That's when it clicks.

Contracting isn't about owning decisions. It's about access—access to a team, a project, and a set of responsibilities for a specific period of time. Freelancing, by contrast, comes with a different expectation: being trusted to guide the work and shape outcomes.

By the end of the night, the designer isn't unsure anymore. He may still take the contract, now that he understands it. But he also knows it would ask him to show up differently—less as a decision-maker, more as someone brought in to execute within an existing structure.

And that clarity is exactly what he needed before replying to the email.

Helping UX Designers bridge gaps and grow