Services · Development & Customization
When the standard Microsoft applications (Dynamics 365, Power Platform, Microsoft 365) don't suffice, we build further precisely on the Microsoft platform. Instead of custom solutions on the side — clean as an extension in the same tenant, in the same data model, with the same identity and compliance rules.
Managing Directors · Owners
When the standard isn't enough, the question becomes: in-house development, customization, or third-party product? We deliver the build-vs-buy comparison on one page — one-time cost, follow-on cost over three years, risks. Result: a recommendation in euros you can decide on in the advisory board — no consulting folklore and no open hourly volume.
Department Heads · Business Lines
Not every special request needs code. In the Discovery Spike (fixed price, price on request) we cleanly separate configuration, low-code workflow, and real development. You get an outcome report with a use-case list, effort estimate per option, and a recommendation defensible in the steering committee and procurement — including risk notes for the next Release Wave.
IT Leadership · CIO · Solution Architect
We stay on the platform: C# plug-ins, Power Automate cloud flows, PCF code components, SPFx web parts in TypeScript/React, custom connectors. Code quality standards with unit tests, build pipelines in Azure DevOps, solution layering, managed-vs-unmanaged discipline. Directly with the developer team — no account manager in between.
For Managing Directors · fixed price, not hourly billing
Every development engagement starts with a fixed-price Discovery Spike and ends in sprint fixed prices with a clear delivery promise. You know before sprint start what you get and what it costs. The CFO sees no timesheet, just milestones in euros. ROI is quantified in the build-vs-buy comparison — before the first line of code is written.
For Department Heads · Discovery Spike path
In the Discovery Spike (fixed price, price on request) we evaluate your use case for standard, low-code, or pro-code and deliver a documented outcome report. Contents: prioritized backlog, effort estimate per user story, architecture outline, and business-case skeleton. With that you go cleanly into the steering committee and procurement — with clear scope and fixed-price options for sprint 1.
For IT Leadership · 45-min architecture conversation
Topics on the whiteboard: plug-in pipeline stages and async plug-in boundaries, PCF component lifecycle and bundle-size strategy, SPFx tenant- vs. site-scoping, solution layering with managed and unmanaged layers, ALM setup with Azure DevOps pipelines, service principals, and Power Platform build tools. Code quality, unit tests, tenant boundaries — no marketing slides.
Six development disciplines
We don't leave the Microsoft platform. Each of these six disciplines is a supported extension — not a hack alongside the standard, but a building block in the same tenant, with the same identity and the same compliance rules.
Dynamics 365 Customer Engagement: forms, views, business rules, plug-ins, Dataverse schema. We've been building since Dynamics CRM 4.0 — the data model is still the same concept.
Power Apps Canvas for pixel-precise interfaces on mobile and desktop. Ideal for field service apps, inspection workflows, and forms with complex UX requirements.
External portals on Dataverse — for customers, partners, applicants, or suppliers. Authentication via Entra ID External Identities, same data model as the internal application.
Web parts, extensions, and application customizer in TypeScript and React. Cleanly branded intranet, modular content blocks, Microsoft Graph integration without workarounds.
Office.js-based apps for Microsoft Teams and Outlook, complemented by Microsoft Graph for deep integration into calendar, mail, and chat. One of our live references runs Dynamics 365 natively in Teams.
App Service, Azure Functions, and Logic Apps as an extension layer — wherever Dataverse plug-ins or Power Automate hit their limits. Same tenant, same governance.
Methodology
We don't start custom projects on a daily-rate basis. Three phases, each with a clearly defined outcome — you know what you get before the first hour is billed.
Compact sprint with one or two workshops, a senior developer on your use case. The result: a clickable prototype or a technical walking skeleton, a documented data model, and a realistic implementation proposal with a cost frame.
Two-week sprints, weekly demos, continuous deployment into dev and test environments. Solutions as the deployment unit, source code in your repository, ALM pipeline from day one. You see progress live, not in a status report.
After go-live the application moves into our Application Care flat rate — second- and third-level support, Release Wave care, small adjustments without daily-rate arguments. Or your internal team takes over because the documentation supports it.
Example projects
Excerpts from our portfolio — anonymized where clients ask for it, with names where we still serve them today.
Canvas app for around 80 field service reps with offline sync, photo upload, signature capture, and a Dataverse backend. Integration with Dynamics 365 Sales, real-time order processing. Rollout in under four months.
Corporate intranet on SharePoint Online with branded web parts, application customizer for header and footer, Microsoft Graph-driven people finder. Twelve languages, three regions, one codebase.
Our own live reference: Dynamics 365 Customer Engagement natively in Microsoft Teams — contacts, activities, and pipeline without switching browsers. Office.js, Microsoft Graph, and the Dataverse API in one app.
Why stay on the platform
Many custom solutions historically grow next to the Microsoft world: their own web stack, own database, own identity system, own backup strategy. On paper that looks flexible — in practice you pay for identity management, compliance, permission care, and audit trail twice.
Our approach is different: we extend inside the Microsoft platform. A custom app on Dataverse automatically inherits the Entra ID-based permission model, the audit logs, the backup routine, and the compliance certifications of your tenant. You pay once — and gain the custom functionality on top.
The result: less shadow IT, fewer duplicate licenses, less audit effort — and a security model that grows automatically with every Microsoft Release Wave.
We build on the platform, not alongside it. If the standard is enough, we say so. If it isn't, we build the extension in the same tenant, in the same data model, with the same identity and compliance rules.
Frequently asked questions
If your process is a competitive advantage and a standard product flattens that process, customization pays off. If it's only about covering a standard requirement faster (marketing automation, accounting, contract management), take a standard product. We don't build customization that just paints a good Microsoft standard in a different color — we build where the standard has real limits.
We start with a Discovery Spike: five days at a fixed price, ending with a clickable prototype, a documented data model, and a realistic cost frame. A typical canvas app in Power Apps with a Dataverse backend and one or two integrations sits in the EUR 25,000–80,000 range. Larger model-driven applications with plug-ins and SPFx extensions sit higher. The Discovery sets this, not the first phone call.
Yes — and that's an explicit design goal. We document the data model, solutions, plug-in code, and deployment pipelines so your internal team or another partner can take over the solution. We deliver source code into your repository, solutions into your tenant, licenses on your contracts. Vendor lock-in comes from platform choice (Microsoft), not from undocumented custom constructs. Alongside this we offer our Training Subscription for your citizen developers.
When built cleanly, yes. We use only supported customization paths: plug-ins via the Dataverse SDK, Client API for forms, SPFx instead of classic sandbox solutions, Office.js instead of VBA hacks. So when activating the next Dynamics 365 or SharePoint Release Wave there are no surprises — and via Application Care we test every Release Wave in a sandbox before activation.
With a 30-minute discovery call. Then comes the Discovery Spike — five days at a fixed price, one to two workshops, ending with a clickable prototype and an implementation proposal with cost frame. If both sides are satisfied, we move into the implementation phase with two-week sprints and weekly demos. After go-live, Application Care takes over ongoing care.
To take with you · two materials
Two depths for different reading needs. The factsheet is a quick reference (3–5 min) and immediately downloadable. The whitepaper is market education with methodology and comparison data (15–30 min) — you get it by email after a short request.
3–5 min read · direct download · no form
Concise overview: scope, key figures, pricing model, process — ideal to forward to CFO, procurement, or the business line.
15–30 min read · by email on request
Methodology, comparison data, recommendation framework — material for internal argumentation with stakeholders.
Related services
When development is part of a larger implementation effort.
Read more →
When customization primarily means integration to third-party systems.
Read more →
Low-code customization with governance — citizen development with safety rails.
Read more →
Architecture decisions before code — ALM, data model, extension patterns.
Read more →
Discovery call
30-minute initial conversation — we check whether customization is the right path in your case and propose a Discovery Spike. Honest assessment, no pitch. An overview of all services is at Services.
