Assisted drafting
Test Copilot for preparing drafts from a clear brief, then have a person check facts, tone and commitments before using the content with a client or including it in a business document.
Microsoft Copilot
Microsoft Copilot for SMEs: choose a first use case, check licences and document permissions, train your teams and evaluate the quality of the results they obtain.
Suitable tools. Local support. A team close to you.
Geneva
Lausanne
Fribourg
Neuchâtel
Valais

Copilot can be considered for preparing a draft, summarising information or helping find relevant work material. For an SME in French-speaking Switzerland, a first project benefits from a recurring task whose output can be checked.
Define the documents involved, who reviews the response and what would count as a useful improvement. Our approach to artificial intelligence in business can help scope the pilot. The aim is to test a use case in your environment, without announcing productivity gains before they have been observed.
Test Copilot for preparing drafts from a clear brief, then have a person check facts, tone and commitments before using the content with a client or including it in a business document.
Evaluate Copilot on summaries of authorised documents, compare the result with the original information and record omissions or errors to measure the verification work required before relying on that particular use.
Try Copilot for finding work information within the available scope, using current documents with identified owners, then check sources and answers with the users who need that information for their day to day tasks.
Check the applications accessible through the proposed Copilot offering and the data involved, then select a recurring task to test in your environment before assuming that demonstrated functions suit every employee and workflow.
Review Copilot agents and their connections to other services separately, check requested permissions and applicable terms, and identify uses that may involve consumption billing before introducing them into an authorised business workflow.
Train Copilot users to examine sources and reject a doubtful answer, then measure the quality achieved and the time needed for review before deciding whether to expand the rollout to additional employees.
From initial scoping to ongoing support, the agreed work and each party’s responsibilities are defined with you before implementation.
Prepare data, accounts and cutover stages, with testing and a rollback plan.
Configure tools and integrate them into your environment within the agreed scope.
Define permissions, available protections and useful checks.
Clarify workspaces, responsibilities, sharing rules and team practices.
Check data protection needs and prepare recovery procedures.
Support adoption and agree ongoing assistance suited to your employees.
We start with your teams’ needs, business applications and organisational constraints.

Share client files between colleagues, with appropriate access and documents that are easy to find.

Protect patient records and maintain the tools needed for consultations.

Find plans and files on site while keeping control of access for everyone involved.

Organise access for employees, elected representatives and volunteers, and make handovers easier when teams change.
Tools alone are not enough. Ongoing management, access and documentation need to remain clear over time.
Roles, permissions and protections suited to the agreed scope.
Identified dependencies, with backup and recovery arrangements to prepare.
Documented joiners, leavers and changes in responsibility.
Accessible configuration, licence and upcoming renewal records.
Uses, limitations and frequently asked questions: the points to clarify when preparing your project.
The current Microsoft Copilot overview distinguishes experiences by data grounding, application integration and licensing. The names Microsoft 365 Copilot and Microsoft 365 Copilot Chat may still appear during the transition to Microsoft Copilot and Microsoft Copilot Chat.
This page concerns business use. Before purchasing, check the exact offering, account used, available applications and any consumption-based charges. A demonstration does not prove that every feature shown will be available in your environment or to every employee. Confirm the capabilities needed for the chosen pilot rather than relying on the product name.
A Copilot project should include a review of access to work information. According to Microsoft's privacy documentation, responses operate within the user's permissions. Overly broad access therefore remains a problem to address beforehand.
Review the relevant SharePoint spaces, outdated documents and external sharing. Start with a limited collection, named owners and guidance on permitted information. Agents and connections to other services need a separate review of permissions and terms. Keep that review tied to the actual pilot, rather than granting wide access in anticipation of possible future uses.
Use representative situations in the pilot and define criteria before testing. Record response quality, the time needed for checking, errors encountered and tasks that remain simpler without assistance.
Training should show people how to frame a request, inspect sources and reject an uncertain answer. Sunitech can scope workshops, tests and a review of findings; wider deployment then depends on results and priorities. IT governance defines who approves use cases, monitors licences and updates internal rules. Include examples that did not work, so the decision reflects limitations as well as successful demonstrations.
It should not be treated as a way to bypass permissions. However, where an employee already has overly broad access, assistance can make that information easier to discover. Checking groups, links and ownership remains essential. Testing with several user profiles helps examine the boundaries of the selected scope and identify access that needs correction.
For the relevant business services, Microsoft states that prompts, responses and data accessed through Microsoft Graph are not used to train foundation models. Still check the experience in use and the terms of additional agents or services. This does not remove the need to define permitted data and control access.
Generated output may contain errors, omissions or an unsuitable interpretation. A person should validate facts and context before using it in customer communications, commercial commitments or sensitive documents. Measure that checking effort during the pilot: a fast answer is useful only when reviewing it remains practical for the task and its consequences.
Review of your needs, comparison of options and clearly explained priorities.
Preparation, configuration, testing and coordination with the relevant providers.
Agreed support scope, documentation, licences and next steps.
A project? A question?
An initial conversation to understand your situation and decide on the next steps together.
Contact us