Opportunity case studies · Reviewed September 5, 2026

Five enterprise workflows worth testing.

Each brief separates what the company documents from what we propose. Read the integration boundary, a small pilot, measures to collect, and reasons to stop—not just the brand name.

Cisco · Proposed scenario

Make public support discovery easier to maintain

An illustrative pilot for a Cisco digital-experience team: review a public product-support finder, improve supported interface gaps, and attach source evidence to its release. No Cisco deployment has been inspected or evaluated.

Read the Cisco proposal →

Akamai · Proposed scenario

Keep source findings attached to edge releases

An illustrative pilot for Akamai web-platform engineering: check an owner-approved public reference property after releases and preserve comparable source evidence. This is not an Akamai security assessment or a built-in Akamai integration.

Read the Akamai proposal →

Microsoft · Proposed scenario

Add evidence to an already-public Power Pages release

An illustrative pilot for a Power Pages engineering or reference-solutions team: review anonymous-page source and check supported fixes after release. Private sites remain private, and no Microsoft product integration is claimed.

Read the Microsoft proposal →

Adobe · Proposed scenario

Review form-template changes before repeating them

An illustrative pilot for an Adobe AEM Forms reference-team workflow: identify supported source issues in one public form template, review a reusable fix, and check later releases. No conversion improvement or Adobe endorsement is claimed.

Read the Adobe proposal →

Salesforce · Proposed scenario

Evaluate a public content-discovery component

An illustrative pilot for an Experience Cloud reference-solutions team: review a public content-discovery page and its proposed search contract. Start with source coverage and platform compatibility, not claims about Agentforce or live CRM automation.

Read the Salesforce proposal →

How to read this selection

Cisco, Akamai and Microsoft were requested reference enterprises. Two additional platforms were selected for concrete web application surfaces and documented extension paths. This is a five-company opportunity screen, not a size ranking or a claim that these companies have agent-readiness problems. We did not scan their applications. Any pilot requires a willing application owner and approved data handling.