Boring Future
Contact us
An open notebook and a glass of water on a windowsill table, looking out to a bright sea

Give Copilot a useful job. And a clear boundary.

A licence does not make a workflow better. Start with the work people actually do, check what Copilot can reliably access, and run a small pilot that earns its place.

Start a free conversationSee how it runs

Pilot readiness

Before any licences

A task worth improving
Agreed first
Who can see what
Reviewed
A baseline
Measured before
Success
Time and quality
Illustrative example, not client data

It can only see what’s there. And everything your people can see.

Copilot answers from the files, mail and chats each person already has access to. That makes tidy permissions and findable content the real readiness work, and the part most worth getting right first.

Before you roll out, ask what should improve.

  • No agreed task. “Use AI more” is not a measurable business objective.
  • Untidy permissions. A helpful assistant should not expose documents users were never meant to access.
  • Unclear evidence. Usage statistics alone do not tell you whether good time came back.

Where it helps

Three parts of a Copilot rollout.

Readiness

Overshared sites, old teams and files everyone can open, found and fixed before Copilot surfaces them in an answer.

Adoption that sticks

Training built around your team’s actual tasks, so Copilot becomes part of the week rather than a novelty.

Knowing its limits

Copilot drafts and summarises; it doesn’t run your process. We show where a Power Automate flow or a Copilot Studio agent should take over.

Start with one job, not a hundred licences.

Suggested pilot — not a claim of client deployment

  1. Choose a taskFor example, prepare meeting context
  2. Check accessContent, permissions and sensitivity
  3. Run the pilotA personHumans verify outputs and usefulness
  4. Measure adoptionQuality, time and repeatability

See it run: Tina sketches this workflow, step by step, and shows which parts a person keeps.

What we do

  • A readiness review: permissions, sharing, sensitivity labels and stale content
  • A pilot with the people and tasks most likely to benefit
  • Prompts and practices for your own work, not generic tips
  • A clear view of which tasks need more than Copilot, and what that would take
  • Measurement against the time the pilot was meant to save
  • A use-case shortlist, success measures and an adoption plan

What stays with your team

  • What gets sent, signed or decided
  • Checking what Copilot drafts
  • Who has access to what

AI prepares. People decide. Routine actions run only within limits you agree.

Usually built with

  • Copilot Studio
  • Microsoft 365
  • SharePoint & Lists

Technologies we work with. Product names and logos belong to their owners, who do not endorse Boring Future.

The evidence. Each with where it came from.

Related founder experience · not a Copilot rollout case study

Task first. Licence second.

Capability approach informed by adjacent work; no Microsoft 365 Copilot customer outcome claimed.

The same principle, proven in operational automation.

The problem
In previous operational work, the effort was collecting the right evidence before people could make a decision.
What was built
Designed automations that gather context from existing systems, retain business rules and leave uncertain or consequential steps to a person.
What changed
That experience informs our approach to Copilot pilots. We are not claiming a completed Microsoft 365 Copilot deployment or adoption result here.

What we’ll tell you straight

  • If the pilot doesn’t save a role any time, we’ll say so before you license the whole team.
  • Copilot won’t follow a multi-step process across your systems on its own. That’s a workflow.
  • Meeting notes are already in Teams with Copilot. If you have it, we’ll point you to it rather than build our own.

How it works

  1. Free conversationFree
  2. Discovery & Design£2,500 + VAT, fixed
  3. CompleteFixed scope and fee
  4. OperateOptional, monthly

Running a business of 5 to 50 people? Essentials starts with a £395 + VAT half-day session

Questions. Anything else, just ask.

Ask us directly
Is Copilot safe with confidential information?

Copilot works within your Microsoft 365 tenant and respects the permissions people already have. The risk is usually those permissions: if a sensitive file is shared too widely, Copilot can surface it. That’s why readiness comes first.

Can we start without a company-wide rollout?

Yes. A bounded pilot with the roles that write, summarise and search the most is often a better first move than broad deployment.

What’s the difference between Microsoft 365 Copilot and Copilot Studio?

Microsoft 365 Copilot helps individuals inside Word, Outlook, Teams and the rest. Copilot Studio builds agents for a specific job, connected to your own knowledge and systems. We do both.

How do you measure whether it worked?

Against a baseline: how long the target tasks took before the pilot and after, for the same people.

Can you guarantee Copilot will save us time?

No. We set a baseline, choose suitable tasks and measure whether it improves real work.

Will you review who can see our documents?

We include permission and information access in the readiness conversation, with the appropriate technical owner.

Ask Tina. Your answer will appear above, just like the other FAQs.

AI answers use our service information. Your question is sent to Anthropic; leave out personal or confidential details. Privacy

Where it’s used. Where to go next.

ServiceCopilot Studio agentsAgents with a job and a limit.ServiceDiscovery & Design£2,500 + VAT, fixed. Two to three weeks.ServicePower Platform & Power AutomateFlows and apps inside Microsoft 365.Services and pricingThe engagement path, with a price at every step.
Sunlit clouds in a blue sky

Buying Copilot is not the strategy. Finding the work is.

Start a free 30 to 45 minute conversation. No deck, no obligation.

Start a free conversation