stampp.consulting

tools low-code platform

Microsoft Power Platform

Apps, automations and reports on top of Microsoft 365, all working on the same data. Our main platform when a process needs software.

Palm silhouettes
your process
dataverse
power appspower automatepower bi
fig. 01 · apps, flows and reports on one data layer
§ 01 / 05the building blocks

Six parts, one platform

Power Platform is a set of low-code tools that sits next to Microsoft 365 and uses the same sign-in and security. We use whichever parts the process needs.

N° 01

Power Apps

Apps for phone, tablet and desktop, built around your process. Canvas apps for task-focused screens, model-driven apps for data-heavy back-office work.

N° 02

Power Automate

Flows that move data between systems and send approvals, notifications and documents, so nobody has to do it by hand.

N° 03

Power BI

Dashboards and reports, from KPIs on the shop floor to overviews for management.

N° 04

Dataverse

The data layer underneath, with tables, relations, security roles and an audit history, so every app works on the same record.

N° 05

Copilot Studio

AI agents and chatbots that use the same data and the same security.

N° 06

Power Pages

Websites and portals for people outside the organisation, such as customers or suppliers.

§ 02 / 05how a project runs

From process to a platform you own

  1. Process first

    We walk through the work with the people involved before we design a single screen.

  2. One data model

    One record per job in Dataverse, with security roles per department.

  3. Short rounds

    We build in small steps and test each one with the people who will use it.

  4. Licences checked

    We work out which licences the design needs before we build, so there are no surprises later.

  5. Handover

    Documentation and training, so your own people can maintain and extend it.

§ 03 / 05when it fits

When Power Platform is the right choice

it fits when

  • You already work in Microsoft 365, with Teams, SharePoint, Outlook and Entra ID. Sign-in, security and much of the licensing build on what is there.
  • The process runs on paper, Excel, email or chat, and the people doing the work are on the shop floor as often as in the office.
  • Several departments need to see the same job, for example operations, field staff, the office and management.
  • You want to own the solution after the handover and change it yourself.

it does not fit when

  • The process itself is not clear yet. Then the first step is the process, not an app.
  • A standard package such as an ERP, CRM or WMS already does the job well. Then configuring that package is the better route.
  • The volumes are very high or the logic needs custom software. We will say so, and help you find the right party.
§ 04 / 05

Governance and adoption

Low-code makes building easy, which also makes it easy to end up with dozens of unmanaged apps and flows. From the first day we set up separate environments for development, testing and production, deploy through solutions, and agree data loss prevention policies and naming conventions. We also agree who may build where, which connectors may share data and who owns each app.

Adoption gets the same attention as the build, because an app that nobody uses has not improved the process.

§ 05 / 05

Questions

Is it secure?

Power Platform runs in your own Microsoft tenant. People sign in with their existing work account, access follows security roles, and data loss prevention policies decide which services may exchange data.

Do we need extra licences?

Often, yes. Apps that use Dataverse or premium connectors need Power Platform licences on top of Microsoft 365. Which ones depends on the number of users and apps. We check this before building.

Can we maintain it ourselves?

That is the goal. We document the data model and the logic and train the people who will own the solution.

Low-code or custom software?

Low-code is faster to build and easier to change, and it suits most internal processes. Custom software makes sense for very high volumes, unusual technical demands or a product you sell to others.

used in

24/7 technical service company

From paper work orders to one platform

From paper work orders, WhatsApp and email to a handheld app for mechanics and desktop apps for the office and operations, all working on the same data.

  • 2025–2026
  • Power Platform
  • 85+ users
  • 3 departments

← All tools

contact

Where does the work get stuck?

Describe where work stalls between teams, suppliers, partners or customers. In the first conversation we talk about the process, before any software.