Every small business owner eventually asks me for “a really thorough guide” and then flinches when they see the word count. Long pieces get a reputation for being padding with chapter headings. Earned, mostly. A 3,000-word guide can hold a reader for fifteen minutes and send them straight to a contact form. The same length can lose them at paragraph two. The difference lives in structure, and structure is fixable by anyone willing to outline before drafting.
Here is how I build one that people actually finish.
Start with one real question
A guide needs a single job the way a homepage does. Not “everything about roofing.” A sharper question: “what does a hail damage roof inspection involve, and what should it cost?” The owner of a roofing company groans at the narrowness and then watches the narrow version pull in work for two years. Broad guides get read by nobody in particular and remembered by the same.
Write the question on a card. Every section that does not help answer it comes out in the edit.
Kill the throat-clearing intro
Here is a real opener I cut last year: “In today’s competitive marketplace, consumers have more choices than ever when selecting a service provider. Making the right choice can feel overwhelming.”
Fifty words that would read the same on any page about any industry. The reader closes the tab.
Now the opener that replaced it: “A hail damage inspection runs 45 to 90 minutes, costs nothing at any reputable company, and should end with a written report and photos. Here is what the inspector does on your roof, what the report should contain, and the three numbers that decide repair or replace.”
Same page, same topic. The second opener promises a specific answer and gives three pieces of it in the first breath. Readers who want that answer keep reading. Readers who do not leave happily. Both outcomes are wins.
The rule I work by: deliver one concrete answer in the first hundred words, even at the price of spoiling a “reveal” later. Guides have no plot twists.
Write headings that carry weight
Headings in a long guide do three jobs at once: they let a skimmer build a usable summary in ten seconds, they promise the next section’s payoff, and they carry the rhythm the body then has to keep. Weak headings (“Introduction,” “Why It Matters,” “Conclusion”) throw away all three.
Compare “Why It Matters” with “A bad inspection misses 40 percent of hail hits.” A reader who lands mid-page knows exactly where they are and what the section promises. That specificity also forces me to actually deliver the number, which keeps me honest.
More pairs from the same guide. “Cost factors” became “Three things decide the price, and one of them is a scam risk.” “The report” became “What a written report must contain, line by line.” Same sections, different promises. I count the words in every heading before the body gets written. If a heading carries no specific noun and no number or promise, it goes back to the bench.
I draft all the headings first, in order, and read them as a table of contents before writing a single paragraph. If the headings alone do not tell the story, no amount of body copy will save the piece.
Rhythm keeps a reader moving
Long does not have to feel long. Vary the length of your paragraphs deliberately. Follow a dense paragraph with a two-line one. Like this.
Readers skim on screens and piece the story together from the parts they stop on, so every paragraph needs a visible job in its first line. Break a stretch of solid text with a list when the content is genuinely a list (steps, prices, symptoms), and leave it in flowing prose when it is an argument. A guide that lists everything reads like a manual nobody finishes.
One more trick I use constantly: the aside. A short parenthetical or a one-sentence paragraph that sounds like me leaning toward the reader. “Yes, inspectors walk on wet roofs. Good ones wear soft shoes and take photos before they take a step.” Asides break the essay voice and remind the reader there is a person behind the words.
Examples before explanation
Abstract advice deserves two sentences at most before an example arrives. When I say a report should be itemized, the next line shows the itemization: “Line 1: 14 hail hits, south slope, 2 square feet of decking soft. Line 2: flashing seal failed at chimney, 3 feet. Line 3: no damage to gutters.” Real rows of a real report beat three paragraphs of description, and they take up less room while telling the reader more.
The same test works on money. “Inspections are free; repairs vary” explains nothing. “Inspection: $0. Minor repair: $400 to $1,200. Full replacement: $8,500 and up, itemized” hands the reader three numbers they can carry into a phone call. Vague pricing sentences protect the writer and cost the buyer trust.
The same holds for pricing, timelines, and scope. Show the actual number, the actual week, the actual thing that goes wrong. Every example you can show is a claim you stop having to argue.
The ending does one job
A long guide that trails off leaves the reader with a nice feeling and no next step. The last section should be small and practical: a checklist they can screenshot, the five questions to ask before hiring anyone, the one thing to do tomorrow morning. Then one invitation, in the same tone as the rest. “If you want a second pair of eyes on an inspection report, send it over. I read them free on Fridays.” One invitation. The guide already made the case.
The checklist works harder than the summary. Five boxes they can screenshot: written report received, photos included, damage measured in square feet, price itemized by line, schedule in writing. A reader who screenshots that list carries your words into a meeting you are not in.
The editing pass that pays for itself
Finished draft in hand, I do three things before it ships.
First, the cut pass. I remove every sentence that would fit unchanged on a competitor’s guide, and every definition the reader already knows. Real drafts lose fifteen to twenty percent here.
Second, the read-aloud pass. Awkward rhythm shows up in the mouth hours before it shows up on the screen, and a piece that is easy to say is easy to finish.
Third, the heading read. The table of contents again, top to bottom, with the numbers checked. If the headings still answer the original question in order, the guide is done.
Long-form work is the slowest writing I do and the hardest to fake. It also outlasts everything else on a small business’s page. A careful guide keeps answering customers’ questions at two in the morning for years, which is a better return than most of the short pieces any of us will ever write. Write one guide properly and the next one takes half the time.