The people behind your Salesforce assessment
Richard Fleck developed Pariveo's methodology. His more than eight years on the Salesforce platform shape the assessment criteria and how Pariveo interprets the findings.
Certifications
- Application Architect
- Data Architect
- Sharing & Visibility Architect
- Development Lifecycle & Deployment Architect
- Platform Developer I
- JavaScript Developer I
- Platform App Builder
- Platform Administrator
- Platform Administrator II
- Agentforce Sales Consultant
- Agentforce Service Consultant
- AI Associate (retired)
How I work
I have spent nearly my whole career inside Salesforce orgs: first configuring them, then building on them, and for more than five years now leading the platform team behind one. So I am rarely the person who moves on once a project ends. I am the one who still works with those decisions years later. That shapes what the assessment checks and how I interpret the findings.
Where the criteria come from
Every check rests on hands-on experience in real system landscapes. The examples below show how that experience becomes a criterion.
Automation grown over the years
When a platform moves off older systems, the new and the old logic often run next to each other for years. The assessment shows which era an automation comes from, and where several generations affect the same object.
Integrations without a full picture
Rigid direct connections between systems settle over time into a web few people can still see in full. Reworking such a landscape into an event-driven architecture produced one of the central criteria: the assessment shows who exchanges data with whom, and which of those connections are still in use today.
Changes without a history
Anyone who makes adjustments straight in the interface, instead of relying on versioned metadata and automated delivery, loses the history of those changes. The current state is visible at any time, but how it came about is not. Who changed what, and when, can barely be reconstructed after the fact.
Permissions that grew over the years
A sharing model grows along with every new department and every new process. After a few years, what stands is rarely the model that was once designed. So permissions are a focus area of their own in the assessment.
Knowledge that depends on individuals
Where a small platform team runs an environment that has grown over the years, every handover takes longer once documentation is missing. So the assessment measures how far a structure explains itself.
The new benchmark: AI readiness
How a Salesforce environment is built is written down in its metadata: which automations run, which systems exchange data, who is allowed to see what. That description is what AI agents and AI coding agents read before they suggest or change anything.
How well they work depends on how clear that description is. What a new team member understands after two weeks, an AI can process reliably too. So the assessment asks not only whether something works technically, but also how traceably it is built.
See every area the assessment coversWant this for your org?
Book a free 30-minute discovery call. In it, we identify which points matter most to you and focus the assessment accordingly. You then receive your executive report within 5 to 10 business days after access is granted.
Book a Discovery Call