Foxglove Group

The headline this month is the functions enquiry scoring model. Two hundred enquiries ran through the v2 model for four weeks; selection is converting to confirmed bookings at 18% above the legacy scorer, and the functions team's read has moved from "this list is noise" to "most of these are real". We're ready for full cutover at the end of June.

The Mailchimp to Marketing Cloud migration is on schedule, but the list-migration pilot surfaced a guest-record dedup bug on multi-touch arrivals. Angus patched the immediate entry and the pattern detector picked up the broader category — see the dedup analysis above. I think it's right; I'd rather scope a fuzzy-match pre-pass than keep patching record-by-record. The functions team is absorbing 4+ hours of manual merging a week, which is a poor use of their time.

Two slow burns. The procurement-tender pattern on creative work is now a clear category — Theo at Northlight has flagged three entries in 30 days, brand continuity across the six venues is suffering, and the spring launch reel is the live test of whether we can change the policy in time. I'd recommend the one-meeting fix with procurement; happy to write the proposal. Separately, Knowledge staleness keeps biting at the functions-agent edge — Jenny pulled the audit, agents are quoting articles last updated in September.

The pattern I'd most like your attention on operationally is the cluster of critical workflows running under individuals' personal accounts. Priya's leave in four weeks surfaced a sync pinned to her laptop, and the audit Angus ran off the back of it found three more in the same shape. Separately, the functions team is sending booking follow-ups through their own Gmail and reputation is starting to show it. They're the same problem from two angles — auth and sending — and the cleanest scope is one project that fixes both, with the sending moved onto Marketing Cloud properly. Move before the leave, not under it.

And then the throughline under all of it. The re-tendering, the stale Knowledge, and this week's winter-offer miss — where the new price went live on the website, the EDM and the booking pages but not the Knowledge article, so staff quoted the old number for two days — are not three problems. They're one: an offer lives in four places and gets reconciled by hand. My recommendation is to make the offer a governed object — run the graphic-design tender and offer process as an SOP on a Monday board, and on approval push the finished offer to Webflow, Marketing Cloud and Salesforce Knowledge in a single move. Approve once, every surface updates. It pays down the procurement, Knowledge and campaign-ops debt at the same time, and it's what finally lets us put an Agentforce concierge in front of guests after hours without it quoting them the wrong thing.

That's the job, really — none of Collins, Mailchimp, Salesforce, Webflow, Instagram or the studio sees the whole picture on its own. Reading the pattern across all of them and finding the one move that makes the rest line up is what we're here for.