The Contact Protocol
SETI's principles for first contact: confirm a signal before announcing it, and don't reply until a careful response has been agreed. We treat your Salesforce the same way.
Listen
We learn your world before touching anything: your team, your process, what is broken and what it costs you.
Verify
We read before we write: the objects, the automations, the records a change will touch. Your setup is backed up in version control.
Respond
We change things the safe way: prototypes for big changes, dry runs, data in stages, pilot releases before everyone.
Stay in contact
Plain-language updates, a dated work log, handoff documents and illustrated guides for your users.
Listen
We understand your world before touching anything: your team, your process, what's broken and what it costs you.
Verify
We read before we write. We describe the objects, read the automations, and count the records a change will touch. Every one of your automations and settings is backed up in version control, and checked at the start and end of every work session, so nothing changes unnoticed.
Respond
We change things the safe way:
- Prototype first for big changes, so you approve the logic before Salesforce changes
- Dry runs: tests that do the real work and then roll themselves back
- Data in stages: preview → 3-record test → the rest, with a backup before every change
- Scripted changes, never hand edits, each one with a backup and a written reason
- Pilot releases to a small group before everyone
Stay in contact
Plain-language updates for your team, a dated work log, handoff documentation, and illustrated guides for your users. When something goes wrong, we find the cause from the data, fix it, and write the rule that stops it happening again.
Proof, from our flight logs
- 0 failed records across every data load
- 115,000+ and 55,000+ history records rebuilt from Salesforce's own audit trail
- 60+ automations under version control, each checked to be the version actually running
Start with a 30-minute call
Tell us what's slowing your team down. You'll get an honest read on what to fix first, even if the answer is that you don't need us.