A major compliance company needed to make supplier readiness faster, cheaper, and more measurable without increasing risk. What began as a targeted Salesforce and Snowflake automation grew into three parallel streams of automation across program management, document verification, and supplier visibility.
A four-act CRAWL/WALK/RUN buildout across three parallel streams: Program Automation (Salesforce/Snowflake), Batch AI Doc Verification (AWS Bedrock, Step Functions), and a Supplier Profile data product, with an embedded fractional tech leadership engagement to surface gaps and establish governance frameworks.
A major enterprise client needed suppliers to move from registered to fully compliant faster, without delays on live projects. A CEO "Supplier Forward" initiative demanded measurable improvement, and manual, spreadsheet-driven processes were not built to scale.
No automation tooling, no shared data model, manual CSV-driven Salesforce workflows, no provenance between systems, and compliance knowledge scattered across six departments with no structured documentation.
RTW programs ran on spreadsheets and ad-hoc CSV uploads. Every wave required a labour-intensive reset across multiple teams and systems.
Salesforce campaign creation and case triage relied on manual CSV uploads from Snowflake exports. No systemised flow existed for wave execution or supplier selection.
ProcessCritical compliance knowledge lived across Supplier Support, QHSE, Insurance, RTW, BizSys, and Analytics, with no shared source of truth.
Business rules were undocumented and inconsistently interpreted across six departments. No unified data model or shared knowledge layer existed.
KnowledgeEvery increase in supplier volume or new client program meant a proportional increase in team effort. There was no mechanism to grow capacity without hiring.
Case volumes scaled linearly with program size. Supplier lookup loops averaged several minutes each and were repeated across many cases per day.
ScaleTeams could not see overall supplier readiness or form-level compliance status without time-consuming manual lookups in Connect.
Compliance status lived in Connect, not surfaced in Salesforce. Each lookup loop could take several minutes and was repeated across many cases per day.
VisibilityThe engagement followed a disciplined Discover, Pilot, Scale model. Each phase built directly on what the previous one validated.
A CRAWL/WALK/RUN delivery model with structured discovery feeding into three parallel streams, each with its own release cadence and integration surface.
Towards the end of WALK, with three streams in production and the platform stabilised, a senior technology consultant was embedded for four to five weeks to document the underpinning business rules, establish governance frameworks, and identify opportunities for deeper system improvement.
Towards the end of WALK, with PA v6–v8, Doc Verification, and Supplier Profile all in production, a fractional CTO was embedded for four to five weeks to run structured stakeholder discovery and produce a queryable service specification as a governing reference for future development.
In CRAWL, the engagement expanded from one engine into three parallel streams, each tackling a distinct operational problem and designed to work together by the end of WALK.
Three streams with distinct integration surfaces but shared data foundations, each independently releasable and designed to compose into a coherent system by WALK.
The core RTW engine, evolved from a basic wave runner into a lifecycle-aware orchestration system. By WALK it knows which suppliers belong in RTW, guards against double-enrollment across multiple client programs, surfaces compliance data to operators in context, and automates outreach and follow-up scheduling.
Every automation was instrumented from the start. The figures below come directly from the RTW Program KPI analysis, measured baselines compared against automated performance, not estimates.
Baseline measurements captured before each automation; post-automation timings measured against the same task types. The combined picture reflects one 45-day wave plus annualised document verification.
The RUN phase applies the same automation approach across more supplier journey moments, with smarter prioritisation and client-facing visibility powered by the Supplier 360 data product.
RUN extends the event-trigger model beyond RTW waves, activates Supplier 360 for risk scoring and channel selection, and optionally formalises Autopilot as a distinct orchestration layer.