Skip to main content
Sample Report

Sample Assessment

On this page we show you excerpts from our sample report. You'll see the scores achieved per module, an AI readiness rating, prioritized findings, and quick wins. In an assessment we surface all of it from more than 200 deterministic checks. The values on this page are sample data and illustrate how we present the results.

0/100
Pioneering
01

Report Preview

Your full report has three parts: an executive summary for the overview, an architect deep-dive for the technical detail, and a developer punch list for the work itself.

Criteria reference page listing every check with its severity and weight
Executive summary page with the overall maturity score and module scoreboard
AI readiness dashboard and feature adoption breakdown

Actual pages from a sample assessment

02

Module Scoreboard

Every one of the 15 analysis modules gets its own maturity score. We sort the list by improvement potential, so the areas with the most room to grow sit right at the top.

01

Agentforce

58
Evolving12 Agents
02

Automation

64
Evolving393 Flows
03

Reports & Dashboards

64
Evolving487 Reports
04

DevOps

69
Evolving84 Deployments
05

Apex Health

71
Scaling302 Apex Classes
06

UI Components

72
Scaling278 Components
07

Object Maturity

73
Scaling142 Objects
08

Integrations

77
Scaling23 Connections
09

Layouts

81
Scaling156 Layouts
10

Data Model

82
Scaling2703 Fields
11

Packages

85
Pioneering14 Packages
12

Access Control

88
Pioneering47 Permission Sets
13

Org Security

90
Pioneering18 Settings
14

Data Governance

91
Pioneering134 Rules
15

User Health

93
Pioneering842 Users
03

AI Readiness

The following five dimensions show how well your org supports AI agents, AI coding agents, and LLM grounding. After all, descriptions, labels, and data-model and code quality form the working context AI coding agents work with.

Field Descriptions & Labels68
AI & Agent Readiness58
Data Model Quality76
Automation Quality64
Apex Code Quality71
04

Feature Adoption

Of the 30+ adoption transitions we track, here are eight. They show how far your org has moved from legacy patterns to modern Salesforce standards, ranked by what Salesforce itself recommends.

82%
8
active transitions
4
urgent items
Overall Adoption Progress82%

697 / 846 adopted

Urgent(2)
87%

Workflow Rules → Record-Triggered Flows

Workflow RulesRecord-Triggered Flows

312/ 359 adoptedM

72%

Process Builder → Record-Triggered Flows

Process BuilderRecord-Triggered Flows

58/ 81 adoptedL

Important(2)
83%

Profiles → Permission Set Groups

ProfilesPermission Set Groups

39/ 47 adoptedL

72%

Visualforce → Lightning Web Components

VisualforceLightning Web Components

89/ 123 adoptedXL

Notable(2)
83%

Aura Components → Lightning Web Components

Aura ComponentsLightning Web Components

67/ 81 adoptedL

93%

Page Layouts → Lightning Record Pages

Page LayoutsLightning Record Pages

83/ 89 adoptedS

Advisory(2)
78%

Legacy Named Credentials → Named Credentials + External Credential

Legacy Named CredentialsNamed Credentials + External Credential

18/ 23 adoptedM

72%

Change Sets → Metadata API / SF CLI

Change SetsMetadata API / SF CLI

31/ 43 adoptedL

05

Priority Findings

Here are four selected findings from this org. They're just a small slice of what your full assessment will surface.

209 Objects With Unrestricted Public Read/Write Sharing

Urgent

Organization-Wide Defaults leave 209 objects fully open to all internal users, including AI agents operating on their behalf. Tightening sharing rules would reduce the AI data surface area by an estimated 60%.

Sensitive Fields Editable Without a Field-Level Security Review Cycle

Important

19 permission sets grant edit access to fields matching PII patterns (national ID, payment reference, contract value), with no automated cycle to detect permission drift as teams evolve.

8 Named Credentials on Legacy Embedded-Credential Architecture

Important

8 integration connections use the pre-API v55 model with static embedded credentials. This pattern is incompatible with per-user OAuth token contexts required by AI agent callouts and Flow-based external service invocations.

Automation Hotspot: Account Has 14 Active Record-Triggered Flows

Notable

Account accumulates 14 record-triggered flows from 6 different teams, including 3 before-save flows sharing the same entry point without entry conditions. This creates unpredictable execution order and complex debug paths.

06

Quick Wins

These changes take little effort but noticeably raise your org's maturity. They make good first steps when you want quick, visible progress.

Add Descriptions to Core Fields

Fill 340 empty descriptions on high-traffic custom fields to boost AI readability by +12 pts.

Effort: XSImpact: 5/5

Deactivate Legacy Workflow Rules

Safely deactivate 47 migrated workflow rules still running in parallel with replacement Flows.

Effort: SImpact: 4/5

Consolidate Redundant Permission Sets

Merge 6 near-identical permission sets into 2 consolidated groups, reducing admin overhead.

Effort: SImpact: 4/5
07

High-Impact Objects

These objects carry the largest combined potential across several dimensions, from field quality and automation to permission scope. They point you to where modernisation pays off the most.

ObjectMaturity ScoreFieldsFlowsTop Findings
Case381422712
Opportunity4498198
Commission_Payment__c5176146
Subscription__c5763115
Invoice__c624583

Want 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