From code to cash: going from “I can code” to “it pays the bills”

You can build things that 95% of the population doesn’t even understand. You can spin up an app, automate a workflow, deploy an API on a Sunday evening in your pyjamas. And yet your bank account doesn’t reflect any of that.

The problem isn’t technical. It never was.

Monetising your code isn’t about “learning to sell”. It’s about unlearning a toxic belief: that the code is the product. Code is never the product. The product is the transformation you deliver to someone who has a problem and a wallet.

This article is a concrete guide. No startup theory, no “find your passion”. Just what actually works when you’re starting from zero, working alone, and want your first income without raising a single cent.

---

1. The dev trap: confusing “knowing how to build” with “knowing how to sell”

There’s a precise moment when most developers go wrong. It’s not when they pick their stack. It’s not when they write the code. It’s when they tell themselves: “My product is good — people will come.”

Nobody comes.

The eternal side-project syndrome

You know the pattern. An idea on a Friday evening. A GitHub repo on Saturday. A working MVP two weeks later. Then… nothing. No users. No feedback. The project joins the side-project graveyard, somewhere between the Trello clone and the Discord bot nobody asked for.

The problem isn’t the quality of the code. The problem is that you built before checking whether anyone would pay.

Building ≠ Selling

Knowing how to build is an execution skill. Knowing how to sell is a connection skill: connecting a real problem to a solution, and making that connection clear to the person who’s suffering from the problem.

These are two completely different muscles. And the second one doesn’t get trained in an IDE.

The good news: you don’t need to become a salesperson. You need to understand three things — who you’re talking to, where that person hangs out, and what word they use to describe their pain. That’s it. Everything else is iteration.

The real advantage of the indie hacker dev

A dev who picks up the basics of distribution has an unfair advantage. Where a marketer needs to hire someone to build, you can iterate alone. You can test an idea over a weekend, measure, pivot, relaunch. Your feedback loop is ten times shorter than any non-technical person’s.

You just have to actually use that loop to validate, not to build in a vacuum.

---

2. Why revenue needs to come early (and small)

The classic beginner indie hacker mistake: aiming for €10,000/month from the very first project. So they spend six months building a full SaaS — onboarding, Stripe, admin dashboard, transactional emails — and nobody signs up.

The first euro changes everything

Your goal isn’t €10,000. Your goal is €1. A single euro earned in exchange for something you created. Not your salary. Not freelance work. One euro that comes from a product, a template, a tool, an access pass.

That first euro is proof that someone, somewhere, values what you produce enough to take out their card. It’s a more powerful signal than 10,000 GitHub stars.

Small revenue, big learning

When you sell a Notion template for €9, you learn:

• How to write a sales page (even an ugly one)
• How to set up an online payment
• How to handle a customer who has a question
• Why someone buys (and why someone else closes the tab)

Each of those micro-lessons is worth more than any online entrepreneurship course. Because it’s grounded in reality — your reality.

The “not ready yet” trap

“I’ll launch when it’s finished.” Finished doesn’t exist. Every feature you add before you have a single paying user is a bet. And statistically, you’re going to lose that bet.

Launch ugly. Launch incomplete. Launch with a Stripe button and a three-paragraph page. If nobody clicks, you’ll know the problem isn’t your CSS — it’s your positioning.

Your first SaaS revenue never comes from a perfect product. It comes from a well-identified problem, framed in the customer’s own words.

---

3. Distribution first: who, where, how

You can have the best product in the world. If nobody knows it exists, it’s worth zero. Distribution isn’t a “nice to have”. It’s the topic.

Who are you talking to?

“Everyone” is not a target. “Freelance designers who struggle to invoice their clients” is.

The more precise your target, the sharper your message. A product that speaks to everyone speaks to no one. A product that solves one problem for one type of person almost sells itself — because that person recognises themselves instantly.

Concrete exercise: write a sentence that starts with “I help [who] to [result] without [friction]”. If you can’t complete it, you’re not ready to sell.

Where does that person hang out?

Your ideal customer is somewhere right now. Reading a subreddit. Scrolling Twitter/X. In a Discord server. Searching for a solution on Google. Watching a YouTube video.

Your mission: be where they are, before they come looking for you.

A few channels that work when you’re starting from zero:

• Twitter/X: build in public, share your progress, your numbers, your failures. Authenticity attracts. You don’t need 10k followers — 300 engaged people in your niche is enough.
• Reddit / specialist forums: answer questions, add value, mention your tool when it’s genuinely relevant (not before).
• Product Hunt / Indie Hackers: for the initial launch and credibility.
• SEO: slow but durable. One well-targeted article can bring traffic for years.
• Slack/Discord communities in your niche: often underestimated, often highly qualified.

How do you talk about it?

Not by describing your features. By describing the outcome.

Bad: “A SaaS for invoice management with PDF export, multi-currency support and a REST API.”

Good: “Spending 3 hours a week on invoices? Cut that down to 10 minutes.”

People don’t buy features. They buy time saved, pain avoided, status gained. Speak their language, not yours.

---

4. The first euros: what actually works when you’re starting from zero

Forget the €49/month SaaS for now. When you have no audience, no credibility, and no sales experience, you need to start with the lowest-friction option.

Level 1: Sell a simple digital product

• A template (Notion, Figma, Excel, Airtable) that solves a specific problem
• A theme or starter kit (Next.js, Tailwind, WordPress)
• A script or automation (Zapier, Make, Python)
• A mini-course or PDF guide

Price: €9 to €49. Platforms: Gumroad, Lemonsqueezy, or your own site with Stripe.

The advantage: no infrastructure to maintain, no ongoing support, no server. You create once, you sell N times.

Level 2: The micro-SaaS

A micro-SaaS is an online tool that solves one single problem for one single type of user, with a monthly subscription.

Real examples that work:

• A tool that checks for broken links on a website → €9/month
• A dashboard that aggregates Google reviews for a local business → €19/month
• A bot that automatically reposts recycled content → €15/month

The key: recurring value. If your tool saves time or money every month, the subscription justifies itself naturally.

To sell a micro-SaaS type product, start with 1 to 3 features. No more. Your first customer doesn’t need an analytics dashboard. They need the thing to work.

Level 3: The productised service

Take a skill you have (scraping, automation, API integration, deployment…), package it into a fixed offer with a listed price.

“I’ll connect your CRM to your email tool in 48 hours — €300 flat fee.”

This isn’t classic freelancing. It’s a service with a defined scope, a fixed price, a clear deliverable. You control your time. And every project brings you closer to a product: when you’ve done the same thing for the tenth client, you know exactly what to automate.

What doesn’t work (at the start)

• Consumer mobile apps (too much competition, insane acquisition costs)
• Marketplaces (chicken-and-egg problem)
• “For developers” tools with no existing audience
• Anything that requires a network effect to function

---

5. The role of AI in moving faster without cutting corners

AI won’t build your business for you. But it will compress the time between idea and first euro.

What AI does well (and what you should delegate to it)

Write faster. Sales pages, emails, product descriptions, Twitter posts, SEO articles — anything that’s marketing-oriented text. You stay in the driving seat, but AI gives you a first draft in 30 seconds instead of 2 hours.

Code the boring parts. CRUD, API integrations, forms, validation, database migrations. All the “commodity” code you’ve written a hundred times. AI writes it, you review and adjust.

Explore niches. You can ask an LLM to analyse Reddit discussions, summarise recurring complaints in a forum, list existing tools in a niche. That’s not cheating — it’s accelerated research.

Prototype interfaces. Generate a first HTML/CSS skeleton, iterate on a design, test landing page variants. You save hours of layout work.

What AI doesn’t do (and what you shouldn’t ask it to)

• Choose your market. AI doesn’t know your strengths, your network, your time constraints. That decision is yours.
• Talk to your customers. An email generated by GPT is obvious from a mile away. Real conversations — the ones that reveal real problems — happen person to person.
• Replace quality. A product entirely generated by AI with no human oversight shows. And it doesn’t retain anyone.
• Guarantee relevance. AI can produce fluent content that is factually wrong or strategically off-target. Your judgement remains the final filter.

The right mindset

Use AI as an accelerator, not a substitute. The dev who uses AI to ship in 2 weeks what used to take 2 months has a real competitive advantage. The dev who lets AI make all the decisions is building a house of cards.

Your edge as a technical indie hacker is your ability to understand what AI produces, correct it, improve it, and integrate it into a coherent system. A non-technical person can’t do that. You can.

---

The action plan (for those who want to start this week)

1. Monday: Choose a niche. Not the perfect one — one that resonates with you and where you see people complaining about a concrete problem.
2. Tuesday: Read 30 discussions (Reddit, Twitter, forums) in that niche. Note the exact words people use to describe their pain.
3. Wednesday: Write your “I help [who] to [result] without [friction]” sentence. Create a single-page landing page.
4. Thursday: Build the simplest possible version of your solution. A script, a template, a minimal tool.
5. Friday: Set a price. Add a payment button. Share it in 3 places where your target hangs out.
6. Weekend: Watch. Who clicks? Who buys? Who asks a question? That’s your first signal.

You probably won’t make money that week. That’s not the point. The point is to complete the loop: problem → solution → offer → distribution → feedback. Once you’ve done that full cycle once, you know exactly what to improve.

---

Final word

Monetising your code isn’t a question of technical talent. It’s a question of direction. You can be an excellent developer and never earn a euro outside your salary. Or you can be an average dev who understands who they’re talking to, where to find them, and how to frame an offer — and generate independent income within a few months.

Code is your tool. The cash comes from the value you create for someone else.

Start small. Start now. Start ugly.

The first euro is the hardest. Everything after that is optimisation.

---

Need a hand building something — a website, a SaaS or an AI automation? Sébastien de Bollivier, the dev behind SEK, can help.

Also worth reading: the solopreneur & AI stats 2026.

Got an idea to ship? A website, a SaaS, an AI automation — built with you.

Talk about your project