Skip to content
OZBI
← All services
Sheet 01

Microsoft Power Platform

Starting point

Microsoft 365 is already in the building, but the process runs on mail, Excel and word of mouth. A large custom build blows the budget and the timeline.

What OZBI builds

We analyse the process, automate it and turn it into an application — on the Power Platform, within your existing licences.

Discuss a project
FORMULARGENEH-MIGUNGDATENDASHBOARD
Fits when
  • +You already run on Microsoft 365
  • +The process hangs on mail and Excel
  • +Data should stay in your tenant
Does not fit when
  • A public site or customer product
  • Very compute-heavy logic
  • Not on Microsoft 365
What's on the sheet
Capture & approval apps
Workflows & approvals
Structured data model in the cloud
Business-intelligence reporting
Conversational AI assistants
Technology layers
  • Low-code application layer
  • Event-driven process automation
  • Conversational AI assistance
  • Structured cloud data storage
  • Document & records management
  • Business-intelligence reporting
  • Federated identity & access management
  • Central productivity platform
Stations
  1. 01

    Intake

    Review the process and the numbers

  2. 02

    Draft

    Sketch, data model, effort

  3. 03

    Build

    Short stages, testable early

  4. 04

    Handover

    Docs, access, operation

Case file

Resource request

Context
Industrial company, Switzerland.
Solution
An application with a request form, an automated approval route and a structured data store in the cloud.
Result
One route instead of many mailboxes — every request traceable, status visible at any time.
Technology
Low-code platform · automated workflows · cloud data storage
Done
Follow-up questions
Do we need extra licences?+

Often the rights included in Microsoft 365 are enough. Where a premium licence is required, we say so before the build.

Can our IT maintain the app afterwards?+

Yes — a clean model, documentation and a handover with your key users are part of it.

How long does a project take?+

A first usable version in four to eight weeks, then extended in stages.