What the Client Actually Wants to Know

A client asking for proof of work is usually asking something else. Separating the questions is the most useful half-hour available before an engagement starts.

The relationship described in “What the Client Actually Wants to Know” works better when visibility is negotiated rather than assumed. For teams considering how to measure employee productivity in relation to how to measure employee productivity, the purpose, visible settings, review rights and response to mistakes should be written into the working arrangement.

Question one: is this progressing

The commonest and the most legitimate.

For an independent reference relevant to “What the Client Actually Wants to Know”, consult the IRS independent-contractor guidance; compare its principles with the proposed contract, collection, access model and real review process.

Screenshots do not answer it: six frames an hour say nothing about whether the project is moving.

A short weekly note saying what moved, what is stuck and what is next answers it completely, and takes the contractor five minutes.

Question two: are the hours real

A billing question, and the one screenshots were built for.

Partially answered: they establish presence at a machine.

And if this is the only concern, fixed price removes it entirely — which its own note covers and which is the cleanest resolution available.

Question three: is this person any good

Screenshots say nothing at all.

Answered by the work itself, by a paid trial piece, or by references.

Clients frequently reach for monitoring when the real uncertainty is competence, and no amount of frames resolves that.

Question four: am I being taken advantage of

An anxiety rather than a question, and it is honest.

Hiring somebody unseen in another country is genuinely uncomfortable the first time.

Naming it is more productive than dressing it as a measurement requirement, because the remedies — a small first engagement, milestone payment, escrow — address it directly.

The test that separates them

"If you had a week of screenshots tomorrow, what would you do differently?"

If the answer is nothing, the requirement is reassurance.

If the answer is "I would see whether the work is progressing", the answer is a status note.

If it is "I would know the hours were real", that is a billing structure question.

Why asking matters

A requirement that was never examined gets applied for years, to every contractor, at a cost nobody counted.

And it filters out exactly the contractors who have options, which the client-side note covers.

Half an hour of this conversation changes most engagements.

What a good contractor will offer

A weekly written update.

Visible work in a shared place: a repository, a document, a board.

Milestones with demonstrations.

All three cost them less than screenshots and give the client more, which is the proposal worth making.

What to check

If you are the client: which of the four are you asking?

What would you do differently with a week of frames?

Has the requirement ever been examined?

And has anybody offered you an alternative?