Hiring, working with, and briefing a developer

Hiring one engineer to own a whole product is a different decision from hiring for a role on a team. This is the sequence that makes it a decision rather than a gamble: define the outcome, write a brief, ask questions whose answers mean something, and agree ownership before any code exists.

Most freelance engagements that go wrong go wrong on communication, not on code. The practices below are the ones that survive not being in the same room — written scope, visible progress, and a defined path for the conversation nobody wants to have.

Two quotes for the same website routinely differ by a factor of five, and the reason is almost never greed. It is that they are quotes for different work. Here is what actually drives the number, and how to tell which quote is describing the project you asked for.

Two separate changes get discussed as one: AI changing how applications are built, and AI changing what applications can do. They have different evidence behind them, and conflating them is why so many teams are disappointed by both.