What compliance, legal and IT get before anyone touches a live system.
Headlines do not work on this audience. Documents do. Here is how access, environments, releases and paperwork work on every engagement, so your review can start before the first call.
What compliance, legal, IT and your admin get from us.
Four people usually have a veto. Each gets a different document, and all of them exist before the first change is proposed.
One sheet you can show at an examination
- Who approves each change
- What is stored, and where
- Who has access, by name
- A change log per release
An NDA before any data is seen
- Data-handling terms in writing
- Security questionnaire answered in five business days
- Continuity plan: backup power, connectivity, handover
Read-only first. Then governed releases.
- Named individuals, least privilege
- DEV, QA and UAT environments
- A rollback path on every release
- No lock-in: the org stays readable by anyone
We do not replace you. We clear the queue.
- You stay the owner of the org
- The backlog you never get to, worked through
- Documentation you keep after us
Read-only first. Named people. Least privilege.
Access lives in your Salesforce, under your admin's control. Nobody on our side shares a login.
- 01
Health Check: read-only, five days
One read-only user, created by your admin, used by the named lead engineer. Nothing in the org changes. The user is deactivated when the report is delivered.
- 02
Projects: named individuals, least privilege
Each person on the proposal gets their own user with the permissions the work needs and nothing more. Your admin can see who has what, and revoke it, without asking us.
- 03
Data stays in your org
We work inside your Salesforce and the systems you connect to it. Exports, if any, are agreed in writing first. Test environments use masked or synthetic data unless you approve otherwise.
Every change tested, approved, logged and reversible.
Development, test and user-acceptance environments; a release window you choose; a rollback path tested before go-live; a change record your compliance officer can file.
The record on the right is the format every client keeps. Thirteen changes to GoodLeap's live lending system, none caused an incident.
Nightly loan-org sync moved to a scheduled job
- Requested by
- Head of Lending OperationsTransfers failed silently twice a month; found in the morning
- Built by
- Lead engineer, named in the proposalSame two people since release 1
- Tested in
- A full copy of the system, then by the usersTest script signed by the operations lead
- Approved by
- Compliance ✓ IT ✓ Business owner ✓
- Release window
- Friday, 02:00–06:00 ETRollback tested: 20 minutes, no data loss
- Result
- No incidents. Thirteenth change to the live system. None of the thirteen caused one.
What we send for a legal or security review.
Within five business days of the request, in writing.
Company and people
- Registration documents of the contracting entity
- NDA signed by every team member
- Named team list with roles
- Liability statement
Data and access
- Data-access scheme: who sees what, where
- Data-handling terms in writing
- Security questionnaire answers
- Access log on request
Continuity
- Continuity plan: backup power, connectivity, handover
- Change log per release
- Documentation you keep after us
- Rollback procedure, tested
We do not claim certifications we do not hold. If your review requires a specific attestation, ask on the first call and we will say yes, no, or by when.
Questions from legal and IT.
Do you sign US NDAs?
Who owns the work?
Which time zones do you cover?
How fast do you answer a security questionnaire?
Can our IT revoke access at any time?
What happens if a release goes wrong?
Make your Salesforce earn.
Thirty minutes, one hypothesis about your business, no pitch. We reply within one business day.
One reply from a person, within one business day.