Case Study: IT Consultant Reaches €18,000/Month With Retainer Model

Stefan: A Typical IT Consultant Stuck on the Project Treadmill

Stefan (name anonymized) is a self-employed IT consultant based in Vienna, Austria. His focus: IT infrastructure, cloud migration, and system administration for mid-sized companies with 50-200 employees.

When we first spoke with Stefan, he described his situation in a single sentence that every freelancer knows:

"I earn well — but I never know if that will still be the case next month."

For seven years, Stefan had been working as an IT freelancer. One-off projects, one after another. Server migration here, network setup there, security audit over there. His hourly rate: €120. His technical skills: excellent. His business model: a problem.

The Numbers Before the Shift

Stefan's situation in the year before the transition looked like this:

Annual revenue (gross):                    €98,000
Average monthly revenue:                   €8,167
Best month:                                €14,200
Worst month:                               €2,800
Months below €5,000:                       4 out of 12
Time spent on client acquisition:          ~25% of working hours
Evenings/weekends with acquisition stress: "too many"

At first glance, the average looks solid. But the volatility was the real problem: Nearly 80% difference between the best and worst month. Four months below €5,000 meant four months of existential anxiety — even though Stefan earned well on an annual average.

The Feast-or-Famine Pattern

Stefan's year followed a predictable pattern that he himself called "the roller coaster":

Phase 1 — Acquisition (4-6 weeks): Few or no active projects. Frantic networking, writing proposals, cold outreach. Revenue: minimal.

Phase 2 — Project Sprint (6-10 weeks): Two to three projects simultaneously. 60-hour weeks, no room for acquisition. Revenue: high.

Phase 3 — Completion and Void (2-4 weeks): Projects completed, invoices sent, but pipeline empty. Back to Phase 1.

This pattern repeated three to four times a year. And with each cycle, Stefan's frustration grew.

The Realization: Why One-Off Projects Are a Treadmill

The turning point came when a long-time acquaintance — also an IT consultant, but with three steady retainer clients — showed Stefan his numbers. Same qualifications, similar region, but a fundamentally different business model:

Acquaintance (with retainers):
  Monthly minimum revenue (retainers):     €12,000
  Additional one-off projects:             €2,000-5,000/month
  Acquisition effort:                      ~5% of working hours
  Revenue fluctuation:                     Max. 20%

Stefan (one-off projects only):
  Monthly minimum revenue:                 €0 (no guarantee)
  Acquisition effort:                      ~25% of working hours
  Revenue fluctuation:                     Up to 80%

The comparison was sobering. Stefan was not working less or worse — he simply had the wrong model.

The core question Stefan asked himself: "How can I turn my existing clients into long-term partners instead of starting from scratch after every project?"

The answer was not in better acquisition. It was in better proposal design.

The Retainer Strategy: From One-Off Project to Ongoing Contract

Stefan developed his strategy in three steps. The key principle: The retainer is not sold separately — it is positioned as the natural extension of the one-off project.

Step 1: Use the One-Off Project as a Door Opener

Stefan fundamentally changed his project proposals. Instead of offering a self-contained project with a clear end date, he built a "Phase 2" into every proposal:

Old proposal format:

Project: Cloud Migration
Scope: Migration of on-premise infrastructure to Azure
Duration: 8-10 weeks
Price: €18,500 (fixed price)

New proposal format:

Project: Cloud Migration + Ongoing Optimization

Phase 1 — Migration (one-time):
  Scope: Migration of on-premise infrastructure to Azure
  Duration: 8-10 weeks
  Investment: €18,500

Phase 2 — Ongoing Cloud Management (monthly):
  Scope: Monitoring, optimization, security, support
  Start: After completion of Phase 1
  Investment: From €2,500/month (see package options)

The crucial difference: Phase 2 is not a separate proposal that comes later. It is included in the initial proposal from the start — as the logical continuation.

Step 2: The 3-Tier Package Model

For the ongoing management (Phase 2), Stefan developed a tiered package model. Three packages, clearly differentiated, with the goal that the client chooses the middle one:

| Service | Essentials | Professional | Enterprise | |---------|-----------|-------------|------------| | Monitoring & Alerts | Yes | Yes | Yes | | Monthly Health Check | 1x | 2x | 4x (weekly) | | Security Updates | Quarterly | Monthly | Immediate (within 24h) | | Support hours included | 5h | 15h | 30h | | Response time | 48h | 24h | 4h (business hours) | | Strategy call | - | 1x/month | 2x/month | | Disaster Recovery Test | - | 1x/quarter | 1x/month | | Quarterly reporting | - | Yes | Yes + optimization plan | | Dedicated contact person | No | Yes | Yes + backup | | Monthly investment | €2,500 | €7,500 | €12,000 |

The psychology behind it: The Essentials package is intentionally thin — just enough to look serious, but too little for a mid-sized company with serious IT dependency. The Enterprise package is oversized for most. The middle option — €7,500/month — therefore feels like the sensible choice.

Stefan calls this his "Goldilocks pricing": not too little, not too much, but just right.

Step 3: The ROI Calculation in the Proposal

The third and perhaps most powerful component: Stefan adds a concrete ROI calculation to every retainer proposal. Not as a vague promise, but as a traceable calculation:

Cost WITHOUT retainer (reactive):
  Average IT incidents/year:                12
  Average resolution time (reactive):       8h per incident
  Cost per incident (emergency rate €150):  €1,200
  + Productivity loss (estimated):          €2,000 per incident
  = Annual cost of reactive IT support:     €38,400

Cost WITH retainer (Professional package):
  Monthly retainer:                         €7,500
  = Annual cost:                            €90,000
  - Avoided incidents (proactive monitoring):  ~80%
  - Faster resolution of remaining incidents:  50% less downtime
  = Actual savings (downtime avoided):      €30,720
  + Productivity gain (optimized systems):  €25,000-40,000/year

  Net additional cost retainer vs. reactive: €51,600/year
  But: Productivity gain + downtime avoidance: €55,720-70,720/year
  = ROI of the retainer:                    8-37% positive

Why this works: The client does not see "€7,500/month for IT support." They see "an investment that pays for itself through fewer outages and higher productivity." This shifts the conversation from cost to return on investment — a fundamental change in negotiating position.

The First Retainer Win: The Practical Example

Stefan's first retainer client was a mid-sized trading company in Lower Austria. 85 employees, in-house warehousing, heavily dependent on ERP and inventory management systems.

The Starting Situation

Stefan had already successfully completed a project for this company: migrating their local server to a hybrid cloud solution with Azure. Project value: €22,000. Duration: 12 weeks. Result: client satisfied, system running smoothly.

Two weeks after project completion, the expected call came: "Stefan, we have a small issue with the VPN connection. Can you take a look?"

Previously, Stefan would have spent an hour on it, sent an invoice, and that would have been it. This time, he reacted differently.

The Pitch

Stefan resolved the VPN issue (30 minutes, free as a goodwill gesture) and then said:

"This is exactly the kind of issue that will keep coming up. Your new cloud infrastructure needs regular monitoring, security updates, and someone who proactively optimizes the systems. I have prepared three support packages — may I present them to you next week?"

The managing director said yes. Stefan sent a professional proposal with a package structure — Phase 1 (completed), Phase 2 (ongoing support) with the three packages.

The Decision

One week later, the response came: Professional package, €7,500/month, 3-month pilot period.

Stefan had his first retainer. And he had not won it through cold outreach, but through an existing project — exactly as planned.

"The moment the confirmation came in was surreal. I knew: no matter what happens next month, I have €7,500 secured. I had never experienced that in seven years of freelancing."

Scaling: From One Retainer to a Predictable €18,000/Month

After the first success, Stefan optimized his strategy and applied it systematically to additional projects. Within eight months, he won two more retainer clients.

Retainer Client 2: Software Company in Vienna

Background: Stefan had conducted a security audit (project value: €8,500). In the process, he identified ongoing security vulnerabilities that required regular patches and monitoring.

Retainer: A customized package built on the Essentials tier — €4,500/month for security monitoring, monthly penetration testing, and incident response.

Conversion trigger: Stefan showed three critical vulnerabilities in the audit report that would have gone undetected without ongoing monitoring. The potential damage: data loss with estimated costs of €200,000+. The retainer felt like cheap insurance by comparison.

Retainer Client 3: Tax Advisory Firm in Linz

Background: The project was a full IT infrastructure transition from another provider to Stefan's setup. Project value: €15,000.

Retainer: A Professional-style package adapted to the firm's needs (GDPR compliance, client data protection, encrypted communication) — €6,000/month.

Conversion trigger: The firm had previously used an IT provider that only acted reactively. Stefan demonstrated the difference between reactive and proactive IT management using concrete incidents from the client's own history. The question was not whether, but which package.

The Retainer Portfolio After 8 Months

Retainer Client 1 (trading company):         €7,500/month
Retainer Client 2 (software company):         €4,500/month
Retainer Client 3 (tax advisory firm):        €6,000/month
────────────────────────────────────────────────────────────
Monthly Recurring Revenue (MRR):              €18,000/month
= Annually secured:                           €216,000/year

The Proposal Template That Worked

Looking back, Stefan identifies six elements that set his retainer proposals apart from ordinary proposals:

1. Project Results as a Bridge

Every retainer proposal opens with a summary of the completed project — what was achieved, what results were delivered. This reminds the client of the value of the collaboration and creates a natural transition: "The project is done. Now it needs ongoing management."

2. Problem Scenario Without a Retainer

A brief section describes what happens if the client has no ongoing support: systems become outdated, security gaps emerge, small problems snowball into major outages. Stefan uses real examples from the client's industry — not generic scare tactics.

3. Three Package Options

Always three packages, always clearly differentiated. The middle package is the target. Stefan deliberately invests time in naming: "Essentials," "Professional," "Enterprise" — never "Basic," because it sounds dismissive.

4. ROI Calculation

Concrete numbers the client can verify. Before every proposal, Stefan researches industry-specific downtime costs and IT risks relevant to the client. This investment in preparation pays off directly in close rates.

5. Pilot Offer With a Clear Exit

Every retainer starts as a 3-month pilot. After that, it is cancellable monthly with 30 days' notice. This dramatically lowers the psychological barrier: the client is not committing for a year — they are "testing" for three months. The renewal rate on Stefan's pilots: 100%.

6. Professional Design

Stefan uses a professional tool for his proposals instead of Word documents or PDFs. The proposal is interactive, the client can select their package directly in the proposal and sign digitally. This conveys the same quality standard as Stefan's technical work.

Results: Before vs. After

After 12 months with the new model, Stefan's business looks fundamentally different:

Financial Transformation

| Metric | Before (projects only) | After (retainer + projects) | |--------|----------------------|-------------------------------| | Annual revenue | €98,000 | €246,000 | | Monthly minimum revenue | €0 (no guarantee) | €18,000 (retainer base) | | Revenue fluctuation | Up to 80% | Max. 15% | | Acquisition effort | ~25% of working hours | ~8% of working hours | | Average hourly rate (effective) | €120 | €165 |

Personal Transformation

Stefan describes the difference like this:

"Before, I would go to bed on Sunday evenings with a knot in my stomach because I did not know if enough work would come in next week. Today I plan vacations three months in advance. I sleep better. I work less. And I earn more than double."

The concrete lifestyle changes:

• Working hours: From 50-60 hours/week to 38-42 hours/week
• Vacation: From 2 weeks/year (with a guilty conscience) to 5 weeks/year (without pipeline anxiety)
• Weekend work: From regularly to "almost never"
• Financial reserves: From 2 months to 8 months of operating costs

Client Quality

An unexpected side effect: the quality of client relationships has fundamentally changed.

• Price discussions: Used to happen with every project. Now barely at all — the ongoing value is proven.
• Negotiating position: Stefan now actively selects projects instead of having to accept every engagement.
• Referrals: All three retainer clients have actively referred Stefan. Two new project inquiries came solely through referrals.

Stefan's 5 Most Important Lessons

To close, we asked Stefan for his five most important insights:

1. The Retainer Starts in the First Proposal

"Do not wait until after the project to talk about ongoing support. Build Phase 2 into the proposal from the start. The client gets used to the idea that after the project comes support — not nothing."

2. Do Not Sell Hours, Sell Peace of Mind

"No managing director buys '15 hours of IT support per month.' What they buy is the peace of mind that their systems work and they do not have to worry. Frame your proposal accordingly."

3. The ROI Calculation Is Your Best Tool

"Since I started including a concrete ROI calculation in every retainer proposal, not a single client has argued about the price. The numbers speak for themselves — if you put in the effort to research them properly."

More on value-based pricing and how to calculate ROI for your clients.

4. The 3-Month Pilot Is the Secret

"I never say 'sign a one-year contract.' I say 'try it for three months. If it does not work, we stop.' So far, every pilot has been renewed. The barrier drops, the value proves itself."

5. Professional Proposals Make the Difference

"My first retainer proposal was a Word document. It was rejected. The same proposal — virtually identical in content, but professionally designed with an interactive package selector and digital signature — was accepted. Packaging matters."

Conclusion: The Retainer Is Not a Luxury — It Is a Necessity

Stefan's story is not an isolated case. It is the result of a systematic shift in business model — from transactional project work to partnership-based ongoing support.

The key takeaways:

1. One-off projects are a treadmill. Without recurring revenue, you are working against yourself.
2. The retainer is sold in the first proposal — as a natural Phase 2, not a separate product.
3. Three package options shift the question from "yes or no?" to "which package?"
4. An ROI calculation turns the price discussion into an investment decision.
5. The 3-month pilot lowers the entry barrier and proves the value.
6. Professional proposal design is not a nice-to-have — it is part of the persuasion.

Stefan made it happen. And the strategy is replicable and actionable for any IT consultant — and any freelancer with recurring client needs.

The first step? A proposal that does not end with the project. But truly begins there.

Further reading: Retainer Model for Freelancers · Value-Based Pricing in Proposals · Calculate Your Freelance Rate · Create a Project Proposal: Step by Step