Services · Interim Management
PM, PO, Solution Architect, CIO/CTO as interim. Monthly packages with defined days per month. A transition arrangement until you fill the role yourself — with handover discipline. We don't turn interim into a long-term relationship. If no handover path is visible after 6 months, we raise it actively.
Managing Directors · Owners
A vacant key position often costs more per month than the interim bridge itself. We staff defined time windows with a clear mandate and fixed days per month. You get a monthly package instead of open-ended daily rates, an effectiveness report instead of a friendly status call, and a clean handover to the permanent hire — with a date.
Department Head · Business Unit
When a project starts to derail or a PM seat wobbles, you don't need a generalist — you need someone who understands the Microsoft situation. We deliver interim PM, PMO reinforcement, or project rescue with a clear mandate, documented outcome report, and a handover date. Steering-committee-ready, defensible internally — with an exit clause, not with an extended engagement.
IT Lead · CIO · Solution Architect
We staff narrowly — where Microsoft-stack understanding and delivery experience make the difference. Topics: Dynamics 365 and Power Platform architecture, ALM pipeline strategy, tenant boundary decisions, Release-Wave discipline, vendor management, architecture board, solution-layering doctrine. Directly at the whiteboard, with code understanding — not a slide-deck manager without stack depth.
For Managing Directors · Monthly packages
Interim engagements are not open-ended hourly billing. You choose a monthly package (typically 4–12 days/month), a mandate objective, and a handover date. What the CFO sees: a predictable line item, no hourly jungle. What the board sees: a defined transition engagement with an effectiveness report instead of a creeping consulting relationship. Extension only on resolution, not by default.
For Department Heads · PMO reinforcement
Deliverables: mandate brief with measurable objectives, monthly steering-committee status, risk matrix, vendor management, documented handover plan to the permanent hire. Plus outcome report for CFO and procurement — so the engagement stays defensible internally. No consultant camping, no creeping extension — end with a date.
For IT leads · 45-min architecture conversation
Whiteboard topics: architecture board setup, solution-layering doctrine, ALM pipeline strategy in Azure DevOps, environment topology and tenant boundary, Release-Wave discipline, vendor and partner management, architecture decisions with ADR discipline, technical onboarding path for the permanent hire. Direct with the architect — no account manager layer.
Four interim roles
Generalist interim agencies staff broadly. We staff narrowly — where Microsoft-stack understanding and delivery experience make the difference.
Project leadership for Dynamics 365 or Power Platform implementations. Steering committee, scope management, risk management, vendor coordination, budget and schedule discipline. Suitable for a sudden loss of PM staffing or external PM need for a time-bound undertaking.
Product ownership for citizen-development programs, center-of-excellence situations, Power Platform backlog management. Maker community build-up, prioritization, stakeholder translation between business and platform team.
Architecture ownership for Dynamics 365, Power Platform, or Microsoft 365 — deliberate design decisions, architecture review board participation, architecture documentation, technology referee between implementation teams.
Strategic IT leadership with Microsoft focus, when the mid-market sits between two permanent CIO phases or the Microsoft transformation needs explicit top-down steering. Board, supervisory board, and investor communication included.
Example packages
One typical monthly package per role. Day counts are adjustable — the packages serve as anchors for sizing. Special arrangements for more intensive phases are possible.
Price on request
Operational project leadership, steering-committee participation, risk-register maintenance, vendor coordination, status reporting. Suitable for ongoing implementation or migration projects of medium complexity.
Price on request
Backlog management, maker coaching, sprint preparation, stakeholder translation, demo and review leadership. Suitable for ongoing Power Platform programs with a citizen-development share.
Price on request
Architecture reviews, design decisions, architecture decision records, technology referee role, architecture documentation. Suitable for strategic programs with multiple implementation teams.
Price on request
Strategic IT leadership, board and supervisory-board communication, Microsoft roadmap steering, vendor strategy, budget responsibility. Mid-market companies in transformation or between permanent appointments.
How we deliver
A good interim engagement has a clean beginning, a productive middle, and a responsible end. We structure the phases explicitly — so that knowledge transfer at the end isn't left to chance.
Weeks 1–2. Reading into documentation and code, conversations with key people, stakeholder mapping, initial status assessment. At the end: jointly defined success criteria for the operational phase and an initial risk register.
Monthly, ongoing. The role is actively performed — along the agreed days per month. Monthly status report, quarterly review with client, ongoing maintenance of the handover pack (so nothing is documented only at the end).
Final 4–8 weeks. Structured handover to internal successor or other provider. Knowledge-transfer sessions, handover pack with open topics and stakeholder landscape, co-pilot phase with the successor. Clean closure.
Frequently asked questions
Typically 1–3 weeks between contract signing and operations start. During this time we read into the material, talk to key people, review documentation and code, and define the first success criteria with you. For very acute situations we can start faster — onboarding then runs in parallel with operational start.
Yes, the monthly packages can be extended. But we deliberately do not recommend an open-ended interim relationship — interim should stay interim. If no handover path is visible after 6 months, we'll raise the topic with you. That's part of our handover discipline.
The final 4–8 weeks of the engagement are explicitly structured as a handover phase. We document ongoing decisions, open topics, risks, and stakeholder landscape in a handover pack. On request, we hand over to your internal successor or to another provider. Documentation is in standard formats, with no lock-in.
Yes. We have experience with corporate structures, matrix organizations, steering-committee logic, and stakeholder management at C-level. Our CMMI-oriented methodology is especially well suited to environments with audit, compliance, or regulatory requirements. For pure startup-velocity roles, other providers are a better fit.
Dynamics 365 (CE, F&O, BC), Power Platform (Apps, Flows, Pages, Copilot Studio), Microsoft 365 (incl. SharePoint, Teams apps), Azure integrations, Copilot and AI strategy. For deep Azure infrastructure roles (DevOps platform engineering, Kubernetes operations) we refer to specialists — that's not our core business.
Related services
Structured second opinion when the role is to be assessed first, not yet filled.
Read more →
When a one-off architecture question needs answering without a long-term interim role.
Read more →
When the task is not a role but a defined implementation initiative.
Read more →
Book an interim conversation
30-min initial conversation — we clarify role, scope, preparation need, and realistic engagement duration. Monthly packages — prices on request. Onboarding sprint in weeks 1–2, structured handover phase.
Take-away · two materials
Two depths for different reading needs. The factsheet is a quick reference (3–5 min) and instantly 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
Compact overview: scope, key metrics, pricing model, process — ideal to forward to CFO, procurement, or the business unit.
15–30 min read · by email after request
Methodology, comparison data, recommendation framework — material for internal argumentation toward stakeholders.
