We Pivoted Our Entire ICP Mid-Quarter. Here’s How I Rebuilt the Content Strategy in Real Time.

I’d been at the company for a few months when it happened. The go-to-market strategy shifted, not a gradual drift but a deliberate, leadership-driven decision to change the primary buyer persona from Admissions Directors to IT leaders: CIOs, CTOs, Heads of Infrastructure. The reasoning was sound. The product’s strongest competitive advantages were technical (integrations, security, architecture), and the deals that were stalling were stalling because IT wasn’t bought in. Moving the primary persona to IT made strategic sense.

From a content perspective, it was a crisis.

I’d spent my time building out a content library that served the admissions audience well: blog posts, product pages, LinkedIn campaigns, case studies, FAQ sections, all tuned to the language, pain points, and evaluation criteria of Admissions Directors. That content was performing, organic traffic was climbing, engagement was strong, the machine was working.

The IT audience? We had nothing credible to show a CIO. No integration documentation, no security pages, no architecture guides. A CIO landing on our website would have found a platform that talked exclusively about admissions workflows, and they’d have bounced in thirty seconds.

And I was one person. This is the story of how I handled the pivot, what worked, what I’d change, and what it taught me about building content systems that can absorb strategic shifts without falling apart.

What should you do in the first 48 hours of an ICP pivot?

The first thing I did was resist the urge to start writing immediately. The instinct when a pivot hits is to scramble and start producing content for the new persona as fast as possible, but producing content without a plan would have meant producing the wrong content, or producing the right content in the wrong order, which is almost as bad.

Instead, I spent the first two days on triage. I needed to answer four questions before I wrote a single word:

• What does the new persona need to see in the first two weeks to take us seriously?
• What existing content can survive the pivot without changes?
• What existing content needs to be paused, reworked, or killed?
• What can I realistically produce given that I’m still one person and the other four personas haven’t disappeared?

The answers shaped everything that followed.

How do you triage an entire content library during a pivot?

I went through the entire content library and sorted everything into four buckets:

1. Keep as-is covered content that was persona-neutral or already relevant to IT buyers: some product pages, general platform content, and a handful of blog posts that focused on capabilities rather than persona-specific use cases. This was a smaller bucket than I wanted it to be.
2. Deprioritise meant active content campaigns aimed squarely at Admissions Directors. These weren’t wrong or bad; they just weren’t the priority anymore. I paused the planned blog posts and LinkedIn campaigns for this audience and moved them to the “opportunistic” tier of my tiered content calendar. They’d get done if I had capacity, but they were no longer committed work.
3. Rework applied to content that had the right information but the wrong framing: product pages that led with admissions use cases but could be restructured to lead with platform capabilities, website copy that assumed the reader was an Admissions Director when the information was actually relevant to anyone evaluating the platform. These needed editing, not replacing.
4. Build from scratch was everything IT buyers needed that didn’t exist yet: integration blueprints, security documentation, architecture overviews, technical credibility content that would let a CIO evaluate the platform without talking to sales first. This was the biggest bucket and the most urgent.

The triage took about a day and a half. It felt slow at the time, but in hindsight it was the most important day and a half of the entire pivot, because it meant every piece of content I produced after that point was aimed at a specific, prioritised need rather than whatever felt most urgent in the moment.

How do you negotiate adjusted targets after an ICP pivot?

Here’s something that doesn’t come up enough in content marketing case studies: when the strategy changes, the targets have to change too.

I’d set quarterly KPIs based on the original content strategy: blog traffic targets, LinkedIn engagement benchmarks, organic growth goals. All calibrated to an audience that was no longer the primary focus. Hitting those numbers while simultaneously building an entirely new content vertical for a different persona was not realistic, and I knew it.

So I had that conversation with leadership. I framed it as “here’s what I can do, and here’s what needs to change,” and laid out what the pivot meant for the content calendar: roughly 50% of my capacity was going to the new IT persona, the other four personas were getting compressed into the remaining half, and some planned content was getting cut entirely. The blog traffic targets for the original audience would probably dip, and the LinkedIn campaigns aimed at Admissions Directors would slow down.

In return, I proposed new KPIs for the transition period:

• Number of IT-specific content pieces published per month.
• Coverage of the critical technical topics (integrations, security, architecture).
• Qualitative feedback from sales on whether they now had material they could actually send to IT buyers.

This conversation matters because the alternative is absorbing an impossible workload silently and then either burning out or delivering mediocre work across the board. A strategic shift like this requires honest conversations about trade-offs, and the content marketer’s job is to name those trade-offs clearly enough that leadership can make an informed decision about what to prioritise. I’ve written about why ownership and direct communication matter in content roles, and an ICP pivot is one of the moments where that principle gets tested most directly.

How do you build technical content from zero during a pivot?

I’ve written about this process in detail in a separate piece, so I won’t rehash the full methodology here. But the short version: I had no technical writing background, and I needed to produce content that CIOs would find credible.

The approach was structured. Internal help documentation and product specs were the factual foundation. For gaps in the documentation, I talked to Product and Engineering with specific questions rather than open-ended ones (asking “is the REST API integration with System X still accurate?” gets a usable answer, while asking “tell me about our integrations” gets a twenty-minute monologue). I also studied how competitor SaaS companies structured their technical content for buyer audiences, which gave me a format to work from.

The sequencing was driven by sales urgency:

• Integration blueprints came first because prospects were already asking questions that sales couldn’t answer.
• Security documentation followed because it was a dealbreaker for any IT buyer evaluating a SaaS platform.
• Architecture overviews came after because CIOs needed to understand how the platform fit into their existing stack before they’d even consider a demo.

Each piece followed a consistent structure so that a CIO comparing different aspects of the platform could find information in the same place every time. And everything went through a verification process where every claim got traced back to a documented source before publication. The pivot didn’t change the editorial standards; it just applied them to completely unfamiliar subject matter.

Research on B2B buyer behaviour supports how critical this sequencing decision was. According to Effiqs’ 2026 GTM strategy research, 81% of B2B buyers choose their vendor before ever talking to sales, which means the content a CIO finds on your website during their independent research phase is often the only chance you get. If that content doesn’t exist or isn’t credible, you lose the deal before sales ever knows about it.

How do you keep other personas alive during an ICP pivot?

The four other buyer personas (Admissions Directors, Deans/CEOs, Marketing Directors, CFOs) hadn’t vanished. Those deals were still in pipeline, and prospects in those segments were still evaluating the platform. If I’d gone completely silent on those audiences, we’d have lost active opportunities to feed hypothetical future ones.

My approach was to shift those personas to maintenance mode with no new net campaigns. Instead, I focused on bottom-of-funnel content that directly supported active deals:

• Updated sales enablement materials aligned with the current positioning.
• Refreshed product pages with accurate, current information.
• Answers to specific prospect questions that sales was fielding in real time.

I also kept the existing LinkedIn content running on a reduced cadence rather than stopping it entirely, because going dark on social signals something is wrong and prospects notice. During the pivot period, I maintained a reduced LinkedIn cadence of about 20 posts per quarter for the non-IT personas (down from 39+), which was enough to keep the audience engaged without pulling significant capacity from the IT content build.

The key was being explicit with the team about what this meant. Some personas were getting less attention, and that was a deliberate, communicated choice rather than a failure to keep up. I’ve written about how I balanced five personas as a solo operator in more depth, including the prioritisation framework (impact, urgency, and debt) that made these decisions systematic rather than reactive.

What would I do differently if I faced another pivot like this?

I’ve had time to reflect on this, and a few decisions stand out as things I’d change:

1. I’d start the triage before the official announcement. In reality, the signs that the company was moving toward IT-first positioning were visible weeks before it became a formal strategic decision. I could have started the content audit earlier, identified the gaps, and had a plan ready to execute on day one instead of spending the first 48 hours building one.
2. I’d push for a dedicated engineering contact from day one. My biggest bottleneck during the ICP pivot was getting technical information verified. I was chasing multiple people for different answers, and having one designated engineer as my go-to for content verification would have saved hours every week and improved the speed of the entire technical content pipeline.
3. I’d document the pivot process itself as a playbook. While living through it, I was too focused on execution to document what I was doing. By the time the quarter was over, the institutional knowledge of how we handled the ICP pivot was all in my head. If I’d documented it in real time, even as rough notes, it would have been useful as a template for future pivots and as proof of what the content function delivered under pressure.
4. I’d set more specific expectations about the ramp-up timeline. I told leadership that some metrics would dip, but I could have been more precise: “IT content will start producing measurable results in week six, not week two” would have been better than a general “it’ll take time.” Specificity in expectation-setting prevents the anxiety that comes when week three arrives and leadership wonders why the new content hasn’t transformed the pipeline yet.

What does an ICP pivot teach you about content marketing?

ICP pivots are not rare in B2B SaaS. Companies do this, and when they do, the content function absorbs a disproportionate share of the impact because content touches everything: the website, sales materials, social channels, thought leadership, SEO, brand positioning. All of it needs to shift. According to Sybill’s 2026 ICP guide, successful startups often pivot their ICP multiple times in the first year, which means the ability to absorb and execute on strategic shifts is a core capability for content marketers, not a nice-to-have.

The content marketers who handle this well are the ones who have a content system already in place: a tiered content calendar that can absorb reprioritisation without falling apart, editorial standards that keep quality consistent even when the topics change completely, verification processes that work regardless of the domain, and enough confidence to sit down with leadership and say “here’s what’s realistic and here’s what’s not” before unrealistic expectations become a problem.

I didn’t handle the ICP pivot perfectly. But I handled it, alone, while keeping four other personas alive and delivering results that showed up in pipeline. The system is what made that possible. Without it, I’d have spent the quarter scrambling instead of executing.