Listing Alignment Grader¶

Beta

Listing Alignment Grader is a Beta capability (is_beta = true). It's stable enough to act on, but dimensions, weights, and wording may change as the proof model matures.

Capability slug: listing_alignment_grader Plan Tier: Command Backend: One external website read + a single Bedrock (Claude Sonnet) judge call Estimated credits: 12

Overview¶

A buyer researching your product — or their AI assistant doing it for them — doesn't just read your AWS Marketplace listing. They cross-check it against your website, third-party review sites, and any content AWS has co-published. When those sources disagree with your listing, you look unproven, and assistants reach for a rival they can corroborate.

The Listing Alignment Grader runs that cross-check for you before you publish. It grades how well your external proof aligns with what your listing claims, against your stated GTM objectives, and turns every shortfall into a concrete next action.

It is the pre-publish counterpart to the Discovery Dashboard's Live Mirror:

Live Mirror — "Do AI assistants surface me?" (what buyers see now)
Alignment Grader — "Is there consistent, credible proof for them to surface?" (whether that proof exists)

What it grades¶

Three dimensions, scored 0–100 each and combined into a weighted overall score:

1. Website alignment¶

Does your company website clearly present this offering, and is its positioning consistent with the listing? A resilient external read pulls your site text, and a single Bedrock judge call scores alignment strictly from that text — it degrades honestly when there's no website on file or the site can't be read.

2. Third-party validation¶

Does credible third-party proof corroborate the offer — G2, Capterra, TrustRadius, Trustpilot, Gartner, named customer logos, quantified testimonials, awards, case studies? The same judge call lists only the signals actually present and scores by strength and specificity.

3. AWS co-authored content¶

Does first-party AWS proof exist — joint blog drafts or Partner Central case studies? This is read from internal records (no external call): 0 pieces = none, 1 = thin, 2+ = established.

Category-aware weights¶

Each AWS Marketplace category proves itself differently, so the three dimensions carry different weight per category. Each profile sums to 100%.

Category	Website	Third-party validation	AWS co-authored content
SaaS (baseline)	40%	30%	30%
AI Agents & Tools	45%	20%	35%
AMI	45%	25%	30%
Container	45%	25%	30%
Professional Services	35%	40%	25%

The category keys mirror the Listing Optimizer's ListingScoreWeights, so a listing resolves its category once and both tools weight consistently. The rationale tracks the discovery physics: agent-native products lean on website + AWS technical proof (young domains, thin reviews), while professional services lean on third-party trust because humans procure.

What you get back¶

Field	Meaning
`overall_alignment_score`	0–100, the weighted composite
`status`	`launch_ready` (≥85, no high-priority gaps) · `mostly_aligned` (≥70) · `needs_proof` (≥40) · `unproven` (<40)
`dimension_scores`	Per-dimension score, weight, and weighted contribution
`objectives`	Prioritized list of gaps, each with why it matters and a CTA
`summary`	One-line, publish-aware verdict

Objectives — every gap becomes a next action¶

Each dimension that comes up short (below the ready threshold of 70) becomes an objective, ranked by priority and expected score gain. Where a Vellocity capability closes the gap, the objective carries its slug and route so the dashboard renders a button:

Gap	Objective	Wired capability
Website weak / missing	Make your website tell the same story as your listing	`enrich_brand_voice`
No third-party proof	Earn third-party validation buyers trust (set up a G2 profile)	(external — no in-app CTA)
No AWS co-content	Co-author proof content with AWS	`aws_blog_co_author`

Required & optional inputs¶

Required: brand. Optional: offering, website_url, category (and category_key to select the weight profile), user_id, listing_published.

On-demand and cached — never on page load

Like the Live Mirror, a grade involves an external read plus a model call (~seconds). It is designed to run on demand and be cached, not on every page load.

Plan availability¶

Capability	Starter	Accelerate	Command
`listing_alignment_grader` (Beta)	—	—	✅