In the previous article (Part I) on the self-serve model, I discussed where it works and where it does not, and why to use a self-serve model.
The self-serve model has its own risk. So before thinking of implementing that, it is important to evaluate the risk and its mitigation strategy:
1) Spreading too thin and losing track of the beachhead: A company that has grown by focusing on SMBs may end up spreading itself too thin in a pursuit of a self serve business model.
Mitigation strategy: Use a small team to validate the idea. Lean methodology can evaluate and create a much bigger opportunity without significantly diverting the resources
2) Complexity of the platform with the two models: Features team may be going in two different directions and launch competing product that dilutes experience for both sides of the user
Mitigation strategy:
3) Margin may get hurt while chasing volume
Mitigation strategy:
4) Running after too many segments in a long tail may lead to catching none
Mitigation strategy:
5) Operational costs may be prohibitively high to justify acquiring the long-tail customer
Mitigation strategy:
The following inputs is important to take an informed decision in entering this market: Customer, product, and Market and competitive landscape.
a) Desk research (Gartner, Factset, etc.) — Market size, etc.
b) Qualitative insights — Ask your customers
c) Plot customer journey map on how they achieve their goal today — This will help understand inefficiency and friction in the customer journey
d) Prioritization:
e) Packaging and Pricing — Value proposition and value captured
f) Mock and Focus groups
g) Prototyping and user interviews
h) MVP and user interviews
i) A/B Testing with feature rollouts
j) Build measure learn — Iterate, Iterate, Iterate
Now that you have launched the MVP, Congratulations! It is important to measure the success both in short term and near terms. While it may change from business to business, a few metrics that we may track are:
North star metric: Short term (% New sign ups for self serve model) Long term — WAU (Weekly active users)
Once MVP is launched, idea is to observe and learn from how users are engaging with platform. This is the best time to detach yourself from the idea and enter the student mindset.
Few methodologies that I find really help to guide my product strategy post launch are:
a) Quantitative insights — Collect data around key metrics, will share the ‘what’ behind the usage
b) Qualitative insights — Recording of users are interacting with the landing page, CTAs etc. This will help understand the ‘Why’. User interviews of the self serve users to understand whether you are solving their core problems. I would use the feedback to inform the future iteration.
c) Generate hypothesis: The marriage of ‘What’ and ‘Why’ will define the hypothesis. Generate as many hypotheses as possible
d) Define, Prioritize, re-prioritize backlog as new data comes in, implement, launch, test, and measure: Small iterations to test each hypothesis and use that learning to inform the next version of experiment. I would avoid achieving local minima here such as CTA should be green vs red and instead will go for bigger picture.
e) Launch, learn, and iterate
f) Expand from one beachhead segment to the next
g) Experiment around following levers to discover 10x ideas
The order of carrying out these experiments should be guided by
Order: The order of experiments depends upon qualitative, quantitative analysis and also cost analysis but in general philosophy is:
Self-serve mode is not a replacement for the high-touch model. What works for one business model may not work for others so before implementing a self-serve model, get to the basics. When the self-serve model stops working time to assess the product and customer requirements.
Hope this was helpful. I enjoy writing on growth and monetization. Feel free to connect on Linkedin. Read our other articles on Product Leadership, Product Growth, Pricing & Monetization strategy, and AI/ML here.
As a photographer, it’s important to get the visuals right while establishing your online presence. Having a unique and professional portfolio will make you stand out to potential clients. The only problem? Most website builders out there offer cookie-cutter options — making lots of portfolios look the same.
That’s where a platform like Webflow comes to play. With Webflow you can either design and build a website from the ground up (without writing code) or start with a template that you can customize every aspect of. From unique animations and interactions to web app-like features, you have the opportunity to make your photography portfolio site stand out from the rest.
So, we put together a few photography portfolio websites that you can use yourself — whether you want to keep them the way they are or completely customize them to your liking.
Here are 12 photography portfolio templates you can use with Webflow to create your own personal platform for showing off your work.
Subscribe to our newsletter to receive our latest blogs, recommended digital courses, and more to unlock growth Mindset