Your CI was sized for humans.
AI coding tools doubled your pull request volume. Your pipeline didn’t get faster. I halve median pipeline time for engineering teams of 50 to 500 developers in three weeks, or the second half of the fee is refunded.
Read-only. Two days. You get minutes lost per developer per day, in euros, before any money changes hands.
5+ years enterprise DevOps · GitHub Actions, GitLab CI, Azure DevOps, Jenkins · Based in Romania, working UK and EU hours
Companies I’ve worked with
Why now
AI coding tools changed how much code your team pushes. The pipeline it pushes through did not change with it.
Nobody inside your company owns pipeline speed. It’s everyone’s annoyance and no one’s job. For three weeks, it’s mine.
What is your pipeline costing you?
Tap plus or minus, hold to go faster, or type a number. The defaults are typical for a 150-developer team.
€ per year
€2,032,800
Hours waiting per year
25,410
Recovered per year after halving
€1,016,400
Your engagement pays for itself in 3 working days.
How it works
Three weeks, one pipeline, one number at the end. Nothing lands without your team's review.
Bars: median pipeline time in an example engagement.
Rules that hold for all three weeks
-
Pull requests only I never push to the main branch. Every change is reviewed and merged by your team.
-
Read-only diagnostic Access to CI configuration and run history. Nothing executes.
-
Scoped access A named, scoped account on your CI and runner infrastructure. No production credentials, ever.
-
Revoked at handover Access is revoked at handover, and I confirm the revocation in writing.
-
Written every Friday A short report with the minutes. No status meetings.
-
Exports deleted Diagnostic exports are deleted 14 days after the report. I keep only the report.
-
Your NDA I’ll sign it before the diagnostic starts.
-
After handover Questions by email for 30 days, included. No retainer, no upsell.
One CI system (GitHub Actions, GitLab CI, Azure DevOps or Jenkins) and one main pipeline. More pipelines, or more than 500 developers, is a second tier, priced after the diagnostic. No surprises, because I look before I price.
Proof, not promises.
A merged pull request anyone can open is stronger than a quote nobody can check.
Three findings:
- 1 [finding one]
- 2 [finding two]
- 3 [finding three]
The fix is a merged pull request: [link]
Case studies
All case studies
[One sentence a VP Engineering would repeat to their CTO: what was slow, what changed, and the measured number.]
Read the case study
[One sentence a VP Engineering would repeat to their CTO: what was slow, what changed, and the measured number.]
Read the case study
[One sentence a VP Engineering would repeat to their CTO: what was slow, what changed, and the measured number.]
Read the case studyEntries in brackets are placeholders until the first engagement ends.
What engineering leaders say
“[One or two sentences in the client’s words about the measured result and how the three weeks felt.]”
[First Last]
[VP Engineering], [Company A]
“[One or two sentences about access, safety and communication during the engagement.]”
[First Last]
[Head of Platform], [Company B]
“[One or two sentences about the diagnostic and whether the number landed.]”
[First Last]
[CTO], [Company C]
“[One or two sentences about what the team noticed in the first week.]”
[First Last]
[Director of Engineering], [Company D]
“[One or two sentences about the handover: dashboard, runbook, policies.]”
[First Last]
[Staff Engineer], [Company E]
“[One or two sentences about the refund rule and whether it mattered.]”
[First Last]
[VP Platform], [Company F]
Price and guarantee
Start free. Pay a fixed price only for the three weeks, and only in two halves, the second one refundable.
Step 1
CI diagnostic
Free · two days
- Read-only access to your CI configuration and run history. Nothing executes.
- Two days after access: a one-page report with minutes lost per developer per day, in euros.
- The three biggest findings, with the minutes each one costs.
- A yes or no on whether the three-week engagement is worth it for you.
No commitment. Most teams use the report even if they stop here.
What you pay
Half on signing. Half when the measured result is delivered.
No retainer, no hourly billing, no change requests. The scope is the three weeks and the number.
How the result is measured
- Metric
- median pipeline duration on the main branch, queue time included.
- Source
- your CI system’s own run data, exported. Not my dashboard.
- Windows
- the five working days before week 1, and the five working days of week 3.
- Target
- after is 50% of before, or less.
- Miss
- the second half is refunded within five business days. You keep every change that shipped.
Faster runners are the first 40%. I do the rest.
| What you get | Drop-in runners (Blacksmith, Depot) | Your own team | DevOps agency | Me |
|---|---|---|---|---|
| Runner speed and cache | Yes | Yes | Yes | Yes, and I’ll recommend one |
| Test suite, flakes, merge queue | No | When someone finds the time | Sometimes | Yes |
| Measured before/after number | No | Rarely | Rarely | Always, from your CI’s data |
| Guarantee | No | No | No | Second half of the fee refunded |
| Who does the work | Your team | An engineer pulled off the roadmap | Whoever is free that month | The person on this page |
| Time to result | An afternoon, for the first 40% | A quarter, if it starts | 6 to 12 weeks | 3 weeks |
| Price | Monthly minutes | A senior engineer’s quarter | A quote | Fixed, €12,000 |
Who this is for
Saying no to some teams is how the rest can trust the yes.
This works when
- You have 50 to 500 developers.
- You’re on GitHub Actions, GitLab CI, Azure DevOps or Jenkins.
- Your pipeline takes over 15 minutes.
- Your team already uses AI coding tools.
- Someone can grant access within a week.
This isn’t for you if
- You have under 50 developers. Switch runners; you’re done.
- Your procurement cycle is longer than the engagement.
- You want a report instead of changes.
Andrei Badescu
5+ years running CI/CD, Kubernetes and cloud infrastructure for cybersecurity and enterprise software companies at enterprise scale. Pipeline speed was always the thing everyone complained about and nobody owned. I decided to own it.
I work alone, so you get the person who does the work, not an account manager. Based in Romania, working UK and EU hours.
- 5+ years
- enterprise DevOps, CI/CD, Kubernetes and cloud
- 4 CI systems
- GitHub Actions, GitLab CI, Azure DevOps, Jenkins
- Romania
- working UK and EU hours
Replies within one business day.
FAQ
The objections in the buyer's own words, with straight answers.
Can’t we just do this with Claude Code or Copilot?
For the YAML, yes. The result comes from the test suite, the flakes, the runner fleet and the policies, which need access, judgment and someone accountable for the number. I use AI tools myself; that’s why it takes three weeks and not eight.
We already switched to Blacksmith, Depot or self-hosted runners.
Good. You’re the ideal client. The runner was the easy 40%; I do the rest.
What access do you need?
Read-only for the diagnostic. For the engagement, a scoped account on your CI system and runner infrastructure, revoked at handover. Every change goes through a pull request your team reviews.
What if you don’t hit the number?
The second half of the fee is refunded. You keep everything that shipped.
Do you work with Jenkins?
Yes. Jenkins gets the same diagnostic, the same three weeks and the same guarantee: the number is measured on your own Jenkins run data.
Our pipeline is already under 10 minutes.
Then you don’t need me, and I’ll say so after the diagnostic.
How soon can you start?
Diagnostic within two days of access. Next engagement starts [date]. I run two at a time.