PRODUCT UPDATES

Changes worth
knowing about.

Release notes should describe what users can actually access—not announce unbuilt features as shipped.

Explore the product proposal

September 20, 2026 — Website content prototype

A first content and navigation prototype has been prepared for Ad8’s proposed research service. It includes product pages, a $29/20-competitor pricing proposal, onboarding copy, an illustrative report, and help and trust drafts.

This is a website-content milestone only. It is not the launch of a working database connection, checkout, account system, monitoring service, or MCP endpoint.

Future release-note format

Released: the user-visible feature and who can access it. Changed: any relevant workflow or limit. Fixed: the actual resolved defect and user impact. Known limitation: remaining constraints. Date: the actual release date.

Publishing rule

Do not insert a fictional product history, customer adoption figure, or roadmap deadline. Planned work should be labeled planned and remain distinct from a release announcement.

Start with a better
creative question.

Explore the sample. Review the proposed plan. See how Ad8 could fit your research workflow.

Explore the sample report →

Frequently asked questions

What is on the Ad8 product updates page?

It is a content preview of release notes. It says release notes should describe what users can actually access and not announce unbuilt features as shipped.

What does the September 20, 2026 entry say?

It describes a website content prototype, including product pages, a $29/20-competitor pricing proposal, onboarding copy, an illustrative report, and help and trust drafts. It is a website-content milestone only.

Has the working service launched?

The page says the prototype is not the launch of a working database connection, checkout, account system, monitoring service, or MCP endpoint.

What will future release notes include?

Each release note should state what was released and who can access it, any relevant change to workflow or limit, any actual fix and its user impact, known limitations, and the actual release date.

Will the changelog include a roadmap?

The publishing rule is not to insert a fictional product history, customer adoption figure, or roadmap deadline. Planned work should be labeled planned and remain distinct from a release announcement.