Mark Hay

What's new

Release notes for the public side of markhay.net.

A customer-facing changelog covering live routes, new tools, proof surfaces, and the quieter improvements that make the site more useful and more trustworthy.

See the latest release Browse live work

Older entries are backfilled from published routes, retained proof assets, and the release history. Only customer-visible changes are logged here. The latest release stays more detailed; older entries stay concise.

Release log

9

customer-facing release entries documented

Cadence

Meaningful updates

published when a useful change is verified

Proof

7

screenshots retained where they improve the release story

Latest release

Week ending 3 October 2026

The latest verified release is described here. Earlier updates are retained as concise historical entries below.

Latest releaseWeek ending 3 October 2026

A consistent blue theme across markhay.net and Owner Support.

The public site now shares Owner Support’s blue and navy palette, typography, rounded cards and controls. Existing content, routes and tool functionality are retained.

Why it matters

Moving between the public site and its business tools feels more consistent, with clearer controls and visible keyboard focus. Existing quoting, pricing, saving and export journeys remain available.

In this release

  • Introduced shared design tokens for the public site, Owner Support and No Fuss Tools.
  • Checked the public layouts at 320px, 390px and 1440px, including navigation, contact validation and a completed pricing output.
  • Verified the deployed revision with 249 active public checks. These are automated checks, not claims of customer demand or observed owner testing.
Open Owner SupportUse No Fuss ToolsBrowse business support
No Fuss Tools pricing inputs and a calculated selling price using example figures.
No Fuss Tools uses the shared blue theme. This retained example shows a pricing calculation, with fictional figures.

Historical backfill

Earlier release weeks, kept concise.

These are the meaningful weeks with customer-visible changes. Quiet internal or private-ops work does not get padded out here just to simulate motion.

Weekly summaryWeek ending 31 July 2026

Free business tools now lead into clearer, honest next steps.

The business-support routes were reviewed from the customer outcome backwards. The procurement shelf now starts with its usable free pack and handles optional template work by enquiry, while the Shopify route opens a real public-page critique in product-page mode.

Customer impact

Visitors can get a useful result before speaking to anyone, understand exactly where automated checks stop, and avoid a checkout whose payment-to-delivery journey has not yet been revalidated.

  • Connected the Shopify CRO route directly to the live Conversion Critic with product-page context and a Shopify-specific human-review handoff.
  • Kept the free Procurement Starter Pack live and removed purchase-ready claims, fixed prices and checkout links until paid fulfilment is proven again.
  • Clarified that optional scope, files, delivery, terms and price are agreed in writing before paid work starts.
  • Aligned the wider portfolio pages so planned, paused and available products are described consistently.
Scan a Shopify pageDownload the procurement starter packBrowse business support
Conversion Critic on markhay.net opened in Shopify product-page mode with the public URL field ready.
The Shopify route now starts with a working public-page critique and carries context into the optional human review.
Procurement templates page on markhay.net leading with the free starter pack and written scope boundary.
The procurement route now leads with the usable free pack and makes the paused checkout explicit.
Weekly summaryWeek ending 20 June 2026

Live buying paths were tightened, and the site now shows its release cadence in public.

This week concentrated on two revenue-facing surfaces: Website Fitness was clarified and instrumented so live buyer intent is easier to handle properly, and the procurement template shelf launched with an initial fixed-price experiment. That checkout was later paused when the full payment-to-delivery journey was reviewed; the current page now leads with the usable free pack and written scoping for anything more.

Customer impact

The public routes now look more deliberate, the buying path asks for less guesswork, and repeat visitors can see that the site is being run with a visible operating cadence rather than drifting between quiet rebuilds.

  • Added a public procurement template shelf. Its original fixed-price routes are historical; the current page provides the free pack first and handles optional template work by enquiry.
  • Sharpened the Website Fitness starter path with clearer homepage positioning, token-aware follow-through links, and checkout-intent tracking so paused buyers do not disappear into a blind spot.
  • Improved paid-tool challenger pricing and procurement conversion copy so visitors can judge fit faster before buying.
  • Published this customer-facing weekly changelog so visible progress, release rhythm, and proof surfaces are now documented in the open.
Open Website FitnessView procurement templatesBrowse business tools
Website Fitness Checks route on markhay.net showing the public scan offer and email follow-through path.
Website Fitness is now positioned as a clearer public entry point rather than a buried experiment.
Historical procurement templates shelf on markhay.net showing the original product experiment and buyer guidance.
Historical launch view. The public checkout is now paused while the end-to-end delivery route is revalidated.
Weekly summaryWeek ending 13 June 2026

Core commercial routes were rebuilt around usable tools, clearer proof, and stronger trust surfaces.

The second week of June concentrated a large set of public changes into one release window: Website Fitness arrived on a markhay.net route, native conversion and e-commerce tools went live, AI Support was rebuilt, QuarterReady received a trust-oriented landing page, and publisher example surfaces were added.

Customer impact

Visitors could reach working tools faster, judge them from clearer proof, and see that newer products were being presented as maintained public surfaces rather than as loose project cards.

  • Added the public Website Fitness route on markhay.net and strengthened the supporting trust and conversion copy around it.
  • Added native Conversion Critic and e-commerce calculator routes, including URL scanning support and QA hardening.
  • Rebuilt Copilot Support as a clearer AI Support hub with assistant-specific routes and workshop coverage.
  • Added the QuarterReady trust surface and publisher article support/examples pages so the portfolio looked more complete and more credible.
Open AI SupportView QuarterReadyBrowse publisher examples
Weekly summaryWeek ending 16 May 2026

Context Switch was reframed as a build house, and the site foundations were hardened.

Mid-May was less about a single shiny release and more about improving the shape of the business: Context Switch was repositioned as a research and build house, AI delivery notes were surfaced, and the production plumbing around contact, build stability, and image handling was tightened.

Customer impact

The site became easier to understand and more reliable at the trust-critical edges, which matters more than adding another thin surface that looks active for a week and then goes stale.

  • Upgraded Context Switch into a clearer research and build-house route instead of a fuzzy portfolio label.
  • Added AI delivery notes to explain how work is actually shipped without leaning on generic service language.
  • Hardened contact handling, build memory, and image configuration so the public site behaves more predictably.
  • Added rate limiting and supporting reliability work around the public contact flow.
Open Context SwitchRead notesContact Mark Hay
Weekly summaryWeek ending 26 April 2026

Project pages adopted a proof-first maturity model instead of startup theatre.

Late April focused on portfolio clarity. Project detail pages were aligned to a clearer maturity taxonomy, proof language was tightened, and route descriptions were made more consistent so the site explained what was live, what was in progress, and what was still exploratory.

Customer impact

People browsing the work could tell what was usable now, what was still being built, and what remained early without needing to decode portfolio jargon.

  • Aligned project detail pages with consistent maturity labels and proof tone.
  • Tightened trust hierarchy and public microcopy across the main site.
  • Standardised project descriptions and supporting metadata for better portfolio consistency.
Browse projectsSee work approach
Weekly summaryWeek ending 12 April 2026

UK Shortlists became a visible proof surface across the site.

Early April shifted UK Shortlists from a background reference into a more explicit proof case. The site also received public tone and hierarchy polish, helping the live-build evidence read more like a real operating asset and less like a tucked-away experiment.

Customer impact

The site gained a stronger answer to the question of what has actually been built and run, which is a better trust signal than generic claims about capability.

  • Featured UK Shortlists more prominently across homepage and project surfaces.
  • Added supporting notes and structure around the iterative build model behind the work.
  • Polished public hierarchy and tone leading into broader publication.
View UK Shortlists proofBrowse projects
UK Shortlists homepage showing the category-led public proof surface.
UK Shortlists became a visible proof surface rather than a quiet background reference.
Weekly summaryWeek ending 5 April 2026

Proof routes, analytics diagnostics, and publishing foundations were put in place.

The first full April release window concentrated on operability rather than cosmetics. Example-output routes were published for the main analysis tools, sitemap coverage improved, contact handling was hardened, and the production analytics/deployment checks were documented properly.

Customer impact

The site became more believable because important pages started showing working examples and the operational plumbing behind them was treated seriously rather than left as implied competence.

  • Added proof-led example-output pages for Conversion Critic and Competitor Intelligence.
  • Improved sitemap coverage, including deeper calculator routes.
  • Documented hosting and analytics setup while stabilising PostHog smoke testing.
  • Hardened contact email flow and preview failure handling.
View Conversion Critic exampleView Competitor Intelligence example
Weekly summaryWeek ending 27 March 2026

The public site launched with live project proof instead of placeholder pages.

The first release window established markhay.net as a working portfolio surface with Context Switch identity, Copilot Support tooling, the CQS Smart Operations project page, and early e-commerce and product routes. The initial standard was proof-led from day one rather than brochure-first.

Customer impact

From launch, the site offered working proof surfaces and real project context instead of a polished shell waiting to be filled later.

  • Published the application and established the main domain foundations.
  • Added Copilot Support tooling, project wiring, and the update refresh pipeline.
  • Published the CQS Smart Operations project page and early e-commerce/project surfaces.
  • Replaced placeholder branding with the Context Switch logo suite and updated homepage presentation.
Open Copilot SupportView CQS Smart OperationsBrowse projects
CQS Smart Operations dashboard screenshot showing the live software proof surface.
CQS Smart Operations was part of the early proof set used to launch the public site.

Update policy

This page records verified customer-visible releases. The latest update has more detail; older entries remain available as concise summaries.

Included here

Only customer-visible changes, live proof surfaces, and meaningful route updates. Private dashboards, internal queue work, and hidden experiments do not get padded into fake release notes.

Historical note

Older weeks were backfilled from published routes, retained screenshots, and the release history so the visible cadence starts from the point the site became real enough to deserve one.