Find out what your licence can already do.
Book a free 30-minute call. Tell me what's slow, and I'll tell you what your Microsoft stack could be doing about it. Local and want the on-site version? I'm a Christchurch-based Power Apps developer.
Most NZ firms use a fraction of what's in Microsoft 365. The rest is apps, automated workflows and agents nobody's built yet. That's what I build.
Job intake, inspections, approvals, asset tracking. Apps your team opens on a phone, backed by SharePoint or Dataverse, built around how the work actually flows.
The invoice that files itself, and the Monday report that is already sitting there when the meeting starts. Flows that quietly remove jobs from someone's plate.
Agents that answer staff questions from your own documents, triage enquiries, and hand off to a human when they should. Built with proper guardrails, not bolted on. The reading order: Copilot vs a Copilot Studio agent, the pricing, the use cases, grounding without leaks.
Your SharePoint is already a database. Lists, libraries and structure that make it the backbone for apps and automation, instead of a folder graveyard. If the data is stuck in an old SQL Server or Access system, I move it in at a fixed price; the migration hub shows how, per source.
Power Apps has edges. When you hit one, I write the custom component, the API connector, or the standalone tool. No second consultant required.
Inherited a flow that breaks every month, or an app only one person understands? I audit, fix, document and hand it back maintainable.
What makes me different is that I build Power Apps and I write proper code. That matters because the right answer is sometimes neither one alone. Low-code shops sell Power Apps for everything, and the dev shop down the road will quote you a custom build for the same job. I get paid the same either way, so I'll tell you where each one wins.
The licence is on your bill right now. Most of what I build runs on it as-is, and where premium features cost extra, you'll know the number before we start.
Apps, flows and agents run inside the environment your business already trusts. No third-party platform holding your client data, no new vendor to vet.
My day job is building this stack for a large NZ healthcare organisation. Governance, permissions and documentation are the default here.
Often no. A lot of useful work runs on the standard Business licence you already have: SharePoint lists, standard flows, Power Apps against SharePoint data. Premium connectors, Dataverse and Copilot Studio have their own pricing, and I'll put the exact licensing cost in front of you before any build starts. No surprises on the first invoice.
SharePoint, until it isn't enough. For most firms under 50 staff, SharePoint lists handle the job and cost nothing extra. Dataverse earns its licence fee when you need relational depth, row-level security, or serious volume. I'll tell you which side of that line you're on. It's usually the cheap side.
The standard engagement is 4–8 weeks to working software, and smaller ones land at the short end. A focused app on SharePoint data is a short-end job; something with flows, approvals and an agent on top runs the full range. You see it working early and test it on real jobs while it's still easy to change.
Yes, and it's a common ask. Half-built Power Platform setups are everywhere: a flow that breaks monthly, an app one person understands. I'll audit what's there, fix what's worth fixing, and rebuild what isn't. You get documentation either way, so it never depends on one person again.
Microsoft prices Copilot Studio by consumption, in Copilot Credits rather than per seat, and for a small firm's realistic usage it's usually modest. An agent isn't always the right tool either. Sometimes a plain automated flow does the job for less. I'll cost both options before you commit to either.
No. Low-code wins on speed and cost when the problem fits its shape. When it doesn't, forcing it gets expensive and slow. I write custom code as well, so my recommendation isn't bent by what I'm able to build. If custom is cheaper over three years, that's what I'll tell you.
Book a free 30-minute call. Tell me what's slow, and I'll tell you what your Microsoft stack could be doing about it. Local and want the on-site version? I'm a Christchurch-based Power Apps developer.