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
| Field | Engagement detail |
|---|---|
| Client | Nordwind Automotive |
| Client and industry | Nordwind Automotive, automotive distribution |
| Locations and overlap | Munich, Germany and Lisbon, Portugal. Full working-day overlap with the Munich team and two shared ceremonies daily. |
| Salesforce and systems | Experience Cloud, Sales Cloud, Service Cloud, MuleSoft and SAP |
| Delivery tools | Azure DevOps, GitHub and Salesforce CLI |
| Roles and term | Three full-time specialists from 12 February to 20 September 2024 |
| Client ownership | The 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.”
Role Contributions and Acceptance
| ForceFolks role | Work and outputs | Client review or acceptance |
|---|---|---|
| Experience Cloud consultant | Defined 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 lead | Designed 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 developer | Built 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
| Measure | Baseline | Result | Window | Source |
|---|---|---|---|---|
| Dealer satisfaction | 61% in the legacy portal survey | 96% in the October survey | October 2024 vs. legacy portal survey | Nordwind dealer surveys |
| Code review turnaround | 3.2 days with prior vendor | 1 business day median | February to September 2024 | Client Azure DevOps records |
| Dealer access validation | 1,180 external-user access tests | 1,180 of 1,180 passed | August 2024 | Client UAT record |
| Dealer conference release | 20 September 2024 deadline | Deadline met | September 2024 | Client programme milestone log and dealer council sign-off |
| Pod onboarding | Engagement start | All three roles committing in client repositories within 8 business days | February 2024 | Client repository activity log |
Related roles and delivery services
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