SIGNAL & SYLLABLE / PAGECRAFT
Own-site page and enquiry journey specimen
Studio example · 25 October 2026

BUYER
A founder or marketing lead choosing a focused marketing engagement.

QUESTION
What should I commission first, and what happens when I enquire?

THE PAGE CONTRACT
Home: identify the audience and route the buyer by problem.
Service: explain the kind of work, buyer fit, deliverables and dependencies.
Package: define the engagement, scope, review allowance and commercial basis.
Specimen: make the actual work inspectable and label its evidence status.
Contact: carry the selected service/package into a brief and a review step.

ONE WORKING ROUTE
Home visibility route -> Recallant -> Visibility Pilot -> original research specimen -> preselected enquiry.
https://signalandsyllable.com/recallant
https://signalandsyllable.com/packages?offer=Visibility%20Pilot
https://signalandsyllable.com/sample
https://signalandsyllable.com/contact?service=Recallant&package=Visibility%20Pilot

THE INTERACTION CONTRACT
Draft: nothing is sent; required fields identify the sender and business question.
Review: show the supplied context and chosen engagement; permit corrections.
Explicit send: submit to the studio only after the visitor chooses to send.
Accepted: display a reference only after the provider accepts the submission.
Unconfirmed: preserve the brief and provide deliberate retry/email/copy/download options.
Edited after an attempt: make clear that an earlier version may have arrived; a changed version is a new enquiry.
No script: a native POST must reach a review screen without personal data in the URL.

OBSERVED DEVELOPMENT CHECKS — 26 OCTOBER 2026
28 pages across four viewport widths (320, 390, 768 and 1440 CSS px): 112 page/width checks recorded no horizontal overflow or resource/script errors. 601 local targets were valid. Controlled form checks used a mock mail service and did not send email. These are development-build observations, not verification of the new production release or inbox placement.

CHECKS TO RETAIN WITH EACH RELEASE
Page destinations and selected context; keyboard order; visible focus; narrow-screen composition; long text; review/edit; failed or slow sending; repeated actions; safe no-script behaviour.

WHAT THIS DEMONSTRATES
The studio's own information architecture, copy and interface design. It is not a client project, a conversion experiment or evidence of revenue uplift. The state map is an interaction contract, not a claim that every possible assistive technology or failure mode has been tested.