Content Piece

Origin & evolution

The concept is plain. The thinking that gives it weight is content atomisation, the practice of taking one substantial asset and breaking it into many smaller derivative pieces. A research report becomes a webinar🎥WebinarCustomer EducationA live or recorded webinarView reference →, the webinar becomes five short clips, the clips seed a dozen social posts🐦Social PostMarketingA social media postView reference →, and the transcript becomes three blog articles. The economics changed once teams realised the cost of a content piece is mostly in the idea and the source material, so squeezing one source into many formats lowers the marginal cost of each piece sharply.

Repurposing as a deliberate motion grew alongside the pillar-and-cluster model that HubSpot popularised around 2017. If a pillar page anchors a topic and cluster pieces target specific questions beneath it, a single substantial piece of work can be decomposed into a structured family of assets that reinforce each other and the pillar. The content piece became a node in a system, valued partly for what it links to and supports, not only for itself.

This is where the asset divides cleanly from the strategy. A content piece is a thing that exists; content strategy✍️Content StrategyGo-To-MarketA content strategy for thought leadershipView reference → is the plan that decides which pieces should exist and why. A library can be full of well-made pieces and still fail, because no plan connected them to an audience need🫀NeedUserA user need, pain, desire, or constraintView reference → or a business goal. The piece is necessary and never sufficient.

How it works in practice

A developer-tools company runs a webinar on migrating a legacy database, 320 live attendees. Before atomisation that webinar is one asset that decays the day after it airs. With a repurposing plan it becomes a content engine. The recording is gated as a lead magnet. The transcript is rewritten into a step-by-step migration guide targeting a specific search query. Three customer questions from the live Q&A become three short how-to posts. Six 90-second clips go to social, each linking to the guide. One webinar yields eleven content pieces, each tied to a keyword and a stage of the funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference →, all tracing back to the original recording. The same source material now works for months across channels.

Content piece vs. its neighbours

• Content strategy is the plan; a content piece is the unit the plan produces and governs. Strategy decides the migration guide should exist and which audience it serves; the guide is the deliverable. Counting pieces measures output; the strategy measures whether the output was the right output.
• SEO keyword#️⃣SEO KeywordMarketingAn SEO keyword targetView reference → is the demand signal a piece is built to answer. The keyword is the question people are typing; the piece is the answer you publish. One keyword can justify a piece, and one rich piece can rank for many keywords.
• Content calendar📅Content CalendarContent & KnowledgeA content publication calendarView reference → is the schedule a piece lands in. The calendar holds the slot and the date; the piece fills it. A piece can slip its calendar date without changing what it is.

In the graph

In the Unified Product Graph, content_piece🗒️Content PieceContent & KnowledgeA piece of content (article, video, etc.) sits in the content domain as the granular, countable asset that higher-level plans resolve into. A product owns its output through product_publishes_content_pieceProductpublishesContent Piecehierarchy, and demand pulls it into being via seo_keyword_drives_content_pieceSEO KeyworddrivesContent Piececross-domain. Scheduling runs through content_calendar_schedules_content_pieceContent CalendarschedulesContent Piecehierarchy, while purpose is captured by content_piece_supports_messagingContent PiecesupportsMessagingcross-domain and content_piece_part_of_growth_campaignContent Piecepart ofGrowth Campaigncross-domain. The atomisation pattern is modelled directly: webinar_generates_content_pieceWebinargeneratesContent Piececross-domain records that one event spawned many derived assets. Holding the piece as its own node, with edges to the keyword that justified it and the messaging✉️MessagingGo-To-MarketMessaging framework and key messagesView reference → it carries, makes an otherwise invisible library queryable, so a team can see which pieces serve no keyword, support no message, and belong to no campaign, the orphans worth retiring.