Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More

Memberships

SaaS Life

92 members • Free

6 contributions to SaaS Life
SaaS API advice
Hey everyone! I've been loving reading everyone's insights and thier SaaS journeys. I've run into some issues and if love anyone's advice on what I should do: Some quick context: I'm building a SaaS tool for a trading card game that will allow users to fairly score and compare decks (even if they aim to do 2 completely different things). My initial gameplan is to run B2B and let other platforms use my tool via an API (to get my name out there before I run my own platform). 1. I have no idea if the API I have set up is built correctly for what I want it to do. (I'm not too code savvy) 2. I haven't had any luck getting B2B responses to my emails I appreciate any help on these issues and I hope you all have a great day!
2 likes • 20d
Maybe I don't fully understand your product, but I don't see the value in just providing an API. If I want to use your product I would have to build a frontend for it. Since users are using it to score and compare their decks I would think they would want a frontend to enter their card data into. Unless you are wanting to sell the API to other folks that already have a trading card app, then I would ask why should they use your API and pay you instead of just building it yourself. Do you have a source of data that is difficult to get?
Anyone else building a B2B product?
I am curious is the product you are building B2B or B2C? I am asking because it feel that most of the startup advise I read online is for B2C products. My product is B2B and I feel that most of what I read doesn’t apply. For example, I see people saying put up a landing page where folks can sign up before you start building to gage interest. That won’t work for my product. The sales process is going to be high touch and decision makers are not going to do anything until they can see it working. My validation instead comes from working in the industry and having decision makers flat out say they need a product that does this, or that other products that do similar things are too expensive. So I have been able to validate but it is a high touch process based on my existing relationships.
How many times do you post on Reddit a week?
I was hoping for some advice! Without blowing my own trumpet, I would say that I am a relatively okay-ish writer. As a result, I have been able to rack-up over 1,000,000 views on Reddit and grow both my personal brand (that feels icky to say) and SaaS business by doing less than 1 hour of work a week. The reason why I don't post more frequently is because: 1) Reddit doesn't have a community feeling and therefore replies to asking for help need to be taken with a pinch of salt. 2) [MAINLY] I don't know how much it is acceptable to post and as a result, I can't see a path to scaling further than I already am... Has anyone got any experience or thoughts about this?
3 likes • 23d
I post to Reddit a lot, but it is mainly stupid jokes that end up getting lots of upvotes. Anytime I post anything serious it usually gets no upvotes or even downvoted. I just don’t find Reddit a good place to have serious conversation. Like you said there is not much of community. People will just flat out lie about who they are and pretend to be someone they are not just to get upvotes. Unfortunately those people end up getting lots of upvotes, because they speak boldly with false confidence, so they end up drowning out the real experts. Add to this that the Reddit population tend to skew young, and thus not much life experience, it is just not a good place for serious conversation.
1 like • 23d
@Connor Jones I don’t know of any published demographic information, but my experience has shown it is a lot of teenagers and early 20s folks. Especially in the more popular subs.
MVP vs MLP vs MMP
Which one should we launch first? MVP (Minimum Viable Product) = just works, testable MLP (Minimum Lovable Product) = works + satisfies users MMP (Minimum Marketable Product) = ready to sell ME: MLP!
1 like • 24d
I would argue that all of these are the same thing. Thanks to startup influencers the definition of MVP has become distorted. It has become what ever you can slap together over a weekend and it may or may not work or even do what the customer needs. How can a product be viable if the doesn't satisfy the users requirements. You don't have to include every possible feature, but if the customer doesn't walk away saying "wow this solved my problem", then it is just not a viable product. I'm not sure where this rush to initial release pressure has come from. I guess it has come from the trend of building simple CRUD apps that offer little value that you market to other start up people on ProductHunt. If you are building an application that solves complicated real world problems it is going to take a while to build it out.
Favourite stack?
AWS, cloudflare workers, supabase? What’s yours?
0 likes • Aug 27
I’m building on GCP with Firestore. I really like it. I had started on AWS and Postgres because that is what I always used at work. Then I realized that it is my project and I can built it with whatever I want. I’m finding that the GCP SDKs are so much more ergonomic than the AWS ones. At least on Python.
0 likes • 28d
@Damon Bree I haven’t ran into any issues with that yet, but I haven’t done too much with auth so far.
1-6 of 6
Eric Moody
2
9points to level up
@eric-moody-6822
Early stage founder, just trying to get the MVP done.

Active 2d ago
Joined Aug 24, 2025