How we approach your systems and data
We treat your information, and how it moves through a workflow, as part of the design. We agree the tools, access, safeguards and responsibilities with you before anything is built. The specific terms are set out in the MSA and SOW for each engagement.
The short version
Information is part of the design
What a workflow touches, how sensitive it is and who should see it shape the design from the first conversation.
Tools and access are agreed first
Which tools are used, where they run and who can access what are agreed with you before implementation.
People stay accountable
AI drafts, checks and summarizes. A named person on your side decides, and review steps are part of the first version.
Privacy and client information
By default, client information stays in the client's own systems and licensed tools. MSL's own AI tools work on de-identified or synthetic material. Anything else is agreed in writing first.
We work with the information the job needs, and we prefer to look at systems and documents with your people rather than take copies. Whether any AI service may process your information, and with what safeguards, is your decision, agreed before implementation. Prototypes can run on sample or synthetic data.
Choosing tools
We are stack neutral. No vendor pays us. We recommend what fits your systems, skills and policies, including buying or configuring an existing product over building one.
Many operations run on Microsoft 365. We are fluent in that stack, from SharePoint and the Power Platform to Copilot, and build inside it when it is the best fit. We are not captive to it: when a licence you already pay for covers the job, we'll say so, and when it doesn't, we'll say that too.
Your reviewers
Your security and privacy reviews are part of the plan, not a hurdle at the end. We describe the data flows and access for your reviewers, and build to what they approve.
Review, evaluation and monitoring
A named person owns every decision the workflow supports, and review steps ship in the first version. Before a pilot goes live, it is checked against criteria and an evaluation set agreed with you; monitoring and a way to switch it off are planned as part of going live.
The production readiness checklistHandoff
Someone on your side owns the workflow in day-to-day use. We plan the handover with them, and agree any ongoing support in the scope.
Where the terms live
The specific obligations, from confidentiality and data handling to ownership, fees and payment, are agreed for each engagement and set out in its MSA and SOW, not on this page.