Starter kits, not finished products.
Working foundations from our own Dynamics 365 and Power Platform delivery. Each one shows the approach and saves weeks of set-up. Then we plan your specific requirements with you, and adapt the kit to fit them.
From kit to your solution
AI-ready means each kit is built so AI can help plan and adapt it. People review every change.
Explore the kit
See it running, read the code, and decide whether the foundation fits.
Plan your requirements
A short workshop maps your rules, data and users against the kit. AI helps us turn that into a gap list and a build plan.
Customise and deploy
We adapt the kit in your tenant, under your publisher, with your security model. You own the result.
Improve continuously
Start with the smallest useful version, then add rules, reports and automation as you learn.
Built with
AI-ready
Ships with a Copilot Studio agent, so rule changes can be planned and drafted conversationally.
Configurable Form Engine
A starting point for moving model-driven form logic out of per-table JavaScript and into Dataverse configuration.
The problem. Every Dynamics 365 project accumulates form scripts: the same "show this, require that" logic written again for each table, and every change needs a developer and a deployment.
What you start with
- One web resource that applies visibility, requirement, editability, default values and value locking from Dataverse records
- Configuration tables and an unmanaged solution to import
- A Copilot Studio agent that drafts rules in plain language and confirms before any write
What we tailor for you
- Rules for your own tables, forms and business processes
- Extra action types your forms need
- Who may change rules, and an approval step before they go live
- The agent’s vocabulary, matched to your terminology
Built with
AI-ready
Built from plain, readable source (PBIP/TMDL and Markdown guides), so an AI assistant can help extend the model and report.
Dataverse Audit Insights
A starting point for turning the Dataverse audit trail into usable reports and a record-restore tool.
The problem. Dataverse records a detailed audit trail, but the audit table is not exposed through the Dataverse (TDS) connector, so most organisations never use it.
What you start with
- A four-page Power BI report: user activity, tables, trends and compliance
- A star-schema model fed from the Dataverse Web API
- A build guide for a canvas app that shows field-level changes and restores previous values
What we tailor for you
- Which tables and columns matter for your audit and compliance needs
- Report pages and measures for your regulators, auditors or adoption goals
- Who may restore values, with row-level security in Power BI
- Refresh, retention and environment set-up for your tenant
Built with
AI-ready
Includes AI build guidance (project instructions and a Power Platform setup skill), so Claude can help adapt it to your tenant.
PP Governance Hub
A starting point for your own Power Platform governance hub, as a lighter, code-first alternative to the CoE Starter Kit.
The problem. Tenant-wide visibility of environments, apps, flows, agents and makers usually means installing and maintaining the full CoE Starter Kit, even when you only need part of it.
What you start with
- Daily inventory sync of environments, apps, flows, agents, connectors, makers and licences into Dataverse
- A findings engine with nine example governance rules (orphaned resources, stale apps, stopped flows, DLP gaps and more)
- A Power Apps Code App to review, acknowledge and resolve findings
What we tailor for you
- Governance rules and thresholds that match your policies
- Notifications and escalation to the right owners
- Your environment strategy, DLP policies and licence cost model
- Tenant set-up: app registration, permissions and scheduling
Starter kits: honest answers
Are these finished products?
No. They are starter kits: working foundations that show the approach and save weeks of set-up. Every organisation’s rules, data and security are different, so each kit is meant to be adapted before it is used in production.
Can we use them ourselves?
The public kits are on GitHub, and your team can explore and extend them. Test thoroughly in a development environment first. The governance hub is not public yet; ask us for a walkthrough.
What does a customisation engagement look like?
A short requirements workshop, a written gap list and plan, then customisation and deployment in your tenant in small increments. You own the resulting solution and source.
What makes them “AI-ready”?
Each kit is structured so AI can help: readable source and build guides, project instructions for assistants such as Claude, and in the form engine’s case a Copilot Studio agent. That makes planning and adapting the kit faster, while people review every change.
Have requirements a kit almost fits?
Tell us what you need. We will show you how close a kit gets, and what tailoring the rest would involve.