01
Start high level
We begin with a description of the work, not your records. Redacted or generalized examples are usually enough.
Trust and privacy
Start with the workflow, not the sensitive records.
A high-level description is enough to find a useful starting point. Before anything is connected, we agree on what is needed, who can access it, which tools can process it, and when it is removed.
FIRST-CALL BOUNDARY
A description of the problem is enough.
No customer records, patient details, case files, financial data, or credentials.
Request a mutual NDA01 / THE SHORT VERSIONFOUR WORKING RULES
The short version.
02
Agree before access
Client information supports only the agreed Audit or build. It is not authorized for unrelated training or secondary use.
03
Keep a person in charge
Your team approves the sources, rules, important outputs, and the points where a person must review or take over.
04
Own the outcome
Your source material stays yours. The agreement defines ownership, handoff, access removal, and deletion.
02 / WHAT TO SHARETHREE CLEAR BOUNDARIES
What can I share?
Use this simple rule: start with the process, then add only what the agreed work needs.
Intro call
Share the process, not the records
Talk about roles, repeated work, delays, handoffs, software, and the outcome you want.
After an NDA or signed scope
Share only what the work needs
Use approved SOPs, scripts, pricing, templates, and operational details. Redact anything outside the agreed scope.
Only after written approval
Keep sensitive records out
Customer, patient, case, employee, financial, credential, health, and other regulated information requires approved tools, permissions, and terms.
03 / BUILD CONTROLDECIDE BEFORE CONNECTING
Before a build, you approve four things.
The minimum information needed and what it will be used for
The people, access levels, tools, and providers involved
The outputs or actions that always require human review
The retention, handoff, access-removal, and deletion plan
04 / AGREEMENTSRIGHT DOCUMENT / RIGHT TIME
The right agreement at the right time.
Before the free call
Mutual NDA, when requested
Keep the intro call high level, or request a mutual NDA before discussing confidential operations.
Before the paid Audit
Audit scope and confidentiality
The written scope covers fees, permitted information, confidentiality, ownership, and retention.
Before a build
Service and data-handling terms
The build agreement records scope, ownership, tools, access, review points, retention, and deletion.
Before regulated data
Required addenda
A BAA, DPA, or other applicable terms must be completed before the relevant regulated information is introduced.
Talk through the work without exposing the records.
Describe the operational friction at a high level. If confidential detail is necessary, request a mutual NDA before the call.