Case Study

The BigTech Reseller IBM Exposure Campaign: Eighteen Doors Into the Same Building

One IBM Question, Eighteen Properties, Each Answering It From a Different Angle

Krisada / Claude 16 views
Proof Point

A trailing 30-day pull from the live Digital Karma Data Warehouse across all 18 properties shows 81,615 GSC impressions,…

Measurement Frame

What was measured.

Total Properties 18
AS400 Family Properties 17
Reseller Layer Properties 1
Measurement Window trailing 30 days
Measurement Date 2026-08-21
Total GSC Impressions 30d 81,615
Total GSC Clicks 30d 268
Total Good Bot Requests Captured 30d 37,888
Properties With Zero GSC Signal 2
Properties With Zero Captured Bot Data 11
Known Bot Data Blind Spot flashsystem.as400system.com (confirmed heavily AI-crawled despite zero captured rows)
Properties Returning HTTP 403 2
HTTP 403 Properties power5.as400system.com, power6.as400system.com
Documented Sub Campaigns 2
Why It Matters

The short version.

The BigTech Reseller IBM Exposure Campaign is the Project Everywhere thesis applied to one vertical: instead of one AS400/IBM Power site trying to rank for every generation, product line, and buyer intent at once, the portfolio runs 17 AS400-family properties plus BigTechReseller.com as 18 separate leverage nodes, each with its own commercial role, cross-linked and cross-referenced rather than competing with itself. The IBM FlashCore Module campaign and BigTechReseller's Editorial Voice Guide arc, both already documented as their own case studies, are chapters inside this larger strategy, not separate initiatives.

Context

What was the system?

AS400System.com, AS400Software.com, AS400IBMSystem.com, and AS400IBMSystems.com are the flagship base properties. Around them sit Power5 through Power12 generation-specific subdomains, an AI subdomain covering IBM Bob and watsonx on IBM i, a FlashSystem storage-hardware subdomain, two Pricing subdomains splitting hardware and software economics, and a Security subdomain for IBM i-specific protection. BigTechReseller.com sits outside the as400.* namespace entirely, as the multi-vendor comparison layer where IBM competes against Dell, HPE, and others on the same buyer's page. None of these were built as duplicate coverage of the same content. Each one exists because a different real buyer question needed a property built around answering just that question well, per Krisada's established portfolio philosophy that redundancy crowds out competitors rather than competing with itself.

Methodology

What changed?

The build order tracked real gaps as they were found, not a fixed roadmap. Power9.AS400System.com got dedicated lifecycle, sourcing, and migration content in mid-August after earlier end-of-life articles showed real demand. AI.AS400System.com launched from scratch to cover IBM's AI-on-IBM-i push, catching and removing a fabricated feature ("Db2 for i Machine Learning") the first content pass had invented, and adding IBM's real flagship product (Bob, GA'd March 2026) that had been missing. FlashSystem.AS400System.com launched as a major build, then got substantially expanded eleven days later once IBM shipped a fifth FlashCore Module generation and a competitive-analysis pass identified specific model pages the portfolio had never built. Two paired Pricing subdomains, Pricing.AS400System.com and Pricing.AS400Software.com, split hardware economics from software licensing economics rather than mixing both on one page. Security.AS400Software.com shipped in two sessions, built and verified locally first, then actually deployed once its subdomain and SSL were provisioned, rather than claiming a launch before the infrastructure existed. Power5 and Power6, the two oldest and quietest properties in the family, got formally added to the Big Tech constellation and given real krisada.com portfolio listings only in mid-August, after sitting outside that connective structure for longer than the newer builds. As of this writing, both currently return an HTTP 403 rather than a live page, a gap this case study is flagging rather than glossing over.

Findings

What did the evidence show?

A trailing 30-day pull from the live Digital Karma Data Warehouse across all 18 properties shows 81,615 GSC impressions, 268 clicks, and 37,888 captured Good Bot and AI-crawler requests, concentrated unevenly: AS400Software.com, AS400System.com, and AS400IBMSystems.com together account for roughly two-thirds of total impressions, while Power5 and Power6 currently register zero GSC signal, the two most recently integrated properties in the family.

The honest gap is in the bot data, not the search data. Eleven of the 18 properties show zero captured Good Bot or AI-crawler requests in this window, including FlashSystem.AS400System.com, a property separately confirmed to be heavily AI-crawled with a documented warehouse ingestion blind spot rather than genuinely quiet. Reporting those eleven as literal zero traffic would misstate what's actually known. They're better read as unconfirmed, not unvisited, until the nightly import gap closes.

The subdomain strategy's real test isn't whether every property ranks. It's whether a buyer question that used to have one flagship site trying to answer it now has a property built specifically around that question, and whether the flagship sites get to stop being generalist pages competing with their own specialist siblings for the same search intent.

Key Takeaway

What can be reused?

Eighteen properties answering eighteen different versions of "what do I need to know about IBM Power and AS400" isn't fragmentation. It's the same Project Everywhere logic, an interconnected system built for entity clarity and authority, run at the scale of a single vertical instead of the whole portfolio. The FlashCore Module campaign and the BigTechReseller Editorial Voice Guide are what two chapters of that strategy look like up close. This case study is the map of the building they're both rooms in.

Evidence Library

Keep Browsing the Case Library

Move from this evidence file back into the full proof system.