White Wolf Nutrition and BlackWolf Nutrition share an operator, not an interchangeable identity. Their operating layer had to know which brand it was serving, use the correct credentials and report the difference between a live connection and a prepared wrapper.
Evidence at publication: four configured agents and 16 bindings were observed on 30 May 2026; Klaviyo access was configured for both White Wolf and BlackWolf, and segment retrieval was verified. Shopify, Cin7, Mintsoft, Xero, HubSpot, GA4 and Google Ads expansion remained credential-dependent.
The company
Matt Bignold runs White Wolf Nutrition and BlackWolf Nutrition. Across the two brands, customer records, email marketing, inventory, fulfillment, advertising, analytics, accounting and team communication touch a long list of systems. Shopify, HubSpot, Cin7, Mintsoft, Xero, Gmail, Klaviyo, Meta, GA4, Google Ads, Slack and Discord all matter to the operating picture.
The complexity is not only technical. A useful assistant must know which brand is in scope before it retrieves an audience, applies a tone of voice or prepares an asset.
The constraint
Valuable data lived in separate platforms, and brand-specific knowledge was split across the team. Connecting the platforms mechanically would not resolve the ambiguity. The operating layer still had to select the right brand, credential, policy and workspace for each request.
The risk worked in both directions: cross-brand context could be mixed accidentally, while disconnected providers could be presented as available when they were only planned. Both failures erode trust.
Why existing tools were not enough
Klaviyo can segment an audience and Shopify can return an order, but neither decides which specialist should receive a request or what context may safely cross between brands. A dashboard can expose data without enforcing brand-specific behavior. A generic assistant can speak confidently without proving that its provider call succeeded.
RECAST organized the work into operations, ads, content and strategy lanes, then built brand-aware wrappers with explicit connection states. The architecture could grow toward more providers without calling the whole roadmap live on day one.
Transformation map
Before
Two brands across commerce platforms → team selects accounts and reconciles context → one-off analysis or asset
After — verified Klaviyo read lane with provider-gated expansion
Brand request → specialist workspace → correct brand wrapper → verified data or explicit missing-key status → human-reviewed action
One workflow, end to end
The safest retained proof is the Klaviyo inspection route.
- Input: The team requests an email-segment check for White Wolf or BlackWolf.
- Brand resolution: The operating layer selects the brand-specific Klaviyo wrapper and credentials.
- Routing: The request moves to the appropriate operations, content or ads-and-copy workspace.
- Retrieval: The wrapper queries the selected Klaviyo environment; segment retrieval was verified for both brands.
- Interpretation: The specialist turns the returned audience context into an analysis, email direction or content requirement.
- Human gate: Any live campaign change or send remains supervised rather than inferred from read access.
- Honest fallback: If a request needs Shopify, Cin7, Mintsoft, Xero, HubSpot, GA4 or Google Ads before credentials are active, the system reports the dependency instead of fabricating a result.
What changed
- Built: Four role-specific workspaces, brand-aware wrappers, a live Command Center service and document and creative production tools.
- Connected: Klaviyo access for both White Wolf and BlackWolf was configured in the operating environment.
- Tested: Segment retrieval was verified for both brand accounts; system hardening included SSH changes, fail2ban and a controlled reboot.
- Data lane and foundation verified: Four agents, 16 bindings and the Command Center service were observed on 30 May 2026.
- Actively used: The source does not retain routine request volume or evidence of unsupervised campaign execution.
- Provider or client dependency remaining: Shopify, Cin7, Mintsoft, Xero, HubSpot, GA4, Google Ads and wider provider actions require credentials and lane-by-lane verification.
- Financial result reported by client: None retained.
Proof
- Data receipt: Klaviyo segment retrieval succeeded for both brands.
- Agent receipt: Main/Max, Ads & Copy, Content Engine and Strategy & Research were configured.
- Routing receipt: 16 bindings were observed at verification.
- Runtime receipt: The Command Center service was live in the inspected environment.
- Claim boundary: Read access and retrieval do not imply campaign sends, store writes, inventory changes or financial outcomes.
Technology - revealed last
The system uses OpenClaw 2026.5.6, Slack, Discord, billing-proxy routing, a Command Center service, Klaviyo wrappers, gws-auth, PDF/OCR tools, Higgsfield, Printing Press and dedicated content and advertising skills. Meta, GA4, Google Ads and Shopify/Cin7 paths were prepared as brand-aware wrappers or scaffolding. They are named here as architecture, not represented as active provider evidence.
Client quote
No source-backed verbatim client quote is published for this case. The public evidence is the two-brand Klaviyo retrieval and the inspected operating environment.
Next transformation
See how Ramon's provider-ready commerce layer separates shared knowledge from store-specific credentials. White Wolf adds a verified two-brand data lane; Ramon shows the architecture for a larger store portfolio.
Get your AI blueprint
If every cross-brand request begins with finding the right login and reconstructing context, the constraint is not another dashboard. Book a free AI audit to identify the first read-only data lane worth proving safely.
Source record
- OPENCLAW-DEEP-CLIENT-CASE-STUDIES.pdf, page 8.
- RECAST_CASE_STUDIES_2026_UPDATED.pdf, page 11, document RA-CASES-001, version 2.0.
- RECAST_WEBSITE_MASTER_BLUEPRINT.md, sections 10.4, 11 and 58.