Case studies/Embedded Outlook CRM
Property and professional services
A bespoke CRM built inside Outlook
Before Copilot summaries or an intake agent can be trusted, the client data underneath has to be clean. The design gives the firm a single SharePoint backbone first, surfaced in Outlook where the team already works.
Workflow illustration
One email, one client record
- 01 An email is open
- 02 The client record beside it
- 03 A note added in place
- 04 Saved to one list
- Starts with
- An open email and the client's SharePoint record.
- Leaves you with
- Notes and activity saved from the inbox to the same record.
The team stays in control
Fee earners add the notes. Administrators manage the shared records through Power Apps.
Illustration of the workflow described in this case study.
Client and matter data centralised on SharePoint lists rather than scattered spreadsheets.
Power Apps gave administrators a clean management interface without a heavy custom build.
A bespoke Outlook add-in put records, notes and activity beside the emails staff already had open.
Licensing cost a fraction of an off-the-shelf CRM at the same user count.
Case study
Situation
The team was managing client and matter information across spreadsheets, mailboxes and a generic CRM nobody enjoyed using. Data was duplicated between systems, contact history was lost in inboxes and meaningful reporting was effectively impossible.
The work the team did all day still happened in Outlook. The CRM sat alongside it as a separate tab people opened reluctantly, if at all.
Case study
Challenge
Switching to a different off-the-shelf CRM would have meant another change programme and another per-user licence bill, with no guarantee the team would use the new tool any more than the last one.
The real issue was not which CRM the firm had bought. It was where client information was being touched. As long as the system of record sat outside the inbox, staff would keep working out of email and the CRM would keep drifting out of date.
Case study
What the firm needed to avoid
The brief deliberately stayed away from a like-for-like CRM replacement. The aim was to put the client record in front of the user at the moment they needed it, with as little new behaviour to learn as possible.
- Yet another standalone app for staff to remember to open.
- Per-user licence costs that scaled badly across the firm.
- A second source of truth running in parallel with the inbox.
- An IT-heavy admin burden for routine updates.
- A migration that tried to clean every record before anything went live.
Case study
What changed
SharePoint lists became the data layer. They were already familiar, already governed by the firm's Microsoft 365 tenant and capable of holding the client, matter and activity records the team needed.
Power Apps sat on top as a management interface for administrators who needed to add, edit and report on records in bulk. The custom build stayed light because Power Apps did the heavy lifting.
A bespoke Outlook add-in surfaced the same records inside the email pane. When a fee earner opened an email from a client, the client record, recent activity and matter status appeared next to the message. Notes and calls could be logged without leaving Outlook.
Case study
Adoption
There was no new app to learn. The CRM appeared where the work already happened. Training was closer to a five-minute walkthrough than a programme.
Administrators got Power Apps. Fee earners got Outlook. The data sat in SharePoint underneath both, with the same permissions model the firm already understood.
Case study
Outcome
The firm ended up with a single source of truth for client data, faster onboarding for new staff, and a licensing model that cost a fraction of an off-the-shelf CRM at comparable user counts.
Reporting was possible for the first time. Contact history stopped getting lost in inboxes. The CRM stopped being something the team avoided.
What appeared inside Outlook
Client records, notes and activity next to the email already open.
Client record beside the email
Opening a message from a client surfaced the matching record, recent activity and current matter status in the same view.
Notes and calls from the inbox
Logging a note, a call or an update happened in the email pane rather than in a separate CRM tab.
Matter status updates
Fee earners could move a matter forward against the record without context-switching.
Contact tagging and triage
Inbound enquiries were tagged against accounts and routed without manual reconciliation.
Administrator management view
Power Apps gave administrators a clean editing interface for bulk updates, merges and corrections.
Reporting against a real backbone
SharePoint as the data layer meant reporting on activity, pipeline and matter throughput was finally possible.
Where Copilot fits next
Useful once the data layer is reliable.
With a clean SharePoint backbone in place, Copilot, agents and document automation became sensible later additions rather than the starting point.
Copilot summarisation against matter notes
With a reliable record of activity, Copilot can summarise the history of a matter or contact for a fee earner picking it up cold.
Intake agent
A focused agent can collect missing information from new enquiries and prepare a handover against the same SharePoint records.
Document automation
Letters, quotes and standard documents can be generated from matter records rather than redrafted by hand.
Power BI reporting
The SharePoint backbone supports a reporting layer for partners without exporting to spreadsheets.
What the firm learned
Adoption gets easier when the CRM stops looking like a separate app.
- Where data lives matters less than where staff actually touch it.
- An Outlook add-in lowers the cost of adoption more than any training session can.
- SharePoint lists scale a long way when treated as a real data layer rather than a notes pad.
- Custom does not have to mean expensive when Power Apps handles the management interface.
- Per-user CRM licensing is the wrong shape for a lot of professional services firms.
Sensible next moves
Layer Copilot and automation on top of the same backbone.
- Next Layer Copilot summaries against matter history and notes.
- Next Add a narrow intake agent for new client enquiries.
- Next Extend document automation against the same backbone.
- Next Build a reporting view for partners and office leads.
Related routes
Where this example connects to FiveForward services.
Power Automate consultancy
Designing, building and stabilising workflows that the business can understand and maintain after launch.
SharePoint workflow automation
SharePoint lists, libraries and workflows kept tidy enough that agents grounded in them return trustworthy answers.
Microsoft Copilot agents
Where agents fit once the underlying records and workflows have a clear owner.
Next step
Get the client record clean, then give an agent something to ground in.
Talk through where client data sits today, where staff actually work and whether an intake or matter-summary agent in your own tenant needs a SharePoint backbone built first.