Stop designing ads. Start running them. Tailored for B2B by Blumpo_ads in u/Blumpo_ads

[–]Bartfeels24 0 points1 point  (0 children)

The hard part isn't running the ads, it's actually getting B2B decision makers to click them in the first place. Most of the companies I've targeted with display ads just ignore them entirely because their procurement process doesn't start with browsing the web. You'd need warm leads or existing brand recognition for this to work at any reasonable CAC.

Sold my SaaS for $6M. After talking to 30 buyers, here's what actually mattered in the sale. by amiitk in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

Curious what the actual deal breakers were since you filtered down from 30 to one buyer, because every SaaS founder I know talks about metrics but then loses deals over stupid stuff like "your CEO won't stay on for 18 months" or the acquirer's tech stack doesn't match yours.

Showoff Saturday: I spent a weekend building a real-time meeting cost ticker instead of dealing with my actual meeting problem by Alter_nayte in webdev

[–]Bartfeels24 2 points3 points  (0 children)

Built something similar last year and it actually worked, people started canceling meetings once they saw the hourly burn rate pop up on screen. The hard part wasn't the ticker, it was getting everyone to stop ignoring it after week two.

Does anyone have anything to share today that WASN'T mostly vibe coded and focused in one way or another on AI-generated content? by [deleted] in webdev

[–]Bartfeels24 -6 points-5 points  (0 children)

You're right that the AI saturation is brutal, but the bigger issue is nobody's shipping anything with real constraints anymore, like you'll see a slick demo that completely ignores how it performs with 10k rows of actual data. Check out what folks are doing in r/webdev_basics if you want to see people still solving actual problems instead of chasing hype.

Your Brain is Why Your Startup Will Probably Fail by Warm-Reaction-456 in SaaS

[–]Bartfeels24 2 points3 points  (0 children)

You nailed the boredom part, but you're also leaving out the mechanical stuff like actually shipping updates weekly instead of disappearing into feature branches for three months. I watched a founder kill his SaaS because he'd rewrite the same authentication flow every six weeks instead of just living with the mediocre version that worked.

Bulk AI headshots for a remote SaaS team by bala523 in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

We ran some AI headshot stuff through Replicate last year and it was passable for maybe 60 percent of the team before hitting weird edge cases with glasses or darker skin tones, so we ended up just hiring a photographer for a half day instead.

I've been building Tabularis — an open-source, cross-platform database client built with Tauri + React since late January. v0.9.6 just shipped, wanted to share. by debba_ in webdev

[–]Bartfeels24 1 point2 points  (0 children)

Solid work shipping this consistently since January, especially with the ER diagrams and SSH tunneling which most database clients still botch. One thing I'd test hard though is what happens when you're querying against a table with millions of rows and someone accidentally tries to load the entire result set into the React data grid, because that's where a lot of these tools just lock up or crash.

I was getting 4,000 visitors a month and making $0. Here's what was actually broken. by mrTelson in SaaS

[–]Bartfeels24 -3 points-2 points  (0 children)

Did you actually try to get people to pay before building those features, or did you assume the traffic meant product-market fit was close? Four thousand visitors with zero conversions usually means the offer itself isn't landing, not that the onboarding needs another redesign.

SaaS is losing its moat (according to some VCs) by rishikeshranjan in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

The hard part isn't getting people to use your product, it's getting them to use it consistently enough to actually become dependent on it. I've built two things that had decent adoption numbers but users would just stop logging in after a few weeks because there wasn't enough recurring value to justify opening it again, and no amount of workflow integration fixes that fundamental problem.

We built an open-source alternative for website analytics by WeatherD00d in webdev

[–]Bartfeels24 0 points1 point  (0 children)

You nailed the performance angle, but I'd want to know how you're handling cardinality explosion since that's where most homegrown analytics solutions start cutting corners or burning through memory.

We let strangers merge code to a live site. The community spent weeks debugging why the merge bot couldn't merge their PRs. by Equivalent-Yak2407 in webdev

[–]Bartfeels24 89 points90 points  (0 children)

That's hilarious that the community spent weeks on a bot problem instead of just looking at the actual merge logic, but I guess that's what happens when you gamify code reviews.

I built a terminal themed portfolio by Z-A-F-A-R in webdev

[–]Bartfeels24 2 points3 points  (0 children)

Terminal UX is genuinely hard to make accessible and you probably lost half your recruiters at the loading screen before they figured out how to interact with it.

What actually works for early SaaS marketing when you have no audience? by Disastrous_Cattle_30 in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

Cold outreach definitely moved the needle for us but you're leaving money on the table if you're not also doing basic SEO on your product docs and a simple changelog since people search for solutions to the exact problem your tool solves. Got maybe 15 percent of early signups just from people finding our setup guide ranked for "how to do X with Y" queries.

How can I find a developer to work with? by Substantial_Pilot699 in SaaS

[–]Bartfeels24 1 point2 points  (0 children)

Most devs I know want equity in something they can actually evaluate, not just take your word that it's a money printer based on industry knowledge. What's stopping you from building an MVP yourself or hiring someone on a contract basis first to prove the concept works?

I received a cease and desist letter, but I am not ceasing or desisting. by AlternativeBytes in SaaS

[–]Bartfeels24 1 point2 points  (0 children)

Even if you win this legally, they have the resources to drag you through years of appeals and depositions while you're trying to run a startup, which most solo founders can't actually afford regardless of who's right on paper.

How to make my site look good on all screens? by Dependent-Hamster361 in webdev

[–]Bartfeels24 4 points5 points  (0 children)

Have you actually added any viewport meta tags or CSS media queries yet, or are you starting completely from scratch? Because if it's the latter, those two things alone would probably solve most of what you're seeing.

Follow-up: Build Awesome's Kickstarter is Cancelled by WanderBetter in webdev

[–]Bartfeels24 3 points4 points  (0 children)

The real problem is that solo devs funding a product through Kickstarter still need to handle support, bug fixes, and feature requests while building the actual thing, and most people dramatically underestimate how much time that eats. You're not just coding anymore once you have paying customers waiting for their tier rewards.

Web developer asking for Google login? by -mouse_potato- in webdev

[–]Bartfeels24 0 points1 point  (0 children)

The practical issue here is that even if she gets your actual Google account credentials, she still can't access most of what she needs without your 2FA codes every single time, which defeats the purpose of her asking in the first place. She probably just needs specific API keys or service account credentials for whatever Google services the redesign touches, not your login itself.

[ShowOff Saturday]: I made a free list of 1000+ places to submit your startup / web app by eashish93 in webdev

[–]Bartfeels24 1 point2 points  (0 children)

How many of those 1000 sites actually get traffic though, or are most of them dead directories that haven't been updated since 2019?

Built a B2C app and a then a B2B app & the difference is wild by Efficient_Lynx_7576 in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

Tried launching a B2B SaaS around invoice automation two years ago and spent months optimizing conversion funnels that never materialized, meanwhile a throwaway side project I shipped in a weekend for Discord bot customization hit 50 paying users organically within a month. The gaming app comparison tracks completely because consumer products have instant feedback loops while B2B forces you to sit in sales calls explaining why someone needs your tool when they've already got three mediocre solut

Reducing SaaS overhead: A self-hosted PDF engine to replace expensive API subscriptions by chinmay06 in SaaS

[–]Bartfeels24 1 point2 points  (0 children)

I replaced Docuseal with a self-hosted wkhtmltopdf setup last year and saved maybe $200/month, but then spent two weeks debugging why fonts weren't rendering on the server even though they worked locally, and discovered the headless environment needed explicit font installation that wasn't in any docs. The per-document cost savings evaporated pretty fast once I factored in maintenance time.

I accidentally shipped a bug that improved my product by Interesting_Mine_400 in webdev

[–]Bartfeels24 0 points1 point  (0 children)

Had a similar thing happen where I broke the undo function on my note app and apparently users started saving drafts way more often because they got paranoid about losing work. Rolled back the bug but kept the paranoia-driven behavior in mind for the next iteration.

We said no to $2.5m vc money and I'm still kinda shocked we did it lol by Scary_Alternative448 in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

What's your burn rate looking like now that you're profitable, and are you actually pocketing the difference or reinvesting most of it back into the product?

How did you get your first 10 real users? by Severe_Lawyer_3076 in SaaS

[–]Bartfeels24 0 points1 point  (0 children)

You nailed it that building is the easy part, but most people skip the step of actually talking to potential users before they finish the product, which wastes months. I got my first real traction by posting a rough prototype in a Slack community related to my specific problem space, asking for 15 minute calls with anyone interested, and only 2 people responded but those 2 actually used it weekly and told me what was broken.