News

WahInnovations has merged into MoreYeahs IT Technologies, enhancing our Salesforce solutions with AI and Data Engineering.

WahInnovations joined MoreYeahs.

Get in touch

Power Automate & Power Apps Development Services

Replace the approval chains living in email, the spreadsheet trackers only one person understands, and the paper forms someone re-keys by hand. We build the automation and the applications, and when the low-code platform runs out, we keep going rather than handing the problem back.

Tell us about the process you want to fix See what we have automated

The processes nobody designed

Almost every organisation runs on a handful of processes nobody ever actually designed. They accumulated. Someone set up an email chain, someone else built a spreadsheet, a form got printed, and over a few years it became how the business works.

They usually announce themselves the same way:

Power Automate and Power Apps are built for exactly this. The work is not complicated, but it does need someone to design the process properly rather than automating the mess as it stands.

  • An approval sits in someone's inbox and nobody can tell you where, or whether it was approved at all, because there is no record.

  • A spreadsheet tracker that one person maintains, that everyone else distrusts, and that stops entirely when they are on leave.

  • A form filled in on paper or PDF, then typed into a system by someone else, with the errors that always introduces.

  • Field, site or warehouse teams who cannot record anything until they are back at a desk, so data arrives days late and half-remembered.

  • InfoPath forms still holding a critical process together on a platform Microsoft has retired.

What we build with Power Automate and Power Apps

Purchase requests, capital expenditure, leave, travel, contract sign-off, content publishing, IT access: anything that currently moves by email. We build conditional routing so a request goes to the right approver based on value, department or type; escalation when it sits too long; delegation when an approver is away; and a complete audit history of who approved what and when. Approvers can act from Teams, from their phone or from the intranet, which is usually what determines whether a new process is adopted or quietly ignored.

Custom applications for the processes that run your operation: inspections, asset registers, quality checks, site reports, onboarding, request handling. Built in Power Apps where the low-code model fits, with a data model designed properly rather than improvised: SharePoint lists where that is sufficient, Dataverse or Azure SQL where volume, relationships or performance demand more. The design decision matters commercially as well as technically, and we make it deliberately rather than by default.

Applications for people who do not work at a desk. Photo capture, GPS location, barcode scanning, digital signature, and offline capability so a form can be completed on a site with no signal and syncs when the device reconnects. This is frequently the highest-return automation in an organisation, because it removes an entire re-keying step and gets data in on the day it was collected rather than at the end of the week.

Contracts, certificates, reports, proposals and compliance documents generated from your data: populated into your templates, formatted correctly, filed in the right place with the right metadata, and routed for approval. Built with Power Automate where the formatting is straightforward and extended with Azure Functions where it is not. For document-heavy businesses this removes a daily task that is tedious to do and expensive to get wrong.

Power Automate connects to hundreds of systems out of the box, but rarely to the one that matters most to you. We build custom connectors that wrap your internal APIs or a third-party system so it becomes available to every flow and app in your environment, with authentication handled properly and credentials held in Azure Key Vault rather than embedded in a flow. Built once, reusable everywhere, which is what turns a single automation into a platform.

InfoPath is end of life, and a surprising number of organisations still have business-critical forms running on it. We assess what each form actually does, rebuild it in Power Apps, or in a custom SPFx form where the logic is too complex for the low-code model, and migrate the data and the process with it. Most of this work runs in phases so the existing forms keep working until their replacement is live.

Signing off a document with a fountain pen

Approval workflows and process automation

Purchase requests, capital expenditure, leave, travel, contract sign-off, content publishing, IT access: anything that currently moves by email. We build conditional routing so a request goes to the right approver based on value, department or type; escalation when it sits too long; delegation when an approver is away; and a complete audit history of who approved what and when. Approvers can act from Teams, from their phone or from the intranet, which is usually what determines whether a new process is adopted or quietly ignored.

Built with
Power AutomateApprovalsTeams
Business applications open on a tablet beside a phone

Business process applications

Custom applications for the processes that run your operation: inspections, asset registers, quality checks, site reports, onboarding, request handling. Built in Power Apps where the low-code model fits, with a data model designed properly rather than improvised: SharePoint lists where that is sufficient, Dataverse or Azure SQL where volume, relationships or performance demand more. The design decision matters commercially as well as technically, and we make it deliberately rather than by default.

Built with
Power AppsSharePoint listsDataverse

Mobile and field data capture

Applications for people who do not work at a desk. Photo capture, GPS location, barcode scanning, digital signature, and offline capability so a form can be completed on a site with no signal and syncs when the device reconnects. This is frequently the highest-return automation in an organisation, because it removes an entire re-keying step and gets data in on the day it was collected rather than at the end of the week.

Built with
OfflinePhoto & GPSBarcode
Generated documents coming off an office printer

Document generation and automation

Contracts, certificates, reports, proposals and compliance documents generated from your data: populated into your templates, formatted correctly, filed in the right place with the right metadata, and routed for approval. Built with Power Automate where the formatting is straightforward and extended with Azure Functions where it is not. For document-heavy businesses this removes a daily task that is tedious to do and expensive to get wrong.

Built with
Power AutomateAzure FunctionsTemplates
Two hands joining puzzle pieces, connecting separate systems

Custom connectors and integration

Power Automate connects to hundreds of systems out of the box, but rarely to the one that matters most to you. We build custom connectors that wrap your internal APIs or a third-party system so it becomes available to every flow and app in your environment, with authentication handled properly and credentials held in Azure Key Vault rather than embedded in a flow. Built once, reusable everywhere, which is what turns a single automation into a platform.

Built with
Custom connectorsKey VaultAPIs
Frustrated employee working through a paper form on a clipboard

Replacing InfoPath and legacy forms

InfoPath is end of life, and a surprising number of organisations still have business-critical forms running on it. We assess what each form actually does, rebuild it in Power Apps, or in a custom SPFx form where the logic is too complex for the low-code model, and migrate the data and the process with it. Most of this work runs in phases so the existing forms keep working until their replacement is live.

Built with
Power AppsSPFxPhased migration

What happens when low-code runs out

Power Automate and Power Apps cover a great deal. They also have real limits, and most organisations find them the hard way, usually after a solution is already live and being relied on.

The limits are predictable:

  • Complex business logic that becomes unreadable as a flow
  • Data volumes that make a canvas app slow
  • A process that needs to run against thousands of records rather than one
  • An integration with a system no connector supports
  • Performance requirements a low-code runtime cannot meet

Most Power Platform consultancies are low-code only. At that point they either build an elaborate workaround that becomes its own maintenance problem, or they tell you it cannot be done.

We carry it through instead

Because we are an engineering team that also works in low-code, not a low-code team alone, the solution can cross the boundary without changing supplier. In practice that means:

  • Azure Functions called from a flow, so the complex logic lives in proper code while the process stays in Power Automate
  • Custom connectors that make an unsupported system available to the whole platform
  • SPFx components where the interface genuinely needs to live inside SharePoint rather than beside it
  • A move to Dataverse or Azure SQL when SharePoint lists stop being the right data layer

And the honest converse

Custom development is not automatically better. It costs more, takes longer and your own team cannot change it. Where a flow will do the job, a flow is the right answer, and we will say so. The value is in knowing where the line actually falls, not in being on one side of it.

Licensing: the part most people find out too late

More Power Platform projects are derailed by licensing than by any technical constraint. A solution gets designed, built and demonstrated, and only then does someone discover it depends on a premium connector, or needs Dataverse capacity, or requires a licence tier nobody budgeted for. It is avoidable, and it is a design question rather than a procurement one.

Standard versus premium connectors

Some connectors are included with Microsoft 365; others are premium and require additional licensing for every user who touches the solution. The distinction is not intuitive, and a single premium connector deep inside an otherwise standard flow changes the cost of the whole thing. We check this at design time and tell you what a given approach implies before it is built.

Per-app versus per-user licensing

Microsoft offers different licensing models depending on how many applications a person uses. Which is cheaper depends entirely on your usage pattern, and the answer can reverse as adoption grows. We model it for your actual numbers rather than assuming.

Dataverse and capacity

Dataverse is the right data layer for some solutions and unnecessary for others. It carries storage and capacity costs that SharePoint lists do not. We choose deliberately, and where SharePoint is sufficient we use it, a decision that can change a solution’s running cost significantly over a few years.

We can advise and supply

MoreYeahs is also a Microsoft cloud services provider, so we can advise on licensing and then supply it, rather than telling you what you need and leaving you to source it. Most Power Platform consultancies cannot do the second half.

Power Platform governance and estate control

If your organisation encouraged citizen development a few years ago, you probably now have hundreds of flows and apps, no clear picture of what runs where, and solutions owned by people who have since left. The individual automations may be useful. The estate is a risk.

We help bring it back under control:

Environment strategy: separating development, test and production rather than everything running in default

Data loss prevention policies that stop business data reaching connectors it should not

ALM and solution deployment, so changes move between environments properly instead of being rebuilt by hand

A Centre of Excellence setup that gives you visibility of every app and flow, who owns it and whether it is still used

Rescuing orphaned solutions: identifying what matters, re-homing ownership and retiring what does not

Governance work usually starts with an audit of what exists. In most organisations the audit itself is the revelation. For keeping it under control afterwards, see ongoing managed services.

Automation we have delivered

Capital expenditure approval: from email threads to an auditable process

A capital expenditure approval process running entirely on email and spreadsheets. Requests were raised by email, approvals were granted by reply, and there was no reliable way to answer two basic questions: where is this request now, and who approved the last one.

We built a Power Apps front end for raising and tracking requests, with a Power Automate process behind it handling conditional routing by value threshold, automatic escalation when a request sat too long, delegation when an approver was unavailable, and a complete approval history against every request. Approvers act from their phone, which matters when the people authorising capital spend are rarely at a desk.

Altera: IT intake and multi-level approval system

For Altera, we implemented an IT intake and multi-level approval platform to streamline the submission, assessment, prioritisation and approval of IT requests across the organisation. Employees submit requests in one place, and each is routed through defined approval stages based on request type, business ownership, priority and budget.

Automated workflows improve visibility into request status, reduce manual follow-ups and give stakeholders a consistent approval experience, while structured tracking and reporting let management monitor request volumes, approval progress and outstanding actions. By replacing fragmented email-based processes with a governed digital workflow, Altera gained greater transparency, accountability and consistency across its IT intake and approval process.

Low-code extended: CMAP CRM synchronised into SharePoint

We built a custom integration between CMAP CRM and SharePoint to synchronise project information. CMAP was not natively supported for the required scenario, so the integration used CMAP REST APIs and webhooks with Power Automate, enabling project data to be received, processed and synchronised into SharePoint.

This provided near-real-time updates without relying on manual data entry.

See custom development
See all SharePoint case studies

How to start

Most Power Platform relationships start small. We would rather you began with one process and judged us on it than committed to a programme before you knew how we work.

01

One process, fixed price

Pick the process that causes the most friction. We scope it, build it and hand it over for an agreed fee. The lowest-risk way to find out whether this works for your organisation, and most clients come back with a second process before the first is finished.

02

Automation programme

A sequence of processes automated over an agreed period, prioritised by return. Best when you already know there are ten of these and want them addressed systematically rather than one at a time.

03

Dedicated capacity

Power Platform and SharePoint engineers working as part of your team on a monthly basis. Best for continuous development, or where your own makers need engineering support behind them.

Power Automate and Power Apps: common questions

What teams ask us before automating their first process.

Power Automate handles process: what happens, in what order, triggered by what, routed to whom. Power Apps handles interface: the screens people use to enter data and take action. Most real solutions use both: an app someone submits a request through, and a flow that routes it, notifies people and records the outcome. You rarely choose between them.

Sometimes. Microsoft 365 includes Power Automate and Power Apps for use with standard connectors and SharePoint data, which covers a great deal. Additional licensing applies when a solution uses premium connectors, Dataverse, or certain platform capabilities. Whether you need it is largely determined by how the solution is designed, which is why we raise it at design time rather than after the build. We are also a Microsoft cloud services provider, so we can supply the licences as well as advise on them.

That is usually the point. Solutions built in Power Automate and Power Apps are designed to be readable and changeable by your own people, and we document them and run a handover session so your team can take them on. Where a solution has been extended with custom code, that portion needs engineering support. We will tell you clearly which parts fall into which category rather than leaving you to discover it.

We build past it. Complex logic moves into an Azure Function the flow calls, an unsupported system gets a custom connector, and where the interface needs to live inside SharePoint we build it as an SPFx component. The solution stays coherent and the supplier does not change. Most low-code consultancies stop at this point, which is the single most common reason organisations come to us with a half-finished automation.

Yes. Applications can be built to capture data with no connection and sync when the device reconnects, which is important for site, field and warehouse teams where connectivity is unreliable. Offline capability does constrain how the app is designed, particularly around data volume and conflict handling, so it is a decision to make at the start rather than retrofit. If your teams work in low-signal environments, tell us early.

Regularly. Solutions built by internal makers often work well until the person who built them changes role, or until the process outgrows how it was put together. We review what exists, tell you what is sound and what carries risk, and then stabilise, extend or rebuild. We are not precious about who built it first.

We advise on where Copilot Studio and AI Builder fit, but we do not currently build with them. If AI capability is genuinely the right answer for a process, we will say so and tell you plainly what it would involve.

No. Both work independently of SharePoint and connect to a wide range of systems. That said, if you are already on Microsoft 365 then SharePoint is frequently the most sensible data layer: it is included in what you already pay for, it handles documents and permissions natively, and it keeps the solution inside one platform. We use it where it fits and something else where it does not.

Other SharePoint services

01SharePoint Intranet Development02Custom SharePoint Development03Power Automate & Power AppsCurrently viewing04SharePoint Migration05SharePoint Managed Services

Pick one process. We will show you what automating it looks like.

You do not need a strategy or a business case to start. Tell us about the process that causes the most friction: the approval that always gets stuck, the spreadsheet everyone works around, the form that gets typed in twice. We will tell you what automating it would involve, roughly what it would take, and whether it is the right one to start with.

Response within one business day from a technical lead, not a bot.
NDA on request before you share anything sensitive.
Prefer to book directly? Grab a 30-min architecture slot on our calendar.