Generative Assets · Industry demo 450
How the Forewarn Pilot Services page was built
Forewarn Pilot Services is a fictional heavy vehicle pilot operator in Kewdale. The audience is a transport operator, crane hirer, machinery dealer or house-mover holding a permit and a movement date. The page has one job: price the pilots for a named movement in under thirty seconds, and be the one page in the search results that does not try to sell the whole haul.
The proof element
Four inputs — one-way distance, pilots required as stated on the permit, a return-leg toggle and nights away — produce the kilometres travelled, the per-pilot kilometre charge, whether the half-day minimum applied and by how much, and the total. Beneath the figure the route is drawn to kilometre scale, with a marked point at 196.2 km travelled: the distance at which $2.65/km per pilot overtakes the $520 half-day minimum. That marker is the second-read detail. It is the only place on the page where the pricing model explains itself as a shape rather than a sentence.
| Movement | Travelled | Kilometres, per pilot | Minimum | Total |
|---|---|---|---|---|
| 320 km each way, 1 pilot, return | 640 km | $1,696.00 | Not applied | $1,696 |
| 48 km each way, 1 pilot, return | 96 km | $254.40 | Applied, +$265.60 | $520 |
| 610 km each way, 2 pilots, return, 1 night | 1,220 km | $3,233.00 | Not applied | $6,836 |
| Any distance, 0 pilots | — | — | — | No figure at all |
Rates: $2.65/km per pilot, $520 half-day minimum per pilot, $185 per night away, per pilot, all ex GST. Line items print to the cent; the figure the customer acts on is rounded exactly once, at the end. Every one of these numbers was produced by the wave's arithmetic script before a line of page code was written, and the running page is asserted against them on each pass.
The branch that argues against the sale
Select 0 pilots and the card stops being a quote. It says the movement does not need us, states that the movement's own permit is the authority on how many pilots it requires, quotes Main Roads WA on why no table could answer it, names the Traffic Escort Warden threshold as work this business does not sell, and ends with the one thing the reader can do today: send the permit, we read it for nothing. The card is asserted to contain zero dollar signs — the temptation to slip a figure in underneath an honest answer is exactly what the assert exists to stop — and the route bar redraws in grey for that branch rather than disappearing.
The metro branch does the same work in the other direction. At 48 km each way the kilometres come to $254.40 and we charge $520, so the card volunteers that the minimum is costing the customer $265.60 before it shows the total, and offers to requote without it if the movement can be paired with another the same morning. A third computed line runs in every state: dropping the return leg on a long haul saves a real, printed figure ($848 on the 320 km run, $3,233 on the 610 km one), and on a short metro run it saves nothing at all — which the card says out loud rather than letting the customer discover it.
Palette
Argued from the trade: the sign is black on yellow and the lights are amber, but amber at sign brightness fails as text, so the amber is darkened to a legible ochre and the true warning yellow appears only as a drawn fill inside the SVG — never behind a word. Ratios below are measured, not estimated.
Four further grounds were minted for the drawing and the service-area map and measured before use: sea #E0E4E3 (muted 6.24:1), hairline #D6D6D0 (muted 5.48:1), region tints #F0F1F1 and #F3EFE6 (ink 15.87:1 and 15.65:1) with a selected state at #ECE5D6 (ink 14.32:1). Where the ochre marker crosses the charcoal route bar it is redrawn in #F4F4F1 for that segment, because ochre on charcoal measures 2.15:1 and no mark on this page is allowed to sit on a ground its ratio has not cleared.
Type
Barlow Condensed 600/700 for headings and Barlow 400/500 for body — one family, two widths. A pilot operator's entire visual language is a road sign, and condensed grotesque caps are what a sign is set in. The condensed face carries the headline, the section titles and every figure label; the normal width carries the prose so nothing important is read in caps. Figures are tabular everywhere a number can change under the reader's hand.
Techniques
- No libraries, no build step, no raster images. Two self-contained files.
- The route bar is a single inline SVG rebuilt from a small state object on every change. Its axis domain is a nice round maximum of the kilometres travelled (floor 260 km), so the 196.2 km marker stays in frame on a metro run and on a Port Hedland run alike.
- The drawn subject has real substance rather than hairlines: a road band, a travelled bar, vehicle bodies, cabs, wheels, beacons, a diamond sign, a turnaround divider and an axis. Chrome reports the geometric bounding box for an SVG shape excluding stroke, so a line-drawn diagram can measure as zero-height; every mark here is inflated by its stroke width before the frame check measures it.
- The pilot vehicle beacon pulses between 0.58 and 1 opacity, so the signature is visibly alive at any capture instant rather than phase-tuned to the seven-second thumbnail. It is killed by prefers-reduced-motion in CSS, and the page runs no animation loop in JavaScript at all.
- At 1024px and above the proof card floats into the hero's second grid column while the DOM order stays masthead, hero, services, proof — so mobile reads in the conventional order and the desktop thumbnail still carries the answer.
- The state model is exposed at window.__pilotvehicle, so the verification harness asserts on the model rather than scraping pixels.
Iteration log
Pass 1 — Craft
Drove the form empty (six fields flagged, confirmation stayed hidden) and filled (confirmation shown, form hidden), and drove the proof element through all four cases, asserting the model each time: $1,696 on the long haul, $520 charged against $254.40 of kilometres on the metro run, $6,836 on the two-pilot overnight, and no figure at all on zero pilots.
Three defects, none of which any state assert could see. (1) The main element had no horizontal padding, so the hero eyebrow, headline and trust line ran flush to the viewport edge at every width — invisible to the overflow probe, obvious the moment the 1200×750 capture was opened. (2) The proof card's route bar ended at y 1128, well outside the thumbnail frame; the card was restructured so the headline total is followed immediately by the drawing, with the itemisation and the honest flag below it. (3) Once the padding landed the hero copy overran the 375 px fold by 110 px, measured against the viewport minus the sticky bar rather than the viewport; the headline, subline and trust line were rewritten shorter.
Pass 2 — Depth
Re-drove all four proof cases plus a rapid-fire sequence — six control clicks dispatched in one evaluation with no settle between — and asserted the resulting model was coherent and the console clean.
Added the computed return-leg comparison, which is now the strongest line in the card: on a long haul it names what one way would cost and how much less that is ($848 less on the 320 km run, $3,233 less on the 610 km one), and on a metro run it says plainly that dropping the return leg would not change the figure because the minimum does the charging either way. Added the turnaround divider and its notch so the drawing shows where the outbound leg ends. Fixed a legibility fault the screenshot found and the asserts did not: the ochre marker line crossed the charcoal travelled bar at 2.15:1, and is now drawn in three segments so that crossing is pale. Fixed a label collision on short runs, where “back at depot” overlapped “Kewdale”; the destination label now flips to the other side of its flag when the run is under 150 axis pixels.
The service-area map was thrown away and redrawn. The first version tiled the state with filled rectangles pretending to be region boundaries, and looked in a screenshot exactly like what it was: a blob with rectangles on it, a Great Southern label sitting outside the coastline, and a Mid West polygon overlapping the Pilbara. The outline is now plotted from real longitude and latitude — Cape Londonderry, the 129th meridian, Eucla, Albany, Cape Leeuwin, Steep Point, North West Cape, Broome — and the five regions are labelled markers joined to the Kewdale depot by dashed run lines, which is honest about what the page actually knows. Selecting a region on the map highlights its row in the list beside it, and that drive is asserted.
Pass 3 — Hardening
Drove the form a third time, including a junk-in-a-constrained-field case: typing “ring me maybe” into the phone field must be rejected by the pattern attribute, which browsers compile with the v flag — where an unescaped bracket or hyphen inside a character class silently discards the whole pattern and the field then accepts anything. The attribute is asserted alive, not merely present. Drove the proof element at 375 and confirmed the metro case still computes and the page still does not scroll sideways.
Found the masthead sub-label “· Kewdale” overlapping the phone pill at 375 by about eight pixels. The element box was clean because the text overflows a shrunk flex item, so the check was re-cut to measure the text's own ink box with a Range, and the label is now dropped below 480 px. Confirmed reduced motion settles to a finished frame with the beacon animation off and the model still computing, the focus ring is visible on every control, the section reading order is unchanged on mobile, and the zero-pilot card contains no dollar sign. Removed one ornament: the return-leg arc that had been drawn above the road, which said nothing the turnaround divider does not say better.
Then the verification suite was tested rather than believed. Ninety-three checks passing on the first run is evidence of nothing until they have been watched fire, so eight defects were planted into the page one at a time — a second h1, a banned LocalBusiness block in the live structured data, a dollar figure slipped into the zero-pilot card, the route bar pushed out of the thumbnail frame, a real street number in the footer, the masthead label allowed to overlap the phone pill again, the phone pattern rewritten with an unescaped bracket, and a console.error on load. All eight fired the check they were aimed at, and the file was restored byte-for-byte and compared after each one.
Why this converts
The first thing on the page is a price for a movement the operator can recognise, not a contact form, because a transport operator with a permit in one hand is comparing two or three pilot outfits on the same morning and the one that answers first wins the call. The form asks for six things — name, phone, route, date, pilots on the permit and what is moving — because those six are exactly what a dispatcher needs to quote, and every extra field is a lost enquiry. The half-day minimum is disclosed before the total rather than after it, and the card volunteers the $265.60 the customer is paying for time we will not use, because a quote that admits its own worst line is the one that gets believed. The zero-pilot card is built at full size and carries no price at all, which loses the occasional job and wins the operator who rings back three weeks later with one that is real. Everything trustworthy on this page is a number the reader can drive themselves — that is the difference between a site that looks credible and one that is.
Conversion decisions
- Phone in the masthead at every width, plus a sticky bar on mobile. Most of this traffic is a phone in a depot yard. The sticky bar owns a real tel: link and a jump to the form, and the hero's headline, primary button and trust line are all asserted to finish above the fold minus the bar's height, not merely above the viewport.
- The proof card sits in the hero at desktop and after the services grid on mobile. The 1200×750 card that represents this page elsewhere has to show the answer, and a page whose thumbnail shows only a headline sells nothing.
- Prices are published, per pilot, ex GST. The trade's habit is “contact us for a quote”. Publishing $2.65/km, $520 and $185 puts the operator in a position to decide before they ring, and the page says which of those is a minimum and when it stops applying.
- A free permit read is a services-grid line at $0. It is the lowest-commitment thing a hesitant operator can ask for, and it is the offer the zero-pilot branch hands back to.
- The FAQ answers the questions a pilot operator is actually asked — what a pilot does, who decides how many, what an HVPL is, what a Traffic Escort Warden is, what happens on a postponement — and answers the pilot-count question by pointing at the permit rather than inventing a table.
- Reviews name loads and routes, are declared as demonstration copy on the page, and are deliberately not marked up as structured review data.
What we did not publish
Everything this page says about Western Australian pilot requirements is attributed to Main Roads WA and quoted from what that authority publishes: that all heavy vehicle pilots operating in WA are required to hold a Heavy Vehicle Pilot Licence, introduced in 2016 with requirements detailed in the Road Traffic (Vehicles) Regulations 2014; that a pilot vehicle is recognised by a large yellow reflective “Oversize Load Ahead” sign and amber flashing lights on the roof; that pilot vehicles escorting loads in excess of 4.5 metres in width also display white flashing lights on the front; that the number of pilots varies with the complexity of the load and their positioning varies with where they are needed; that directions given by pilots are lawful directions that must be obeyed; and that Traffic Escort Wardens, not pilots, accompany vehicles exceeding 5.5 metres in width and/or 40 metres in length.
There is deliberately no table of pilots by load width on this page. Main Roads sets pilot numbers inside the operating conditions of each permit, and those vary by permit, so any table would be wrong for somebody — the page says the permit is the authority instead. The standard, non-oversize dimension limits are not stated anywhere either, which is why the zero-pilot branch is framed as “your permit does not require one” rather than as a claim about what counts as oversize. And nothing on the page implies this business can obtain, vary or interpret a permit on the operator's behalf: it reads what the permit already says and prices the pilots it calls for.
Two figures on the page are the fictional business's own and are labelled as such: the rate card, and the postponement policy. The route distances on the quick-pick chips are approximate road distances, marked approximate, and the field is editable.
Local SEO we would implement for the real business
This demonstration emits only WebPage schema naming itself a demonstration, because marking a fictional business up as a real one with real reviews would pollute a real index. For an actual pilot operator we would ship the block below, populated from their own Google Business Profile, their real HVPL registrations and a live review feed rather than hand-written copy.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"@id": "https://example.com.au/#business",
"name": "Forewarn Pilot Services",
"description": "Licensed heavy vehicle pilot escort across Western Australia.",
"url": "https://example.com.au/",
"telephone": "+61 8 XXXX XXXX",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "Unit X, Example Road",
"addressLocality": "Kewdale",
"addressRegion": "WA",
"postalCode": "6105",
"addressCountry": "AU"
},
"geo": { "@type": "GeoCoordinates", "latitude": -31.99, "longitude": 115.97 },
"areaServed": [
{ "@type": "State", "name": "Western Australia" },
{ "@type": "City", "name": "Perth" },
{ "@type": "City", "name": "Kalgoorlie" },
{ "@type": "City", "name": "Port Hedland" }
],
"openingHoursSpecification": [{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "05:00", "closes": "18:00"
}],
"hasOfferCatalog": {
"@type": "OfferCatalog",
"name": "Pilot services",
"itemListElement": [
{ "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Metro half-day pilot" },
"priceSpecification": { "@type": "PriceSpecification", "minPrice": "520", "priceCurrency": "AUD" } },
{ "@type": "Offer", "itemOffered": { "@type": "Service", "name": "Regional pilot, per kilometre" },
"priceSpecification": { "@type": "UnitPriceSpecification", "price": "2.65",
"priceCurrency": "AUD", "unitCode": "KMT" } }
]
},
"aggregateRating": {
"@type": "AggregateRating", "ratingValue": "4.9", "reviewCount": "63"
},
"review": [{
"@type": "Review",
"author": { "@type": "Person", "name": "Real reviewer name" },
"reviewRating": { "@type": "Rating", "ratingValue": "5" },
"reviewBody": "Pulled from the client's live review feed, never written by us."
}]
}
</script>Alongside it: a Google Business Profile in the primary category that matches the trade, service-area pages for the runs that actually earn (Great Eastern Highway, Great Northern Highway, the South Western), consistent name-address-phone across the profile, the site footer and the industry directories, and an FAQ block marked up as FAQPage once the answers are the client's own.
What would change for a real client
Their photographs of their vehicles signed and lit, their real HVPL numbers and insurance certificates, their live review feed, and their actual rate card — which usually differs from the published market figures by more than the page would guess.
Then the integrations, which is where a pilot operator's day actually lives. The permit itself comes out of Main Roads WA Heavy Vehicle Services, so the enquiry form's permit-number field is the natural hand-off point into their job file. Dispatch and job records sit in a transport job system — MyTrucking, Transvirtual or CartonCloud for the operators who already run one, ServiceM8 for the smaller outfits treating each movement as a job. Vehicle tracking and the run history that backs an invoice come from Geotab, MTData or Teletrac Navman. Fatigue and work-diary compliance sits in Logmaster or the equivalent NHVAS record-keeping. Fuel goes through Smartfill. Invoicing lands in Xero or MYOB. The version of this page we would ship a real operator writes the enquiry into their job system with the movement date, the route and the pilot count already populated, and sends the quote from the same numbers the page showed the customer — so the figure on the screen and the figure on the invoice cannot drift.