B2B Content Marketing Strategy: What 15 Leaders Changed

A full calendar is easy to mistake for a strategy. The harder question is why a buyer would trust a page enough to use it. We asked 15 leaders across software, services and ecommerce the same two questions: What did you change on your website or blog, with an example? What prevents you doing more, and what would you expand if that constraint disappeared? Their answers reveal the work behind the pages buyers actually use.

• Answer a specific job. Publish the steps, product detail and next action that job needs, rather than choosing topics by volume alone.
• Put proof near the claim. Bring an expert's facts, examples and current sources into the page while they are still accurate.
• Make the path onward obvious. Give the page a descriptive title, useful internal links and a relevant product route.
• Measure the result you actually want. Keep search data, buyer actions and AI-answer checks separate.

The 15 leaders at a glance

Leader	Company	What they changed	What slows them down
Teri Maltais	iTacit	Content on frontline jobs and training questions	Subject experts have limited time
Olga Kokhan	Tinkogroup	Problem-led articles with answers near the top	Getting customer knowledge into regular drafts
Dora Bloom	iotum	Titles, descriptions, image text and load time	A small team owns the whole site
Rahul Agrawal	QuickIntell	Pages for payer, authorization and claim questions	Payer rules need frequent source checks
Andrew Izrailo	Astra Trust	Expert bylines and consolidated jurisdiction pages	Practitioners must verify changing legal facts
Ian Lawson	Slickplan	Page research linked to design and performance history	Experienced review takes time
Runbo Li	Magic Hour	Use-case pages with outputs and a tool route	New use cases outpace production
Neil Webzell	Trafalgar Wireless	Guides to mobility costs and workflows	Expertise sits across sales and operations
Jae Jun	Gorilla ROI	Answers on Amazon reports and formulas	Three ventures share a small team
Shawn Mintz	MentorCity	Resources on mentoring setup and engagement	Specific guidance takes specialist time
Siim Kostabi	Pageloot	Industry pages with setup steps and links	Each vertical requires research
Nicolas Falourd	CT Cyber Techwear	Product copy organized around functional uses	Technical content and site upkeep compete
Val Narodetsky	Odesa	Pages answering pre-signing process questions	Operators must confirm process figures
Paul Towers	Playwise HQ	Battlecard page tied to live sales work	Founder time limits field-tested detail
Kruno Sulić	Cliprise	Task-led pages with workflows and product links	Depth needs product and support input

Start with the problem, not the publishing calendar

Jae Jun of Gorilla ROI gave the clearest example of the shift. Rather than another broad ecommerce article, his team explains Amazon report fields, SP-API edge cases and spreadsheet formulas. He pointed to an article about why inventory figures differ between Seller Central reports. A seller searching that question already has a problem the product addresses. Jun attributes US$600,000 in annual revenue to organic search.

Playwise HQ founder Paul Towers described a similar decision on a sales page. The promise changed from broad sales-software language to competitive battlecards that remain useful during real deals. The supporting questions are operational: who updates a battlecard, what happens after a lost deal, and how does a representative handle an objection? That is a stronger page brief than “write about sales enablement.”

The tactic is not to make one page for every keyword spelling. It is to find the distinct task behind a search. Google's people-first guidance favors useful material made for people, not pages produced chiefly to capture traffic. Use keyword research to choose among buyer problems; use the buyer problem to decide what the page must actually contain.

Put the product proof beside the answer

Magic Hour co-founder Runbo Li described use-case pages that show sample outputs and let visitors try the tool. Its face-swap-video page puts the task, the output and the next step on one page. Li said it brings in thousands of organic visits a month and converts better than the homepage. The useful lesson is the page design: a visitor can see the result and act without navigating through a general product pitch.

Pageloot CEO Siim Kostabi described restaurant-menu QR-code pages with setup steps and a scan flow. Instead of making the visitor translate a general QR-code product page into a restaurant workflow, the page starts with that workflow. He also linked relevant industry pages together. Google's guidance on crawlable links explains why descriptive links help both discovery and understanding.

The same principle appeared outside SaaS. Nicolas Falourd of Cyber Techwear said his team rewrote product descriptions around functional uses, clarified variants and linked editorial posts to relevant products. The audience and purchase cycle differ, but the editorial test is the same: can the reader move from explanation to the right product decision without starting again?

The bottleneck is often the person who knows the answer

Rahul Agrawal of QuickIntell described pages for individual healthcare payers, authorization rules and claim codes. He reported about 7,200 Search Console clicks and 1.67 million impressions over 28 days; nine of his ten most-clicked pages concerned individual payers. His constraint is more interesting than the traffic number: payer instructions change, and someone must check the source before a page goes live.

Andrew Izrailo of Astra Trust made the same point for jurisdiction and compliance pages. A qualified practitioner must check the details while serving clients. Val Narodetsky of Odesa said process detail sits with the team doing the work, so documenting it requires an operator interview and checked figures. His reported average placement time of 4.2 days only helps a buyer when the page explains what the average covers.

This is where a content process can save real time. Give the expert the exact statement, its source and a focused question to decide. A short fact check is easier to complete than a full draft handed over at the end. At Xtrusio we call this standard Citation-Grade Content: every figure and claim is traced to a source and confirmed by the person who owns it before the page ships. Xtrusio connects buyer questions to AI answers and cited sources, turns the gaps into a content plan, and later checks whether the published URL appears in an answer. The customer team confirms its own product facts before publication.

Repair the pages you already have

Ian Lawson of Slickplan treats important pages as maintained assets. His response connected research, design, copy, launch and performance history, so the team can decide whether an existing page needs a rewrite, a structural fix, a user-experience change or nothing. He would expand that process across more existing pages before increasing output.

Izrailo described consolidating pages that competed for the same jurisdiction topic. Dora Bloom of iotum described site work during a rebuild: clearer titles and descriptions, image descriptions and compressed images after loading slowed. Google's title-link guidance supports concise, descriptive page titles. The right repair depends on what is stopping that particular page from serving its reader.

Before assigning a new article, ask whether a page already serves the same question. If so, the brief may be to repair its missing fact, structure, links or next step. A second page that repeats the same answer can add work without helping the buyer.

The 15 responses, in their own business contexts

These accounts show how the same strategic shift looks in different businesses. Each leader identifies a customer question worth answering and the work required to answer it well. Examples and results are paraphrased from their written responses; proposed pages are described as ideas, rather than finished work.

Teri Maltais, iTacit

Teri Maltais

VP of Revenue

iTacit

Changed: Maltais focuses iTacit content on frontline communication, mobile training, forms and compliance questions. Her example is a page answering how to improve training completion for deskless employees, with the practical detail that question deserves. Constraint and next move: The people with the strongest subject knowledge are busy. She would publish more expert-led answers to specific use cases and customer questions.

Olga Kokhan, Tinkogroup

Olga Kokhan

CEO

Tinkogroup

Changed: Tinkogroup favors problem-led articles with the answer near the top. Kokhan's example, outsourced versus in-house data entry, would let a buyer weigh cost and operating tradeoffs before choosing an approach. Constraint and next move: Publishing that kind of comparison consistently means bringing customer knowledge from subject experts into the draft, rather than working from a keyword list alone.

Dora Bloom, iotum

Dora Bloom

Chief Revenue Officer

iotum

Changed: During a site rebuild, iotum rewrote page titles and descriptions, added image descriptions and compressed images when loading slowed. Bloom watched load time and traffic afterward. Constraint and next move: A small marketing team owns the website alongside other work. She would add fair softphone comparisons for buyers considering alternatives.

Rahul Agrawal, QuickIntell

Rahul Agrawal

Founder & CEO

QuickIntell

Changed: QuickIntell built pages about individual payers, authorization and eligibility questions, and claim codes instead of broad AI-in-healthcare articles. Agrawal reported 7,200 Search Console clicks and 1.67 million impressions in 28 days, with nine of the ten most-clicked pages focused on payers. Constraint and next move: Payer rules change, requiring source review. He would cover more payer and specialty combinations and improve titles on high-impression, low-click pages.

Andrew Izrailo, Astra Trust

Andrew Izrailo

Senior Corporate and Fiduciary Manager

Astra Trust

Changed: Astra Trust added named qualified authors to compliance and jurisdiction pages, answered journalist inquiries under those experts' names and consolidated pages competing for one jurisdiction topic. Constraint and next move: Practitioners must verify changing legal information while serving clients. With more review capacity, Izrailo would cover more jurisdictions.

Ian Lawson, Slickplan

Ian Lawson

Founder | Website Planning, UX & Content Strategy Expert

Slickplan

Changed: Slickplan connects page research, design, copy, launch and performance history. Lawson uses search and behavior data to decide whether a page needs a rewrite, structural change, UX work or no change. Constraint and next move: Experienced people still decide what to do. He would apply the maintenance system across more existing pages before increasing volume.

Runbo Li, Magic Hour

Runbo Li

CEO

Magic Hour

Changed: Magic Hour makes pages for particular AI-video jobs, with output examples and a route to try the tool. Li pointed to its face-swap-video page, which he said brings in thousands of organic visits monthly and converts better than the homepage. Constraint and next move: Use cases emerge faster than the team can build pages. He would watch demand and prepare assets and drafts for human review.

Neil Webzell, Trafalgar Wireless

Neil Webzell

CEO

Trafalgar Wireless

Changed: Trafalgar Wireless favors explanations of unused lines, roaming costs, provisioning and billing over broad enterprise-mobility articles. Each topic begins with a cost or workflow problem a buyer can recognize. Constraint and next move: The knowledge lives in sales, support and operations, where documenting it competes with other work. Webzell would add guides on line audits, roaming controls, device replacement and zero-touch provisioning.

Jae Jun, Gorilla ROI

Jae Jun

Founder

Gorilla ROI

Changed: Gorilla ROI writes about Amazon seller reports, SP-API edge cases and formulas. Jun cited an explanation of differing Seller Central inventory figures. He attributed US$600,000 in annual company revenue to organic search. Constraint and next move: A small team runs three ventures without a dedicated marketer. He would hire a writer who understands Amazon seller operations.

Shawn Mintz, MentorCity

Shawn Mintz

CEO

MentorCity

Changed: MentorCity moved from broad mentoring benefits toward resources about setup, matching, engagement and measurement. Those are the decisions a program manager must make to get a mentoring program running. Constraint and next move: Specialist material takes time to produce without falling into generic copy. Mintz would create a library for program managers before, during and after launch.

Siim Kostabi, Pageloot

Siim Kostabi

CEO

Pageloot

Changed: Pageloot rewrote pages for industries rather than one generic QR-code term. Kostabi described a restaurant-menu page with setup instructions, a scan flow and links among relevant industry pages. Constraint and next move: Each industry page takes research. He estimated 30 to 40 possible verticals and would cover more, then translate useful pages into six to eight languages for a customer base he said was mostly non-English.

Nicolas Falourd, Cyber Techwear

Nicolas Falourd

CEO

CTCyber Techwear

Changed: Cyber Techwear rewrote product descriptions around functional uses, clarified variant information and linked trend-led posts to products and style guides. Falourd said the changes improved discoverability. Constraint and next move: The team has limited time for technical content and site maintenance. He would add localized guides, product how-to pages and more detailed structured data.

Val Narodetsky, Odesa

Val Narodetsky

CEO

Odesa

Changed: Odesa rebuilt pages around questions asked before signing. Narodetsky said a placement-time page puts the company's reported average of 4.2 days from sourcing to onboarding near the top and explains the steps. Constraint and next move: The detail sits with client-facing operators and its figures need checking. He would document each core process and refresh the numbers as they change.

Paul Towers, Playwise HQ

Paul Towers

Founder & CEO

Playwise HQ

Changed: Playwise HQ moved a landing page from broad sales-software language to a promise about battlecards useful during live deals, supported by questions about objections and deal reviews. Constraint and next move: Field-tested detail competes for founder time while the product is built. Towers would publish more practical competitive-sales and buyer-question pages.

Kruno Sulić, Cliprise

Kruno Sulić

Founder & SaaS Product Builder

Cliprise

Changed: Cliprise structures pages around particular jobs, with direct answers, workflow detail, comparisons and relevant product links. Sulić's example is a page that walks through turning one idea into several short-form creative variations, including the decisions a user makes along the way. Constraint and next move: Depth needs marketing, product and support input. He would add use-case, comparison, workflow and glossary pages while refreshing current pages.

Turn the interviews into a 30-day content plan

1. Choose five buyer questions. Include questions asked near a purchase decision, not only broad category definitions. Search demand helps prioritize; customer fit decides whether the work belongs on your site.
2. Find the best existing page for each question. If one already answers it, mark the missing fact, example, structure or next step. If the task is truly different, plan a new page.
3. Get facts from the person who owns them. Ask for the exact claim, a source or demonstration, and the last date it was checked. Do not ask a specialist to review an entire vague article when one paragraph is the real dependency.
4. Publish the answer and the route onward. Put the useful answer high on the page. Show the workflow, evidence or product detail the buyer needs, then link to the relevant next action.
5. Check three different outcomes. Search Console's Performance report can show queries, impressions and clicks. Site analytics can show what visitors do next. If AI visibility matters, save the engine's answer, date and exact cited URL. Google's AI-features guidance explains the search foundations behind AI features.
6. Decide what to maintain. Keep the owner, source and review date with a page whose facts change. A maintained page may beat another entry in the calendar.

The pattern across these responses is specific: leaders knew more useful questions than their teams could answer well. The next move is to remove the one constraint blocking a valuable page, whether that is an expert review, a missing example or a neglected existing URL. Xtrusio can help a team connect its buyer questions to AI answers and cited sources, plan the needed content and check whether a later answer cites the published page. If that is the gap in your process, start with the free plan or ask about the managed trial.