They Hired Us to Move to Microsoft 365. Their Legal Team Had a Bigger Problem.

The tools you're already paying for, finally put to work.

A few years back, a mid-sized company brought us in to manage their migration from Google Workspace to Microsoft 365.

That was the stated project. But the actual engagement was bigger than a migration — and it was designed to be. They didn't just need someone to move their data and configure their tenant. They needed someone to audit each department, understand how their teams worked, identify where Microsoft 365 could improve their operations, and then build what needed building and train the people who needed training.

They knew they were moving to a new platform. What they didn't know was what was possible. That's why they brought in outside expertise — not just to move files, but to help them think through what a modern, well-configured Microsoft 365 environment could actually do for a business like theirs.

We run this kind of engagement regularly. Advise. Build. Train. We come in, we understand the operation, we design the right solution, we build it, and we make sure the team can use it. The migration was the context. The process review was the work.

The legal department is one of several success stories from that engagement — and the one that ended up touching the most people in the company.

The First Problem: NDAs Were Eating the Team Alive

The legal department was four people. Small team, serious workload. One of the first things that surfaced in our audit was a volume problem that had nothing to do with the complexity of their work — it was about the mechanics of how requests reached them.

The sales team was growing. Every new deal started with an NDA — that's the first step before any real conversation happens. When a sales rep needed one, they sent an email to legal. Can you draft an NDA for this prospect? That email went into the same inbox the attorneys used for everything else. Vendor negotiations, contract reviews, internal policy work, compliance questions — all of it competing with a steady stream of templated NDA requests from sales.

The attorneys weren't doing complex work on these NDAs. They were filling in names and sending standard agreements. But the requests were unpredictable, the volume was high, and each one interrupted real work. A sales rep might wait a day or more to get a standard NDA back — not because the work was hard, but because it was buried in a queue with everything else that needed the legal team's attention. Real work — the negotiations and reviews that actually required legal expertise — kept getting pushed aside for something that shouldn't have needed legal involvement at all.

We fixed that first. We built a self-service NDA process — a form that sales reps filled out themselves, connected to an automated workflow that pulled the right template, populated the standard fields, and delivered a ready-to-send NDA directly to the rep's inbox. The whole thing ran in under 60 seconds from form submission. What had previously taken the legal team a day or more to turn around was now in the sales rep's hands before they'd finished their next call. A copy was automatically stored in the legal team's SharePoint NDA library — organized, searchable, and out of anyone's inbox. The legal team reviewed the templates once. After that, sales handled the rest.

That took a few days to build. The attorneys noticed the difference within the first week.

The Second Problem: The One Nobody Had Named Yet

After the NDA fix landed, the lead counsel said something I hear a lot when a quick win builds trust in the engagement.

"What else can you do?"

That's the question that opens the real conversation. And my answer is always the same.

Tell me about your day.

Not "what are your pain points." Not "what would you like to improve." Those questions get surface answers. Walk me through your day — what you do first, what you look at, who you talk to, what takes longer than it should — and the real friction shows up on its own.

She walked me through it. About ten minutes in, the problem was sitting right there.

Their entire matter management operation ran on a shared spreadsheet. Every open contract, every active revision cycle, every vendor agreement in negotiation — one row per matter. Everyone on the team touched it. Nobody fully trusted it.

The spreadsheet wasn't disorganized. It was the wrong tool for the job — and it had been the wrong tool for a while.

What the Spreadsheet Couldn't See

Most of their contract work involved third-party paper. A vendor sends their standard agreement. Legal reviews it, marks it up, sends it back. The vendor revises and returns. Legal reviews again. This cycle — review, redline, return, wait — might go three or four rounds before anything is final. Each round could take days.

Here's what the spreadsheet couldn't show: whether a matter was in someone's hands or waiting on the other party.

When a contract was sitting with a counterparty waiting for a response, the attorney who'd last touched it still showed an open matter in her name. To anyone looking at the spreadsheet and trying to route incoming work, she looked fully loaded. She might have been completely free.

The reverse was also true. An attorney buried in active work looked the same in the spreadsheet as one who was waiting on several counterparties to respond. You couldn't tell the difference between someone at capacity and someone with nothing to do — because the spreadsheet had no concept of where a matter was in its cycle. It knew a matter existed. It didn't know whether it was in someone's hands or sitting in someone else's inbox two time zones away.

The result was chronic misallocation. Urgent work routed to people who were swamped. Available capacity invisible. Attorneys asking each other by email who had what and where things stood. The lead counsel knew the system was broken. She just hadn't had a name for the specific mechanism that was causing it — or a path to something better. The company had invested in Microsoft 365, and she now had a new set of tools in her toolbox. She just didn't yet know what was in it.

The volume had grown past what the spreadsheet could hold. It was a slow collapse rather than a single catastrophic failure, but it was collapsing.

What We Built

We built them a full matter management system inside Microsoft Dataverse — which sits inside the same Microsoft 365 tenant they'd just migrated to, at no additional platform cost.

The center of it is a model-driven app. When you open a new matter, you select the matter type — vendor agreement, service contract, lawsuit, or whatever category applies — and the system generates a complete task set automatically. The right tasks for that specific type of matter, assigned to the right owner, with an expected schedule built from the start. NDAs were handled separately by the automation we'd already built; those never needed to enter the matter management system at all. Everything else did.

Planner Premium handles the task layer. Opening a matter in the app generates the corresponding Planner tasks with it — owner assigned, timeline set, stages defined. As the matter moves through the cycle, the status updates. When it goes to a counterparty, it's marked as waiting. That status is visible to everyone, in real time. The difference between active work and waiting work — the thing the spreadsheet could never surface — became a column in a dashboard.

Every team member sees the same live view. Open matters, current stage, who owns what, when responses are expected back. The lead counsel can see at a glance who is genuinely loaded and who has capacity, because the system knows the difference.

Power BI reporting sits on top. Matter count by type, cycle time by matter type, pipeline by expected close date, workload distribution across the team. The kind of visibility that used to require a weekly status meeting to approximate — now available any time, without asking anyone for an update.

The last phase was training. We didn't hand them a system and walk away. We made sure the team understood not just how to use what we'd built, but why it was designed the way it was — so they could maintain it, adapt it, and extend it as their needs changed.

The Engagement Model in Practice

I want to name what happened here, because it's the same pattern that runs through every engagement where we have the space to do the full job.

We were hired for a migration. That was real work and we did it. But a migration is a platform change, not an operational improvement. The operational improvement — the NDA bottleneck fix, the matter management system, the training that followed — came from the audit work that ran alongside the technical implementation.

The lead counsel knew she had a problem. She knew the spreadsheet wasn't working. What she didn't have was a clear picture of the specific mechanism that was breaking it, or a path to something better built on tools the company had already invested in.

That's the gap we fill. Microsoft builds for everyone, which means they finish for no one. The platform ships with extraordinary capability and almost no guidance on how to configure it for a four-person legal department managing third-party paper cycles. The last mile — the design, the build, the training — is where the investment in Microsoft 365 either pays off or sits idle.

Most of the time, the tools to fix the problem are already there. The question is whether anyone has taken the time to ask the right questions and build the right thing with them.

Frequently Asked Questions

Our legal team is two or three people. Is something like this too complex for a small operation?

The visibility problem doesn't care how small the team is. Two attorneys tracking fifteen active matters in a spreadsheet have the same fundamental issue — no real-time status on what's waiting versus what's active, no automatic task generation when a matter opens. A simpler matter management system is still a matter management system. The build scales down. The impact doesn't.

Is Dataverse included in our Microsoft 365 subscription?

It depends on your license. Microsoft 365 Business plans don't include Dataverse by default, but Power Apps per-user or per-app licenses do, and some enterprise plans include it. If you're not sure what's available in your subscription, that's worth checking before assuming it's out of reach. It's often closer than people expect.

We already have a legal software platform. When would Dataverse make more sense?

When what you need doesn't match what the platform was built for. Off-the-shelf legal software is designed around assumptions about how legal departments work — assumptions that may not match your specific operation. Dataverse lets you build exactly what your team needs, inside the Microsoft 365 environment your organization already uses. For a small internal legal department managing a specific mix of matter types, that precision is often worth more than a feature-heavy platform designed for a law firm.

The legal department still runs on the system we built. The lead counsel manages it herself. The NDA requests don't land in anyone's inbox anymore. The team knows who has what and where it stands without asking.

We came in to run a migration. But this is what we were actually hired to do.

J. Scott Clark is the President and CEO of The 365 Collective, Inc., a Microsoft 365 consulting and training firm serving small and mid-sized businesses across healthcare, finance, construction, engineering, publishing, and retail.