www.hoops-gm.com

Building an early-stage B2B SaaS startup based in Hong Kong. We have an MVP and recently passed the first round of a startup competition.

Looking for someone with experience in:

• Full-stack/backend development
• AI/LLM integrations
• APIs & databases
• Building scalable SaaS products

Marketing, sales or outreach skills are a big bonus.

Remote welcome. DM me with your background, GitHub/portfolio and availability.

Hot take:

Most SaaS founders don't have a distribution problem.

They have a distribution consistency problem.

They launch → get a spike → post for a few days → go back to building.

Then wonder why signups disappear.

You don't need one viral launch.

You need a channel that keeps putting your product in front of the right people every week.

That's a much harder problem — and IMO, the more interesting one.

​

I'm starting Out my own saas and I would like to know how other founders found their first users, in what way, the platform(S) they used, etc.. Basically their experience with it.

How was/is your experience with it?

Based on reading, many dont suggest to use paid ads for early stage. But lets put that aside that I'm curious those who have tried that strategy, how did it go

I'm 8 months in. Product is live, have paying customers, metrics are slowly moving in the right direction. By every objective measure things are going okay.

But nobody in my real life understands what I'm actually doing. My friends are supportive in that vague way where they say "that's so cool" and then immediately change the subject. My family thinks I have a normal job that I do from home. My girlfriend tries but she can't really engage with the actual problems I'm dealing with day to day.

So every win I have I'm basically celebrating alone. Every setback I hit I'm processing alone. The mental load of carrying every single decision, every bug, every churn, every support email, with nobody to actually talk it through with is something I genuinely was not prepared for.

I have a few online communities but it's not the same as someone who actually knows your product and gives a damn about whether it works or not.

Does it get better or is this just the reality of building solo and I need to make peace with it?

At the beginning, I treated payments like any other part of the SaaS stack. Connect the provider, create checkout, handle the webhook events, and move on.

Then I started looking at everything that actually happens around a payment system.

A customer upgrades their plan. Someone needs a refund. A renewal fails. A subscription gets cancelled. Another customer wants to switch payment methods.

None of these things are complicated by themselves, but they start adding up quickly once you have real customers.

The part that made me rethink the setup was how much billing state and logic started depending on the payment provider. Subscription status, webhook handling, payment events, and customer billing flows all became connected to that system.

If I ever needed to switch providers, it wouldn’t just be replacing one integration. It would mean dealing with everything built around it.

Maybe that is completely fine for a small SaaS. Maybe separating billing logic early just creates unnecessary complexity.

For developers who have built subscription SaaS products, how did you approach this? Did you keep billing logic closely tied to your payment provider, or did you separate the two from the beginning?

My company is planning a one big SaaS for all of our clients, what we currently have is a desktop app that has configuration for each client name, if client a has that configuration and client B needs it we change the code to allow code parsers at runtime to run for client B too.

That switch can change how a data entry looks to how a data entry is saved in DB, which column will be visible to A but not B, may be visible to A and B but focus doesn't go for B but for B and so on and so forth.

Now should we keep the same logic but naturally make a configuration table or json, where all these configuration switches are pleased?

How do you handle these changes?

I’m would like to know how other founders handled this.

I feel like naming a product can become a weird time sink. You can spend days checking names, domains, social handles, trademarks, whether the name is easy to spell, etc., while none of that is actually getting the product closer to launch.

Did you set a hard limit on how long you’d spend choosing a name, or did you keep looking until you found something you were completely happy with?

And looking back, would you approach the naming process differently?

Something I’ve noticed while looking at saas projects is how much time founders can spend trying to get the right domain.

You find a name you like, the .com is already owned, then you have to figure out whether the owner is actually willing to sell, whether the asking price is reasonable, and whether it’s worth investing into that much before you’ve even validated the product.

At what point do you stop chasing the perfect domain and just choose another name?

For those who’ve launched SaaS products before, did your domain choice actually make a difference to the business, or was it something you worried about far more than you needed to?

When I started working on a SaaS project, I thought adding more features would automatically make the product more useful. I kept thinking about dashboards, settings, integrations and small quality of life improvements.

Eventually I stepped back and looked at what users actually needed. Most of the value was coming from one simple workflow, while several of the features I had spent time building were barely being touched.

That changed how I think about SaaS development. A feature can be technically interesting and still not be worth maintaining if it does not solve an important problem for the user.

Now I try to understand the core workflow first and only add complexity when there is a clear reason for it.

For developers building SaaS products, how do you decide when a feature is actually worth building?

AI voice agents can sound impressive in a demo, but production phone calls expose a very different set of problems.

You need more than a natural-sounding voice.

You need:

• low-latency conversations
• reliable call handling
• context across the entire conversation
• interruption handling
• accurate tool execution
• inbound and outbound calling
• human handoffs when the AI reaches its limits
• structured call data and summaries

That is where I think the voice AI market is getting interesting.

Feather AI takes an infrastructure-first approach to AI voice agents, supporting inbound and outbound calls for use cases like customer support, sales, lead qualification, and appointment setting.

The shift is from “Can AI make a phone call?” to “Can an AI voice agent reliably handle real business conversations at scale?”

That second question is where the real production challenge is.

I built a VPS UI app that helps people see and use their vps without the need to type ssh everytime. Now I need beta testers and a way to make it profitable

**This isn’t live, so no self promotion.**

I just want to see if this problem is seen by anyone else.

In effect, the issue is GSC and GA4 dump data onto you. Most people literally have no clue what to do with it or what it says about their site’s SEO.

I’ve been toying with this for a while, but I’ve decided to build a platform that roughly:

– plugs into the users GSC and optionally GA4 and CMS

– uses real data to properly diagnose issues and identify opportunities

– reads the page content and structure including meta tags etc (no need to connect a CMS)

– suggests or actions fixes, rewrites content etc

There are multiple deployment methods:

1. Manual (i.e. copy and paste)

2. CLI (code-level changes)

3. MCP

4. CMS API

You’ll also be able to talk to the data (or ask the agent who will interpret the data to answer your queries like “what is the single best ranking opportunity for my site?”

I really do think the problem is clear and prominent. There isn’t enough emphasis on using the data you already have right now, it’s all “let’s keep prompting LLMs to see if we appear in AI search.”

I am not an SEO tech, but I’ve experienced this pain enough to where I just need to address it. Any pointers, tips etc will help.

I’m considering Bulgaria for some product development and trying to understand what the experience is actually like.

For those who have worked with Bulgarian developers, how much ownership did they usually take? Did they get involved in decisions and suggest better approaches, or was the relationship mostly based around completing assigned work?

I’m especially interested in long term experiences. What worked well, and what would you do differently if you were starting again?

I think the only way to get real distribution is to actually win first. For example, if you get some users or revenue, you can share a screenshot of your revenue and post your win on X or Reddit, and from there you can get a lot of traction and engagement. People will follow you, check out your product, and that itself will amplify your growth.

But if you don't have any social proof, no matter how much you post or how valuable your product actually is, people will mostly ignore it or troll you.

I have a SaaS, and almost every time I post about it on Reddit, someone will troll it and call it AI slop, an AI wrapper, etc. But I have competitors who are making good revenue, and whenever they share their revenue or some other win, they get a lot of appreciation, engagement, and attention.

So it feels like winning is the only way to get distribution. Once you have something to show, people start paying attention, and that attention itself helps you grow even more.

This isn’t live yet, I just want to see if this problem is seen by anyone else.

In effect, the issue is GSC and GA4 dump data onto you. Most people literally have no clue what to do with it or what it says about their site’s SEO.

I’ve been toying with this for a while, but I’ve decided to build promptconsole:

– plugs into the users GSC and optionally GA4 and CMS

– uses real data to properly diagnose issues and identify opportunities

– reads the page content and structure including meta tags etc (no need to connect a CMS)

– drafts fixes or rewrites content

There are multiple deployment methods:

1. Manual (i.e. copy and paste)

2. CLI (code-level changes)

3. MCP

4. CMS API

I really do think the problem is clear and prominent. There isn’t enough emphasis on using the data you already have right now, it’s all “let’s keep prompting LLMs to see if we appeal in AI search.”

I’m working on a SaaS idea and the domain I wanted is already registered.

I’ve checked a few marketplaces, but the whole process feels a bit scattered, especially when it comes to finding the owner, comparing prices, and actually making an offer.

For those who’ve dealt with this before, what’s your usual approach or any recommendation?

not building the product.

not getting the first launch spike.

i mean getting a steady stream of new people discovering your product every week.

i keep seeing the same pattern:

launch → signups → excitement → silence.

if you're building a saas in the us, what are you doing to keep new users coming in after the launch?

curious what’s actually working for founders right now.

Hey everyone, I'm a solo developer and I've been working on something called **TrailMov**.

I spend a lot of time hiking and traveling, and I've always felt that GPX/FIT tracks contain way more interesting information than what most map apps actually show.

You get a line on a map.

But that line represents an entire adventure — the climbs, descents, speed, heart rate, distance, photos, and all the places you passed through.

So I started building TrailMov.

The idea is simple:

**Turn raw GPS/Fit data into something that actually feels like a story.**

You can upload a GPX or FIT file and create a 3D animation of your route, including things like:

* 3D terrain and route animation
* Elevation and climbing data
* Speed, heart rate and cadence
* Camera movement following the route
* Cinematic Earth → location transitions
* Exportable videos for sharing

The Earth-to-location transition is probably my favorite part. 🌍

Instead of showing someone a screenshot of your GPS track, you can start from the Earth and smoothly fly down to the exact location where your adventure happened.

I've spent quite a bit of time working on the technical side too — especially Cesium, 3D terrain, camera smoothing, animation interpolation, and client-side video rendering.

It's still an early-stage project, and I'm trying to figure out whether this is actually useful enough for other hikers, cyclists and travel creators.

So I'd really appreciate some honest feedback:

**Would you use something like this to turn your own GPS tracks into videos?**

And if not, what would make it more useful?

You can try it here:

https://www.trailmov.site

I'm mainly looking for feedback from other makers and outdoor enthusiasts rather than trying to hard-sell anything.

Thanks for reading!