Understanding your business shouldn’t mean collecting more information than the work requires.
Our approach starts with agreeing on the data, tools, and access needed for your project. The safeguards for an engagement should be documented before client records are shared or systems are connected.
Start by identifying what information the project involves, where it currently lives, and who is authorized to use it. Confidentiality requirements, approved services, and any restrictions on copying or sharing belong in the project scope.
The preferred approach is to work within client-owned systems using named accounts and limited permissions. Where copies are necessary, their purpose, storage location, and access should be agreed in advance. Account access, multifactor authentication, and secure credential exchange are part of that discussion—not something to handle through an inquiry form.
Before introducing a connected service or AI-assisted workflow, identify what information it will receive, the provider’s data practices, and where human review is needed. Confidential information should not be entered into a new tool simply because the tool is available.
Agree on what will be handed back, which permissions will be removed, and whether any working copies need to be retained or deleted. Retention periods and handling requirements depend on the engagement and belong in its written agreement.
The form asks for your name, email address, and a description of your concern. Your business name, desired outcome, and current tools are optional.
Your submission is sent over HTTPS to FormSubmit and forwarded to our Microsoft Outlook inbox so we can respond. This website is not a secure client-document portal and does not accept file uploads.
Please don’t include passwords, access tokens, payment-card details, medical records, or confidential customer files. Describe the issue in general terms; project information can be discussed separately.
HTTPS protects the connection in transit. It does not mean that an inquiry is end-to-end encrypted. FormSubmit and Microsoft process information under their respective policies.
FormSubmit privacy information · Microsoft privacy statement
Ask about data handling before sharing client information. This page outlines our approach; it is not a certification or a substitute for a project-specific agreement.
