Salesforce consulting and managed services in Providence.

Either works. Some clients keep the internal admin for user support and password resets and send development, integration and release work to us. Others hand over the whole queue and let the admin move to other priorities. We agree the split in writing, share one ticket tracker, and review the arrangement after the first few months to see whether it still fits the workload.

Before every upgrade, a refreshed sandbox gets the preview version, and we rerun the processes your compliance and operations teams depend on, such as case routing, approval steps and field history. Where behavior shifts, we correct it or write it up before your production org moves to the new version. You receive a short summary listing what changed for users and what, if anything, needs a training note.

We start with a documented inventory: objects and fields in use, automation by type, integrations and their credentials, installed packages, and profiles and permission sets. Conversations with the current admin and a few heavy users explain why things were built the way they were. Anything fragile or undocumented goes onto a risk list, reviewed with your business owner, before we change it. That groundwork keeps routine requests safe and shows where cleanup would reduce effort later.