Monetizing Your Skills
As an engineer, you have skills that are worth money outside your day job. The question is not whether you can monetize them but which monetization strategy fits your goals, time constraints, and risk tolerance. This chapter covers the realistic options -- what actually works, what the income potential looks like, and what most people selling you a course about "passive income" will not tell you.
The Monetization Spectrum
Not all income streams are created equal. They fall on a spectrum from pure active income (trading time for money) to mostly passive income (money comes in while you sleep). Here is an honest breakdown.
Strategy $/Hour Effort Level Passivity Time to First $
---------------------------------------------------------------------------
Consulting $150-400 High None 1-4 weeks
Freelance development $100-250 High None 2-6 weeks
Technical writing $50-200 Medium Low 2-4 weeks
Online courses $20-100 High upfront Medium 2-6 months
SaaS product $0-1000+ Very high Medium-High 3-12 months
Open source sponsors $5-50 High Low 6-24 months
Digital products $10-50 Medium Medium 1-3 months
Affiliate content $5-30 Medium Low-Medium 3-12 months
The pattern is clear: the more passive the income, the longer it takes to build and the less predictable the return. There is no shortcut around this.
Consulting
Consulting is the highest-paying way to monetize your skills, but it is purely active income. You trade hours for dollars.
What Engineering Consulting Looks Like
- Architecture review and system design
- Technology evaluation and selection
- Performance audits and optimization
- Security assessments
- Due diligence for investors evaluating technical companies
- Fractional CTO or VP of Engineering roles
The Economics
Consulting rate: $200-400/hour
Hours per week: 10-15 (alongside a full-time job)
Weekly income: $2,000-6,000
Monthly income: $8,000-24,000
Annual side income: $50,000-150,000+
The catch: consulting at this level requires deep expertise in a specific domain. Generalists get 300+.
Getting Started
- Identify what you know better than 95% of engineers
- Write about it publicly (blog, Twitter, conference talks)
- Tell your network you are available for consulting
- Start with one client, deliver exceptional results, get referrals
Consulting is the best first step because it requires no upfront investment and generates income immediately. But it does not scale and it is not passive. Every dollar requires your time.
Technical Writing
Technical writing sits in a middle ground. The hourly rate is lower than consulting, but the content can generate income after publication.
Opportunities
Type Pay Range Notes
---------------------------------------------------------------
Blog posts (company) $300-1,500/post One-time payment
Documentation $50-150/hour Contract work
Technical books $5,000-30,000 Advance + royalties
Paid newsletter $5-15/month/sub Recurring revenue
Platform writing $100-500/article Dev.to, Medium partners
Ghost writing $200-1,000/post Write for someone else
The Newsletter Model
A paid technical newsletter can generate meaningful recurring income if you build an audience. The economics:
Free subscribers: 5,000
Conversion to paid: 5% = 250 paid subscribers
Monthly price: $10/month
Monthly revenue: $2,500
Annual revenue: $30,000
Time investment: 8-12 hours/week writing
Effective hourly: $50-75/hour
This takes 12-24 months to build. The first six months, you are writing for free to build an audience. The income is semi-passive -- you must keep writing to retain subscribers, but older content continues to attract new ones.
Writing a Technical Book
The romanticized version: write a book, collect royalties forever. The reality:
Traditional publisher:
Advance: $5,000-15,000
Royalty rate: 10-15% of net
Average book sales: 3,000-5,000 copies
Total lifetime: $10,000-25,000
Time investment: 300-600 hours
Effective hourly: $17-83/hour
Self-published:
Revenue per sale: $20-40 (you keep most of it)
Sales (with audience): 1,000-5,000 copies
Total lifetime: $20,000-200,000
Time investment: 300-600 hours
Effective hourly: $33-666/hour (huge variance)
Self-publishing pays better if you have an existing audience. Traditional publishing pays more reliably if you do not. Either way, writing a technical book for money alone is a bad bet. Write it for reputation, career advancement, and the satisfaction of creating something lasting.
Building a SaaS Product
SaaS (Software as a Service) is the dream: build software once, charge a monthly subscription, collect recurring revenue. The reality is more nuanced.
Realistic Revenue Expectations
The vast majority of side-project SaaS products never generate meaningful revenue. Let us be honest about the distribution.
Revenue distribution for indie SaaS projects:
60% - $0/month (never launched or no customers)
20% - $1-500/month (pays for its own hosting)
10% - $500-5,000/month (meaningful side income)
7% - $5,000-20,000/month (could replace a salary)
3% - $20,000+/month (life-changing money)
The engineers who succeed in the top 10% typically share these traits:
- They solved a real problem they experienced personally
- They charged from day one
- They focused on distribution (marketing) as much as building
- They picked a boring but necessary niche
The Time Investment
Building an MVP: 200-400 hours
Launching and getting first customer: 100-200 hours
Iterating to product-market fit: 500-1,000 hours
Ongoing maintenance and support: 10-20 hours/week
Total first-year investment: 1,000-2,000 hours
If revenue is $2,000/month by year end: $12-24/hour effective
SaaS is a long game. The effective hourly rate in year one is almost always terrible. It gets better in year 2-3 if the product gains traction, because revenue grows while time investment stabilizes.
More detail on building SaaS products is covered in the next chapter.
Online Courses
Engineers teaching other engineers is a well-established model. Platforms like Udemy, Coursera, and self-hosted options make distribution accessible.
Platform vs Self-Hosted
Udemy/Skillshare:
Revenue per sale: $5-20 (heavy discounting)
Discovery: Platform provides traffic
Typical earnings: $100-2,000/month
Your control: Low
Self-hosted (Teachable, Podia, own site):
Revenue per sale: $50-500 (you set the price)
Discovery: You must drive traffic
Typical earnings: $0-10,000+/month
Your control: High
Creating a Course Worth Buying
The market is flooded with mediocre courses. To stand out:
- Teach something specific and practical, not broad and theoretical
- "Build a CI/CD pipeline with GitHub Actions" beats "Introduction to DevOps"
- Include real projects, not just slides
- Keep it concise -- engineers value efficiency
- Update it regularly -- stale technical content loses value fast
The Economics of a Successful Self-Hosted Course
Course price: $199
Students per month: 30
Monthly revenue: $5,970
Annual revenue: $71,640
Creation time: 200-400 hours
Ongoing updates: 5-10 hours/month
Marketing: 10-15 hours/month
A successful course is semi-passive. You front-load the creation effort, then spend ongoing time on marketing and updates. The course itself generates revenue without direct time input per sale.
Open Source Sponsorship
Getting paid for open source is possible but difficult. The paths:
GitHub Sponsors:
Average monthly sponsors: 5-50 for established projects
Average per sponsor: $5-25/month
Typical income: $100-1,000/month
Corporate sponsorship:
Company uses your project → pays for support/features
Typical: $500-5,000/month per sponsor
Very rare, requires widely-used project
Open source + consulting:
Maintain popular project → companies hire you to customize it
Highest-paying model but requires active consulting
Open source sponsorship rarely generates enough to live on. It works best as supplemental income for engineers who are already maintaining popular projects for other reasons.
What Actually Works vs What Influencers Sell
The internet is full of people selling courses about making money. Here is an honest assessment.
What influencers sell: What actually works:
-----------------------------------------------------------------
"Build a 6-figure course Most courses earn under $1,000
in 30 days" total
"Passive income from SaaS" SaaS requires years of active
work before becoming semi-passive
"Drop shipping is easy money" Has nothing to do with your
engineering skills
"Affiliate marketing Requires massive traffic, pays
while you sleep" poorly per click
"Write one e-book and retire" Most e-books sell under 100 copies
What actually works for engineers:
- Consulting -- immediate income, requires expertise
- SaaS products -- potential for recurring revenue, requires years of work
- Courses and educational content -- semi-passive with audience, requires platform building
- Technical writing -- steady income, requires consistency
- Everything else -- possible but much harder than advertised
Building Multiple Income Streams
The real power comes from combining strategies:
Year 1: Start consulting on the side ($3,000/month)
Year 2: Begin writing about your expertise (builds audience)
Year 3: Launch a course based on your content ($2,000/month)
Year 4: Build a small SaaS tool in your niche ($1,000/month)
Year 5: Total side income: $6,000-10,000/month
Each stream feeds the others:
Consulting → gives you material for writing
Writing → builds audience for courses
Courses → validates ideas for SaaS
SaaS → generates consulting leads
This flywheel takes years to build. There is no shortcut. But the compound effect of multiple streams creates both income stability and growth.
Common Pitfalls
- Trying to be passive from day one. Every "passive" income stream starts with massive active effort. Accept this and front-load the work.
- Building before validating. Engineers love to build. Force yourself to validate demand before writing a line of code or a chapter of content.
- Spreading too thin. Pick one monetization strategy and commit to it for at least 6-12 months before adding another.
- Ignoring marketing. The best product with no distribution earns nothing. Allocate at least 30% of your side project time to marketing and distribution.
- Comparing yourself to survivorship bias. You see the engineer who makes 0. Calibrate expectations accordingly.
- Neglecting your day job. Side income is great. Getting fired because you are distracted is not. Protect your primary income while building alternatives.
- Thinking income equals profit. A SaaS making 2,000/month in hosting, tools, and marketing. Track expenses.
- Following advice from people who make money selling advice. The person selling you a "how to make money online" course makes their money from selling courses, not from the strategy they teach.
Key Takeaways
- Consulting is the fastest path to side income for engineers -- high rates, immediate results, but not passive
- SaaS and courses offer recurring revenue potential but require 12-24 months of upfront work
- Most side projects generate $0-500/month -- set expectations accordingly and be pleasantly surprised
- Technical writing and content creation builds an audience that compounds across multiple revenue streams
- The "passive" in passive income is misleading -- every stream requires ongoing work to maintain
- Focus on one strategy for 6-12 months before diversifying
- Build on your unique expertise -- the more specialized your knowledge, the more you can charge