Momcilo Popov, founder of a digital product development studio, created BCMS to address common frustrations with existing content management systems. His product now generates $4000 in monthly recurring revenue. BCMS, an API-based platform, is a headless CMS that separates content management from content presentation, offering flexibility for use across various platforms.
Popov's journey began when he noticed a gap in the market while running his digital product development studio. Existing content management systems were often difficult for developers to use, lacked necessary features, had poor designs, or were too expensive. This led Popov to create BCMS as a solution that could serve both developers and clients effectively.
BCMS is a headless CMS, meaning it separates content management from how the content is displayed. This approach offers more flexibility in using content across different platforms. The system is built using Vue and Node.js, with extensive use of TypeScript, providing a powerful and scalable foundation.
In this article. We’ll discuss how Popov developed BCMS and his strategies for acquiring customers. Let’s get right in!
Momcilo Popov - co-founder, BCMS
What is BCMS?
BCMS stands for API-based Content Management System. It's a tool that helps people manage the content on their websites or apps. But BCMS is special because it's what we call a "headless" CMS.
To understand what "headless" means, think about a regular website. Usually, the content (like the words and pictures) and how the website looks are all mixed together. But with a headless CMS like BCMS, these two parts are separate.
BCMS takes care of storing and organizing all the content. But it doesn't worry about how that content will look on a website or app. This separation is useful because it lets developers use the same content in different ways. For example, they could show the same information on a website, a mobile app, and even a smart TV, without having to copy and paste it everywhere.
BCMS is designed to be easy for developers to work with. It uses programming languages that many developers already know, like Vue and Node.js. At the same time, Popov made sure that people who aren't tech experts can also use BCMS easily. This means that both the tech team and the content team in a company can work together smoothly using BCMS.
Why Popov created BCMS
Momcilo Popov didn't just wake up one day and decide to create a new content management system. The idea for BCMS came from real problems he faced in his work.
Popov runs a digital product development studio. This means his company builds websites and apps for other businesses. In this work, they often needed to use a content management system. But Popov and his team were never quite happy with the options available.
They found that existing content management systems often had problems:
1. Some were very hard for developers to set up and use. This meant projects took longer and cost more.
2. Others were too simple. They worked fine for a basic blog, but couldn't handle more complex websites.
3. Many looked ugly or were confusing to use. This was a problem because Popov's clients needed to use these systems themselves.
4. Some had all the features needed, but were very expensive.
Popov realized that what he needed was a content management system that was powerful enough for developers to do complex things, but also simple enough for clients to use easily. And it needed to be affordable.
When he couldn't find a system that met all these needs, Popov decided to create one himself. This was the beginning of BCMS.
How BCMS started
The story of how BCMS started is closely tied to Popov's existing business. Remember, he already had a digital product development studio with clients who needed websites and apps.
When Popov and his team created the first version of BCMS, they didn't immediately try to sell it to the world. Instead, they started by showing it to their existing clients. These were people who already trusted Popov's company to build their websites.
The reaction was very positive. Clients liked BCMS and were happy to switch from their old content management systems. This was a big deal because changing a content management system can be a lot of work. It showed that clients really saw value in what BCMS offered.
Popov offered these early users lifetime licenses as a thank you for their support. This was smart because it encouraged clients to stick with BCMS long-term.
Starting with existing clients also helped Popov avoid a common problem for new products: the struggle to get the first few users. Instead of starting from zero, BCMS had users and real-world use cases from day one.
This early start with trusted clients laid the foundation for BCMS's growth. It provided the feedback and real-world testing needed to improve the product quickly.
Getting the first customers
Getting the first customers for a new product can be tough, but Popov had a head start with BCMS. He already had a group of potential users: the clients of his digital product studio.
When Popov's team finished the first version of BCMS, they didn't go out looking for new customers right away. Instead, they showed it to the companies they were already working with. These companies were building websites and needed a way to manage their content.
This approach worked well for several reasons:
1. Trust: These clients already knew Popov and his team. They trusted them to do good work.
2. Understanding: Popov understood these clients' needs because he had been working with them.
3. Easy switch: Since Popov's team was building the websites, they could easily set up BCMS for the clients.
The first 20 to 30 customers were especially important. They used BCMS and told Popov what they liked and didn't like. This feedback was very valuable. It helped Popov's team improve BCMS quickly.
To thank these early customers for their help, Popov gave them lifetime licenses for BCMS. This meant they could use BCMS forever without paying more. It was a way of saying "thank you" and also encouraged these customers to keep using BCMS for a long time.
As these first customers used BCMS, they often asked Popov to add more users. Sometimes, a client would want to add 50 team members at once! This helped BCMS grow its user base quickly.
Word started to spread about BCMS. The first customers told other people about it. This word-of-mouth advertising helped BCMS get even more customers without spending money on marketing.
Smart design choices
When Popov created BCMS, he made some smart choices about how it should work. These choices helped BCMS grow and adapt to different needs.
The main idea was to make BCMS like a set of Lego blocks. Here's what this means:
1. Flexible parts: Instead of making specific features for every possible use, Popov created "abstract" features. These are like basic building blocks that can be put together in different ways.
2. Combining features: Users can take these basic features and combine them to do more complex things. It's like using Lego blocks to build different structures.
3. Avoiding the feature trap: Many software products fall into a trap of constantly adding new features for every request. This can make the product complicated and hard to use. By using the "Lego block" approach, BCMS could do many things without needing to add new features all the time.
4. Easy to learn: Because the basic parts of BCMS stay the same, it's easier for people to learn how to use it. They don't have to keep learning new things all the time.
5. Adaptable: This design means BCMS can be used for many different types of websites or apps without needing to be completely changed.
This smart design had big benefits:
1. Saved time: Popov's team didn't have to spend all their time making new features. Instead, they could focus on improving the core parts of BCMS.
2. Helped customers: Popov could spend more time teaching customers how to use BCMS in different ways.
3. Got more feedback: Because customers could do more with the existing features, they gave more useful feedback about how to improve these core parts.
This "Lego block" design is a big reason why BCMS could grow and adapt to different customers' needs without becoming too complicated.
The technology behind BCMS
Popov built BCMS using specific technologies. Understanding these can help us see why BCMS works the way it does.
The main technologies used are:
1. Vue: This is a tool for building user interfaces. It helps make the parts of BCMS that people interact with.
2. Node.js: This is used for the behind-the-scenes part of BCMS. It helps BCMS handle lots of information and requests quickly.
3. TypeScript: This is a special version of JavaScript, a popular programming language. TypeScript helps catch mistakes early and makes the code easier to understand.
Popov says this combination is "powerful and scalable." Here's what that means:
- Powerful: It can handle complex tasks and lots of information.
- Scalable: As more people use BCMS, these technologies can handle the increased load without slowing down.
For their own website, Popov's team uses:
1. Nuxt.js: This works with Vue to make websites faster and easier to find on search engines.
2. BCMS itself: They use their own product, which shows they believe in it.
3. Docker: This is a tool that helps package up all the parts of BCMS so it's easy to set up on different computers or servers.
Using these technologies has several benefits:
1. Fast development: These tools are modern and efficient, helping Popov's team work quickly.
2. Good performance: Websites and apps built with these technologies tend to work smoothly and quickly.
3. Large community: Many developers know and use these technologies, making it easier to find help or new team members.
4. Future-proof: These technologies are actively developed and improved, meaning BCMS can easily adopt new features and improvements.
By choosing these technologies, Popov ensured that BCMS would be powerful enough for complex tasks, but also able to grow as more people start using it.
The challenge of marketing to developers
When Popov started selling BCMS, he discovered that marketing to developers was very different from regular marketing. He found this both challenging and refreshing.
Developers, as a group, tend to dislike traditional marketing tactics. They often see through sales pitches and prefer straightforward, honest information. This meant that Popov and his team had to change how they talked about BCMS.
At first, they struggled. They were used to marketing to regular business clients, not to other technical people. Popov realized they were using too much "fluff" - unnecessary, fancy-sounding words that didn't really mean much. They had to unlearn these habits.
The team found that the best approach was to be direct and technical. Instead of making big claims, they focused on explaining exactly what BCMS could do and how it worked. They talked about the specific problems BCMS solved and the technologies it used.
Popov noticed something interesting: when developers try to sell products, they often stop talking like developers. They start using marketing language that they wouldn't like if they were the customer. Recognizing this helped Popov's team avoid the same mistake.
They're still learning and improving how they market BCMS. But they've found that being clear, honest, and technical works best when talking to other developers. This approach has helped them connect with their target audience and grow their customer base.
Growth strategy
Popov's strategy for growing BCMS was different from many new products. Instead of trying to get as many new customers as possible, he focused on his existing clients first.
Word-of-mouth played a big role in BCMS's growth. Happy clients told other people about BCMS. This kind of recommendation is very powerful, especially among developers who often trust their peers' opinions.
Popov also offered lifetime licenses to early customers. This was a smart move for two reasons. It encouraged these early users to stick with BCMS for the long term. It also showed that Popov valued their early support and feedback.
As BCMS grew, Popov started looking at other ways to reach new customers. He mentioned trying paid ads, but found they didn't work well for BCMS. This is common for developer tools, which often rely more on community reputation than traditional advertising.
The importance of early feedback
The first 20 to 30 customers of BCMS played a crucial role in its development. Popov understood that their feedback was incredibly valuable, and he made the most of it.
These early users helped in several ways. First, they used BCMS in real-world situations. This showed Popov and his team how BCMS performed in actual projects, not just in test environments. They could see what worked well and what needed improvement.
Second, these customers provided detailed feedback. They told Popov what features they liked, what was confusing, and what additional capabilities they needed. This information was gold for improving BCMS.
Popov's team used this feedback to refine BCMS quickly. They could fix problems and add useful features based on real user needs, not just guesses about what might be helpful.
This approach saved Popov a lot of time and trouble. Instead of adding lots of new features that might not be useful, they focused on improving the core features that customers actually used. This kept BCMS from becoming overly complicated.
Popov also spent time educating these early customers about BCMS. By teaching them how to use the system effectively, he got even better feedback. Customers could suggest improvements based on a good understanding of how BCMS worked.
This focus on early feedback helped BCMS improve rapidly. It also built strong relationships with these first customers, who appreciated that their input was valued and acted upon.
Current success and future plans
BCMS has grown significantly since its launch. It now generates $4000 in monthly recurring revenue. This means that every month, customers pay $4000 to use BCMS. This steady income is a sign that BCMS is providing value to its users.
While Popov didn't share specific numbers, the growth from the initial customers to this level of monthly revenue suggests that BCMS has found a market for its services. People are willing to pay for what BCMS offers, which validates Popov's original idea.
Looking to the future, Popov is exploring new ways to grow BCMS. He mentioned several strategies:
1. Content marketing: This involves creating helpful articles, videos, or other content that attracts potential customers to BCMS.
2. SEO (Search Engine Optimization): This means improving how BCMS appears in search engine results, making it easier for potential customers to find.
3. Strategic partnerships: Popov is looking at working with other companies that serve similar customers but don't compete directly with BCMS.
4. Improving the Affiliate Program: This could encourage more people to recommend BCMS to others.
Popov is also likely to continue improving BCMS based on user feedback. The "Lego block" design of BCMS means they can add new capabilities without making the system overly complex.
While the future is always uncertain, BCMS's current success and Popov's clear plans for growth suggest a promising path forward. The challenge will be to maintain the balance between adding new features and keeping BCMS simple and easy to use, which has been key to its success so far.
Learning resources
Popov shared two podcasts that he finds helpful for entrepreneurs. These are "The Bootstrapped Founder" and "Indie Hackers." Both can be found on Spotify, a popular music and podcast streaming platform.
"The Bootstrapped Founder" is a podcast that focuses on starting and growing a business without outside funding. The term "bootstrapped" means using your own resources to build a company, rather than relying on investors. This podcast likely offers advice on how to manage money carefully, find customers efficiently, and grow a business steadily.
"Indie Hackers" is a podcast that features interviews with founders of successful online businesses. "Indie" in this context means independent - these are often small teams or individuals who have created profitable products or services. The podcast probably covers a wide range of topics, from coming up with business ideas to overcoming challenges in growing a company.
By recommending these podcasts, Popov suggests that he values learning from other entrepreneurs' experiences. These resources likely provide practical advice and real-world examples that Popov finds useful in running BCMS. They may cover topics like product development, marketing strategies, and how to handle the day-to-day challenges of running a business.
While Popov didn't mention books or newsletters, podcasts can be a convenient way to learn. They allow you to absorb information while doing other tasks, like commuting or exercising. This might be particularly useful for busy entrepreneurs like Popov.
Conclusion
Momcilo Popov created BCMS to solve problems he faced with existing content management systems. Starting with his own clients, he grew BCMS to 110 paying customers and $4000 in monthly revenue over 10 months. Popov focused on making BCMS easy for both developers and non-technical users. He found that marketing to developers required a different approach, favoring direct and technical communication over traditional tactics. As BCMS grows, Popov plans to explore content marketing, improve SEO, and develop strategic partnerships. While challenges remain, BCMS's current success suggests Popov has found a market for his developer-friendly, flexible content management system.
