Design a pillar-and-cluster topical map for a subject you're not yet ranking for, sized to what you can actually publish

You are architecting a pillar-and-cluster topical map for a subject area we want to build authority in but don't currently rank for at all.

SUBJECT AREA
Remote-team payroll compliance across US states

WHAT WE CAN REALISTICALLY PUBLISH
One 1,500-word article every two weeks, one writer, no dedicated legal reviewer.

COMPETITORS ALREADY STRONG HERE
Gusto and Deel each have upward of 150 pages covering state-by-state payroll compliance in depth.

BUSINESS GOAL FOR THIS TOPIC
We want to rank for the handful of states our actual customer base is concentrated in, not compete nationally.

DESIGN THE MAP IN THIS ORDER

1. Pillar page: define the single broad page that will anchor this topic, its target keyword, and the scope it needs to cover to plausibly earn topical authority signals — broad enough to link out to every cluster piece, specific enough to actually rank on its own.
2. Cluster articles: list the supporting articles that link into the pillar, each with its own long-tail target keyword, and explicitly state how each one links back — the internal-linking relationship is what makes this a topical cluster instead of a pile of unrelated blog posts, so name it for every single cluster piece, not just describe the concept once.
3. Sequencing: given the stated publishing capacity, order the cluster articles into a realistic build sequence — which ones should go first because they're both high-opportunity and needed to make the pillar page's internal links non-empty on day one, versus which can wait.
4. Reality check: if the full map as designed exceeds what's realistically publishable in a reasonable timeframe given the stated capacity, cut it down explicitly rather than handing back an aspirational map that assumes unlimited output — say what got cut and why, and offer a phase-two list for the cut items instead of dropping them silently.

WHAT NOT TO DO
Do not produce a topical map so large it functions as a wish list rather than a plan — if publishing capacity is one article every two weeks, a 30-piece map is not useful even if every piece is individually well-chosen. Do not treat established competitor coverage as something to simply out-list; if a competitor has 200 pages on this subject and we can publish 12, name the realistic subset of the topic where 12 well-chosen pages can plausibly compete, rather than a shallow imitation of their full breadth.

OUTPUT FORMAT
1. Pillar page: title, target keyword, scope summary.
2. Cluster table: Article title | Target keyword | Links to pillar via (anchor text / context) | Build order.
3. One paragraph on what was cut from an idealized version of this map and why, plus a phase-two list.