Autonomous MSP — Command Center
4
Active Channels
3
Pilot Spots Q2
78+
Posts Planned
€19.5k
Pilot Price
Community

Autonomous MSP on Skool

skool.com/autonomous-msp-2162

5 spaces live: Start Here, AI in the Wild, Build With Me, Ask Edy, Pilot Program.

Status: Live and public. Founding members: Vijay + Umang invited.

LinkedIn

Profile Updated

Headline, About section, and Featured links updated.

4 campaign posts scheduled. Substack summary post every Tuesday 8am CET.

LinkedIn CSV export requested — process with outreach_system.py when received.

Substack

Weekly Technical Articles

eduarddulharu.substack.com

Publish every Monday morning. LinkedIn summary follows on Tuesday.

Save drafts as Substack/{week}/*.md so they appear in the Calendar workflow.

Pilot Offer

€19,500 — Founding Client Rate

8-week structured engagement. 3 on-site days (all Europe).

3 tracks: Autonomous NOC · Compliance Automation · Alert Intelligence.

Standard rate from Q3 2026: €45,000+. File: pilot-offer.html / .pdf

Next Actions

Do These Now

1. Publish Post 1 on LinkedIn — Friday 8am CET
2. Wait for LinkedIn CSV — run outreach_system.py
3. Post Week 1 content in Skool spaces
4. Send pilot offer to any MSP lead who replies
5. Follow up with Vijay and Umang after they join

Type B — Cold MSP Owner / IT Director

4-Message Sequence
Message 1 — Connection Request
Send with connection request. Max 300 characters.
Hi [Name], I work with MSPs building AI-powered NOC and compliance operations in DACH. Your profile caught my attention — would be good to connect. — Eduard
Message 2 — First DM After Accepting
Send within 24 hours of connection accepted.
Hi [Name], thanks for connecting. Quick question — what's your biggest operational headache right now? Alert volume, compliance pressure, or just not enough hands on deck? Asking because I work exclusively with MSPs on exactly these problems and the answer is usually different than people expect. — Eduard
Message 3 — Value Follow-Up
Send 5 days after M2 if no reply.
Hi [Name], following up briefly. I recently documented how a small MSP team went from 847 alerts per night to a system that handles triage automatically — thought it might be relevant for you. I share this kind of case study inside a free community I run for MSPs: skool.com/autonomous-msp-2162 No pitch — just operators sharing what works. — Eduard
Message 4 — Breakup Message
Send 5 days after M3 if no reply. Then stop.
Hi [Name], last message — I won't follow up after this. If alert fatigue, compliance pressure, or staff shortage ever becomes the priority — I'd be glad to help. You know where to find me. — Eduard

Type A — Warm Contact (ex-colleague / known person)

1 Message
Community Invitation
Send directly — no connection request needed.
Hi [Name], I've been building something I think you'll find genuinely useful. It's called Autonomous MSP — a professional community for network and security engineers building AI-powered operations. Real case studies, live builds, no fluff. I'm personally inviting a small group of people I respect as founding members — with lifetime free access. Here's the link: skool.com/autonomous-msp-2162 Would love to have you in there. — Eduard

Type C — Post Engager (liked / commented on LinkedIn post)

1 Message
Community Invite After Engagement
Send within 24 hours of their like/comment.
Hi [Name], thanks for engaging with my post. I run a community specifically for people dealing with exactly what I was describing — Autonomous MSP. MSP owners and IT leads building AI-powered NOC/SOC/compliance operations. Free to join, no pitch: skool.com/autonomous-msp-2162 — Eduard

March 2026

Full posts written
The 5-Agent NOC: How It Works (Part 1 of 5)
Full architecture walkthrough. Agent 1 (monitor) and Agent 2 (triage) explained with real metrics — 847 alerts reduced to 12 actionable in one shift.
The Friday Night Incident — 847 Alerts, 1 Engineer
Real incident story. How the autonomous NOC handled triage while the on-call engineer slept. Detection to resolution: 8 seconds vs 4 hours manual.
Why I Use Qwen 2.5 14B for NOC Tasks (Not GPT-4)
LLM selection framework for MSPs. Local vs cloud. Why fine-tuned open-source beats frontier models for structured network tasks. Cost comparison table.
NIS2 Compliance Agent: 23 Gaps Found in 4 Minutes
Live demo of AI compliance checker running against a real MSP environment. What it found, how it scored, and what a human auditor would have missed.
🛠️
Build #1: Anomaly Detection Agent from Scratch (Parts 1 & 2)
Complete working Python code. Telemetry schema, baseline model, agent loop, Zabbix connector, and synthetic data generator. No cloud, no API costs.
🙋
How many alerts does your NOC handle per day?
Weekly prompt. Gets members talking, surfaces real pain data, positions Edy's 5-agent NOC as the solution.
🙋
What's your worst on-call nightmare story?
Community story prompt. Builds trust, surfaces incident patterns, provides case study material for AI in the Wild posts.
🙋
If you could automate one thing tomorrow — what would it be?
Surfaces the highest-value automation opportunities across the community. Answers become Build With Me topics.
🙋
How many tools does your NOC stack use?
Tool sprawl survey. Reveals integration complexity. Sets up discussion about AI as the unifying layer above multiple monitoring tools.
🔒
Q2 Pilot Availability — 3 Spots, 2 Remaining
Monthly availability update. Creates urgency. Describes 3 tracks and outcome. DM to apply.
🚀
Member Spotlight #1
Feature the first active member. Ask them 3 questions about their MSP challenges. Builds community identity and rewards engagement.
🚀
March Digest — Best of This Month
Roundup of top posts, member questions, and key insights from the month. Rewards members who engaged, surfaces best content for new joiners.
April — August 2026

Months 2–6: Topics Planned

66 additional posts planned with titles and descriptions. Open content-calendar.md for the complete calendar including all months.

Key themes: 5-Agent NOC series completion (Parts 2-5), DORA/NIS2 deep dives, LLM fine-tuning walkthrough, digital twin series, ConnectWise/Autotask integrations, 6-month results post.

This Week

Outreach Roadmap

6 Milestones
0
Published
3
Ready to Post
1
In Draft
€60
Boost Budget

Authority Anchor

READY
I tried to get a PhD in AI. Two times actually. First time was in 2001 right after I graduated. It didn't happened – work got in the way. Second time, in 2017, I was seriously considering it again. A PhD student at TUM Munich told me something that I still remember: "Eduard, is better to build real AI systems than to write papers about them." I took that advice. Then in 2022 I was preparing for my 3rd CCIE lab attempt. And I stopped. I realised I was optimising for a world that is already changing – fast. So I chose AI instead of the lab. All in. 25 years of networks. Started with missile and radar systems and NATO communications in Romanian military. Then 10 years at AT&T designing infrastructure for European banks and telcos. Kyndryl after that. Hundreds of enterprise environments across Europe. In 2018 I stood on a stage in Berlin and told a room of network engineers that ML will transform how we run critical infrastructure. In 2019 in Munich I showed how a trained neural network can predict and prevent failures in IP networks before they happen. Most of them didn't believe me then. Last year I built a 5-agent autonomous NOC – locally fine-tuned LLMs, no cloud dependency – that detects and resolves network incidents in seconds. Then a SOC system. Then a digital twin with 3 layers of validation before any change touches production. Then an AI security and compliance scanner that runs MITRE and NIST checks automatically. What human engineers were doing in days, the systems do it in minutes. No PhD. No research lab. Just 25 years of real networks and an obsession that never went away. Now I am building a community for MSP owners and IT consultancies that feel the same – that the ground is shifting and the old ways will not scale anymore. Is called Autonomous MSP. Is free to join. Link in bio.
Boost Settings

Budget: €60 total / 7 days  ·  Audience: MSP owners, IT directors, CTOs  ·  Seniority: Director, VP, C-Suite  ·  Company size: 11–200 employees  ·  Geography: DACH + US + UK  ·  Audience size: ~840K

The Pain Post

READY
A 3-person MSP. Friday. 11pm. 847 alerts in the queue. 3 active incidents. 1 engineer on call. A bank client on the phone. This is not a horror story. This is Tuesday for most MSPs I talk to. And here is what nobody says out loud – the engineer is not slow, is not bad, is not "not enough". The environment is just growing faster than any team can hire. In the last 5 years the average MSP environment complexity increased 3x. The alert volume increased 5x. The headcount? Maybe 1.3x if they were lucky. You cannot hire your way out of this. The math doesn't work. Alert fatigue is not a people problem. Is an architecture problem. The MSPs that will survive the next 5 years are not the ones with more engineers. Is the ones with better systems. AI-powered NOC that triages automatically. Agents that resolve before the human even sees the alert. Compliance checks that run without someone spending 3 days in spreadsheets. I am building exactly this – and I document everything live inside Autonomous MSP community. Free to join. Link in bio.

Manager of Agents

READY
Nobody talks about what happens to the engineer after the NOC automates itself. I will tell you what I think. You don't get replaced. You get promoted. From managing routers to managing the agents that manage the routers. Think about it like this – 20 years ago the network engineer was manually configuring every interface. Then came templates, then automation, then intent-based networking. Each time, the engineer didn't disappear. They moved up one layer. AI is just the next layer. The engineer who understands how the AI agent makes decisions, when to trust it and when to override it, how to train it on your specific environment – that person becomes the most valuable in the room. Not because they write Python. Because they understand what the agents should and should not do. I call this the "Manager of Agents" role. And I think every serious network and security engineer needs to start thinking about this transition in the next 2-3 years. Is not optional. Is the same as when routing protocols replaced static routes. You adapt or you fall behind. The good news – you already have the hardest part. 10, 15, 20 years of real network experience. That knowledge is exactly what makes a great agent manager. The AI doesn't know your environment. You do. I built Autonomous MSP community specifically for engineers and MSP owners making this transition. Is free to join. Link in bio.

Proof Post — Live Demo

DRAFT
DRAFT — To be written after Cisco DevNet podcast. Content brief: Live demo of the 5-agent NOC. Reference the podcast appearance. Show real metrics — detection to resolution time. End with community link and pilot CTA.
Posting Schedule

March 2026

Mar 13 (Fri) — ASAP: Post 1 — Authority Anchor · Boost with €60 / 7 days
Mar 16 (Mon) — 8:00am CET: Post 2 — The Pain Post
Mar 18 (Wed) — 8:00am CET: Post 3 — Manager of Agents
Mar 20 (Fri) — 8:00am CET: Post 4 — Proof Post (draft — write after DevNet podcast)

Name Company Title Type Status Added Notes

Loading contacts...

1

Install dependencies

Open a terminal in E:\vExpertAI\SKOOL\ and run:

pip install anthropic python-dotenv tqdm

2

Set your Anthropic API key

Create a file called .env in E:\vExpertAI\SKOOL\ with this content:

ANTHROPIC_API_KEY=sk-ant-your-key-here

Get your key from console.anthropic.com → API Keys.

3

Place your LinkedIn CSV

When LinkedIn sends the email, download the archive, unzip it, and copy Connections.csv to E:\vExpertAI\SKOOL\

4

Configure warm contacts (optional)

Open outreach_system.py and edit the top section:

WARM_COMPANIES = ["AT&T", "Kyndryl", "Infosys"]
WARM_CONNECTIONS_BEFORE = "2024-01-01"

Contacts from these companies or connected before that date get the warm invite instead of the cold sequence.

5

Run the script

cd E:\vExpertAI\SKOOL
python outreach_system.py

The script processes every contact and generates personalized messages. Takes ~1 second per contact (API rate limiting).

6

Review output

Open outreach_ready.csv in Excel or Google Sheets.

Filter by Action = warm_invite — send those first (they know you).
Filter by Action = cold_sequence and Relevance = high — these are priority MSP/consultancy targets.

Always review and personalise before sending. Never copy-paste blindly.

7

Send 10 per day maximum

LinkedIn's safe manual outreach limit is 10–15 messages per day.
Exceeding this risks account restriction.

Suggested daily routine: 10 connection requests + 5 follow-ups = 15 actions/day = 75/week.