Guide and How-To Writing Service

A guide earns its place by getting somebody from not knowing to knowing, in one sitting, without them having to open a second tab. That sounds obvious. Most published guides fail it, because they were written to occupy a keyword rather than to answer a question.

The test we write against. Could a reader follow this and actually do the thing? If a step assumes knowledge the reader does not have, the guide has a hole in it, and readers find holes immediately. This is why we write the difficult step first and build the rest around it, rather than starting at the introduction and hoping the hard part resolves itself.

The formats we write.

Step-by-step guides. Sequential, numbered, one action per step. The most common failure is combining three actions into one step because they feel related to the writer. They do not feel related to somebody doing them for the first time.

Buyer’s guides. Comparison against criteria the reader cares about, with an honest account of who each option is wrong for. A buyer’s guide that recommends everything recommends nothing.

Onboarding and documentation. Written for someone who is mildly frustrated and wants to stop reading as soon as possible. Short sentences, obvious headings, no throat-clearing.

Explainer guides. Where the goal is understanding rather than action. These carry more analogy and more context, and they are the format where knowing the audience’s starting point matters most.

Structure that readers actually use. Almost nobody reads a guide top to bottom. They scan for the heading that matches their problem, read that section, and leave. So each section has to make sense out of order, headings have to describe content rather than tease it, and anything critical cannot live only in the introduction. Where a guide is long, we open with a short summary of what it covers so a reader can self-select.

Search visibility, done properly. If you want a guide to rank, the research happens before the outline, not after the draft. We look at what the current results actually answer, which questions they leave open, and where the intent behind the query differs from what everyone has assumed. The gap is the brief. Adding a keyword to finished copy at a set density is not optimisation and has not worked for years.

What we need from you. The process itself, in whatever form it exists, plus access to somebody who has done it. Fifteen minutes with a practitioner prevents the specific errors that make a guide feel written by an outsider. If there are decisions where your answer differs from the industry default, tell us, because that disagreement is usually the most useful thing in the finished piece.

Questions we get asked

How long should a guide be? As long as the task requires and no longer. A guide to a four-step process should not be 2,000 words because a competitor’s is. Padding shows, and readers who wanted a quick answer will not come back.

Can you include screenshots or diagrams? We will specify exactly what each one should show and where it goes, so your designer or your own team can produce them. We write the guide; we do not produce the imagery.

Will it need updating? Any guide describing software or regulation will. Build in a review date. A guide that is confidently wrong about a step is worse for your credibility than no guide at all.