By James Aspinwall
Jimmy put together a comprehensive messaging and structural plan for the WorkingAgents website. It’s thorough, enterprise-focused, and shows real thought about how to position an AI governance product. But before building to this spec, several contradictions, redundancies, and gaps need to be resolved. Shipping a site with unresolved internal conflicts produces a page that feels polished but says nothing clearly.
Here’s the plan section by section, with what works, what doesn’t, and what’s missing.
1. Global Positioning Layer
What it says: Establish category ownership with a positioning statement in the first five seconds. Enforce a hierarchy: Business outcome → Risk context → Governance solution → Technical credibility. Maintain a single unified messaging track for Phase 1 — no persona toggle.
What works: The hierarchy is sound. Leading with outcomes and ending with technical proof is the right order for enterprise sales pages.
Issues:
-
Contradiction with later sections. The plan says “single unified messaging track, no persona toggle,” but then creates a dedicated “For Leadership” executive block, separates CTAs into executive-primary and technical-secondary, and isolates architectural content behind accordions. That is persona splitting — it’s just done inline rather than with a toggle. Either commit to a single track that serves both audiences in every section, or acknowledge that Phase 1 already has soft persona separation and design for it.
-
“Prevent regression into feature-first messaging” is a process note, not a design spec. It belongs in a content style guide, not a page structure document. Including it here blurs the line between what the site should say and how the content team should work.
-
“Governance layer” is undefined. The term “governance” appears throughout the entire plan but is never defined. Does it mean access control? Audit logging? Policy enforcement? Compliance reporting? All of the above? A category-defining positioning statement can’t use an undefined category. Before writing the hero line, define what governance means for WorkingAgents in one sentence.
2. Hero Section
What it says: Rewrite the headline to focus on enablement, not danger. State what the platform does, for whom, and why in one subheadline. Replace generic CTAs with outcome-driven ones. Add a three-bullet micro-value strip.
What works: Outcome-first hero messaging is correct. “Explore Platform” is a dead-end CTA — the suggested replacements are better.
Issues:
-
The micro-value strip duplicates the Business Impact section directly below it. Three bullets summarizing core value pillars (deploy securely, enforce least-privilege, maintain auditability) will read almost identically to the Business Impact section’s capability-to-outcome bullets. The reader sees the same message twice in adjacent sections. Pick one location. The micro-value strip works if the Business Impact section is removed or substantially differentiated.
-
“Book Executive Briefing” as primary CTA assumes operational readiness. For an early-stage product, every click on that button creates an expectation the team must fulfill with a human on a call. If the company can’t sustain that volume, the primary CTA should be something self-serve — a demo video, an interactive architecture walkthrough, or a sandbox. Reserve executive briefings for a secondary or gated CTA.
3. Business Impact Section
What it says: Insert an executive translation layer below the hero. Structure each bullet as Capability → Business Impact → Strategic Value. Avoid jargon. Focus on measurable outcomes.
What works: The formula is good. Translating features into outcomes is exactly what enterprise buyers need.
Issues:
-
Redundant with the Executive Summary Block (section 8). Both sections target executives, both avoid technical language, both translate capabilities into business value. The Business Impact section does it with a capability→impact→value formula. The Executive Summary does it with board-level bullet points. These are the same audience receiving the same message in two different formats on the same page. Merge them or give each a distinct purpose — one for operational executives (VP/Director), one for board-level (CEO/CFO), for example.
-
“Measurable outcomes” requires actual measurements. Reduced AI risk exposure, prevention of AI sprawl, accelerated compliant deployment — these only land if there are numbers attached. Without pilot data or benchmarks, “measurable” outcomes are just adjectives. Either produce the numbers or reframe as qualitative benefits until real data exists.
4. Use Case Section
What it says: Add three to five narrative-driven scenarios structured as Context → Risk without governance → Resolution via platform → Measurable outcome.
What works: Narrative use cases are far more effective than feature lists for enterprise buyers. The suggested scenarios (customer operations, procurement, internal analytics, e-commerce, cross-department) cover reasonable verticals.
Issues:
-
The “Risk without governance → Resolution via platform” structure duplicates the Comparison Block (section 6). The use cases tell a before/after story per scenario. The comparison block tells the same before/after story in aggregate. The reader gets the without/with contrast three times: in use cases, in the comparison block, and implicitly in the Business Impact section. Cut the comparison block or make the use cases purely narrative (context, workflow, outcome) without the explicit risk/resolution framing.
-
Five use cases is too many for a homepage. Three is the right number. Each one should be specific enough to feel real and short enough to scan in under 30 seconds. Five will cause scrolling fatigue and dilute the impact of each.
5. Social Proof and Trust Layer
What it says: Add customer logos, testimonials, quantified pilot results, security certifications. Use structural placeholders if real content isn’t available yet.
Issues:
-
Empty placeholders are worse than no section at all. A “Trusted by” section with placeholder logos signals “nobody trusts us yet” louder than the absence of the section. If there are no real logos, testimonials, or pilot results, don’t build the section. Add it when real proof exists. The structural preparation should happen in code (modular components, defined slots), not on the visible page.
-
Security certifications (SOC 2, ISO 27001, etc.) require actual certification. Listing them as “if available” suggests they don’t exist yet. If they don’t, mentioning certifications as a placeholder creates a credibility gap. Instead, describe the security architecture and link to documentation.
6. Comparison Block
What it says: Add a “Without Governance vs With Governance” visual comparison. Left column: credential sprawl, uncontrolled API access, no audit trace, shadow AI growth. Right column: centralized access control, least-privilege enforcement, complete audit logs, structured scaling.
Issues:
-
This is fear-based framing, which contradicts section 2. The hero section explicitly says to avoid danger framing and position security as an enabler. The left column of the comparison block is pure danger framing — credential sprawl, shadow AI, no audit trace. You can’t say “don’t use fear” in the hero and then build a fear-based comparison block three scrolls down.
-
Redundant with the use case section. As noted above, use cases already provide a before/after narrative. The comparison block restates it in a different visual format. Choose one.
Recommendation: If the comparison block stays, reframe the left column as “current state” rather than “danger state” — e.g., “manual credential management” instead of “credential sprawl.” This preserves the contrast without the fear tone.
7. Technical Depth Structure
What it says: Move detailed architecture into accordions or a dedicated page. Keep the homepage outcome-first.
What works: This is correct. Architecture details matter but belong behind a click or on a separate page.
No issues. This is one of the clearest and most actionable items in the plan.
8. Executive Summary Block
What it says: Add a “For Leadership” section with four to five bullets on why AI governance is a board-level issue: regulatory exposure, brand risk, data protection, scalability control, operational visibility.
Issues:
-
Redundant with the Business Impact section (section 3). Both target executives, both avoid technical language, both justify the product in business terms. See section 3 critique above.
-
“For Leadership” as a label violates the single-track principle. Labeling a section “For Leadership” is persona targeting. If the plan says no persona toggle in Phase 1, this section shouldn’t have a persona label. Either remove the label and integrate the content into the main flow, or acknowledge that the page already has implicit persona sections.
-
The bullet points are risk-focused, contradicting the enablement framing. Regulatory exposure, brand risk, data protection — these are all fear-based motivators. The hero section says to lead with enablement. This section leads with risk. The messaging is pulling in two directions.
9. Product Visualization
What it says: Add UI screenshots, an animated explainer, or a governance flow diagram mid-page.
What works: Visual proof that the product exists and does something real is essential. A screenshot or flow diagram worth a thousand positioning statements.
Issue:
- “Governance flow diagram” is vague. What flow? Agent request → access check → execution → audit log? User creates policy → policy applied to agent pool → violation flagged? Define the specific flow before designing the visual, or it will default to a generic architecture diagram that doesn’t communicate the product experience.
10. CTA Strategy Alignment
What it says: Primary CTA is executive-focused (Book Executive Briefing). Secondary is technical (View Architecture). Consistent placement in hero, mid-page, and footer.
Issues:
-
Repeats guidance already given in the hero section. The CTA strategy is stated in section 2 and restated here. This is a duplicate.
-
Three CTA placements with the same language will feel repetitive. Vary the phrasing slightly by context — the hero CTA can be more aspirational, the mid-page CTA more specific (e.g., “See how governance works for [use case]”), and the footer CTA more direct.
11. Maintenance and Modular Structure
What it says: Build modular components to allow future persona toggling without duplication.
This is an engineering requirement, not a messaging item. It belongs in a technical spec for the frontend team, not in a content strategy document. Including it here conflates what the site says with how the site is built.
What’s Missing
The plan is detailed about messaging structure but silent on several things an enterprise website needs:
-
Pricing or pricing philosophy. Enterprise buyers want to know if this is usage-based, per-seat, per-agent, or custom. Even “Contact us for pricing” is a positioning decision. Silence on pricing suggests it hasn’t been decided — which is fine, but the site needs to address it.
-
Integration and compatibility. Which AI platforms does WorkingAgents support? Claude, GPT, Gemini, open-source models? This is one of the first questions a technical evaluator will ask. It’s absent from the entire plan.
-
Team and company credibility. For an early-stage company selling to enterprises, “who are you?” matters as much as “what do you sell?” A team page, founder background, or company story builds trust that no amount of positioning language can replace.
-
Time to value and onboarding. How long does deployment take? Hours, days, weeks? Enterprise buyers evaluate switching cost as heavily as capability. A “deploy in under a day” message (if true) would be more compelling than most of the positioning work in this plan.
-
Open-source or community angle. If WorkingAgents has an open-source component, that’s a significant trust and adoption driver for technical evaluators. The plan doesn’t mention it.
-
Content and resources. No mention of a blog, documentation hub, or resource section. For an enterprise product, a well-maintained blog and documentation library are primary trust signals and SEO drivers.
Summary of Issues
| Issue Type | Count | Examples |
|---|---|---|
| Contradictions | 3 | Fear framing banned in hero but used in comparison block and executive summary; single track declared but persona sections created; enablement vs risk messaging conflict |
| Redundancies | 4 | Business Impact ≈ Executive Summary; micro-value strip ≈ Business Impact; use cases ≈ comparison block; hero CTAs ≈ CTA strategy section |
| Missing info | 6 | Pricing, integrations, team page, onboarding timeline, open-source angle, content/blog strategy |
| Unclear | 3 | “Governance” undefined, product visualization flow unspecified, placeholder strategy risks |
| Wrong document | 2 | “Prevent regression” is process guidance; modular structure is engineering spec |
Recommendation
The plan has the right instincts — outcome-first, executive-focused, technically credible. But it needs a consolidation pass before implementation. Merge the redundant executive sections. Resolve the fear-vs-enablement contradiction by picking one tone and applying it consistently. Define “governance” in one sentence before writing any copy. And fill the gaps — pricing, integrations, team, onboarding — because enterprise buyers will ask these questions whether the site answers them or not.
Build three sections well rather than eleven sections that overlap.