
Development has changed, and pricing by time and materials stops adding up when a build that took weeks can be done in days. We come into your practice, set up the way your consultants will deliver from now on, and prove it on a real client build with your people in the seat.
Thirty minutes on what your team is quoting now, and what it would take delivered this way.
Partners we've worked with





Why partners call us
We hear the same four things from practice after practice, in this order.
A decade of Dynamics and Power Platform, delivered without a full-stack developer on the payroll. Low-code first, custom code only when nothing else would do. That discipline is why the practice is still here.
For years the AI in the maker portals was a pane your team closed on sight. In 2026 that changed: Power Platform now drives properly from Claude Code and GitHub Copilot, and what comes out is a normal solution your architects can open and inspect.
A build that was several weeks of effort can now be most of the way there in days. So the worry is no longer technical. It is quoting a number and losing to a firm that quoted a fraction of it, because they are delivering this way and you are not yet.
Everyone billable is billing. The internal upskilling that would answer this has never once reached the top of the list, and it will not next quarter either. That is not a failure of will. It is what a healthy practice looks like.
Technologies we use
Power Platform now has an official plugin marketplace, and it installs into exactly two coding agents. These are the tools we deliver client work with, and the ones your consultants would be working in.
Anthropic's agentic coding tool, and the one the Power Platform plugins were built against first. Tables, flows and apps come out as a normal solution you can open in the maker portal afterwards.
The same Microsoft plugins, in the agent your tenant may already licence. Several models sit behind it, so a client who wants to stay inside Microsoft's own procurement can.
Microsoft publishes both as the Power Platform Skills marketplace. See it on Microsoft Learn
And it stays that way
There is no non-chargeable bench to send on a discovery mission. The work that would change how you deliver competes with the work that pays this month, and loses.
A hundred pages of Learn and no reliable way to tell what is new since the last release. Official courses that do not cover the authoring experience your team would actually be using.
Plenty of people are enthusiastic in public about things that fall over on a real tenant. Knowing which capability is genuinely ready, and which is a year away, is a full-time job.
The outcome
Installed in six weeks. Yours afterwards.
Not a retainer and not a course. We come into your practice, set up the way your consultants will deliver from now on, and prove it on a real build with your people in the seat. When we leave, the system stays.
Week 1
Audit
Weeks 2 to 5
Install
Week 6
Handover
Rebuild the quick-start package as a model-driven app on Dataverse, to our conventions. Client demo is Friday.
Reading the existing solution and your conventions skill. Planning tables, forms and the approval flow.
Six tables, one app, one flow, in your solution layer. Nothing custom-coded. Ready for your review before it goes to the client.
Solution pipeline, environment variables resolved, your conventions applied. Reviewed by your architect before Friday.
Week 4 · your team, our review
Illustrative. Not any client's build.
After the six weeks
Most partners will not need us every month once the system is in, and we will say so. For the ones who want us close as Microsoft keeps moving, the Partner Capability Retainer keeps the channel open.
Channel
Unlimited, asyncAnswered the same day
Client wants this live Friday. Does the pattern we have survive a tenant move?
No. Here is the version that does, and what to tell them about Friday.
PCRebuilt it. Demo went out this morning.
Days
Each month, on your work
As many as the work needs, agreed up front.
Review
Before your client sees it
Platform
Your whole team, all month
Build your first Copilot Studio agent
25 XPModel-Driven Masterclass
How partners start
01 · Start
Two weeks. How you deliver today, our honest recommendation with the trade-offs, and a 90-day roadmap. Yours whether or not you go on.
02 · Build
Six weeks. Installed on your live client work, measured against a number set in week one, and yours afterwards.
03 · Keep
Monthly, and optional. Days with your team, architecture review before a build reaches a client, and a named channel.
Also available, though neither leaves a system behind: delivery days and consultant training. We will tell you on the call if one of them is the better fit.
You pay, we do the work. If you are not happy with the work, we will work to put it right. If you are still not happy, you receive a full refund.
It goes in writing into every proposal, partner engagements included.
No. The AI Delivery System™ is six weeks, a fixed price, and an outcome written into the proposal, and then it ends. Every partner we speak to says a version of the same thing: help us get set up properly and get going, and we will be self-sufficient after. That is exactly what it is built for. The retainer exists for afterwards, for partners who want us close as Microsoft keeps moving, and it is optional.
No. That is the question every partner asks first, and the answer has genuinely changed. Remembering syntax is not the skill any more. Judgement is: knowing which tool to reach for, what a good solution looks like, and when the output is wrong. Your architects already have that. If your team has spent ten years deciding when config beats code, they are better placed than a developer who has not.
No, and we will not tell you to on day one. The audit exists to understand why you chose what you chose: some tools have better collaboration, some have a phone app your team lives in, some are hosted outside the EU in a way a client will care about. Where the reason is real, we build the system around your tool. Where the reason is habit, we will say that too, and show you what the native plugins give you that stitching things together does not.
Some of it is ready and some of it is not, and the difference is the whole value of the engagement. We deliver client work this way, so when we say a capability is ready you are hearing it from someone carrying the risk of being wrong. When something is not ready, we will say so and tell you what we would use instead. You should expect that answer more than once.
Then start with the audit: two weeks, fixed, and you get our honest read of how you deliver now, which tools fit your practice, and a 90-day roadmap you can run yourself. It is yours either way, and it counts towards the System if you go on. What we would push back on is the assumption that a couple of days finishes it. Getting set up is the easy half; the questions that matter turn up in week three, on a real client build, when the pattern you chose meets something it was not designed for. That is what the six weeks are for.
The system stays and you run it. That is the intended ending, not a loose end. Some partners want nothing more than platform access for the team and a way to reach us when something new lands, and we will say so if that is you. Some want us close for a while, and that is what the retainer is for. Either way we raise it before you have to.
Yes, and that is an argument for a system rather than a course. A fixed syllabus is out of date the month after it is written, which is why the official material is always a release behind. The system is built so your team can absorb what lands next without us. Staying current is our job, and if something significant ships mid-engagement, we bring it to you rather than waiting to be asked.
Consultancy that leaves your team more capable. We do not run a curriculum at your people. We work on what is actually in front of them, and the learning is a side effect of having been in it. If what you want is a room, an agenda and labs, that is a custom workshop and we do those too.
Up to fifteen of them, included, for the six weeks and three months after: the pro courses and the community. It is there so the reference material outlives the engagement. It can also be bought on its own if the System is not what you need.
We work with several partners, and we are careful about it: nothing from your delivery, your clients or your commercials goes anywhere else. Most of our work arrives through partners, and it travels both ways. When something lands that belongs in your practice rather than ours, it comes to you.
Nothing to prepare. At the very least you will come away with a clearer view of where your practice stands on AI-assisted delivery than when you started. If we are not the right fit, we will say so.
Book a discovery callWant to see how we think first? Watch the free tutorials
The AI Delivery System™, installed in six weeks.
Book a discovery call