From a market change to your next piece of content

The content planning meeting is tomorrow. A competitor has changed its homepage. Your sales team has mentioned the same buyer question twice this week. There is a half-written blog post in the queue, and someone needs to decide whether any of this should change what you publish.

If you run marketing at a B2B software company, that decision lands with you. You own the positioning and lead a small team. Nobody on it has the hours to read every competitor page, every community thread and every trade story, and yet you are expected to walk into the room already knowing.

This note is about a routine that fits that week: know what changed, keep only what matters to you, and turn the findings you choose into content your team can review.

Give the reading a direction

Start with your own website. Viewfield reads it and drafts the things every later judgment depends on: your positioning, the audiences you write for, and the competitors worth watching. Correct what it got wrong, once, and add the competitors it missed. From then on, everything it reads is weighed against what you stand for and who you sell to.

This is what makes the difference between a feed and intelligence. A competitor's new headline matters differently depending on whether your buyers care most about speed, cost, control, or something else. Without your position written down, every change looks equally important. With it, most changes turn out not to matter to you at all.

If you have customer conversations in a CRM, a call tool or a support desk, you can connect one of those too. Nothing is read until you connect it, and what is read is counted and paraphrased, never quoted without you.

Start with what changed

Each morning you get a short list: up to three changes from your market, your competitors, your buyers or your own position. Each one says what changed, who on your side it matters to and why now, where your position stands, and one thing you could do about it. The source is one click away when a claim needs checking.

The list is short on purpose. Hundreds of things change in a market every week; the morning carries the few that change something for you. A quiet day is a shorter list, not a padded one.

Decide whether it changes what you say

The useful test is specific. Does this change a question your buyers are asking, an argument you need to make, or the evidence behind your positioning?

A change can be real and still have no bearing on this week's work. Watching it is a valid answer, and dismissing it makes the mornings sharper. Nothing is drafted until someone on your team asks for it.

Find the argument that is yours

Say you sell close software to finance teams, and your positioning centres on a close you can explain: every number in it carries its reason.

A competitor rewrites its homepage to sell the close on speed. In the same week, your customer conversations keep raising a different worry: whether a number can be traced back to its source before anyone signs off on it.

Put those two facts together and an angle appears that belongs to you: what makes a close easy to verify before it reaches the board? The competitor's change brought the question into focus. Your piece stands on your buyers' problem and your own experience. It does not need to mention the competitor, and it should not.

That is the rule underneath all of this. A competitor's move tells you which conversation is live. Your content answers your buyers' question in your frame, and it would stand on its own if the competitor had never moved.

Turn it into a draft

When you choose to act, choose Draft content on the item and say what it is for: a blog post, a LinkedIn post, a single X post or a thread, or a newsletter issue. The draft opens in the editor in your voice, with the finding and the reasoning beside it, so your team can see why the piece exists before they judge how it reads. Every kind is the same editable document, and a thread is numbered paragraphs in it.

For the example, the first piece might be a LinkedIn post on the three checks a close should pass before the board sees it. A blog post could carry the full explanation, and the same argument could open the note you send your customers next month.

Pick the shape your team actually uses. The point is to give each piece a clear reason to exist and to keep that reason attached as the idea becomes a draft.

Keep the review connected to the reason

Reviews go faster when the reviewer knows what the piece is for. For the example, the question is: does this help a finance lead verify a close? That gives your writer and your reviewer something concrete to assess beyond whether they like the opening paragraph.

Keep the source in reach. If it is thin, or a claim goes beyond it, narrow the claim. If the draft does not support your positioning, change the angle before you change the sentences.

When the team is satisfied, take the draft out. Copy it as text or Markdown, download it as a Word file, or open it as a Google Doc, and put it out through whatever you already use. If your site runs on a CMS Viewfield connects to, send the piece there as a draft instead, and publish it there when you are ready. No part of the loop posts in your name on its own: your social accounts and your email stay yours, and a draft in your CMS goes live only when a manager publishes it.

Bring it to leadership

The same reasoning is your update. What changed, why the team paid attention, and what you decided because of it, already written down, with the source behind each step.

After a decision, Viewfield reads what moved around it: what your customers started saying, what your competitors did next, what AI answers say about you. It is written as an association, never as proof that your piece caused it. In the first few weeks, judge the routine itself too: which findings were useful, how much checking they needed, and how much of each draft survived review.

Try it on the work in front of you

Pick an upcoming piece or a question from your next planning meeting. Give Viewfield your website, correct the draft of your positioning and competitors, and follow one finding through to a draft your team reviews.

Start a free trial of Viewfield and judge it on your own market. The example above is illustrative, not a customer.