Next Inject - The best boilerplate service for Nextjs

Believe it or not, the first SaaS (Software as a Service) I developed is actually the website you are reading this article from.

Well... Actually that's only true for everyone reading on this domain and not from medium.com.

Wherever you are reading from, I hope your day is going well, and I hope to make it better with this exciting article about my new SaaS project!

So what is my new SaaS?

Here is my "Purpose Statement" I came up with a few weeks ago:

TLDR: A Next.js website with documentation for a base boilerplate + additional plugins (e.g. metadata plugin) to add onto the base boilerplate.
The plugins are injected using a custom nodejs CLI called next-inject.

Why are we making this?

You might ask:

"There is strong competition for your service (e.g. shipfast), how will you beat them?"

I love this question because it gives me the opportunity to think deeply about my SaaS, and ensure that we are going in the right direction.

To answer the question, we acknowledge the fierce competitors like shipfast, and so I made the executive decision to redesign the playing field.

We are revolutionizing Next.js boilerplate.

We promote the use of composable and modular plugins rather than "ready-made" repositories, which will force the developer to learn technologies they may not be good at, therefore wasting time.

While the competitions main focus is on shipping speed, my main focus is on granularity, flexibility, and affordability.

This means plugins will be independent, there will be many of them, and they will not be expensive since you can purchase plugins individually.

For example, just $5.00 to fully configure static metadata for your app is a bargain!

What are the benefits for you?

1. Easy and Quick to Use

After configuring our CLI, you only have to run one command to inject a purchased plugin inside your Next.js app.

For example, need metadata? Run next-inject add metadata

Need beautiful emails with React Email? Run next-inject add react-email

Note that some plugins will require environment variables configured. For such plugins, there will be detailed documentation explaining how to get this done.

Keep in mind that once you own these plugins, you have unlimited uses. No need to re-purchase any plugins.

2. Modularity

It is our #1 requirement to ensure modularity between plugins.

Without modularity, there will be conflicts between installed plugins, which could break other plugins or even the entire application.

For example, if you install our metadata plugin and the structured data plugin, they should not interact with each other.

In other words, one installation should never cause the other to break.

3. Composability

Expanding on the point of modularity, our SaaS is engineered to allow for comoposability.

This means it is possible to compose an auth, metadata, and stripe plugin to build a full Next.js application with just three CLI commands.

Lets say you decide that stripe does not meet the user requirements.

You can then remove the stripe plugin, and install the lemonsqueezy plugin instead with a single click!

4. Flexible Pricing

We believe in the power of flexible pricing.

For that reason, we will adopt the following payment structures to monetize our plugins:

• One-off: Purchase single plugins for a fixed price.
• One-off (bundled): Purchase a bundle of plugins for a fixed but discounted price.
• Subscription (maybe): Purchase a monthly subscription to gain access to a wide range of existing plugins and new plugins to come.

How will marketing be handled?

At the moment, marketing is a bit of a gray area.

However, we use these techniques to get our SaaS out to the right people:

• Writing articles (Like this one!): Since we have a large audience that is into Next.js, we believe writing articles is a great way to acquire the traffic we need.
• Posting our progress on X and Reddit: These platforms promote engagement and have rich SaaS communities, therefore frequent posting about our SaaS is a fantastic way to get more eyes.
• Engage with higher-profile content creators: We will contact creators like Theo.gg to take a look at this product, and if he likes it, he could make a video on it and effectively market the product to thousands of prospects.
• SEO: SEO is very important for the SaaS since there are many documentation pages, and we need each of these pages to be easily visible when searched for on the internet.

Final Thoughts

Building a SaaS product is tiring, but also very rewarding at the same time.

Thinking about meeting the user demands, marketing, and programming, is not easy.

However, I have great faith in the future of my SaaS.

I hope my vision is clear from this article, and if you have any questions about it please let me know in the comments! Your feedback is as valuable as gold!

If you enjoyed this article, please make sure to Subscribe, Clap, Comment and Connect with me today! 🌐