Services · Managed Services
Whether Microsoft Dynamics 365, Power Platform, a web app, or an Open AI integration — applications keep living after go-live. Updates arrive twice a year, new requirements quarterly, new employees monthly. Application Care is our monthly flat rate that keeps us with you after the project ends — three tier models (Essential · Advanced · Premium, prices on request), clearly calculated, cross-platform, with priority handling.
Managing Directors · Owners
Three clearly calculated service tiers (Essential · Advanced · Premium, prices on request) with a fixed monthly fee. No surprises, no escalation hours, no support calls during lunch. You budget the IT cost and get measurable availability (SLA, quarterly incident report) — like an insurance policy.
Department Heads · Business Lines
Quarterly review with concrete optimization recommendations — what runs well, which processes stall, which Microsoft update is worth adopting. Skill development for your key users via accompanying training sessions. Includes Release Wave tests before rollout (Dynamics 365, Power Platform).
IT Leadership · CIO · Solution Architect
Tenant hardening, ALM pipeline maintenance (Azure DevOps / GitHub), Release Wave regression tests, customization refactoring, code reviews. Direct Slack/Teams channel to the responsible architect — no ticket-to-first-level-support ping-pong. DORA metrics in the quarterly review.
For Managing Directors · predictable monthly flat rate
Essential (up to 25 users) · Advanced (26–100 users) · Premium (100+ users) — three calculated monthly flat rates with guaranteed response times and hour quotas, prices on request. No escalation hours, no surprise invoices, no open consultant accounts. You budget application costs like an insurance policy and get measurable availability (SLA, quarterly incident report). What the CFO sees: one line item, one amount, one person responsible.
For Department Heads · quarterly review for the CFO
Every quarter a structured review report: which tickets handled, which process bottlenecks identified, which Microsoft update pays off for the business line, which adoption gaps remain. Plus a business-case skeleton for the next expansion — ready for CFO, procurement, and steering committee. Accompanying key-user training measurably lifts adoption, Release Wave tests prevent rollout pain in front of the business line.
For IT Leadership · Release Wave and DORA metrics
Release Wave tests before each rollout (Dynamics 365, Power Platform), documented ALM pipeline (Azure DevOps / GitHub Actions / Power Platform Pipelines), tenant hardening and DLP policy care, customization refactoring. DORA metrics in the quarterly review (lead time, deployment frequency, change failure rate, MTTR). Direct Slack/Teams channel to the responsible architect — no first-level ping-pong.
What Application Care means
Application Care is not "support, but monthly". It's the deliberate transition from project mode into ongoing operations and continuous improvement. Three distinctions matter — they show what Application Care delivers and what it isn't.
Application Care is not pure support. Classic Microsoft Dynamics 365 support is reactive, without guarantees, billed hourly. Application Care is proactive with a guaranteed hour quota, priority handling, and a fixed quarterly review. The reactive part is included, but it's only one element.
Application Care is not an implementation project. If you want to introduce a new Microsoft Dynamics 365 module, build a standalone Power App, or set up a new interface — that's a project, not an Application Care line item. We separate this deliberately so the monthly operations budget stays predictable.
Application Care focuses on platform care. Accompanying updates, fixing bugs, maintaining permissions, training new employees, implementing small requirements. Structural architecture advisory — the question "should we set up the platform stack completely differently?" — belongs to our Architecture & Strategy sub-pillar, not here.
Three Application Care models
Which model fits depends on how business-critical your implementation is and how actively you keep evolving it. We typically recommend the middle model — Essential is often too tight, Premium only makes sense for complex setups.
Price on request / month · up to 25 users
The entry model for stable, slow-changing implementations. 4 hours per month are enough for bug fixes, small adjustments, permission care, and the quarterly review.
Price on request / month · 26–100 users
Our recommendation tier for running Microsoft Dynamics 365 or Power Platform implementations with active evolution. 16 hours give room for smaller enhancements and robust update management.
Price on request / month · 100+ users
For complex setups with multiple Microsoft Dynamics 365 apps, intensive Power Platform use, or a fast-growing user base. 40 hours per month cover larger adjustments without project overhead.
What's included in Application Care
Microsoft publishes a Release Wave twice a year with feature additions and (rarely, but real) breaking changes. We check your customizations before each wave date, document affected spots, adjust what's necessary, and test in your sandbox setup.
Functional errors, broken workflows, plug-in pipelines that suddenly overwrite values after an update. We reproduce, identify the cause, fix the error, and document — so the same fault doesn't happen twice.
A new field, a new view, a small workflow extension, an additional Power Automate flow. Within Application Care without project overhead — as long as the effort fits within the monthly quota. Larger requirements go into a separate implementation contract.
We keep an eye on platform telemetry: API calls, storage usage, custom plug-in performance, error rates. We flag anomalies proactively — before you hear about them in the management meeting.
An onboarding block per new employee wave: what's the platform logic, where to find what, how to set permissions. Standard in Advanced and Premium, billed from the hour quota in Essential.
Once per quarter a structured review: what we've delivered, where bottlenecks are, what's coming with the next Release Wave, which optimization recommendations the telemetry suggests. On-site, online, or hybrid.
What's not included in Application Care
We deliberately separate Application Care from three other service categories. This keeps the monthly budget predictable and avoids the creeping scope expansion that service contracts often experience.
No greenfield implementations. A new Microsoft Dynamics 365 app (e.g., Field Service rolled out), a standalone Power Platform project with its own data model design, a new Power BI suite — these are implementation projects. We calculate them as fixed price or T&M, not from the Application Care hour quota.
No big-bang migrations. Switching from Microsoft Dynamics 365 Online to on-premises (or vice versa), tenant consolidation after a corporate acquisition, major version migrations with data flow restructuring — such projects need their own architecture phase and team. Application Care complements them, it doesn't replace them.
No strategic architecture advisory. "Should we stay on Microsoft Dynamics 365 or switch to SAP?" — that's Architecture & Strategy. We do that gladly, but in a separate consulting format, not out of the Application Care hour quota. Sub-pillar Advisory & Architecture.
Frequently asked questions
Application Care is a monthly service contract with a guaranteed hour quota and priority handling for running Microsoft Dynamics 365 and Power Platform implementations. Response within 4 hours during business hours, with clearly defined contents — updates, bug fixes, small new requirements, training for new employees, quarterly review.
Pure support is reactive and billed hourly (pay-per-hour). Application Care is proactive — with a guaranteed quota, priority over pay-per-hour requests, fixed quarterly reviews, and automatic Release Wave adjustment. We recommend covering business-critical implementations with Application Care.
Three models — Essential (up to 25 users), Advanced (26–100 users), and Premium (100+ users), tiered by hour quota and response time. All with response under 4 hours during business hours and automatic Release Wave support. Which model fits depends on the complexity and business criticality of your implementation. Prices on request.
Three things deliberately not: first, completely new implementations (a new Microsoft Dynamics 365 app, a standalone Power Platform project) — we calculate these as an implementation project. Second, major migrations (switching license classes, tenant migration). Third, strategic architecture advisory — that sits in our Architecture & Strategy sub-pillar.
Overflow hours are billed at the agreed preferred rate (discounted versus standard pay-per-hour). Alternatively we upgrade you to the next tier. We review consumption in the quarterly review and propose a timely adjustment.
Yes, this is actually one of our most common entry points. We take over the care of existing Microsoft Dynamics 365 and Power Platform implementations from other partners. A free code review in the initial conversation clarifies whether the takeover is realistic and which pre-cleanup may be needed.
Standard Application Care covers 8 AM – 6 PM CET. For 24/7 readiness (e.g., for business-critical B2B portals or manufacturing environments), we offer extensions or refer to our Strategic Care contract with a dedicated on-call team. We calculate this extension individually.
To take with you · two materials
Two different 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 TCO calculation (15–30 min) — you get it by email after a short request.
3–5 min read · direct download · no form
Three SLA tiers (Essential · Advanced · Premium, prices on request), four delivery areas, three reasons for arades — compact on two pages. Ideal to forward to CFO, procurement, or IT lead.
15–30 min read · by email on request
Methodology, TCO calculation for 50/100/250 users, four migration patterns from the hourly model, 18-point take-over checklist, four common objections with honest answers. Material for internal argumentation with CFO and stakeholders.
Related services
When knowledge about the existing solution needs to be reconstructed before ongoing care.
Read more →
Structured system capture before engagement handover — the entry point into Application Care.
Read more →
Targeted diagnosis when a technical baseline makes sense before ongoing care.
Read more →
When alongside the service a steering role also needs to be filled temporarily.
Read more →
30 min · open-ended · no obligation
Bring your Microsoft Dynamics 365 or Power Platform situation to the initial conversation. We recommend concretely — sometimes Essential is enough, sometimes Premium is needed, sometimes we actively advise against a contract and suggest consolidation first.
