Who this is for
- IT and digital leaders who want to replace spreadsheets, e-mail approvals or ageing InfoPath and SharePoint forms with real business applications.
- Business units that need an app now, but whose IT department requires it to live inside the company’s security, DLP and lifecycle rules.
- Public-sector and regulated organisations where an application has to meet GDPR and security-compliance requirements before the first user opens it.
- Teams whose makers already build apps and who need professional developers to take over the complex or business-critical ones.
Problems we typically solve
- Critical processes run on Excel files, shared mailboxes or legacy forms that nobody dares to touch.
- Apps built quickly by makers grow into unsupported shadow IT: no environments, no testing, no owner.
- Standard controls hit a limit (a demanding UI, heavy calculation, a legacy back end) and the project stalls.
- Business data sits in SharePoint lists that were never meant to be a relational database.
- Frontline users need something that works on a phone, back-office users need dense data entry, and one app style does not serve both.
What we deliver
- Canvas apps: pixel-precise, mobile-friendly interfaces for frontline and field workers.
- Model-driven apps: Dataverse-native applications for complex back-office data entry, case handling and process management.
- PCF code components: custom controls written in TypeScript and React that makers can reuse across many apps.
- Power Apps Code Apps: React, Angular or Vue applications that run inside the Power Platform boundary with Microsoft Entra ID sign-in and access to the 1,500+ platform connectors. We already use this in pilot projects.
- Dataverse data model: relational tables, row-level and column-level security, designed to carry millions of records.
- Extensions with Azure: Azure Functions, custom connectors and API Management where low-code reaches its limit.
- Power Pages portals: secure external-facing sites for customers, partners or citizens on top of the same Dataverse data.
- Migration from InfoPath and SharePoint: assessment, data migration and a rebuild that uses the platform properly instead of copying the old layout.
How we work
- Discovery and prioritisation. We map processes, users and data, then decide what to build, what to migrate and what to retire.
- Data model first. Dataverse tables, relationships and security roles are designed before the first screen, because they are the expensive part to change later.
- Build in short iterations. Agile delivery with regular progress updates, so users see a working app early and steer it.
- Release through environments. Development, test and production with automated pipelines (see ALM and governance).
- Hand-over and support. Documentation, training for makers and administrators, and ongoing support under an agreed SLA if you want it.