The switch from B2C to B2B
I've always been a B2C founder. I've built an app to 100k+ MAU and sold it to a major company. I'm now building a tool called Modu.io to help businesses collect user feedback, taking directly from my own struggles (I got so frustrated with existing tools that I ended up using a single Google form).
I'm not particularly suffering the switch on the building side, I'm actually enjoying it since I'm more interested in using this tool myself, than I was with the B2C one. What I'm finding myself (sort of) uncomfortable at is the distribution/marketing side. I've launched on a bunch of ProductHunt like websites, ended up first on Uneed yesterday (didn't get much traffic-wise honestly), and bought a couple features on some of them as they were relatively cheap.
What unfinished tasks reveal about how teams actually work
Most workflow tools measure completion. I ve found that a recurring task deferred several times can be more revealing: it may point to an unclear handoff, unrealistic timing, or a dependency no one named.
What is one recurring task whose repeated deferrals taught you something important about how your team actually works?
What did you do differently on your best launch compared to your worst one?
I've been reading a lot of launch retrospectives lately and the interesting ones are never about the standard playbook (email list, communities, replying to comments, we all know that part). The good stories are always something specific the founder figured out for their own product, like one who spent the week before launch in the forums stress-testing his premise, so by launch day half the commenters already knew the product and had context.
If you've launched here more than once, what did you actually change between your launches, and which change made a real difference? Just as useful, what did you double down on that turned out to not matter at all?
AI research breaks quietly when provenance disappears
A confident wrong answer is obvious. A plausible answer assembled from stale, duplicated, or weak sources is harder to catch.
For research workflows, I care less about a giant stack of models than about source identity, retrieval time, exact transformations, and a way to reproduce the result. If the evidence trail vanishes, the polished summary is mostly decoration.
What provenance do you preserve in your AI research workflow today?
What evidence made you delete a feature you had already built?
Shipping a feature creates a weird emotional tax. The code exists, the screenshots look good, and suddenly sunk cost starts impersonating customer value.
The strongest deletion evidence I have seen is not a low click count by itself. It is watching the feature add decisions, setup, or confusion without improving the user s actual outcome. Sometimes the cleanest roadmap move is subtraction.
What convinced you to remove something you had already invested in?
Launch traffic is not retention evidence
A launch can tell you whether a message earns attention. It cannot tell you whether the product becomes useful enough to return to. Those are different tests, and mixing them produces very flattering dashboards.
I would rather trace a small cohort from promise to first value to an unprompted return than celebrate a large spike that disappears by Friday.
What is the first post-launch behavior you treat as real evidence?
How should AI tools solve the blank page problem for creators?
I ve been thinking a lot about the gap between having ideas and actually turning them into consistent content.
While building an AI content tool for creators, I noticed something interesting: a lot of people don t seem stuck because they lack creativity. They re stuck because they don t have a clear content direction.
They may have interests, personality, skills, and stories but they don t know how to turn that into a niche, a content plan, or repeatable posts.
For founders building creator tools, marketing tools, or AI products:
Why does AI still struggle to find the right data?
One of the biggest risks with AI analytics is not when the system says, I don t know.
It is when it gives a confident, polished answer based on the wrong source.
A company may have dozens of tables that could technically answer a question, but only one reflects the definition the business actually trusts.
How are teams helping AI distinguish between data that is available and data that is actually correct for the question?
What's the money app you rage-quit — and what finally did it?
Building in public and doing some research on my own scar tissue. I've rage-quit more finance apps than I can count YNAB three separate times, two spreadsheets I lovingly built and abandoned by week three, one app whose notifications made me feel like a parent was scolding me.
Every time it was the same story: the tool slowly turned into a chore, and one day I just... stopped opening it.
So I want the war stories. What money app or system did you rage-quit? Was it the manual data entry, the guilt-trip notifications, the endless categories to maintain or something else?
What made you finally walk away?
How do you recolor SVG icons without editing the source file?
I often download SVG icons or illustrations, but changing their colors can be more time-consuming than expected.
Some people use Figma or Illustrator, while others prefer browser-based tools.
What's your fastest workflow for recoloring SVGs? Any tools or tips you'd recommend?