As a developer I never really thought much about marketing, but as an indie maker I learned that the "build it and they will come" myth is just that. A myth.
I learned that believing so much in something that you've poured your mind, heart and soul into making, but that no one gets to ever see, let alone use, can become an exhausting uphill battle that no one wants to be in.
So marketing is important. Maybe just as important as building a great product. Or maybe even more so.
But where do you start?
Especially as a one person team who's in charge of everything.. and now of marketing too.
The most important thing is to not spread yourself too thin. Pick one strategy to test at a time and commit to it. Pick one platform/audience and commit to them. Have a newsletter and funnel people to it.
This is important because if you experiment with too many strategies at the same time, you'll quickly run out of time for development.
Choosing a marketing strategy
There are a lot of marketing strategies out there, but as a dev, I'd highly recommend the "build in public" strategy. It's perfect for indie makers because it means a lot of your effort doing development is duplicated as marketing.
Newsletters are the best way to grow
Building a newsletter in the process, is the most reliable way of contacting people en mass these days. Twitter/Facebook/etc. all have algorithms that can filter you out. When you really need to tell your audience something, email is a reliable way of connecting.
Start to build in public within a community
Here's how it works:
2. Post what you're working on before, during, and after it's done, sharing your problems, learnings, and emotions along the way
3. Ask for advice and feedback when you need it
This will let people get involved in your product's development and give them a reason to cheer you on when you launch your product or get a new customer.
My most popular tweet of the past year (other than my launch post) was getting my first customer. It was also responsible for me getting my second and third customers.
When you are ready, go a bit further
It might take a while for you to find your feet on these platforms. And that's ok! But once you've gotten comfortable, you can try this more detailed process (which I outlined for myself yesterday):
1. Post a rough idea for an article/product/ebook/course to your social network of choice and get a feel for what people like or don't like about the idea. This doesn't have to be a fancy post, just a sentence or two. e.g. "I'm thinking of making a beginner JS course, what do you think?"
2. After some time, ask a for suggestions on how to proceed with your idea or if anyone has done it before. e.g. "Which course platform for releasing paid courses do you like the best?"
3. A while later, maybe a few days or so, post an outline of your approach for tackling this idea or talk about the content/features you're thinking about including in it. This will again help you measure interest and see where the real value of your idea is. e.g. "Here's what I plan on covering in my course: ___. Would this be useful for beginners to JS?"
4. Work for a few days. Then post a preview of the progress you've made so far (and maybe any blocks you came across, if any). This could be a few lines of code, a blurry screenshot of the final design, or even a picture of you working on your laptop. Just show people that you're actively working on this and give them something to be excited about. Remember one important thing: they're probably just as interested in your journey as the final product. So don't focus on the product too much — you're telling a story about what it takes to build a product.
5. Offer a taste of the final product. Make a thread or post with some of the actual content/features of the ebook/post/product. This could be a 5 minute video from the first lesson of your course. A screencast of you using your app. Or a the first page or two from your eBook.
6. Post a beta tester sign up form that gives people early (or instant) access to the MVP version of your idea. People who sign up are your true fans and will probably give you the best feedback over time. This form can be made with any email marketing software.
7. A week or two later, post a few quotes from early users showing what people said about their first experience of your product. e.g. "I wish I had this when I was first learning JS. I'm learning new things every 2 minutes!"
8. Finally, plan your launch! A few weeks or days before your big launch day, tell people you're launching. Tell them your goals, your hopes, and what your product will let people do (that they couldn't do before) once it's out in the world.
9. Post on Product Hunt, Hacker News, as well as on your social platform of choice. Make sure the product doesn't feel done yet. You want it to be a little rough around the edges. But it should solve a problem and that problem should be clearly stated on the home page alongside your proposed solution
10. After the launch, post about a piece of feedback you got from a user who signed up during the launch. It could be negative or positive piece of feedback, as long as it was useful to you.
11. Post about an update you made because of user feedback. This will show that your audience is important to you and are active participants in your journey.
12. Don't stop posting. Repeat the last two step (gathering feedback and making improvements to the product) over and over again until your product really starts to get good.
12. After you've improved the product enough that it can be considered a 2.0, launch it again.
Your work & your learnings double as marketing
The nice thing about this process is that it's symbiotic. Your audience benefits just as much as you do: for every idea of theirs you implement, they benefit by a) seeing their opinions matter and b) getting a final product that's more useful to them.
And, to top it off, you and your audience get to create a story together. It's the story of a fledgling idea coming into reality and finding its way. And they get to help it grow and help it along. It's a pretty magical process when it's done with intention and the desire to make people's lives better.
Btw, I wrote a really popular thread on Twitter about Building a Product in Public that you might also enjoy!