Part 1 — The brand: Avela
1.1 Brand archetype
Avela is a mid-market B2B SaaS company providing workforce planning software for distributed organizations. The brand has been operating commercially for approximately seven years, has grown through traditional product-led-growth and inside-sales motions, and serves roughly 400 mid-market customers in North America and Western Europe.
Avela’s commercial reality at engagement start is unambiguous: the company has revenue, customers, and product-market fit. What it doesn’t have is presence in AI-mediated discovery. When prospective customers ask AI assistants for workforce planning software recommendations, Avela does not appear. Competitors appear. The brand stakeholder, Avela’s CMO, has noticed the pattern and engages Avonetiq to address it.
This is a representative starting position for many brands entering AVO engagement. The brand is not new; it has substantive existence; it just has not engineered for AI-mediated discovery in any deliberate way. The work of AVO is to address the gap.
1.2 Starting state — what Avela looks like at month 0
Before engagement work begins, Avonetiq conducts the diagnostic baseline. The findings:
| Dimension | State |
|---|---|
| Headline AS | 14 (Critical band) |
| Optimize pillar | 22 — somewhat better than other pillars; reflects basic SEO work done by a prior consultant |
| Manifest pillar | 15 — content exists but is thin and inconsistently structured |
| Generative pillar | 6 — near floor; minimal external authority signals |
| Headline VS (initial measurement) | 3 — recognition gate is blocking; advisory and category tier measurements are structurally premature |
| Recognition gate status | Below warn threshold across all measured platforms |
| Brand stakeholder expectation | ”We need to be in the AI answers within a quarter” |
The decomposition reveals more than the headline numbers do. Within Optimize, V1.1 (Signal Architecture) is at floor — the brand has no Schema.org markup beyond an automatically-generated product schema on the pricing page. V1.2 (Technical Health) is moderate; the site loads acceptably and is crawlable, though hreflang is non-existent because the brand operates only in English. Within Manifest, V2.1 (Semantic Density) is at floor — the brand’s blog has approximately 80 posts, but most are 600-word product-feature announcements and inbound-marketing content with thin claims and minimal attribution. V2.2 (Structural Legibility) is similarly low — content uses generic templates with weak heading hierarchy. Within Generative, both vectors (V3.1 Knowledge Validation, V3.2 Trust Alignment) are essentially at floor — no Wikidata entity, no Wikipedia article, minimal earned media coverage, sparse external citation patterns, no original research published.
1.3 What Avela wants AVO to accomplish
The CMO’s stated goals at engagement scoping:
- “Show up when someone asks ChatGPT or Claude about workforce planning software”
- “Be in the recommendation when someone asks for the best workforce planning tool for distributed teams”
- “Have a real Wikipedia presence”
- “Stop losing to [a specific competitor] in AI-mediated discovery”
The practitioner translates these into Focus and engagement scope:
| Brand goal | Practitioner translation |
|---|---|
| ”Show up when someone asks about workforce planning software” | Navigational and category tier VS in workforce-planning-software prompts |
| ”Be in the recommendation” | Advisory tier VS in workforce-planning-software recommendation prompts |
| ”Have a real Wikipedia presence” | G-11 work, dependent on prerequisite work |
| ”Stop losing to [competitor]“ | Comparative analysis through O-1; subsequent action prioritization |
1.4 Engagement scope, Focus, language scope
| Scope element | Setting |
|---|---|
| Domains in scope | One primary domain (avela.com); the brand has only one domain |
| Focus | ”Workforce planning software for distributed teams” — declared after scoping conversation; specific enough to be defensible, broad enough to support meaningful probe coverage |
| Languages | English only |
| Engagement intensity | Quarterly cycle review; AS measurement quarterly; VS measurement monthly |
| Operational capacity | Avela has small in-house engineering team (3 full-time engineers, focused primarily on product), small marketing team (4 people including the CMO), and no dedicated communications function |
| Engagement bottleneck identified at scoping | Communications capacity. Generative-pillar work will be limited until this is addressed. |
The bottleneck identification is consequential. The CMO acknowledges the gap and agrees that some Generative-pillar work will be commissioned externally as needed; engineering work will be done in-house with prioritization support; content work will be a hybrid of in-house and commissioned.