Productizing your service v.s remaining bespoke.
If you run a service business, I know you might be asking yourself:
Don't worry, this post will shed some light.
TL,DR:
Switching from a typical service company with various clients and multiple offerings to a unique productized service with clear deliveries, led to 3x our revenue and 2x our team in 3 months.
First let's just clarify:
=> Productizing is the process of taking a skill or service and developing it into a standard, fully-tested, packaged, and marketed product.
Ok let's go!
➡️ DEFINE
This is to answer: can I productize my service?
Lay down what the 3 to 5 necessary steps to successfully deliver your service are. The steps you do over and over again, with any client.
👉 Name them and checklist what you're delivering in each.
This gives you a clear guidance on the flow of your service. Input <> Output.
➡️ FOCUS
Once you know what it takes step by step to deliver a streamlined service across all clients, ask the following:
What are the key functions of your service?
In other words, what makes your service perform at high standards.
Ex: a chef could say my secret is: “the ingredients” and “my cooking wear”.
With the best cooking wear but bad ingredients a chef can simply not produce anything good. And good luck for cooking without cooking wear ;)
As an outbound company our key functions are 1/ Data and 2/ Copywriting.
If any of the two fail, we simply won't generate results. Period.
Wrong/bad data means we're engaging with the incorrect prospects.
Bad copy means that even we have the right data, there will be no replies.
💡Note: If you say "everything is a key function", come back to the DEFINE phase and grade each step by importance.
👉Once you know what your key functions are, you have to protect them as if your life depended on them (because it does).
This is undeniably where you (and your productized service) add value.
💡Note: Investing in your core functions will over time, make anything you do faster, better, cheaper.
This is your competitive edge and the reason why customers buy your service.
➡️ STANDARDISE
Now that you know what it takes to deliver your service but also what makes your service standout, it's time to standardize.
And here we're using standardization to go against customization (to all you service owners saying yes to random client requests 😉)
Customization is the enemy of your scale.
Every time you customize, you can't productize 🚫
And if you customize you also can't build a process and system to scale.
💡Note: if you can't standardize 80% of your process, it's likely that your target market is too broad and/or your service offering is too wide.
Closing down on a niche with a unique offering has the advantages of a product:
So, standardise what you do. Not only in terms of process and key functions, but also offering.
Here is an example of how we started showcasing our service:
https://www.thescalelab.com/pricing
In only one week this has become our second most visited page.
And guess what: as prospects know what they get, for what they pay, inbounds have been super qualified.
The result?
=> $10k to $30K MRR in 3 months.
CONCLUSION
If you:
1/ Define precisely what you do
2/ Focus on what makes you standout
3/ Standardize how you deliver
🏅 You have your first step to productizing your service business.
Over to you.
Congrats man, I'll try to launch a lot of productized service and this will help
Nice to hear! Keep me posted when you're getting there ;)
Thanks for sharing the amazing insights and congratulations on the revenue lift! Just curious, how did you go around building your own client base? It would be great if you could help us understand that as that is one of the biggest challenges new start ups have.
That's a great question @atuls22 - I'm planning on making a dedicated post for this.
But essentially, the early days were:
What you're fighting for in your early days is the fact that your brand isn't strong enough yet to establish immediate trust. SO you can hedge this by using your network.
And here you might say "what if I don't have a network?". You build one through outbound, IH/slack channels etc. and sharing valuable content on your profiles (Twitter/LinkedIn or whichever channel your audience is most prone to hang out in).
It requires time and consistency, but everyone can get there :-)
Great insights, thank you!
What do you use for managing tasks, workload and deadlines?
Hey @davmuz, we're not fully there yet. We're using Notion at the moment and are looking at Monday.com
We have SOPs for how to handle every account and what needs to be done in X given week to achieve success (a combination of qualitative and quantitative KPIs).
Do you have something in mind? :)
Actually I'm using Notion for storing the work request details and Asana for the tasks, then I link both using a field in Asana and a task preview in Notion.
My SOPs are in Notion and my task templates in Asana have the link to them inside.
It takes about 5-10 minutes to plan a work request, even complex ones, and few seconds to review it.
I like to improve the workload and deadlines part so I am courious about how you are doing.
Excellent, that sounds like a steady flow.
Can I ask you why Asana over any other task management software?
While comparing I found that Mounday fitted smaller teams (with a little more flexibility) and Asana fitted a little larger teams.
Just curious.
Typing tasks on Asana is fast and it's a good example where less is more.
But I don't use Asana like a database, for that I use Notion because it's much better than a task management system.
Loved the points on how one can productize their services & scale.
Thanks @Priyanshugoyal - have you tried so far?
Thanks Youssef, this was really great insight in to further developing a business. It actually provides some confidence when first thinking of a micro-saas idea that it is worth some amount of effort pursuing the idea.
May I ask, how you realized that standardizing the development process was a better option than allowing a user to customize their experience? I have been thinking of ways to allow users to customize how they use my product to their liking - which you advise against?
Hi @InBlue thanks for sharing.
So first things first, The Scalelab isn't a Saas, rather a service executed like a product. Hence the name Productized Service :)
This said, let me give you some thoughts.
In your case, it depends whether customization is part of your offering. Ex: Notion, Airtable allow for very very wide customization, and that's also why they have users.
It's part of their offering.
But since you're talking about micro-saas, I would say to focus on delivering a streamlined experience as too many use cases might give you a headache in terms of growth.
NOTE: improving your product as you go by collecting user feedback is different than customizing your product to the liking of every single user.
The former will allow you to scale while the second will hinder your scale.
All great points, thanks for that!