Commercial work: the language layer of a product

This page describes how I handle commercial product editorial work when the client material cannot be published. It records the service method; no outcome claim can be drawn from unnamed client work.

The material at the start

An engagement begins with the product artifacts that already exist: screens, support messages, research notes, sales material and the terms used by the team. I mark whether language came from users, from the organisation or from my editorial interpretation.

The first scope can be one consequential flow. Examples include onboarding, an application form, a lesson sequence or the path from an error message to recovery. A bounded flow gives the team something concrete to review and prevents a tone exercise from drifting into a general brand discussion.

Four working artifacts

Source map

A short inventory records where each important claim or term came from. Missing evidence stays visible. A team assumption is labelled as an assumption rather than rewritten as a user need.

Vocabulary table

The table gives each product term an owner, a definition, an approved form and known exceptions. It also records words that should remain legal or technical because simplifying them would change the meaning.

Edited flow

Copy is written in the interface or in a reviewable representation of it. Each screen has a reader task, the information needed to complete it and a clear recovery path when something goes wrong.

Handoff note

The handoff lists decisions, unresolved questions and review triggers. It can live beside the design system or content files so later changes have a visible standard.

How a recommendation earns its place

A recommendation should point back to source material or to an explicit editorial principle. If available evidence only supports a hypothesis, the handoff says so. Claims about conversion, comprehension or retention require a defined measurement method; cleaner copy alone supplies no evidence of those outcomes.

Confidentiality limits what can be shown on this page. Anonymous client quotations would add no verifiable evidence, so none appear here.

Working boundary

The engagement covers product language, information structure and editorial governance. Brand identity, engineering delivery, legal review and security assessment require their own owners unless they are separately included in the scope.

Starting a conversation

The Toolshed lists editorial systems, product writing and research formats. A useful first message names the audience, the flow under review, the existing source material and the decision the team needs to make.

Email spbabinov@gmail.com with that context. Scope follows from the material under review.