For flows that run on their own

Power Automate support and maintenance services for the approval, scheduled and integration flows your business already runs on

Your flows run with no app in front of them — an approval that routes invoices, a nightly job that copies orders between systems, a desktop flow on a PC in the back office — and one of them failed last week without anyone noticing. Our Power Automate support and maintenance services triage those failed runs, repair the connections and take over flows whose maker has left, with each batch of fixes scoped at one fixed fee you approve first. No retainer, no bank of hours.

Free, no-obligation consultation · Reply within one business day

  • Fixed fee agreed before any work starts
  • Senior US-based engineers
  • No retainer or monthly minimum
  • 30 days of hypercare after each batch
Revenue Overview Revenue$4.2M Margin38% Orders12.4k Churn2.1% Monthly performance By segment 64%

Sample dashboard. Illustrative data, not a client’s numbers

What you get

Six things that quietly stop a working flow

A flow with no app in front of it has no screen for anyone to notice. When it fails, the first sign is usually a missing approval, an empty report or an order that never reached the other system.

Failed runs nobody saw

We read the run history, find which runs failed and at which step, and fix the cause rather than pressing resubmit. Then we add error handling so the next failure reaches a named person instead of only the original maker’s inbox.

Broken connections

An “Unauthorized” error usually means a connection lost its sign-in: a password change, a new sign-in policy, an expired key on the other system. We repair the connection and record which flows depend on it.

Flows owned by someone who left

Most flows belong to whoever built them. When that person leaves, their flows are one disabled account away from stopping. We move ownership and connections to accounts that will still exist, and name a co-owner.

Desktop flows and their machines

A desktop flow needs a registered machine and an application that still looks the way it did when the flow was recorded. We keep the machine registered, repair its connection, and update steps an application update has broken.

Premium licence surprises

A flow that uses a premium connector depends on whoever’s licence it runs under. We check that before ownership moves, so a flow does not run through a grace period and then switch itself off.

Small changes to approvals and schedules

An extra approver, a new threshold, a different run time, one more field passed to the other system. None of it is a project; all of it matters to the people relying on the flow. We batch the list and price it once.

How it works

From a failed run to a fixed quote in three steps

  1. 1

    Tell us what stopped

    Through the form below: which flows failed or need changing, what they do, and who built them. A rough list is fine. During a free consultation we ask the questions needed to turn it into specific, testable items.

  2. 2

    Read the flows, then quote

    On the first engagement we read the flows, their run history, their connections, owners and any machines they use, so the quote reflects what is actually there. You get a written list of fixes and changes at one fixed fee, and nothing starts until you approve it.

  3. 3

    Fix, test, release

    Each fix is tested against real runs, released with your sign-off and noted in a change record for the flow. Every batch is followed by 30 days of hypercare in case something we touched misbehaves.

Why a flow that ran for a year stops on a Tuesday

A flow is a chain of steps, and each step reaches into another system through a connection that belongs to somebody. The flow itself may not have been edited since the day it was built and still fail, because the account behind one connection changed its password, the other system renamed a field, or a sign-in policy changed underneath it. Most Power Automate maintenance is not fixing the flow’s logic; it is keeping its connections, owners and the systems on either end in step with each other.

The first job on any failure is finding out what actually went wrong. Microsoft’s guide to troubleshooting a cloud flow (opens in new tab) walks through the 28-day run history, and separates authentication failures (an “Unauthorized” message or a 401 or 403 code, usually fixed by repairing the connection) from action configuration errors (a 400 or 404, fixed by correcting the flow) and temporary 500 or 502 errors that a resubmit clears. Resubmitting without knowing which of the three you are looking at is how one failure quietly becomes a month of them.

What this covers, and what it deliberately does not

Support here means keeping flows that already work running, and improving them in small steps. The line matters because a request on the wrong side of it needs a different engagement, and pricing it as maintenance would hide its real cost.

The request Handled as support? Notes
An approval, scheduled or integration flow has failed or fails intermittently Yes Run history read, cause fixed, error handling added so the next failure notifies someone
Flows broke after the maker left or changed a password Yes Ownership and connections moved to accounts that will still exist; co-owner named
A desktop flow stopped after a PC was reset, rebuilt or updated Yes Machine re-registered, connection repaired, broken steps re-recorded
A premium-connector licence warning after an ownership change Yes Licensing checked against how the flow runs; options set out before anything is switched
An extra approver, a new schedule or one more field sent to another system Yes Batched into a written change list at one fixed fee
The flow is triggered from inside a Power App Yes, alongside the app The app and its flows are supported together — see Power Apps support and maintenance services
A new automation for a different process No That is a build — see Power Automate consulting
Flows that never worked, or a build that stalled halfway No That is a takeover — see Power Platform project rescue services
A 24/7 on-call desk with a guaranteed response time No We do not offer a service-level agreement; a managed service provider is the right fit for that

Not sure which approach suits your flow fixes and changes? A senior engineer will talk it through with you, at no cost.

Talk to an engineer →

Flows on their own, or flows inside an app

Many flows have no app at all. An invoice approval starts when a file lands in a SharePoint library; a nightly job copies new orders from one system into another; a weekly flow emails a summary to the managers. Nobody opens anything to use them, so nobody sees them fail. This service is built for those flows. If your flows are triggered from a canvas or model-driven app and the two are maintained together, our Power Apps support and maintenance services cover the app and its flows as one piece of work, and that page also sets out where Microsoft’s own support ends and a partner’s begins.

The same approach applies elsewhere in the platform. If the thing that needs looking after is a live dashboard, the equivalent is Power BI support and maintenance services; if it is the SharePoint site your flows read from and write to, see SharePoint support and maintenance.

Ownership, licences and the flow nobody owns

Every flow has an owner, and by default it is whoever built it. Microsoft’s guide to changing the owner of a cloud flow (opens in new tab) sets out three details that catch small businesses out. Ownership can only be changed in place on a flow that sits inside a solution; a flow built outside one has to be added to a solution or recreated. A scheduled or automated flow runs under its owner’s licence, so moving it changes whose licence it uses. And if the new owner has no premium licence while the flow uses premium features, Power Automate warns, keeps the flow running for 30 days, then turns it off.

That is why we check licensing before moving anything, not after. Which plan your flows need depends on the connectors they use and how they are triggered, and Power Automate licensing for small businesses explains the options in plain terms. We do not sell licences; we tell you what each flow needs and leave the purchase with you. If a maker has just handed in their notice, what happens when a Power Automate flow owner leaves sets out what to move before their account is disabled.

Desktop flows and the machines behind them

Desktop flows add a moving part that cloud flows do not have: a real or virtual Windows machine. Microsoft’s documentation on managing machines for desktop flows (opens in new tab) notes that a machine loses its registration when the PC is reset, that moving a machine to another environment removes all its current connections, and that maintenance mode lets you pause runs while the machine is updated. Any of those can stop a desktop flow without touching the flow itself. So can an update to the application the flow clicks through, when a button moves or a screen is renamed.

Maintenance for a desktop flow therefore covers the flow, the machine and the application together. If you are still deciding whether a task should be a desktop flow at all, desktop flows versus cloud flows compares the two.

Support priced per batch, not per month

The usual way to buy this is a monthly retainer for a set number of hours. We do not offer one. Flow maintenance is lumpy — nothing for two months, then three failures in a week after a password policy changes — and a flat monthly fee means paying for the quiet months while the busy ones still run over. Instead, each batch of fixes and changes is written down as a list of specific items, and the whole list carries one fixed fee you approve before work starts. When nothing has failed and nothing needs changing, there is nothing to pay. We do not publish a price list, because the fee depends on what is in the batch and how the flows are built; the quote follows the free consultation and, on the first batch, a read of the flows. How our fixed-fee process works is the same for a batch of fixes as for a full build.

Who this fits, and who it does not

The usual fit is a small or mid-size business with a handful to a few dozen flows in daily use — approvals, scheduled reports, integrations between systems, perhaps a desktop flow or two — built by a contractor, an agency or a capable colleague who has since moved on. The flows matter, nobody wants to rebuild them, and no one’s job is to keep them running.

It fits badly in two cases. If you need someone on call overnight with a contractual response time, that is a managed service provider, not us. And if the flows never worked properly, the honest answer is a rescue or a rebuild, and we will say so during the consultation rather than sell a string of fixes that will not hold. Work is delivered remotely across all US states from our Orange County, CA base, by senior US-based engineers.

The overrun risk sits with us, not you

Every engagement starts with a free consultation and a written scope: deliverables, timeline and one fixed price. You approve it before any work begins, and scope changes are agreed in writing. 30 days of hypercare after handover are included.

Get my fixed-price proposal →

FAQ

Questions about keeping flows running

Yes, that is what this service is for. Approval flows, scheduled flows, integration flows between systems and desktop flows on a machine are all supported on their own. If the flow is triggered from inside a Power App, our Power Apps support service covers the app and its flows together.

Usually the flows keep running on that person's connections until the account is disabled or its password changes. We move ownership and connections to accounts that will still exist, add a co-owner, and check licensing first, because a scheduled or automated flow runs under its owner's licence.

No. There is no retainer and no bank of hours. You send us the list of flows that failed or need changing, we scope it, and the batch carries one fixed fee you approve in writing before work starts. In a month when every flow runs cleanly, you pay nothing.

We do not sell a contractual response time. A fix is scoped and scheduled like any other piece of work, with the date written into the scope. Power Automate keeps 28 days of run history, so a failure is still traceable a few days later. For overnight on-call cover, a managed service provider fits better.

Yes. Desktop flows depend on a registered machine, a working connection and the applications they click through. When a PC is reset, rebuilt or moved to another environment, its registration or connections can be lost. We re-register the machine, repair the connections and update steps an application change has broken.

A scheduled or automated flow runs under its owner's licence. If ownership moves to someone without a premium licence and the flow uses premium features, Power Automate warns, keeps the flow running for 30 days, then turns it off. We check licensing before any ownership change and set out your options.

Get your flow fixes and changes scoped in writing

No hourly meter and no retainer. We scope the work in writing, you approve one fixed price, and the engineer who scoped it does the work.

Free consultation · Written fixed price before any work starts · Reply within one business day

Book a free consultation

See what your Power Automate project would take

Tell us what you’re trying to fix. We reply within one business day, and you get a written fixed-fee proposal to approve before any work begins.

Step 1 of 2: What do you need?

How can we help? Pick one

Tap to add, or type your own:

Step 2 of 2: Where should we reply?

Used only to contact you about this inquiry.

We reply within one business day. Fixed price approved before any work begins. We don’t sell your information.

Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.

  • Fixed-fee scope agreed before any work starts
  • Senior, US-based Microsoft engineers — no handoffs
  • Typical 2–4 week delivery
  • 30 days of post-delivery hypercare included
Book my free consultation