Consulting
Power Platform, built to be handed over
Power Automate, Power Apps, SharePoint and Dataverse. Scoped and priced as one piece of work, documented so your own team can maintain it, and honest about when you do not need us at all.
What we actually build
The work that quietly removes a job somebody does by hand every week.
Approvals, document routing, notifications, and the integrations between systems that currently rely on somebody remembering. Built with error handling, so a failure is visible rather than silent.
Internal apps for a team that has outgrown a spreadsheet: inspections, requests, registers, approvals. Canvas or model-driven depending on which one your problem actually needs.
The structure underneath. Lists, libraries, permissions and document sets designed so the thing still works at ten times the data, not just on demo day.
Azure SQL, Microsoft 365, line-of-business systems and third-party APIs. The plumbing that turns several disconnected tools into one process.
Inherited solutions that broke, apps nobody can edit any more, flows that fail silently. Assessed first, with an honest answer about repair versus rebuild.
Structure, ownership, connections and failure modes, written down. You should be able to hire someone else afterwards and have them understand it.
How a project runs
Four steps, with a fixed figure before any building starts.
You describe the problem
Not the solution. The process as it works today, who touches it, and what goes wrong. Half an hour is usually enough to know whether this is worth doing.
We scope it and quote it
A written scope with a fixed figure and an estimate of elapsed time. If we think the problem does not need what we build, we say so at this point, before you have paid anything.
We build and test on your data
A solution that works on sample data and fails on yours is not finished. Testing happens against the real thing before handover.
Handover, documented
Your team gets the solution and the documentation to run it. Ongoing support is available but never assumed, and never bundled in without you asking.
Built to be handed over.
The measure of good automation is that nobody thinks about it six months later.
Why this and not the cheapest quote
What you are actually paying for.
Enterprise habits, small scale
The same discipline used to build business systems for organisations of 500 to 2,000 users, applied to a problem that might only affect eight people.
Microsoft certified
MCSD App Builder, MCSA Web Applications, and Microsoft Certified Trainer. Dated and listed in full on the About page, including which programmes Microsoft has since retired.
Built to be left alone
Error handling, sensible naming, and documentation. The measure of good automation is that nobody thinks about it six months later.
An honest no
If your licences already cover it, or the process needs fixing before it needs automating, we will tell you. That is cheaper for you than finding out in month three.
One person to talk to
No account manager, no ticket queue, no handoff to a different time zone mid-project.
You own the result
The solution, the documentation and the accounts stay yours. Nothing is built inside a tenant only we can reach.
Questions about Power Platform work
How is this priced?
Per piece of work, against a written scope, not as a monthly retainer. You get a fixed figure before anything starts. If the scope changes mid-build we re-quote the change rather than quietly billing more hours.
Do you work with our existing licences?
Yes, and we will tell you if you are already paying for something that does the job. Most Power Platform work sits inside licences an organisation already holds through Microsoft 365, and the honest answer is sometimes that you do not need us to build anything.
What happens at handover?
You get documentation your own team can maintain: how the solution is structured, what each flow does, where the connections live, and what to check when something breaks. Not a black box that only works while we are on the phone.
Can you fix something someone else built?
Often, yes. Inherited flows that broke after a connector change, apps nobody can edit any more, or a solution that works for one person and fails for everyone else. We will assess it and tell you honestly whether repairing or rebuilding is cheaper.
How long does a typical project take?
A single automation is usually days. A departmental app with SharePoint or Dataverse behind it is typically two to six weeks depending on approvals and access. We give you the estimate with the quote, not after.
Tell us the problem, get a number
Half an hour is usually enough to know whether this is worth doing. If it is not, we will say so.