Pagecraft / Own-site specimen
A website is
a series of decisions.
A close look at this studio’s page structure, responsive composition and enquiry state map.
Composition
Give each part
a clear job.
A focused first engagement
One buyer question.
One useful improvement.
Review the evidence. Shape one priority page. Make the next step clear.
Discuss the pilotA working, responsive miniature built from this studio’s offer. Its links open the actual pages; it contains no imitation form.
Information architecture
A route a buyer
can follow.
| Page | Buyer question | Design decision |
|---|---|---|
| Home | Is this for a business like mine? | Name B2B software and service businesses, then offer three problem routes. |
| Recallant | What would you actually do? | Show the scoped review, priority draft, inputs and exclusions. |
| Packages | What am I agreeing to? | Put the price, quantities, review allowance and dependencies together. |
| Research specimen | Can I inspect the thinking? | Show original observations and proposed actions with their evidence limits. |
| Contact | What happens next? | Carry the chosen service and package into a brief, then ask for review before sending. |
Interaction contract
The details
are part of the design.
| State | What the interface should do |
|---|---|
| Draft | Keep the visitor’s context on the page. Explain required fields and the optional supporting material. |
| Review | Show the complete brief. Let the visitor return to edit without losing their choices. |
| Sending | Make the pending action visible and prevent repeated clicks from creating repeated enquiries. |
| Accepted | Show a reference after service acceptance. A receipt is distinct from inbox placement. |
| Unconfirmed | Retain the brief, explain the uncertainty and offer a deliberate retry or an email/copy/download route. |
| Script unavailable | Use a native POST to reach review; keep personal fields out of the address bar. |
The miniature shows composition; the full website supplies the working journey. Release checks should retain the route, build, viewport and observed result, rather than turn a screenshot into a claim of delivery.
Download the page & state mapObserved development checks
Check the build.
Record the result.
| Check | Observed result |
|---|---|
| Responsive page checks | 28 pages at 320, 390, 768 and 1440 CSS px: 112 page-and-width checks recorded no horizontal overflow or resource/script errors. |
| Local destinations | 601 local targets were valid. |
| Controlled form checks | Checks used a mock mail service. No email was sent by these controlled tests. |
These checks describe the development build. They do not establish inbox placement or verify this update on the production site, and they are not a full accessibility certification.
What this shows: How a website connects an offer, supporting evidence and a useful next action.
Evidence boundary: This is our own site, not a client case or a measured conversion result.
Let’s get to the work
A useful next move starts here.
Tell us what your business needs to make clearer.