Dispatches.
Vol. I · Dispatches
Case studies, named and anonymised. Where clients can't be named for confidentiality, we describe the sector and the shape of the work. The substance of each engagement is the same whichever side of that line it sits.
What
Our own product. Strategy through delivery — positioning, architecture, and the continuous work of shipping and iterating. The discipline of running our own product informs how we advise clients.
Outcome
Live. Ongoing. The product we return to between client engagements and the reason our advice on product work is grounded in practice rather than theory.
What
Investigation into suspected unauthorised access to a client Salesforce environment during a sensitive commercial period. We traced the access event to an existing OAuth integration, assessed exfiltration risk under the available logging, and delivered findings suitable for both legal interpretation and commercial due diligence.
Outcome
Reclassified the event from presumed breach to persistent authorised-integration access. Recommendations to revoke long-lived OAuth tokens, enable Event Monitoring, and introduce governance for third-party integrations.
What
A multi-phase programme adding intelligent enrichment across the sales funnel — leads, opportunities, and accounts. Includes n8n automation, two-stage LLM analysis, ~90 custom fields per object, a tabbed Lightning Web Component insights panel, a one-click refresh flow, and scheduled re-enrichment with guardrails.
Outcome
Sales teams receive contextual, explainable intelligence inside Salesforce; the system self-governs against stale data, cost overruns, and silent schema drift.
What
Account-level intelligence for a business selling into law enforcement, government, and financial institutions. Architecture draws on public data sources (Companies House, Google Custom Search, contract-award feeds) and private signals, written back into Salesforce with composite risk scoring and churn prediction.
Outcome
Live implementation programme; ICP-specific enrichment replaces a prior mis-configured pipeline aimed at the wrong vertical.
What
Bidirectional synchronisation of comments and binary attachments between Salesforce Cases and Jira issues — covering feed-post polling, attachment deduplication by Jira ID, non-blocking Teams notifications, paired-item logging, and scheduled recovery paths for missed events.
Outcome
A round-trip sync that survives real-world failure modes — missing fields, Teams permission errors, multi-attachment bursts, and concurrent-edit collisions.