IRONSONG.COM

Heavy Industry · Shipyards · Choral Society

“A bug report delivered to your face is a gift. We simply needed somewhere to put them.”

Ironsong's parts-requisition portal had a proud tradition: any fitter who found a defect was expected to walk down to the floor and tell the responsible engineer directly. Effective, but it did not scale, and it was costing them engineers.

They dropped the thumbs embed onto every page. A single thumbs-down captures a screenshot, the console errors, and the failing network calls — so a report arrives with proof attached and nobody has to defend themselves in person. Escalation rules route each one to the team that shipped the code.

HIVEMESH.COM

Distributed Systems · Acquisitions

“We evaluated your competitors. Their feedback models were irrelevant to us.”

Hivemesh does not run user interviews. It runs telemetry. But its onboarding flow was losing accounts at step four, and nobody in the company could say why — they had never built a way to ask a question and wait for an answer.

The quests embed now runs a five-step questionnaire at the point of drop-off, autosaving each answer as it is given. One quest theme is published to every property at once, so the whole estate changes appearance in the same instant. Responses are pulled through the platform API and go straight into the warehouse.

NIGHTGATE.COM

Security · Encrypted Freight

“We would prefer you did not know what we are building. We would also like to know why they abandon it at step three.”

Nightgate’s tooling review had one requirement that eliminated every other vendor on the shortlist: nothing about a survey may be discoverable before it is deliberately made discoverable.

Quests stay unlisted until they are published, and a published draft never reaches an embed — that takes a separate, explicit call. Platform API keys are project-scoped and stored only as a SHA-256 hash, shown once at creation and never again. A resource in another project answers not_found rather than forbidden, so an id cannot be probed for existence.

TALLYHOUSE.COM

Retail · Franchising · Hospitality

“Never spend money on a thing you cannot measure. We now measure everything.”

Tallyhouse franchises fourteen hundred storefronts and had strong opinions about every one of them, none of which had ever been written down.

Feedback and quest analytics turn raw responses into completion rates and per-step drop-off, so an opinion now arrives as a number. Billing is per seat, which means they pay only for the managers who actually sign in — a fact Ray has raised in every renewal call since.

SCRAPLINE.COM

Salvage · Field Logistics · Water Rights

“Our people are on ten-year-old hardware in bad weather. Yours was the only embed that loaded at all.”

Scrapline’s parts exchange is used from cracked handsets on borrowed bandwidth, out on yards with no reliable signal. Every tool they had tried before pulled down a framework larger than the page it was measuring.

The thumbs embed is around 16 KB gzipped with zero runtime dependencies. On touch devices it captures the page from the DOM instead of the Screen Capture API, so filing a report never raises a permission prompt that nobody standing on a salvage deck is going to grant.

REDGROVE.COM

Rural Networks · Mutual Aid

“There are four of us. The assistant is the fifth.”

Redgrove has no support team, no triage rotation, and nobody whose actual job is reading feedback. They have four people and a community network that finds a new way to break every week.

The dashboard assistant reads the inbox, groups what it finds, and files the issues. A confirmed report can travel from thumbs-down to open GitHub issue to a proposed PR fix without anyone opening the dashboard — and every write it makes runs as the person who asked for it, with their role and no more.

FACETWORKS.COM

Architectural Glass · Structural Lattice

“Your default palette was unreadable to half our floor. We changed it in an afternoon and did not have to ask anyone.”

Facetworks specifies glass for a living, and its tolerance for a contrast ratio that merely looks fine is famously narrow — the specification tool is used all day in a workshop under glare that would wash out most interfaces.

Every colour, label, and dimension is a CSS variable, and both embeds read the same namespace — so one theme covers the thumbs and the quests alike. They built their own and held it to WCAG 2.2 AA, the standard the embeds themselves are tested against with axe-core on every commit.

HAVENMARK.COM

Civic Services · Agriculture · Heritage

“We asked our residents how it felt to use, in their own language. It had been a long time since anyone asked them anything.”

Havenmark runs civic portals for towns rebuilding after decades of underinvestment, in two regional languages no vendor had ever shipped a translation for.

Every string in both embeds is configurable text, so they translated the entire interface without forking anything and without waiting on a release. Conditional questions mean a smallholder and a shipping clerk are asked different things by the same quest.