Skip to content
mekova

Light follow-up after Partner

Delivery Maintenance

Once delivery is stable: maintenance, updates, monitoring, security and test upkeep. Only as a follow-up to a Partner engagement, so the setup is already known.

Who it's for

  • Teams that completed a Partner engagement
  • A product that is stable and changes less quickly
  • Keeping delivery healthy without a fixed day each week

What you get

  • Dependency and security updates
  • Test suite upkeep and flaky tests
  • Pipeline monitoring and small improvements
  • Monthly review

How the arrangements work

Term
Partner packages run for at least three months. You decide how many months; after the agreed period we can extend.
Only hours worked
You pay €95 per hour for the hours actually worked, up to your package's maximum. If an extra hour is ever needed, we agree on it up front.
Monthly invoice
An invoice with a timesheet at the end of each month. Payment within 14 days.
Scale up or down
Switching between 8 and 12 hours a week is possible per calendar month, if we agree on it before that month starts.
Remote, on site by arrangement
The work happens remotely. For a kick-off or an important moment I'm happy to come by.
Contact
Available in your Slack or Teams, a short update every week and a review every month.

How we start

  1. 1

    Introduction

    A free 30-minute conversation about your product, team and delivery.

  2. 2

    Scope document

    A short document with goals, package, term and arrangements.

  3. 3

    Access

    Access to repositories, CI and environments — only what's needed.

  4. 4

    Intake day

    The first working day: review the existing pipeline and tests. The outcome is the backlog.

Are you actively building, and are releases or tests getting harder?

Then this is exactly the right moment. Tell me briefly how you ship today; you'll hear from me within two working days.