NAVIGATION
Discuss a solution

Software. Automation. Connected data.

Case study · CEOFlowStudio · Microsoft Power Platform · Business operations

Building the studio’s own operating system first

For a studio that builds business systems for others, running its own business on spreadsheets, email and separate tools was the wrong way to start. So the first client was the studio itself.

The situation

CEOFlowStudio started as a one-person software studio. Like most new businesses, the first months meant doing everything at once: finding clients, scoping work, delivering projects and getting paid. The admin was spread across spreadsheets, email and separate tools, and nothing connected clients to projects, projects to invoices, or invoices to the money that actually arrived.

The goal

One place to run the business:

  • clients and the projects done for them;
  • invoices, income and expenses, tied to those projects;
  • payments matched to invoices without manual checking, with exceptions surfaced rather than missed;
  • the same discipline the studio offers clients: a development environment, a test environment, and releases that can be repeated and checked.

What was built

  • A model-driven app on Microsoft Dataverse: the working space for clients, projects, invoicing, income and expenses.
  • Automated invoice reconciliation with Power Automate. It matches incoming payments to invoices. Failed steps retry in a controlled way, items are processed one at a time so nothing is matched twice, and anything that cannot be matched becomes a visible exception rather than a silent gap.
  • A release process normally reserved for larger teams:
    • development is the only place changes are made;
    • releases are packaged as managed solutions, with a recorded link back to the exact source they came from;
    • promotion to the test environment is manual and runs a preflight check first;
    • offline validation checks every flow’s structure before anything is packaged.
  • Versions 1.0.2 to 1.0.4, each validated before it moved on, including a round of financial controls work.

What it changed

  • One record of each client, project and invoice, instead of several partial ones.
  • Reconciliation exceptions visible in one place, as they happen, instead of discovered later.
  • Releases that can be repeated and traced, so changes to the business system carry no more risk than they need to.

What came out of it: SolutionPilot

Building CEOFlowStudio with AI coding assistants showed both sides of them. They are fast, but a Power Platform environment is not a place to experiment blindly. The guard rails the studio built for its own work became a product:

  • AI changes stay in development environments;
  • every change is previewed, applied once and read back;
  • changes can be planned for undo.

That product is SolutionPilot, now in an invitation-only pilot.

Why it matters for clients

The studio uses the same approach on client work as on its own: understand the workflow first, build around it, and release in a way that can be checked and repeated. CEOFlowStudio is the working proof.

A good place to start

Have a process that
should work better?

Tell us where the work slows down, breaks apart or depends on a workaround. We can define a sensible next step.

Discuss a solution