Skip to content
2-M Logo2-M
Switch to French

Microsoft Power Apps

The shared spreadsheet has earned the right to become an application.

Entered once, validated, traceable, reachable from a phone as much as from a desk. Here are three applications we delivered, running, not mocked up.

3

delivered applications, shown running

Gross margin · budget entry · receivables follow-up

Expert consultants
11
Projects delivered since 2019
100+
Permissions follow your directory
M365
Free scoping workshop before any quote
2 h

Our work

Three applications, running

These are not mock-ups: all three run at client sites. The captures are animated to show real use rather than a frozen screen.
  • Power Apps

    Calcul de marge brute

    Marge brute par collaborateur, calculée à partir du revenu journalier, du salaire, du coût et des jours travaillés. Saisie sur mobile comme sur poste fixe.

  • Dynamics 365

    Saisie budgétaire

    Interface de budget structurée sur un plan comptable analytique multilingue, avec gestion collaborative des dépenses et des revenus exceptionnels.

  • Power Apps

    Relances clients

    Suivi des créances : factures échues, actions de recouvrement horodatées, commentaires associés. Ce que le tableur faisait, en traçable.

1
Single entry, instead of retyping across three tools
100 %
Of actions timestamped and attributed
M365
Permissions handled by your directory
Mobile
Same application on phone, tablet and desktop

Our most frequent cases

The processes that gain most from becoming an application

  1. Internal requests

    HR, purchasing, IT: one request, one route, one status the requester can see.

  2. Approval flows

    Who approves what, in what order, with what trace. Reminders go out on their own.

  3. Field capture

    Entry on mobile, including offline, synchronised when the network returns.

  4. Follow-up and reminders

    Receivables, claims, sales actions: what the spreadsheet did, made traceable.

The trade-off

Power Apps or an application framework: a question of numbers

Both approaches are sound, on different ground. What separates them is a cost structure, and the slider lets you place your own situation on it.

Deux structures de coût, un point de croisement

The amounts depend on your case and on the pricing of the day. What does not change is the shape of the two models.

Crossing pointCost per userCost per applicationNumber of users →Annual cost →

At that level of adoption, the foundation becomes the cheaper option. The cost stops following the number of users, and external users add nothing to the bill.

Cost per user grows with the number of users; cost per application stays flat. The two cross at a headcount that depends on your case. Below it, Power Apps is cheaper; above it, an application on our foundation is. We cost both scenarios during the scoping workshop.

Going further

The pages that continue this one

Frequently asked

What people ask us about Power Apps

What is Power Apps actually for?

Replacing a shared spreadsheet, a paper form or an inbox with an application where data is entered once, validated and traceable. The most frequent cases we see: internal HR or purchasing requests, approval flows, field data capture, receivables follow-up, budget entry. What they have in common is a process that already exists and deserves its own tool.

How long does a Power Apps project take?

An application focused on one process takes days to weeks depending on the number of screens and the complexity of the rules. The delay rarely comes from development: it comes from clarifying the process, which is also the part that pays off most. So we start with an hour alongside the people who do the task.

Power Apps or a custom application?

Power Apps is at its best when the application lives inside Microsoft 365, users are internal and identified, and development has to move fast. Our application framework takes over when users become numerous or external, when the interface needs particular care, or when per-user billing stops being favourable. We build both and we price both.

Does our data stay in our own environment?

Yes. A Power Apps application runs on Dataverse, SharePoint or a database of your choice, inside your Microsoft 365 tenant. Permissions follow your directory: someone who leaves the company loses access without us doing anything.

Who maintains the application afterwards?

Your teams, if you want to, and we train at least one person for it. A Power Apps application can be modified without writing code, which makes autonomy realistic. We stay available for structural changes, and we document what was built so the handover is possible.

2-M designs Power Apps business applications from Saint-Priest, near Lyon. 11 expert consultants work across Auvergne-Rhône-Alpes, remotely anywhere in France, and in French-speaking Switzerland.

Tell us which process weighs on you.

Eleven expert consultantsSaint-Priest, near Lyon, France

Two hours with a consultant, free of charge. We look at the process as it actually runs, tell you what deserves an application and what a simple flow would settle, and we price both approaches when both stand up.

Request a scoping workshop

Scoping workshop · 2 hours · free · near Lyon or remote

Our technologies

Microsoft FabricPower BIPower AppsPower AutomateMicrosoft Partner