The Quiet Teacher Who Can't Stand Waste
Capability first, time-back second: you turn competence you bled for into things other people can finally do on their own — and you can't watch a manual process without itching to kill it.
01The portrait
Read this as a mirror, not a verdict. You are, before anything else, a teacher who never chose to be one. The pattern shows up everywhere in your answers: you are the person people DM when they're stuck, the one who turns a five-minute "quick question" into a whiteboard, the colleague juniors are quietly routed toward. You don't do this for credit. You do it because watching someone struggle with a thing you've already solved is physically uncomfortable to you — there's an origin story under it, a time you had to figure something out alone and the hard way, and some part of you has decided no one else should have to repeat that.
That instinct is your dominant value: Capability. You don't sell answers; you sell the moment someone becomes able to do the thing themselves. It's a generous profile and a commercially underrated one, because most strong engineers carry it and never realize it — the culture told them to build product, not to transfer skill, so they sit on the most monetizable thing they own.
Underneath it runs a second engine: Time. You have a low, persistent intolerance for waste. A thirty-minute manual process that could be a thirty-second script reads to you as a small moral offense. You automate not because someone asked but because you can't not — and the things you build to save yourself an afternoon are almost always things other people would pay to be handed. Capability + Time is a potent pairing: you teach people to do hard things, and you remove the boring things so they can. The first builds authority; the second builds leverage.
Third, more quietly, is Craft. You spend longer than is "rational" on details no customer will notice — the error message that's actually helpful, the API that's a pleasure to call, the doc that reads like prose. This is the part of you that makes the teaching land and the tools feel trustworthy, but it's also the part most likely to quietly sabotage you. Craft doesn't want to ship at 80%. Capability and Time both need to.
What this means in practice: your natural business is not a closed SaaS that hides how it works, and it's not high-touch consulting that trades your hours for money one at a time. It's something in between — a way to package what you know so it teaches at scale, with the boring parts automated, finished to a standard you're not embarrassed by. You are most alive when someone you've never met sends a message that says "I finally get it, and I built the thing." That sentence — not the invoice — is the actual product. Price accordingly, and protect the part of you that needs to make it good without letting it stop you from making it exist.
02How to turn this into money
Specific shapes calibrated to your context. Not 30-day plans — directions concrete enough to start tomorrow if one of them lands.
- 01
A cohort course for senior engineers — not beginners
Why it fits youCohorts are Capability rendered as a business: live skill transfer, with you in the room watching the moment it clicks. The senior-only framing matches you specifically — you're bored teaching fundamentals, but you light up correcting a staff engineer's mental model. That energy is the product.
Pricing hint$1,200–2,500 per seat, 12–20 seats per cohort, 4–6 weeks. Run it 3–4 times a year. Resist the urge to make it cheaper to 'help more people' — low price attracts the wrong students and burns you out faster.
First customers — whereYour own network first (the people already DMing you), then niche-specific Slacks/Discords where senior people gather — e.g. dbt Community, Locally Optimistic (data), Rands Leadership, staff-eng circles on LinkedIn. One good thread describing the exact mistake you keep seeing fills a cohort.
What makes this not genericMost courses teach syntax. You teach judgment — the 'why this breaks at 3am' that only shows up after years. Build the whole thing around real failure post-mortems, not happy paths.
Watch for: Cohorts are time-bound and don't scale past your calendar. Treat the first two as R&D for a self-paced version, or you'll cap at your own hours.
- 02
Productized internal-tooling templates / an automation kit
Why it fits youThis is your Time engine sold directly. The scripts, templates, and pipelines you already build to save yourself an afternoon are things thousands of teams rebuild badly. Package them once; sell the afternoon back to everyone else.
Pricing hint$49–149 for a template pack; $300–900 for a 'kit' with setup docs and a Loom walkthrough. Higher if it plugs into a specific expensive tool (Snowflake, Databricks, Airflow).
First customers — whereWherever people complain about the exact chore your kit kills — relevant subreddits (r/dataengineering, r/devops), tool-specific forums, and the replies under 'how do you all handle X?' posts on LinkedIn/X. Ship a free, genuinely useful version first; charge for the complete one.
What makes this not genericAnyone can post a gist. You ship it finished — opinionated defaults, the edge cases handled, a doc that explains the reasoning. Your Craft is the moat here; it's the difference between 'a script' and 'a tool I trust in production.'
Watch for: Don't disappear into building the perfect kit for six months. Sell the v1 the week it's useful; let buyers tell you what to finish.
- 03
A paid technical newsletter or handbook
Why it fits youCapability + Craft together: writing is teaching that compounds while you sleep, and you already over-invest in making explanations clear. A focused, opinionated handbook on the one domain you know cold becomes an asset that sells the cohort and the kit for you.
Pricing hintNewsletter: free to build the list, then $8–15/mo or $99/yr for a paid tier with the deep pieces. One-off handbook/ebook: $29–79. The list is the real asset — it makes every other product easier to sell.
First customers — wherePublish in public on the platform your audience already reads (X, LinkedIn, a personal blog with good SEO on the specific problem). Each post is a lead magnet; the best ones become the handbook's chapters.
What makes this not genericThe internet is full of surface-level 'how to' content. You can write the version that assumes the reader is smart and tells them the thing nobody says out loud. Depth + a real point of view is rare and defensible.
Watch for: Writing pays slowly and indirectly. Treat it as the top of your funnel and the proof of your judgment — not as the line item that pays rent on its own, at least not early.
- 04
A focused micro-SaaS that automates one painful workflow
Why it fits youThe highest-leverage expression of Time: take the single automation you and your peers rebuild most often and turn it into a self-serve tool. You don't need a platform — you need one sharp wedge that removes one specific, recurring afternoon of pain.
Pricing hint$19–99/mo per seat or per workspace. B2B, not B2C — businesses pay for time saved without blinking; consumers haggle over $5.
First customers — whereSell to the exact role that feels the pain (e.g. data platform teams, SRE leads). Find them where they already are — tool-specific communities, your cohort alumni, warm intros. Your teaching audience is your beachhead.
What makes this not genericYou've lived the workflow, so your defaults are right and your onboarding teaches instead of confusing. A SaaS built by someone who actually did the job feels different in the first five minutes.
Watch for: SaaS is a long, lonely commitment with support and uptime attached. Don't start here as your first product — start with the kit or cohort, and only build SaaS once you've heard the same request twenty times.
03What to watch out for
The thing most likely to quietly hurt you is teaching when you should be productizing. Capability-types feel most useful in the moment of explaining — so you'll keep saying yes to the live call, the custom answer, the bespoke help, and wake up two years later having helped hundreds of people for free with nothing that compounds. Every time you explain the same thing twice, that's a product screaming to be made. Write it down once and sell the written version.
The second trap is the Craft tax. The detail nobody notices is precisely the detail you'll spend a weekend on, and your standards will tell you the thing isn't ready when it has been ready for weeks. Your Time value should win this fight more often than it does: shipped-and-imperfect beats perfect-and-unshipped every single time in a business that depends on momentum and feedback. Give yourself a hard rule — version one ships when it's useful, not when it's beautiful — and let real buyers, not your own taste, decide what to polish next.
Third: you will under-price. Capability-types systematically undervalue what they know because it feels easy to them now — they've forgotten how long it took to make it easy. The years you spent learning the hard way ARE the product; price for the buyer's outcome, not for the hour it takes you. A senior engineer who saves a team three weeks should not be charging $49.
Finally, watch the pull toward pure consulting. It pays well and it flatters the teacher in you, but it trades your hours for money one at a time and it has no exit — the day you stop, the income stops. Use consulting deliberately, as paid research that tells you which product to build, and put a cap on it. The whole point of your Capability + Time pairing is leverage: teach once, automate the rest, get paid while you sleep. Anything that quietly turns you back into a billable resource is working against your own grain.