Every other platform lets you
find the ceiling the hard way.
Salesforce publishes it.
Governor limits are not an inconvenience — they are the design brief. Our developers start with the org health report, not the backlog, and they stay on the Virtus payroll while they work inside your team.
Six meters, and what each one is really telling you
A real org, five years old, roughly 400 users. Nothing here is unusual — and none of it appears on a roadmap until something breaks during a quarter-end close.
We run this in the first week of any Salesforce engagement, and we will run it for you before you hire anyone.
Apex CPU time, worst transaction
9,100 / 10,000 msOne trigger doing a callout-shaped amount of work synchronously. Move it to a queueable and the number halves.
SOQL queries, worst transaction
78 / 100A query inside a loop, three levels down in a helper class. Classic, and a ten-minute fix once someone looks.
Apex test coverage
76%Above the deployment gate, which is not the same as tested. Half the assertions are System.assert(true).
Daily API calls
412k / 1MHealthy — but two integrations poll rather than subscribe, so it grows with data volume rather than usage.
Data storage
68%Eleven years of closed activity records. Archive policy is a one-week project that buys back years.
Flows per object
14 on OpportunityOrder of execution becomes unpredictable. Consolidate to one record-triggered flow per object, per timing.
Six things they do once the meters are green
Apex that respects the limits
Bulkified triggers, one handler per object, queueables and batch jobs for anything heavy, and tests with real assertions.
Lightning Web Components
Reusable, tested with Jest, and using the platform's data services rather than an Apex call for every field.
Flow versus code, decided properly
Flow for the things admins should own, Apex for the things they should not. Written down so the boundary survives staff turnover.
Integrations
Platform Events and Change Data Capture instead of polling, named credentials instead of hard-coded endpoints, and a retry story.
Deployment that is not a spreadsheet
Source-tracked orgs, SFDX, scratch orgs and a CI pipeline — not change sets assembled by hand at 6pm on a Friday.
Data model discipline
Because the record type someone added in 2019 is why your reports disagree, and nobody has been allowed to remove it.
Three bands
Certifications tell you someone passed a multiple-choice exam. We interview on the org health report instead — it separates the two groups in about fifteen minutes.
Mid-level
3–5 yrs$35–45/hrBuilds LWCs, flows and Apex against an agreed design. Comfortable in the platform, still learning the limits.
Senior
5–8 yrs$45–56/hrOwns the org's technical health. Refactors triggers, sets the flow/code boundary, runs the deployment pipeline.
Architect
8+ yrs$56–75/hrData model, integration architecture and the multi-org strategy. Usually part-time alongside a delivery team.
Give us a read-only user for two days
We will return your own version of the report above, with the three fixes that would buy back the most headroom. No charge, no obligation.