Most bloggers who want to write a book already have one. Somewhere in the archive — behind the seasonal posts, the quick reactions, the three-part series you abandoned halfway — sit twenty or thirty pieces that could form the spine of a nonfiction book. The problem is almost never a shortage of words. It's the distance between a pile of posts and a proposal an editor can read in one sitting and understand immediately. Closing that distance is mostly craft, and it starts with a decision about what your book is actually arguing.

Find the Through-Line Before You Find the Chapters

Blogs are written in the present tense of a topic. A book needs a claim. Those are different things, and confusing them is the most common reason a proposal feels vague.

Suppose you've spent four years writing about small-scale growing: compost, seed sourcing, a disastrous season of brassicas, a piece about selling at market. The book is not "everything I know about growing." It might be the first three years are about soil, not sales — an argument with a shape, a beginning and an end, and a reader who finishes it changed.

Test it with a single sentence: This book argues that… If you can't finish that sentence without listing subjects, you have a topic, not a book. Then ask what the reader will be able to do, believe or decide differently by the last page. If the answer is "know more about the subject," keep working. Editors buy arguments.

Audit Your Archive Properly

Don't do this from memory. Open a spreadsheet and give every post a row: title, date, word count, the claim it makes, the evidence behind it, and whether you still stand by it. Then mark each one as raw material, usable with rework, or reference only.

The keepers tend to share a few qualities:

• It's yours. Your observation, your method, your mistakes — not a summary of someone else's book with a personal introduction bolted on.
• It still holds. Advice you no longer believe, or that has quietly gone out of date, is worse than a gap in the outline.
• It carries evidence. Numbers from your own records, a process described step by step, a failure you can explain. That's the material readers can't get elsewhere.
• It argues rather than describes. "How I priced my first commissions" can become a chapter. "Five tools I like this month" usually can't.
• It serves the through-line. Being ruthless here saves months later.

Expect roughly a quarter of the archive to survive. That's normal, and it's a good sign: it means you've been writing, not hoarding.

Restructure Rather Than Republish

A blog post is self-contained. It front-loads the payoff, assumes no prior reading, and ends by nudging the reader towards the next post or the comment box. A chapter carries someone forward and takes for granted that the previous chapter happened.

So the work is mostly subtraction and stitching. Strip the scaffolding: "as I mentioned last week," "if you're new here," the calls to subscribe. Merge posts that circle the same idea into one chapter with one argument, writing a new opening and a new transition. Add the connective tissue that a book needs and a blog never did — the sentence that tells a reader why this follows what came before.

Order by argument, not by date

Your strongest posts were probably published in the order that suited a blog's rhythm, which is often the reverse of a book's logic. The piece that explains your method may need to come after the piece that establishes why the method matters. Lay the clusters out on the floor, or in a document, and move them around until the sequence persuades rather than merely informs.

Plan on writing new material too. The framing chapters — the introduction that states the claim, the conclusion that lands it — plus transitions, usually add up to at least a fifth of the book. That's not a flaw in the plan. It's what turns a compilation into a book.

What the Proposal Itself Needs

Requirements vary by publisher and agent, so always check the submission guidelines on their website before you send anything. Most nonfiction proposals, though, contain some version of the following:

1. Overview. A page at most: the claim, the reader it's for, and what changes for them.
2. Audience. Who specifically, described in terms of what they read and worry about — not "anyone interested in the subject."
3. Comparable titles. Two or three recent books in the same area, and an honest sentence about how yours differs.
4. Chapter outline. A paragraph per chapter: its argument, the material it draws on, what the reader takes away.
5. Sample chapter. Usually the strongest and most representative one. Not the introduction, and not a blog post with a new heading pasted on top.
6. Author note and platform. What you bring: readership figures, a newsletter, teaching or professional standing, speaking.
7. Practicalities. Proposed length, a realistic delivery timeline, and anything you'll need to finish it.

The sample chapter is where most blog-based proposals are won or lost. Choose the chapter that shows a reader what the whole book will feel like, then edit it as though it were the only thing anyone would read. Because, at that stage, it is.

Being Straight About Previously Published Material

Say so, early and plainly. A line in the overview noting which chapters draw on material published on your blog, and where, does you no harm; editors are used to it, and many are reassured by an author with a proven readership. What causes difficulty is discovering it later.

If some of those pieces appeared on someone else's site — a guest post, a magazine commission, a syndicated column — check the terms you agreed to. Outlets often ask for first publication rights or a period of exclusivity, and those terms vary widely. If you're unsure what yours say, read the contract carefully or take advice before you reuse the material.

There's also a commercial point. If the book simply gathers the best of the blog, regular readers have little reason to buy it. Keep a chapter or two that exists only in the book: a deeper case study, a method you've never fully written up, the part you found hardest.

Your First Week

You don't need a finished proposal to begin. You need a week of steady, unglamorous work.

• Day one: write the one-sentence claim, then rewrite it five times.
• Day two: build the spreadsheet and mark up every post you might use.
• Day three and four: cluster the keepers into eight to twelve groups, and give each group a claim of its own.
• Day five: write the chapter outline, one paragraph per chapter, in the order that argues best.

After that, the overview and the sample chapter are a fortnight's work, not a year's. Editors don't buy blogs. They buy books — and a proposal is simply the proof that you know which book you're making, and that you can make it.

Photo: 27707 / Pixabay