Content Strategy & AI Innovation Case Study:

That fragmentation created a practical content problem. Before a campaign, messaging matrix, executive byline, or article launched, quality depended heavily on who was in the room and what they happened to remember. Audience context had to be reconstructed for each project. AI could accelerate production, but without strong context, it could also accelerate generic language, unsupported claims, and messaging that sounded polished without sounding true.

My opportunity was not simply to write a better persona or create a better prompt. It was to turn what bswift already knew into persistent strategic context, and then put that context inside the workflow where marketing decisions were being made

The Plan

I adapted the Express stage of Loop Marketing into a practical operating layer for bswift. Loop Marketing moves through four connected stages: Express, Tailor, Amplify, and Evolve. It treats market response as intelligence that should improve the next cycle. HubSpot's framework begins with a Taste Profile, then recommends pressure-testing concepts against an ideal customer profile before committing to a direction.

I built the bswift Taste Profile in two parts.

Customer Taste: How the buyer experiences our marketing

Instead of stopping at job titles, firmographics, or surface-level pain points, I synthesized how benefits buyers actually evaluate a message:

• The emotional state they bring to the content
• The vocabulary that signals insider understanding
• The proof that reduces professional risk
• The situations in which a message becomes relevant
• The claims and tones that trigger immediate skepticism
• The peers and practitioners they trust

The verified research behind the profile includes roughly 20 platform reviews, multiple practitioner-community threads, more than half a dozen RFP semifinalist, finalist, and implementation-kickoff transcripts, broker and client interview notes, approved testimonials and case studies, an AEO buyer-query analysis, existing-client working sessions, and a strategy session with a senior benefits leader.

The synthesis revealed a buyer who is less interested in "innovation" as an abstraction than in what changes, what breaks, who owns the handoff, what the client lift will be, and what happens when the data is wrong. The practitioner is battle-tested: tired, alert to hidden labor, and skeptical of sales language, but still deeply invested in making benefits work for employees.

It also surfaced specific anti-triggers. Unsupported ROI becomes "squishy." AI without a defined task, data boundary, human review point, and exception path reads as a badge. "Seamless" without the workflow beneath it sounds like "rainbows and unicorns." For this audience, every major claim needs a mechanism and proof.

Brand Taste: What bswift believes and how it should show up

For Brand Taste, I turned extensive interviews with bswift’s C-suite leadership into a concise, reusable expression of the company’s brand, product, and thought leadership point of view. The goal was not to create another style guide. It was to capture the strategic judgment behind the brand: what bswift believes, how it sees the market, what makes its approach distinct, and where it draws the line on the claims it makes.

I condensed those conversations into three short narrative frameworks: a Brand Story that grounds the company in the human stakes behind benefits; a Product Story that explains how bswift approaches technology, service, complexity, and accountability; and a Thought Leadership Profile that defines the positions the company can credibly take on issues such as AI, personalization, engagement, and the role of technology in benefits.

Around those narratives, I built practical guardrails for how the brand should communicate. Claims had to distinguish evidence from conviction, explain the mechanism behind the promise, acknowledge meaningful limitations, and avoid the kinds of unsupported technology and ROI language our buyers were already skeptical of.

The result was a point of view that could guide very different kinds of work without exposing the underlying internal narratives themselves. You can see elements of it in bswift’s public employee engagement and activation story and in executive thought leadership such as Ted Bloomberg’s Forbes article, AI in Employee Benefits: Usefulness Is the Bar, but Trust Is the Scoreboard. The Taste Profile’s role was to turn what lived in the heads of bswift’s senior leaders into a compact strategic system that human creators and AI tools could apply consistently—even when those executives weren’t in the room.

Customer Story and Perception Gaps: the distance between what we say and what buyers believe

Brand Taste captured the story bswift wanted to tell. I also needed to understand how customers and prospects currently perceived the company—and where their existing beliefs aligned with or diverged from that intended narrative.

I analyzed selected reviews, customer references, demonstrations, prospect and customer interviews, and related material to identify the themes customers and prospects consistently emphasized. Because the evidence was qualitative and selected, I treated it as directional insight rather than representative brand tracking.

The analysis surfaced several recurring themes:

• Flexibility for complex environments
• Service and access to real people
• Integration and ecosystem fit
• Proof of the administrative foundation before personalization
• One connected experience with fewer handoffs
• Practical AI with clear controls

It also revealed areas where customers appeared to place more value than our marketing consistently reflected: the relief of knowing who owns the next step, the usefulness of controlled complexity rather than oversimplification, the operating details behind implementation and exception handling, differences in access across employee populations, and the credibility gained by clearly explaining what a capability does not do.

From there, I mapped the intended bswift story against current or legacy perceptions. For example:

• We wanted administration and activation to be understood as one connected experience, but bswift could still be perceived primarily as an enrollment and administration platform.
• We wanted AI to represent practical improvements in quality and capacity, but buyers could interpret it as a feature badge or future promise.
• We wanted an open ecosystem with accountable ownership, but integration breadth could sound like more complexity for the client to manage.
• We wanted service and scalable technology to reinforce one another, but service could be interpreted as compensation for the technology rather than part of the design.
• We wanted benefits activation to connect to business outcomes, but “engagement” could still be understood as communications activity rather than employee action.

For each gap, I identified what the content needed to clarify and what proof would be required to earn the intended narrative. That proof agenda included time-on-task and workload evidence for strategic capacity; journey-level evidence for reduced fragmentation; baseline and post-campaign action evidence for activation; workflow, error, rework, and human-review evidence for AI; service-resolution evidence; and segmented reach and action evidence for frontline strategies.

This layer was essential because the Buyer Sim needed more than a buyer profile and an internal brand narrative. It needed to understand the distance between what bswift wanted to say and what the market was currently prepared to believe.

Customer Taste captured how the buyer evaluates marketing. Brand Taste captured the company’s intended point of view. Customer Story and Perception Gaps captured existing market belief and the evidence required to move it.

Together, those layers allowed the system to test not only whether a message was relevant and on-brand, but whether it credibly closed—or accidentally widened—the gap between the two.

The Work

Once the customer and brand contexts were complete, I brought them together into a reusable source of strategic guidance. The resulting profile documented not just what the audience looks like, but how its members evaluate marketing, what earns their trust, and what makes them skeptical.

The work established a shared understanding of the buyer's expectations and a consistent way to apply that understanding to content. It also connected those expectations to bswift's brand narrative, giving marketing a way to evaluate whether a message was both relevant to the audience and consistent with what the company could credibly claim.

This created the foundation for a more consistent content workflow. Rather than reconstructing audience context for each assignment, marketing could draw on the same documented understanding of buyer language, emotional states, proof expectations, and anti-triggers.