Throughline v0 previewSigned in asMaya Tan

Brindle & Co.

4 open entries2 patterns worth your attention

Your lead hand at CSFWPNik Thompsonnik@csfwp.comBook 15 min →

What's worth your attention

  1. Pattern detected · yesterdayhigh

    Procurement RFP cycle is breaking creative continuity

    Three entries in the last 30 days point at the same friction: procurement's $15k tender threshold has no carve-out for continuing creative partners. The Q3 product launch is the live example, but the same pattern cost the spring case-study series its brand consistency (flagged in your last QBR) and added two weeks to a webinar timeline through repeated vendor onboarding. Each fresh tender saves roughly $3-4k on the bid but burns 8-10 days of vendor onboarding and erodes the brand cohesion we then spend post-production hours trying to recover. Net cost is well above the savings. The fix is a one-meeting policy change with procurement.

    Recommendation

    Scope as a project — draft a Continuing Creative Partner carve-out for the procurement threshold rule

    auto-detected · 88% confidence
  2. Pattern detected · this morninghigh

    Case-merge logic is leaning too hard on DMN

    DMN is catching about 73% of duplicate cases cleanly. The remaining 27% are fuzzy matches — slight name spellings, missing accents, multi-touch sequences where two engagements fire within seconds. DMN doesn't do fuzzy matching by design; that's a different class of problem. The AE team currently absorbs this as 4+ hours of manual dedup per week. We've patched two specific incidents this quarter (ENT-3y3n44 most recently) but they keep recurring because the root cause is architectural, not configuration. The clean fix is a small fuzzy-match pre-pass that flags candidates before DMN evaluates the strict rules — about a week of work, no disruption to existing DMN logic.

    Supporting entries
    Recommendation

    Scope as a project — add a fuzzy-match pre-pass to the case-merge pipeline

    auto-detected · 81% confidence

See all 3 signals & tag movement →

Open entries

  • ENT-3y8a0pQ3 product launch reel — procurement reopened the tender, we'll lose MarigoldOpenEmailhand Raadad · Celeste Labsopened May 222h ago
    • procurement
    • tendering
    • videographer
    • brand-continuity
    Maya TanClientMay 22 · 9:14

    Comms team just told me procurement triggered a fresh RFP for the Q3 launch reel. We've used Marigold Studio for the last four major videos and the brand is finally feeling cohesive — same shooter, same colourist, same audio levels. Now we're being made to choose from three bids again and the cheapest contender doesn't know our category at all. Can we do something about this?

    Raadad · Celeste LabsCSFWPMay 22 · 11:02

    Confirmed — this is the third time this year the same thing has happened on a creative tender. Procurement's threshold rule kicks in at $15k and the policy has no carve-out for 'continuing creative partner'. The pattern detector is now flagging this as a category — see the analysis below. I'll pull the full spend pattern across all three incidents and Nik can take a scoped proposal to procurement leadership. In the meantime I've messaged your CFO via Nik to see if we can override this round on continuity grounds.

    Raadad · Celeste LabsCSFWP2h ago

    CFO is willing to override but wants a written policy proposal she can take to the procurement director. Nik and I will have a draft ready for your review on Tuesday.

  • ENT-3y7f12AE team manually deduping 40+ cases a week — DMN missing fuzzy matchesIn progressPortalhand Angusopened May 20yesterday
    • dmn
    • case-merge
    • sales-ops
    • dedupe
    • salesforce
    Maya TanClientMay 20 · 16:40

    AE team is spending the best part of half a day a week merging duplicate cases by hand. Marketing-attributed leads come in as new even when the contact already exists on an account. We've added more DMN rules over time but they're getting brittle and the dedup volume isn't going down.

    Angus · CSFWPCSFWPyesterday

    Pulled an audit on the last 30 days: DMN catches 73% of duplicate pairs cleanly. The remaining 27% are fuzzy matches — slight name spellings (Maria vs Marya), missing accents (Müller vs Muller), multi-touch sequences where two engagements fire within seconds. DMN doesn't do fuzzy matching by design; that's not the right tool for that 27%. Two options I'd consider — both with effort estimates in Slack: (a) add a fuzzy-match pre-pass that flags candidates before DMN evaluates, (b) replace DMN with a hybrid scoring layer. I think (a) is the right call; less disruption.

  • ENT-3y6r88Channel partner sent customer wrong pricing — Knowledge article 9 months staleOpenSlackhand Jennyopened May 23this morning
    • knowledge-base
    • knowledge-staleness
    • channel-partner
    • sales-enablement
    Maya TanClientMay 23 · 8:02

    Just off the phone with [Veridian, channel partner]. They quoted a customer at last year's tier-2 price, ~$40/mo lower than current. Customer signed, we're honouring it. This is the third time we've seen it. The Knowledge article they cited was last updated in September.

    Jenny · CSFWPCSFWPthis morning

    Yeah — and the partner has no way to know the article is stale. There's no last-reviewed metadata, no owner field, no flag for 'review-by'. Started a quick spot-check on the top 40 most-viewed Knowledge articles: 31 haven't been edited in 6+ months, 11 are over a year old. Pattern detector is flagging this as a category too — see the analysis below.

  • ENT-3y4s17Sales pitch deck pulling outdated features list from KnowledgeAwaiting clientEmailhand Jennyopened May 18May 19
    • knowledge-base
    • knowledge-staleness
    • sales-enablement
    Jenny · CSFWPCSFWPMay 19 · 10:11

    Inspected the pitch deck — the 'Capability comparison' slide is dynamically populated from the Salesforce Knowledge 'Capabilities matrix' article. That article was last edited in October '25 and references three features that have since been deprecated. Two options: (1) refresh the source article so every downstream surface picks it up, (2) decouple the deck and maintain it manually. (1) is what I'd recommend but it needs an owner. Who do you want me to assign?

Go to entries

From your latest Throughline

May Throughline — Brindle & Co.

The headline this month is the lead-stage scoring model. Two-hundred MQLs ran through the v2 model for four weeks; selection is converting to SQL at 18% above the legacy scorer, and the AE team's feedback has moved from "this list is noise" to "most of these are real". We're ready for full cutover at the end of June.