Build a blog outline by diffing against what's already ranking, not from a blank template

You are building the outline for one specific blog post aimed at ranking for one specific keyword — not a generic outline template, but a structure built by diffing against the pages that already rank for this term.

TARGET KEYWORD
async standup tool for remote teams

CURRENTLY RANKING (TOP 3-5 RESULTS)
Three SaaS comparison posts, all structured as '7 best tools' listicles covering Geekbot, Range, and Standuply, each with a features table and pricing but no discussion of async standup failure modes.

OUR UNIQUE ANGLE
We ran a 6-month internal study across 40 remote teams tracking why async standups get abandoned after the first month.

READER'S INTENT STAGE
Actively comparing 3-4 named tools before a trial signup, not just learning what async standups are.

TARGET LENGTH
1,800-2,200 words

STEPS
1. From the ranking pages I've described, infer the subtopics they cover in common — treat that shared coverage as table stakes the outline must include, since ranking below a competitor rarely happens because our unique angle is better elsewhere while we're silently missing a section every other result has.
2. Identify what none of the ranking pages cover well, using the unique angle I gave you as the seed, and place that as a distinct, named section rather than folding it invisibly into an existing H2 where a skimming reader (or a summarizing AI Overview) won't register it as new information.
3. Order sections by the reader's actual intent stage, not by what's easiest to write first — a reader in an early research stage needs framing and comparison before a deep implementation section; a reader already comparing named options needs the comparison near the top, not buried under generic background.
4. For each H2, write one line stating the single question that section must answer and the minimum subpoints (as H3s) needed to answer it completely enough that a reader wouldn't need to open a second tab.
5. Flag any H2 where satisfying it well would push the piece meaningfully past the target length, and propose either cutting it to a summary with a link to a dedicated piece, or flag that the target length itself may be unrealistic for this keyword's competitive coverage bar.

WHAT NOT TO DO
Do not propose an outline that reads as interchangeable with any other post on this general subject — every H2 should be something you could only have written after reading what I told you about the ranking pages and the unique angle. Do not pad the outline with a generic "conclusion" or "final thoughts" section unless it does real work (a specific next step, not a restated summary).

OUTPUT FORMAT
1. A one-sentence statement of the table-stakes coverage gap this outline closes.
2. The full outline: H1, then H2s with their one-line purpose and H3 subpoints.
3. A flagged note on length risk if any section threatens the target word count.