Four things we do well.
Each engagement is one of these, or a defined combination. Every one ends with something you can run, read and repeat.
Power Platform design and build
Dataverse and the standard controls take an app a long way. The parts that make it feel finished are the parts they stop at: a board you can drag, a scheduler that understands time, a grid that edits in place, a rule that runs on the server. We design the data model, build the app, and build those parts as custom code that packages and updates like the rest of the solution.
What we build
- Dataverse data models, relationships and security roles
- Model-driven and canvas apps
- Custom Power Apps component framework (PCF) controls: drag-and-drop boards, schedulers, editable grids, visualisations
- Dataverse plugins and custom APIs
- Power Automate flows and custom connectors
- Managed solutions, application lifecycle management and a repeatable, localised release
Product engineering
A defined customer or business problem, taken to a shipped change by the same people who understood it. Discovery, workflow design, an interactive prototype, a written technical design, implementation, tests and a reviewable pull request, then delivery documentation and a handover. Fewer handovers between understanding the problem and solving it, with your review, your quality assurance and your production approval kept where they are.
What we build
- Discovery: a problem statement, scoped requirements, user workflows and acceptance criteria
- Interactive prototypes that settle the design before code
- Feature development with tests and a reviewable pull request
- Regulatory and business-rule change: legislation, funding and claims rules turned into data models, configurable rules and software controls that are deterministic and testable
- Technical investigation: root-cause analysis, a targeted correction and evidence of the result
Azure integration
Interfaces and background processing that connect business systems, built to keep working when the other side is slow, throttled or down. Every integration ships with its failure handling designed, its operational signals in place and evidence of how it behaves under the agreed load.
What we build
- Partner and customer APIs with tenant separation, pagination and capacity checks
- Microsoft Graph and mailbox processing
- Background work on Azure Functions and Service Bus
- Data loads into Microsoft Fabric
- Retries, throttling handling, dead-lettering, logging and alerts
AI enablement
Product and engineering teams that use AI on real work every day, with the habits that keep the output reviewable: clear acceptance criteria, the right context, and a human who reads the result. We set up the tools, package what your team knows about its codebase and domain as reusable skills, connect the workflow to work tracking and documentation, and coach on real tasks until it sticks.
What we build
- Assistant and agent tooling set up for your codebase and your policies
- Reusable, versioned skills for your engineering conventions, your domain and your work tracking
- Workflows from a ticket to a reviewed pull request, with documentation kept current
- Coaching for executives, product leads and technical leads on their own tasks
A first engagement is one complete thing.
One feature, control or integration, with a named reviewer on your side and an agreed acceptance process. Scope, estimated effort and a spending limit are agreed for each project. Production approval and operations stay with you unless a project includes them.
Tell us about the work.
One address reaches the company and the product team.