We teach different things
Your courses teach something my students need next. Mine teach something yours need. We point at each other, and we say so on the page.
Partners
Partner with me
I teach WebRTC. I don't teach SIP, and I don't teach the dozen other things a real-time engineer ends up needing. That's what partnerships are for: training companies whose material picks up where my curriculum stops, so an engineer can go deep on both without me pretending to cover ground I don't cover.
The shape of it
What a partnership here actually is.
A discount that is real
Students get a code that saves them money rather than a referral link dressed up as a benefit. If there's nothing in it for the engineer, there's no reason for the partnership.
Separate from sponsorship
Sponsoring bloggeek.me is a different thing with its own rates. It doesn't buy a place here, and being a partner doesn't buy coverage in my analysis.
Who is here now
Current partners.
Both teach SIP, which is what a lot of WebRTC actually sits on once it meets a real network.
The SIP School
SIP training and certification. The SSCA certification is the one most people in telecom go for. Students here get 10% off with the code BLOGGEEK.
SIPsense
Interactive SIP training used by telecom professionals in 138 countries, built on a virtual SIP network that runs in the browser. It's the fastest way I know to get someone reading real SIP logs.
Before you write
What I look for.
Audience overlap without product overlap. If we teach the same thing, we're competitors. That's fine, it's just not this.
Material I'd send my own students to. A recommendation from me is worth something because I don't hand them out, and I'd rather keep it that way.
Someone willing to say what their training doesn't cover. That's the whole basis of a complementary partnership. If your material covers everything, you don't need a partner.
Think we should be partners?
Tell me what you teach, who it's for, and where it touches WebRTC. If it fits, it's a short conversation.