Your Salesforce health check — and the reckoning after it

The ten core areas — every org, every time

Every criterion is rated Good Standing, Improvement Opportunity, or Requires Attention — the same color-coded rubric as our DocGen assessment — so the report reads as a prioritized to-do list, not an essay.

How the engagement runs

1. Week 1 — Discovery. Kickoff, stakeholder interviews (admin, architect, business owners, executive sponsor), and access setup. We learn how the org is supposed to work before judging how it does.
2. Weeks 1–2 — Automated + manual review. The Horus Eye baseline — 90 rules, 7 dimensions, dependency graphs, coverage honesty — plus the part no scan can do: reading your business processes against the configuration, interviewing stakeholders, and weighing governance and cost. Tactical findings and architectural ones.
3. Week 2–3 — Deep dives. Cloud-specific assessment areas (below), governance and release-management review, and a licensing/cost pass most assessments skip.
4. Week 3 — Report & readout. A written, color-coded report: findings, ratings, effort estimates, and a sequenced 90-day/12-month remediation roadmap. Presented live to your team; yours to keep, whoever does the work.

Smaller org? The two-week Health Check

Same rubric, narrower depth, fixed price: a certified architect audits security, technical debt, automation, and data quality in two weeks and hands you the prioritized roadmap. It upgrades to the full assessment any time.

Quote-to-cash breaks quietly: a discount that vanishes between systems, a bundle nobody can quote, a renewal co-termed by hand at midnight. We assess the catalog, the rules, and the process they're supposed to serve — and whether legacy CPQ is ready for the ARM migration on Salesforce's roadmap.

Sound familiar?

• Quotes take days, not minutes — Reps route around CPQ with spreadsheets; deal desk is a bottleneck with a backlog.
• The catalog reads like the ERP — Thousands of SKUs replicated wholesale instead of modeled for how deals are actually sold.
• Rules nobody dares touch — Price rules and product rules stacked over years; changing one breaks three quotes at month-end.
• Finance reconciles by hand — What was quoted, ordered, and billed live in three systems that almost agree.

The findings we see most

Related: Agentforce Revenue Management · CPQ → RCA migration offer · our quote-to-cash practice (Cummins, ATCO, MongoDB, Palo Alto Networks).

Industry research says almost half of field appointments don't go as planned. Most of the causes live in configuration: territories drawn wrong, durations guessed at go-live and never corrected, an optimization engine nobody trusts because nobody tuned it. We assess all of it — before you put agents on top.

Sound familiar?

• Dispatchers override everything — The schedule the engine builds gets rebuilt by hand every morning — so why run the engine?
• Technicians arrive blind — No asset history, no parts context; first-time-fix rate says so.
• The mobile app is optional — Techs call in updates; admin staff re-key them; data quality decays from the field inward.
• Every day has holes — Cancellations and early finishes leave gaps nobody fills until tomorrow.

The findings we see most

Related: Agentforce Field Service · our Field Service practice — including a 12-month energy-sector program whose UAT packages the client called the best they'd received.

Service orgs accumulate debt faster than any other cloud — every escalation spawns a status, every reorg a queue, every tool a channel. We assess the case lifecycle end to end, and score whether your knowledge and data could actually ground an AI agent.

Sound familiar?

• Cases bounce between queues — Routing logic from three reorgs ago; agents cherry-pick; the oldest cases are the least loved.
• Knowledge exists but nobody uses it — Articles stale, search unhelpful, agents keep answers in personal docs.
• SLAs are aspirational — Entitlements configured once, milestones ignored, breaches discovered in QBRs.
• Handle time climbs anyway — More macros, more tabs, more tools — and somehow slower resolution.

The findings we see most

Related: Agentforce Service · the customer service agent, explained · our Service Cloud practice (certified since 2019).

Salesforce Security has publicly warned about threat actors mass-scanning Experience Cloud sites for over-permissive guest access — a configuration problem, not a platform one. If you run a portal or public site, this is the assessment with the shortest path from finding to 'fix it today.'

Sound familiar?

• Nobody has reviewed guest access since launch — The guest profile was opened up to make something work in UAT; it stayed open.
• Sharing model is folklore — Why external users see what they see is explained by 'it's always been like that.'
• The portal is slow — Components stacked without performance budgets; every page loads everything.
• License costs surprise everyone — Member-based versus login-based chosen years ago, never revisited against actual usage.

The findings we see most

Related: our Experience Cloud practice · the security pass follows Salesforce's published guest-user guidance and current threat-research patterns.

Nonprofit orgs carry a special kind of debt: built by volunteers and rotating admins, customized around every campaign, and now facing the NPSP-to-Nonprofit-Cloud question. We assess what you have, what it costs you, and what the migration decision actually looks like for your data — the practice behind our NAACP award-winning delivery.

Sound familiar?

• Donors exist three times — Same constituent, three records, three giving histories — and a development officer merging by hand.
• Reports take a specialist — Answering 'how much did we raise from this campaign' crosses four objects and two workarounds.
• Gift entry is a bottleneck — Batch entry slow, recurring donations fragile, finance reconciliation manual.
• Everyone asks about Nonprofit Cloud — The board read an article; nobody can say what migrating would actually take.

The findings we see most

Related: our Nonprofit practice — including the NAACP program that won the 2022 Nintex Solution Innovation Award · DocGen for acknowledgment letters and grant documents.

Higher-ed orgs are where data models go to be tested: every student is a person, an applicant, an enrollee, an alum, and sometimes an employee — simultaneously. We assess how your EDA or Education Cloud org holds up, with delivery experience at the University of British Columbia behind the checklist.

Sound familiar?

• Students exist in duplicate — Recruiting created one record, the SIS integration another, an event signup a third.
• The SIS sync is a nightly adventure — Banner/Colleague/Workday sync errors reviewed manually — when someone remembers.
• Advisors can't see the whole student — Program, term, and success data scattered; the 360 view requires six tabs.
• Access reviews scare everyone — FERPA-relevant data, and nobody can crisply say who can see what.

The findings we see most

Related: our Education practice — current Education/Sales Cloud architecture work at the University of British Columbia.

FSC orgs answer to two masters: advisors who need everything one click away, and regulators who need least privilege provable. Most orgs drift toward one at the other's expense. We assess both sides — the data model and the compliance posture — with financial-sector delivery from Shift4 to OTIP behind the checklist.

Sound familiar?

• Households don't match reality — Trusts, businesses, and multi-generational relationships flattened into whatever fit at go-live.
• Access reviews take weeks — Book-of-business sharing built from exceptions; proving least privilege is archaeology.
• KYC data ages in place — Refreshed at onboarding, then never; reviews run on stale facts.
• Advisors keep shadow books — The real client picture lives in a spreadsheet because the org's one is incomplete.

The findings we see most

Related: our Financial Services practice — delivery for Shift4 Payments, Big I New York, Alitis Investment Counsel, OTIP RAEO, and CSC Leasing.