For IT

Support and DevOps with an SLA: changes and improvements, month after month.

Monthly DevOps packages for your solutions on Microsoft 365, Power Platform and Azure. We deliver change requests and improvements in Azure DevOps sprints, and the SLA in the contract sets the response times and what we keep running. Including solutions built by someone else.

Discuss a packageThe three phases
  • Annual support contractscontinuing after go-live
  • Managed DevOps in retailwith an SLA, at retail scale
  • SLA in the contractreported monthly

The three phases of taking over support

We take over the solution together with the documentation and procedures of the team that built it.

  1. 01

    We take over operations

    We take over monitoring, releases and open requests, on the Azure DevOps board.

  2. 02

    We document the solution

    The business workflows, the code repositories and the release procedures, documented.

  3. 03

    We run it

    Change requests, improvements and releases, with your approval before production.

  • Change requests

    Each request is estimated and enters the sprint once you approve it.

  • Continuous improvement

    We propose improvements based on how the solution is used and on new platform features.

  • Board in Azure DevOps

    You see every request, its status and who is working on it.

  • Controlled releases

    Every change is checked by automated tests and released to production only with your approval.

  • SLA in the contract

    Response times by severity level and the components we keep running.

  • Up-to-date documentation

    The configuration and the procedures are updated with every change.

What a month of DevOps looks like

One sprint a month, in Azure DevOps.

  1. 01

    The request

    A change or an improvement, from Teams, email or a portal.

    • Teams
  2. 02

    The board

    Estimated, then into the sprint once you approve it.

    • Azure DevOps
  3. 03

    The work

    The senior decides, AI agents implement.

    • Azure DevOps
  4. 04

    The tests

    Automated, then checked by the senior.

    • Azure DevOps
  5. 05

    The release

    Approved by you, documented.

    • Azure

Questions about support and DevOps

What does a DevOps package cover?

Change requests and improvements to your solutions in production, the releases and keeping the solution running, under the terms of the SLA. It is not an end-user helpdesk. Your team sends the requests and we put them on the board. Monthly packages also include technical advice: recurring discussions about the platforms and about preparing the company for AI agents.

What does the SLA cover?

Response times by severity level, support hours and the components we keep running, written into the contract. The monthly report shows how we met them.

How is a change request approved?

We estimate it, you approve it, and it is planned into the sprint. It is released to production after the tests and after you approve the release.

Can you take over a solution built by someone else?

Yes. In the second phase we document the business workflows, the code and the release procedures.

Can we buy the licences from you?

Yes. We are a Microsoft CSP partner.

Workflows that use this solution

Tell us which solution we should develop further.

In 30 minutes we go through the process and agree what to prepare before the project.

Denis Stadler
The first call is with Denis Stadler.Founder · AI Architect & Fractional CTO
Pick a time for a 30-minute call(opens in a new tab)Message us on WhatsApp(opens in a new tab)Call +40 374 616 331