Mini CRM Options on SharePoint or Dataverse for Teams
Global advertising and communications group
In short
What is the simplest way to build a small CRM on Power Platform?
A client list kept in spreadsheets has no history, no clear owner for each relationship and no shared view of who knows whom. A full CRM is too much for a team that needs a simple one. We compared three light options for a mini CRM, so the team could choose with the trade-offs in front of them.
Results in numbers
- model-driven build
- 13 hrs
- per canvas build
- 42 hrs
- shared tables
- 3
At a glance
- Three build options compared side by side
- Model-driven option built in about 13 hours
- Canvas options built in about 42 hours each
The client
The client is a global advertising and communications group with offices worldwide. The request was for a small internal tracker of clients and contacts for one team on Microsoft 365.
What it was costing them
- Scattered contacts: client and internal relationship details live in personal sheets and mailboxes.
- No single client view: addresses, client contacts and the colleague who owns each relationship sit in different places.
- Fragile reporting: lists are filtered and exported by hand, so they age quickly.
- Key-person risk: relationship knowledge leaves with the person.
- Wrong tool risk: a team can spend weeks on a custom app when a simpler option fits.
What we built
We built three options on the same data model: a canvas app on SharePoint, a canvas app on Dataverse for Teams and a model-driven app on Dataverse.
- One data model: Clients with up to 20 columns, plus Client contacts and internal contacts with up to 5 columns each.
- Option one, SharePoint: lists on a SharePoint site with a custom canvas app and no extra licence.
- Option two, Dataverse for Teams: the same canvas app on Dataverse tables inside Teams, with better structure for growth.
- Option three, model-driven: the fastest to build, with forms, views and Excel export from standard features, but it needs a premium licence.
- A client view on one screen: a form with four tabs, General info, Company addresses, Client contacts and internal contacts.
- Easy navigation: a top menu, a main client list with create and edit, and forms to add or remove contacts.
- Simple reporting: filters on the client list and an Excel export, built as a flow in the canvas options and out of the box in the model-driven one.
- Honest trade-offs: each option lists pros and cons, such as design freedom against build time and licence.
Results
- Built in about 42 hours for each canvas option and about 13 hours for the model-driven option.
- The data model has 3 tables and the client form has 4 tabs.
- Result: the model-driven option gave a working version in days, from about 13 hours of effort.
- Result: saved personal views and filters let each person keep a working list, replacing personal spreadsheets.
The risk most teams miss
At month three the mini CRM becomes the real CRM. The canvas options bring delegation limits, list permissions and an endless design debate, and Dataverse for Teams has its own limits on scale and security. The options compare these trade-offs openly. We recommend starting from Dataverse and a model-driven app so data can grow without a rebuild.
What we would add today
Improvements we would add on top of what is live.
- Choose full Dataverse in a managed environment instead of Dataverse for Teams, so row level security, auditing and pipelines are available.
- Link emails and meetings to a client record, with a Copilot Studio agent that summarises the relationship.
- Add duplicate detection and business units to separate teams and protect client data.
- Use Power BI or Fabric over Dataverse for relationship health and coverage reports.
- Move to Dynamics 365 Sales if pipeline tracking or forecasting becomes a need.
Technology
Power Apps (canvas and model-driven), SharePoint Online, Dataverse for Teams, Dataverse, Power Automate, Microsoft Teams.
Tell us how many people need your client list and what they do with it, and we will tell you whether a mini CRM or a full CRM is the right size.
Products and capabilities
- Power Apps
- Dataverse
- Dataverse for Teams
- SharePoint
- model-driven app
- canvas app
- contact management
- options analysis
The service behind this work
Dynamics 365The service behind this work
Power Platform development
Related use cases
Sales and customer serviceDissatisfaction Tracker with AI Builder and a Model-Driven App
When a customer complains, the email trail passes through several inboxes before anyone logs it in a spreadsheet. Each hand-off adds delay, and the monthly picture arrives late. We built a proof of concept that turns a complaint email into a tracked record in one click, with AI Builder suggesting the sentiment and category.
- 10 min
- saved per complaint
- 100
- training emails
Customer Portal for Order Placement and Tracking
When customers order by phone or email, the sales office types each order in again, answers every call asking where a delivery is, and finds mistakes after the lorry has left. We built a customer portal where approved customers place and track orders without the sales office in the middle.
Three Trading Platforms on Model-driven and Portal Power Apps
A trading desk loses time and control when its tools are slow, scattered or closed to the brokers it deals with. The client needed platforms that traders inside the company and brokers outside it could both use at the pace of daily business. We developed three, using model-driven and portal Power Apps.
- 3
- trading platforms
- 100+
- traders and brokers
Have a Microsoft project in mind?
Tell us what you need built, fixed or supported. A senior consultant replies within one business day.