/* eslint-disable */ // Our Work, one library, two content types (case studies + white papers), // filterable by type and industry. Built as repeatable templates for entry ten, not entry three. // Content brief v4, Our Work section. const WORK_ENTRIES = [ // ---------- CASE STUDIES (named clients only, published once the tracker shows // named use approved and quotes signed off) ---------- { type: "case", slug: "accounting-firm-foundations", tracker: "CS-006", industry: "Professional services", client: "Regional accounting firm", clientPending: true, size: "80 staff", service: "AI Foundations", headline: "Controls first, because the client data left no room for guesswork.", summary: "Staff were already testing AI with mixed results, and the firm holds highly sensitive client data. Controls came first, then capability across the whole firm.", situation: "Staff had started using AI tools on their own, with mixed results and no shared rules. As a firm holding highly sensitive client and tax data, leadership needed comfort before encouragement.", engagement: "An AI Blueprint set the direction, and controls were sequenced ahead of training because governance comfort had to come first.", delivered: [ "A Responsible AI Use policy with a named accountability owner", "A leadership workshop to land the position with partners", "Two days of hands-on Copilot training onsite for the whole firm", "The firm's own voice and tax research tools built into the sessions", ], outcome: null, quote: null, }, { type: "case", slug: "shopping-centre-partnership", tracker: "CS-017", industry: "Property", client: "Shopping centre owner and manager", clientPending: true, size: "13 sites", service: "AI Foundations", headline: "Capability built team by team, at the pace the appetite allowed.", summary: "Capability built under an ongoing partnership: the Blueprint set direction, finance put its hand up first, and the rest followed.", situation: "A large, multi-site organisation where switching AI on everywhere at once would have been the fastest way to lose the room.", engagement: "An ongoing AI Partnership, with the Blueprint holding direction and each team joining when it was ready.", delivered: [ "An AI Blueprint setting direction across the business", "Masterclasses and a lunch and learn series, starting with finance", "A capability journey tying the sequence together", "Board updates at each step", ], outcome: null, quote: null, }, { type: "case", slug: "regional-club-right-sized", tracker: "CS-049", industry: "Clubs", client: "Small regional club", clientPending: true, size: "2 leaders", service: "AI Foundations", headline: "The same three essentials, sized to a two-person leadership team.", summary: "A Blueprint workshop to choose the core AI tool, then a compact program delivered remotely, governance documents included.", situation: "A small club with no internal IT function, aware that AI mattered but with no way to tell the useful from the noise.", engagement: "A compact Foundations engagement delivered remotely, scaled to a two-person leadership team.", delivered: [ "A Blueprint workshop to choose the core AI tool", "A short list of starting points worth pursuing first", "A compact literacy program for the club's two leaders", "Position on AI and Responsible Use documents", ], outcome: null, quote: null, }, { type: "case", slug: "content-engine-agent", tracker: "CS-011", industry: "E-commerce", client: "Building products retailer", clientPending: true, size: "3 brands", service: "AI Accelerators", headline: "A month of brand-voiced content from one performance report.", summary: "A two-stage agent turns the monthly performance report into a month of platform-ready content for three brands, with a human approving the plan.", situation: "Every month a marketer read the performance report, planned the campaign, wrote a month of posts for three brands, then re-keyed everything into a 94-column import file.", engagement: "A fixed-scope build, designed around the existing monthly rhythm rather than replacing it.", delivered: [ "Stage one: report to campaign plan, for human approval", "Stage two: approved plan to a month of platform-ready posts", "Brand voice held separately for each of the three brands", "Output written straight into the 94-column import format", ], outcome: null, quote: null, }, { type: "case", slug: "booking-data-automation", tracker: "CS-018", industry: "Property", client: "Shopping centre owner and manager", clientPending: true, size: "13 sites", service: "AI Accelerators", headline: "Monthly booking data moved between two systems, across thirteen sites.", summary: "A manual monthly transfer across thirteen sites, engineered properly and now running in production under ongoing support.", situation: "Booking data was moved between two systems by hand every month, across thirteen sites, with the error rate you would expect.", engagement: "An engineered build under the existing AI Partnership, now extending into payment verification.", delivered: [ "An automated monthly transfer between the two systems", "Running in production under ongoing support", "Payment verification designed on a careful principle: where the AI cannot confirm a match, the correct answer is unable to confirm, never a guess", ], outcome: null, quote: null, }, { type: "case", slug: "email-triage-handover", tracker: "CS-034", industry: "Logistics", client: "Road freight operator", clientPending: true, size: "2 shared inboxes", service: "AI Accelerators", headline: "Shared inboxes triaged, then handed over to run in-house.", summary: "An email triage agent built, proven, then migrated into the operator's own environment with staff trained to run it themselves.", situation: "Shared inboxes for customer service and the warehouse were absorbing the team's day before the real work started.", engagement: "A fixed-scope build with handover as the stated end point, not an afterthought.", delivered: [ "An email triage agent sorting and routing both inboxes", "Proven in our environment, then migrated into theirs", "Staff trained to run and adjust it themselves", ], outcome: null, quote: null, }, // ---------- WHITE PAPERS (IA's thinking; the deep tier of the GEO strategy) ---------- { type: "paper", slug: "three-essentials", industry: "All industries", headline: "Why AI adoption fails without all three essentials.", summary: "Brilliant tools with no guardrails. Policies nobody reads. Training with nothing to apply it to. Why partial adoption keeps failing.", status: "planned", links: [ { label: "Can we start with training before strategy?", to: "faqs" }, { label: "AI Foundations", to: "ai-foundations" }, ], }, { type: "paper", slug: "position-vs-policy", industry: "All industries", headline: "A board's Position on AI versus a Responsible Use policy, and why you need both.", summary: "One is owned by your board. The other is followed by your people on a Tuesday afternoon. Neither works without the other.", status: "planned", links: [ { label: "What's the difference between the two?", to: "faqs" }, { label: "Governance in detail", to: "governance" }, ], }, { type: "paper", slug: "engineered-vs-self-serve", industry: "All industries", headline: "Engineered agents versus self-serve agents.", summary: "Anyone can stand up an agent in an afternoon. What engineering adds once it touches your systems, and when self-serve is enough.", status: "planned", links: [ { label: "What's an AI agent, and does our business need one?", to: "faqs" }, { label: "AI Accelerators", to: "accelerators" }, ], }, { type: "paper", slug: "safe-adoption-smaller-organisations", industry: "All industries", headline: "Safe AI adoption for small and medium organisations.", summary: "Most AI governance material assumes a legal team. What good looks like without one, for a board that still needs to say yes.", status: "planned", links: [ { label: "How we work", to: "how-we-work" }, { label: "Governance in detail", to: "governance" }, ], }]; // The six client engagements, captioned industry + service so the two // Property engagements read as two different pieces of work. const FAN_ENTRIES = WORK_ENTRIES.filter((e) => e.type === "case").slice(0, 6); const ART_FOR = { "accounting-firm-foundations": "professional-services", "shopping-centre-partnership": "property", "regional-club-right-sized": "clubs", "content-engine-agent": "e-commerce", "booking-data-automation": "property-2", "email-triage-handover": "logistics", }; const TYPE_FILTERS = [ { key: "all", label: "Everything" }, { key: "case", label: "Case studies" }, { key: "paper", label: "White papers" }]; function WorkV2Screen({ go, t, sub }) { const [type, setType] = React.useState("all"); const [industry, setIndustry] = React.useState("all"); const [detail, setDetail] = React.useState(() => (sub ? WORK_ENTRIES.find((e) => e.slug === sub) || null : null)); React.useEffect(() => { if (sub) { const e = WORK_ENTRIES.find((x) => x.slug === sub); if (e) setDetail(e); } }, [sub]); const industries = React.useMemo(() => { const seen = []; WORK_ENTRIES.forEach((e) => { if (e.industry !== "All industries" && !seen.includes(e.industry)) seen.push(e.industry); }); return seen.sort(); }, []); const filtered = React.useMemo(() => WORK_ENTRIES.filter((e) => { if (type !== "all" && e.type !== type) return false; if (industry !== "all" && e.industry !== industry) return false; return true; }), [type, industry]); const typeCounts = React.useMemo(() => { const o = { all: WORK_ENTRIES.length }; WORK_ENTRIES.forEach((e) => { o[e.type] = (o[e.type] || 0) + 1; }); return o; }, []); if (detail) return { setDetail(null); if (window.location.hash !== "#work") window.location.hash = "work"; }} go={go} t={t} />; return (
{/* HERO — dark stage, quiet centred type, fanned photo cards below */}

Our work

Every organisation's AI journey looks a little different. Here are some of the ones we've been part of, along with our thinking on what makes AI adoption work.

{/* FILTERS */}
Type
{TYPE_FILTERS.map((f) => ( ))}
Industry
{industries.map((n) => ( ))}
{/* LIBRARY */}
{filtered.length} {filtered.length === 1 ? "entry" : "entries"} {(type !== "all" || industry !== "all") && ( )}
{filtered.length === 0 ? (
Nothing published under those filters yet. We have likely done something close, so{" "} go("contact")}>ask us.
) : (
{filtered.map((e) => setDetail(e)} />)}
)}

Recognise your own situation in one of these? Tell us where you're up to with AI, and we'll tell you what we'd do next.

); } // ---------- Hero corridor ---------- // Six engagements receding to a centre vanishing point behind the headline: // front pair sharp, inner pairs falling out of focus. Cards drift with the cursor. // A chained ribbon per wing: seven tiles, each touching the next, growing from // a tiny tile at the waist to a full panel cropped by the screen edge. const CHAIN_N = 4; const CARD_W = 262; const WK_CHAIN = (() => { const out = []; let cursor = 2; for (let i = 0; i < CHAIN_N; i++) { const s = 0.3 * Math.pow(1.55, i); const wdt = CARD_W * s; cursor += wdt / 2; out.push({ x: Math.round(cursor), z: -420 + i * 130, rot: 23 - i * 2.4, s: +s.toFixed(3), pz: 0.55 + i * 0.28, cap: i >= 2 }); cursor += (wdt / 2) * 0.88; } return out; })(); const MOTION_KEY = { "scroll open": "scroll", "stream": "stream", "fan": "fan", "deal in": "deal", "float": "float", "hover focus": "hover", "still": "still" }; // Fan: six panels overlapping in a shallow arc, anchored to the bottom edge of // the stage so they run off it. Ends sit lower and turn out; z ascends right to // left, so the leftmost face sits on top. const FAN_GEO = [ { x: -352, y: 44, rot: -11 }, { x: -212, y: 12, rot: -6.6 }, { x: -71, y: 0, rot: -2.2 }, { x: 71, y: 0, rot: 2.2 }, { x: 212, y: 12, rot: 6.6 }, { x: 352, y: 44, rot: 11 }, ]; // Stream geometry. Panels butt against each other while growing, so the centre // distance has to follow the integral of the width: X(u) = K(g^u - 1). const STREAM = { n: 5, // panels per wing s0: 0.1, // scale at the waist g: 1.62, // growth per slot rot: 22, // constant fold angle, as in the reference uMax: 5, // slots travelled before a panel recycles period: 14000, // ms for one full traverse }; STREAM.k = (CARD_W * STREAM.s0 * Math.cos(STREAM.rot * Math.PI / 180)) / Math.log(STREAM.g); function WorkPhotoCorridor({ entries, onOpen, motion = "scroll open", nonce = 0 }) { // Outer pair first so the wings read left to right: 1 3 5 | 6 4 2. const order = [0, 2, 4, 5, 3, 1].map((i) => entries[i]).filter(Boolean); const ref = React.useRef(null); // The wings start folded in near the headline and swing open as the visitor // scrolls into the page. const mode = MOTION_KEY[motion] || "scroll"; // Conveyor: each panel walks the chain, recycling at the waist. React.useEffect(() => { const el = ref.current; if (!el || mode !== "stream") return; const cards = Array.prototype.slice.call(el.querySelectorAll(".wk-corr-card")); const { n, s0, g, rot, uMax, period, k } = STREAM; let raf = 0; const tick = (now) => { const base = ((now % period) / period) * uMax; for (let c = 0; c < cards.length; c++) { const side = c < n ? -1 : 1; const slot = c % n; const u = (base + (slot * uMax) / n) % uMax; const grow = Math.pow(g, u); const s = s0 * grow; const x = k * (grow - 1) + 1; const fade = Math.min(1, u / 0.4, (uMax - u) / 0.6); const el2 = cards[c]; el2.style.opacity = fade.toFixed(3); el2.style.transform = "translate3d(" + (side * x).toFixed(1) + "px,0,0) rotateY(" + (side * rot) + "deg) scale(" + s.toFixed(4) + ")"; } raf = requestAnimationFrame(tick); }; raf = requestAnimationFrame(tick); return () => cancelAnimationFrame(raf); }, [mode]); React.useEffect(() => { const el = ref.current; if (!el) return; if (mode !== "scroll") { el.style.setProperty("--open", "1"); return; } let frame = 0; const upd = () => { frame = 0; const p = Math.min(1, Math.max(0, window.scrollY / 380)); el.style.setProperty("--open", p.toFixed(3)); }; const onScroll = () => { if (!frame) frame = requestAnimationFrame(upd); }; upd(); window.addEventListener("scroll", onScroll, { passive: true }); return () => { window.removeEventListener("scroll", onScroll); if (frame) cancelAnimationFrame(frame); }; }, [mode]); if (mode === "fan") { // Honest decoration: the fan signals a body of work, the index below does the // navigating. No click, no cursor tilt, no rise — the panels are just there. return ( ); } return ( {[-1, 1].map((side) => (mode === "stream" ? new Array(STREAM.n).fill(0) : WK_CHAIN).map((g0, i) => { const g = mode === "stream" ? { x: 0, z: 0, rot: STREAM.rot, s: STREAM.s0, pz: 1, cap: false } : g0; const e = order[(side < 0 ? i : i + (mode === "stream" ? STREAM.n : CHAIN_N)) % order.length]; return ( ); }) )} ); } // ---------- Entry card (one template, both content types) ---------- function WorkEntryCard({ entry, onOpen }) { const e = entry; const isPaper = e.type === "paper"; return (
{!isPaper && (
)}
{isPaper ? "White paper" : "Case study"} {isPaper && e.status === "planned" && In preparation}

{e.headline}

{e.summary}

{isPaper ? Intelligence Assist : ( {e.client}{e.clientPending && name pending approval} )} {e.industry}{e.size ? ` · ${e.size}` : ""}
); } // ---------- Detail (one template, both content types) ---------- function WorkV2Detail({ entry, onBack, go, t }) { const e = entry; const isPaper = e.type === "paper"; const layout = (t && t.caseLayout) || "current"; const csl = layout.charAt(0); return (
{isPaper ? "White paper" : "Case study"}

{e.headline}

{e.summary}

{!isPaper && (
)}
{!isPaper && (
{layout === "current" ? (
The situation

{e.situation}

The engagement

{e.engagement}

What was delivered
    {e.delivered.map((d, i) =>
  • {d}
    • )}
The outcome
{e.outcome ?

{e.outcome}

:

Outcome line pending, tracker {e.tracker}.

}
In their words
{e.quote ? (
{e.quote.text}
, {e.quote.name}, {e.quote.role}
) :

Quote pending sign-off, tracker {e.tracker}.

}
) : csl === "A" ? : csl === "B" ? : }
)} {isPaper && (
What it covers

A working paper from Intelligence Assist, written for leaders rather than practitioners. It expands on the questions we get asked most often, and doubles as the material behind our speaking on the topic.

Related reading
{e.links.map((l, i) => go(l.to)}>{l.label})}
)}

{isPaper ? "Want to talk it through? " : "Recognise your own situation here? "} {isPaper ? "We're happy to have the conversation before the paper lands." : "Tell us where you're up to, and we'll tell you what we'd do next."}

); } function CaseBodyA({ e }) { return (
Before

{e.situation}

After

{e.summary}

The build
{e.delivered.map((d, i) => (
{String(i + 1).padStart(2, "0")}

{d}

))}

The engagement. {e.engagement}

{e.outcome || `Outcome line pending, tracker ${e.tracker}`} {!e.quote && Quote pending sign-off}
); } function CaseBodyB({ e }) { const [one, two, ...rest] = e.delivered; return (
How it runs
Step one

{one}

Step two

{two}

{rest.length > 0 && (
{rest.map((r, i) =>

{r}

)}
)}
The situation

{e.situation}

The engagement

{e.engagement}

{e.outcome || `Outcome and quote pending, tracker ${e.tracker}`}
); } function CaseBodyC({ e }) { return (
Client{e.client}{e.clientPending && name pending approval}
Industry{e.industry}
Size{e.size}
Engagement{e.service}
Outcome{e.outcome || "Pending"}{!e.outcome && tracker {e.tracker}}

The situation

{e.situation}

The engagement

{e.engagement}

What was delivered

    {e.delivered.map((d, i) =>
  • {d}
    • )}
{e.quote ? (
{e.quote.text}
, {e.quote.name}, {e.quote.role}
) :
Quote pending sign-off, tracker {e.tracker}.
}
); } function DetailMetaV2({ label, value, sub, highlight }) { return (
{label} {value} {sub && {sub}}
); } Object.assign(window, { WorkV2Screen, WORK_ENTRIES, WorkEntryCard });