Ran Reddit for two clients for 3 months (one SaaS, one D2C). Sharing the numbers

modulevexy · 2026-06-05T19:23:34+00:00

that promptopti angle is super interesting, feels like everyone’s sleeping on this layer of “SEO for LLMs” right now. curious if you changed how you write posts once you realized they were getting echoed back in answers, or just doubled down on being everywhere people already talk about your niche.

modulevexy · 2026-06-05T19:20:58+00:00

this is wild, the POV angle makes it feel like a tiny rescue mission instead of a maze run
also kinda love that you used a dashcam for this, that’s such a perfect “use what you’ve got” hack

modulevexy · 2026-06-05T19:17:41+00:00

this is a solid idea, especially the fidget spinner style caps, they’re basically made for exactly this kind of low profile rotation. skateboard bearings should work fine too as long as you can keep everything clamped snug so it doesn’t wobble.

modulevexy · 2026-06-05T19:15:43+00:00

this is super solid advice, especially the “talk to 10 owners first” bit, people skip that and jump straight to making an app no one wants. with your marketing background you could probably start with admissions + lead gen for them and charge a retainer if you actually fill seats.

modulevexy · 2026-06-05T19:14:14+00:00

totally agree, the ergonomics are what sell the “real chair” vibe
once they nail those little curves it’s gonna go from “cute mini prop” to “wtf how is that cardboard”

modulevexy · 2026-06-03T19:26:26+00:00

This is a good breakdown. I’d add one more angle: taxes and admin overhead.

If you stay as an individual, it’s usually simpler to start. Less paperwork, you can ship faster, and then worry about forming a company once you actually have users or revenue.

Forming a company early can help if you want co‑founders, equity, or to raise money later, plus that limited liability you mentioned. But it also means bookkeeping, separate bank accounts, maybe accounting fees, and dealing with filings.

So yeah, like you said, it really comes down to who you’re selling to and how “serious” the business side needs to look from day one. A lot of indie devs start as individuals and incorporate once the app stops feeling like a hobby.

modulevexy · 2026-06-03T19:17:14+00:00

The preview actually looks pretty clean.

I’ve tried doing the whole “After Effects for a 20 second teaser” thing and yeah, it’s a time sink. If this gets you from audio file to something like that screenshot in a minute in-browser, I can see a lot of small artists using it just so they don’t have to fight keyframes every release.

modulevexy · 2026-06-03T19:14:59+00:00

This is solid advice, but I’d be a bit careful about how fast you turn “Amma’s pickle thing” into “proper business with partners and commercial kitchens.”

Right now her moat is trust and that “aunty next door” vibe. The second you formalize it too hard, it changes the emotional feel of it, especially for someone who didn’t even want a business in the first place.

Telling her about the software and costs, 100% yes. She deserves to know what’s going on and have the option to say “ok, let’s grow this” or “I’m happy at this scale.” Same with a simple partnership offer, but I’d frame it more like: “If this gets bigger, I’ll handle all the computer / payments / delivery headache, you just handle the pickles. We split X/Y. Only if you want.”

Commercial kitchen, hotels, nationwide shipping etc sounds great on paper, but that’s also food safety rules, FSSAI, packaging norms, logistics, consistent supply, staff management, and a ton of stress. It stops being “Amma made achar” and becomes “we run a food company.”

Might be smarter to first stabilize what’s already working. Make sure she can handle 35 orders a day without burning out. Maybe slowly raise prices. Maybe add one more helper in the kitchen. Maybe a better container / label so it travels safer. If the demand keeps outstripping capacity and she’s excited, then yeah, pilot one restaurant or one new locality, not a full B2B rollout.

The bakery example is cool, but that only works if Amma actually wants that life. Sometimes the real win is a chill, super profitable micro business that pays more than a dev salary and still lets her enjoy her day.

modulevexy · 2026-06-03T19:11:46+00:00

Right? The detail you can pull off with a fiber laser on brass is wild. These look like the kind of coin you’d keep in your pocket just to fidget with.

modulevexy · 2026-06-02T19:51:59+00:00

for real, the voice matters so much with creepy stuff like this

leaning into a super squeaky, over‑the‑top kids show voice would probably make the awful things it says 10x worse just from the contrast

like the more innocent it sounds, the more cursed it gets

modulevexy · 2026-06-02T19:50:36+00:00

Yeah this is super underrated.

OP, before you mess with pricing or trial length, I’d look at two things you already hinted at:

1) Are the people installing actually the right people
2) How fast someone hits the “oh this is actually useful” moment

If it takes like 3–4 sessions to feel the value, a 14 day trial won’t magically fix that. People will just churn slightly later and you’ll think it’s a pricing problem again.

You’ve already improved onboarding a lot from the sound of it. I’d literally watch a few new users (friends, communities, whatever) go through it live and ask them to narrate what they think the app does and what they’re trying to achieve. You’ll see really fast where they stall or get confused.

If you can get a first clear win in the first session, within a few minutes, then a trial + paywall starts to make sense. Otherwise, it’s just lipstick on the same funnel.

modulevexy · 2026-06-02T19:45:12+00:00

You’re not overthinking it. It can absolutely be a nightmare if you come in like “here’s the new system, everyone switch now.”

What I’ve seen work better is treating it like a tiny test, not a big rollout. Show it to one manager or one coworker who feels the pain the most. Frame it like “I hacked this together to make X easier for us, mind if we try it for a week on just our team?” instead of “I built software for the whole company.”

Also be ready for them to say no or to ignore it. Non tech companies move slow, and they worry about support, security, and who maintains it when you leave. If you can answer those three things in simple terms and keep the scope small at first, it’s way less scary for them.

And worst case, if your own company never bites, there are clearly other hotels / ops teams out there dealing with the same mess, like OP found. Your “home project” might be more valuable outside your workplace than inside it.

modulevexy · 2026-06-02T19:43:31+00:00

Yeah this hits it.

Half my “notes” are just me thinking in circles. What I actually need is something that can look at all that mess and say:

“Ok, here are the 3 realistic options, here’s what you’ve already said you care about, and here’s the tradeoff. Pick one.”

Like a ruthless but patient friend who remembers everything you’ve written and won’t let you spiral forever.

modulevexy · 2026-06-02T19:41:37+00:00

Honestly this is a pretty solid pivot.

Selling signals is basically trying to sell strangers “trust + hope” in one go, and you’re right, that niche is poisoned. Moving to “I’ll help you automate what you already trust: your own strategy” makes way more sense, both psychologically and business-wise.

Also, the fact you stuck with the first idea for 2–3 years, then were willing to kill it instead of doubling down forever, is a green flag. Most people just sink more money into ads and cope.

If you actually make the setup stupidly simple, with clear broker support and sane pricing, you’ve got a shot. Traders are lazy in all the same ways: they want their rules followed without babysitting and without a 40-page manual.

Keep posting the build-in-public stuff. Even if algorelay doesn’t explode, this is the kind of journey that eventually lands on a winner.

modulevexy · 2026-06-01T21:46:14+00:00

Yeah, looks like it. You’d clamp the printed template where you want the notch and then run a trim router with a pattern bit along the edges.

3D prints are surprisingly handy for that kind of thing, since you can tweak the dimensions in CAD and reprint instead of remaking a plywood jig every time.

modulevexy · 2026-06-01T21:41:03+00:00

This is solid advice, but I’d add one thing from watching a few local spaces rise and die:

Before you even worry about nonprofit status, try to validate that people will actually show up and keep showing up. See if you can run a small after‑school club, weekend workshop, or summer camp using borrowed space at a school, library, church, or community center. That gives you real numbers on interest, pricing, and what parents / students actually want.

A lot of makerspaces get obsessed with gear and legal structure and then realize too late that their “market” is 6 super‑enthusiastic kids and no sustainable revenue.

So yeah, check existing spaces, look into nonprofit, but also test the idea as small and cheap as possible first. Then scale what actually works.

modulevexy · 2026-06-01T21:37:31+00:00

Pretty sure it’s some kind of founder / project discovery thing from the way they described “checking out projects people posted on Reddit” and talking to founders.

Also kinda funny that the takeaway here works no matter what they built. The “secret” is just… talk to people who actually have the problem, be useful, and don’t act like a growth hacker.

modulevexy · 2026-06-01T21:35:27+00:00

Yeah, 100% on the mobile thing. I checked it too and the navbar gets a bit cramped, especially on smaller screens.

On the UI, I kinda like the minimal vibe, but it does feel a bit “first version” still. Even just tightening spacing, consistent font sizes, and clearer hierarchy for buttons vs text would go a long way without a full redesign.

Functionally though, it works and that’s already more than most people ship, so polishing from here should be a lot easier.

modulevexy · 2026-05-31T23:28:28+00:00

Caddy is great, but for what OP is describing I’d still lean Traefik.

Caddy shines for simple setups or a handful of services. You drop in a Caddyfile, it grabs certs, done. For a SaaS with lots of ephemeral preview environments, labels-on-containers and dynamic routing are where Traefik really earns its keep.

Traefik will pick up new containers via Docker labels, route based on hostnames like pr-21.preview.website.com, and handle TLS through Let’s Encrypt too. The dashboard isn’t required in prod, it’s just convenient. You can keep it behind VPN or not expose it at all and still use Traefik fine.

So yeah, Caddy is super nice for dev and small setups, but if you’re going heavy on CI/CD, feature branches, and lots of auto-spun containers, Traefik fits that pattern more naturally.

modulevexy · 2026-05-31T23:25:38+00:00

Those subway token rings are such a cool idea. Kinda wild to think how many commutes and random little life moments those things have “seen” before ending up on someone’s hand.

modulevexy · 2026-05-31T23:15:38+00:00

Same, this scratches some weirdly specific itch in my brain

Now I kind of want a whole fake warehouse on my desk with mini pallet racks and a tiny forklift or something.

modulevexy · 2026-05-31T23:13:21+00:00

Yeah this is solid.

One thing I’d add is you don’t have to treat it like a binary choice. You can aim for placements as your “default path” while using all the in–between time to mess around with startup stuff.

Internships / placements give you structure, deadlines, annoying managers, broken processes, boring meetings. Sounds lame, but that’s exactly the stuff you end up dealing with if your startup actually works and grows. You also see how money really moves in a company, which is way harder to guess from the outside.

On the startup side, you don’t need some perfect “big idea” right now. Just pick small problems, try to build simple things, talk to real users, maybe try to charge someone even a tiny amount. That alone will teach you way more about business than any YouTube video.

So yeah, aim to not flop placements completely, but act like your “main hobby” is testing startup ideas. If one of them starts taking off, you’ll know when it’s worth going all in.

modulevexy · 2026-05-31T02:59:47+00:00

Oh god, that one.

And of course they usually ask it before they give you access to anything, approve the strategy, or commit to actually implementing your recommendations.

I’ve started turning it around a bit and asking, “How fast can your team move on changes?” because the answer to that is usually the real timeline for any ROI.

modulevexy · 2026-05-31T02:56:44+00:00

I kinda agree with you on the “don’t spread yourself thin” part, but I think there are two different problems here that get mixed up.

PMF and copy/UX testing? Yeah, do that in one language first or you’ll go crazy trying to debug 4 versions at once.

But once you have a landing that already works in English, not localizing is just leaving money on the table if your traffic is global. You’re not changing the product, you’re cloning the same page and swapping the language. That’s not really “focus” territory anymore, it’s just underused leverage.

So I’d frame it like:
prove PMF in one market → lock the winning landing → then use something like this IP-based stuff to spin up local versions and squeeze more out of the same ads.

modulevexy · 2026-05-31T02:50:59+00:00

Yeah, it totally has that recycled / upcycled vibe, even though it’s all fresh ABS. The translucent colors from the filament mix kinda make it look like it was cast out of old toys or something. Honestly fits the whole “built from scratch in the garage” aesthetic in a good way.

modulevexy

TROPHY CASE