When the process is the product
Some work fits a standard system. Some doesn't because the process is what makes the business distinctive, and bending it to fit a template destroys the thing you're good at.
That's what we build. Model-driven applications on Dataverse, Power Pages portals, automation, and where the user experience needs to be entirely your own, custom .NET front ends reading and writing Dataverse directly.
What we work with
The number nobody puts in the proposal
Most builds are quoted on development cost. Across five years, licensing is usually the larger number and it's set by architecture decisions taken in the first fortnight.
On a production engagement, roughly 100 external users, our client's own customers and their managing contractors access a Dataverse solution. We architected the app boundaries, security roles and feature usage so those users run on per-app licensing rather than premium, reserving premium seats for internal staff. That's what made the client's commercial model viable.
We model licensing alongside the solution, because discovering it afterwards is expensive and very hard to reverse.
Tell us what doesn't fit
The useful first conversation is about the part of your process that no product handles properly. That's usually where the value is.