01 / Context
Explain what an engagement produces.
The homepage needed to make business consulting and contracted delivery easier to understand while retaining the approved book and folio design and the existing inquiry route.
The projectAlterity Digital’s own website
Internal project · Homepage published October 2026
This is a record of Alterity’s own delivery, rather than an external client engagement or testimonial.
02 / Scope
Make the outputs concrete.
The release connected Understand, Diagnose, Build and Handover to a documented starting point, a prioritized gap assessment, an agreed scope and a receiving owner.
The approved book, native scrolling and continuous folio transitions remained part of the experience. The existing inquiry form and privacy disclosures were retained.
The defined workClearer service language within the approved design
Engagement outputs · service FAQ · page title and description · optional brief
03 / Artifacts
A starting brief that stayed in visitors’ hands.
That release let visitors collect their business question, useful context and decision owner in a starting brief before writing an inquiry. The homepage has since been redesigned, and the brief tool is no longer part of the site.
What remainsThe engagement folio
The four engagement outputs remain in the published approach.
See the published approach ↗
Discuss your business ↗
04 / Handover
Leave a result that can be checked.
The published release has a documented recovery point and post-release checks. At launch, checks at desktop and mobile viewport sizes found no horizontal overflow; required fields blocked an empty inquiry.
What the evidence establishesA scoped website delivery with a documented handover
Published artifacts · recorded release checks · a recovery point
These were browser viewport checks, not physical-device testing. This example does not establish conversion or search-ranking gains.