One fixed day a week
Partner · 1 day a week
Mekova owns your delivery and test automation and grows it with the product. The main package for teams that keep building.
Who it's for
- Teams that keep shipping features (often 20–150 people)
- A pipeline that exists, but that nobody owns
- No full-time platform or DevOps engineer on staff
What you get
- The rhythm: core, broaden, harden, own
- Test coverage keeps pace with new features
- Flaky tests, pipeline speed, dependency and security updates
- Weekly update and monthly review
How it unfolds
At least three months, then as long as you like. Phased, so a new layer lands every week.
- Month 1
Build the core
- CI with lint, typecheck and unit tests as a quality gate
- First deployment pipeline
- PR workflow and branch protection
- Month 2
Broaden
- E2E and integration tests
- Preview and staging environments per PR
- Release automation and rollback
- Month 3
Harden and grow
- Dependency and secret scanning, basic SAST
- Tackle flaky tests, pipeline performance
- Extend coverage across new code
- After that
Own and optimise
- Speed up the pipeline with caching and parallelism
- Developer tooling and delivery metrics (DORA)
- Documentation, plus ongoing tests for new features
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
Introduction
A free 30-minute conversation about your product, team and delivery.
- 2
Scope document
A short document with goals, package, term and arrangements.
- 3
Access
Access to repositories, CI and environments — only what's needed.
- 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.