Case study · Nordwind Automotive

Nearshore Experience Cloud Team for the Nordwind Automotive Dealer Portal

Engagement summary

ForceFolks supplied a full-time Experience Cloud consultant, Salesforce technical lead and Salesforce developer from Lisbon to Nordwind Automotive’s Munich delivery team. The pod worked in Nordwind’s Azure DevOps and GitHub environment from 12 February to 20 September 2024. Nordwind kept the roadmap, SAP backend and release decisions. The team met the September dealer conference deadline, and dealer satisfaction reached 96% in October, compared with 61% in the legacy portal survey.

Client and Engagement Facts

Nordwind Automotive: Client and Engagement Facts
FieldEngagement detail
ClientNordwind Automotive
Client and industryNordwind Automotive, automotive distribution
Locations and overlapMunich, Germany and Lisbon, Portugal. Full working-day overlap with the Munich team and two shared ceremonies daily.
Salesforce and systemsExperience Cloud, Sales Cloud, Service Cloud, MuleSoft and SAP
Delivery toolsAzure DevOps, GitHub and Salesforce CLI
Roles and termThree full-time specialists from 12 February to 20 September 2024
Client ownershipThe Head of Dealer Systems kept the roadmap. The dealer council accepted portal features. The client platform architect reviewed technical design and code.

Why the Client Added Capacity

Nordwind needed a replacement for a legacy dealer portal before its dealer conference. Its internal team owned SAP and dealer data and lacked Experience Cloud capacity. The client added specialists who could join its delivery train and working day, agree acceptance criteria with the dealer council and submit portal and integration changes to its own reviewers.

Client corroboration

“The ForceFolks pod was in our standups from week one, our platform architect reviewed their design work, and our dealer council approved every feature.”

Jonas Keller, Head of Dealer Systems, Nordwind Automotive

Role Contributions and Acceptance

Nordwind Automotive: Role Contributions and Acceptance
ForceFolks roleWork and outputsClient review or acceptance
Experience Cloud consultantDefined ordering, stock visibility and support journeys with dealer stakeholders. Produced 34 approved stories, acceptance criteria, a decision log and business UAT scripts.Head of Dealer Systems and dealer council representatives.
Salesforce technical leadDesigned the integration for three SAP endpoints via MuleSoft, set a one-business-day pull request review standard and prepared the release checklist adopted by Nordwind’s platform team.Client platform architect.
Salesforce developerBuilt 11 Lightning Web Components for ordering and stock views, connected stock and order-status calls through MuleSoft and tested external-user sharing for 1,180 dealer users.ForceFolks technical lead, followed by the client platform architect.

Outcomes and Evidence

Nordwind Automotive: Outcomes and Evidence
MeasureBaselineResultWindowSource
Dealer satisfaction61% in the legacy portal survey96% in the October surveyOctober 2024 vs. legacy portal surveyNordwind dealer surveys
Code review turnaround3.2 days with prior vendor1 business day medianFebruary to September 2024Client Azure DevOps records
Dealer access validation1,180 external-user access tests1,180 of 1,180 passedAugust 2024Client UAT record
Dealer conference release20 September 2024 deadlineDeadline metSeptember 2024Client programme milestone log and dealer council sign-off
Pod onboardingEngagement startAll three roles committing in client repositories within 8 business daysFebruary 2024Client repository activity log

Discuss the work your team needs

Share the Salesforce work, roles and client review responsibilities. ForceFolks will assess the staffing requirement against that scope.

Discuss your staffing requirement