Modern technology, without the experiments
I build on proven enterprise technology that meets real requirements for security, scalability and long-term maintainability. No proprietary traps and no experiments at your expense.
Why this particular stack
Choosing technology isn't a matter of taste. For an internal system, what matters most is whether someone can take it over and keep developing it in five years — and whether the data can be got out if it ever needs to be.
So I build on what already runs in the company. Most clients have Microsoft 365, which means identity, permissions, backup and compliance are already solved. There is no sense rebuilding that alongside.
Where the platform is the wrong fit — typically public portals or unusual integrations — I use a standard web stack instead. The deciding factor is always operability, not what happens to be fashionable.
What a solution is made of
Backend and data
- Dataverse
- A central database for company data with controlled access, relationships between records, auditing and row-level security.
- SharePoint
- Document management, attachments and collaboration around data — and, where Dataverse would be overkill, as the data store itself.
- SQL
- Relational data, warehousing and heavier queries over larger volumes.
- Your existing backend
- If you already run a system with an API, I build on top of it — a new data store is not always necessary.
Interfaces
- Power Apps — model-driven
- For larger Dataverse-backed applications: forms, views, processes and roles. Fast to build and fast to change later.
- Power Apps — canvas
- When one specific task needs a precisely designed interface, typically for mobile or field use.
- Power Pages
- Customer and partner portals with sign-in for external users.
- React and Node.js
- Custom web applications and portals where Power Pages would constrain the result, connected to Dataverse through its API.
Integration
- Power Automate
- Automating steps between systems, notifications, scheduled jobs and approval flows.
- APIs and webhooks
- Connecting internal systems and external services: accounting, stock, e-commerce, time tracking, CRM.
- Data pipelines
- Scheduled transfers and transformations between sources, so reporting never waits on a manual export.
Business intelligence
- Power BI
- Interactive reports and dashboards over the same data the applications run on — with no separate export to Excel.
- The data model
- Agreed metric definitions, so two departments never calculate the same number two different ways.
What this means for you
-
The data stays yours
Everything runs in your own Microsoft tenant. You can export it and walk away at any time.
-
One identity, one set of permissions
Users sign in with the same account they use for Microsoft 365. An employee leaving is an HR process, not a call to me.
-
Handover-ready
Standard technology and documentation mean nothing keeps you with me except being happy with the work.
-
It grows with you
From five users to several hundred without rebuilding the foundations.
Have a specific brief?
Tell me what you need connected or built, and I'll tell you whether it makes sense to solve on the platform you already have.