Everyone uses AI now. To code. To write. To ship faster. But planning still feels stuck in the old days. Roadmaps get built on guesswork. Marketing means posting and hoping.
I am following spec driven development. I write the specs first. Every feature, every decision, ties back to it. It keeps me from drifting into random ideas mid build. My roadmap comes from that spec, not from gut feeling.
I use the same thinking for marketing. I write down what I'm building, who it's for, and why it matters. Before I post anything.
So I'm curious. How are you planning your roadmap right now? Do you have an actual system, or are you winging it like most of us?
I m exploring a problem faced by small businesses that receive supplier price lists in different formats, especially PDF, Excel and CSV. Once the data is structured correctly, updating prices is often simple. The difficult part seems to be turning inconsistent supplier files into clean, reviewable data that can be imported into the company s existing system. My current plan is to avoid building a full product immediately. I would first offer a small paid service: the customer sends one supplier list and a sample of their current catalogue, and receives a checked import file showing the price changes. If two or three businesses pay for this and the same workflow repeats, I would automate only the recurring steps. Would you test it this way, or is there a better validation strategy? What evidence would you require before building the SaaS?
Been hearing a lot of "don't raise money, investors just push you to grow too fast so they can exit, even if it breaks the business" from people around me lately. Never actually raised myself, so can't tell if that's real experience talking or just internet cynicism.
Curious what founders who've actually taken money would say. Was that pressure real, or manageable. Did raising help more than it hurt, or was the warning right
Genuinely trying to hear both sides before forming an opinion on this.
I ve been dealing with something at work that I m still trying to figure out.
I m in a small startup environment where I m responsible for a lot of the technical and product side. I build things, test ideas, fix problems, automate workflows, and usually end up owning the execution.
The difficult part is that sometimes I m expected to make something work or become predictable, even when the result depends heavily on things outside my control.
For example, third-party platforms, algorithms, changing rules, sales, distribution, or decisions that I don t make myself.
I launched a small price-comparison site at the end of July. It tracks current catalogs of guitar models from a handful of major brands and matches them against new stock at independent dealers roughly 1,250 models across 11 URLs (a home page with the comparison table, five brand pages, and the usual about/methodology/legal pages). Static HTML, no client-side framework. The one rule I built it around: no synthetic data if a price can't be kept fresh, it links out to a search instead of showing a number I made up.
Build side works. Discovery doesn't. Seven weeks in, a site: query returns nothing and Search Console shows 11 pages "Discovered currently not indexed" with 0 indexed. The sitemap was read successfully and all 11 URLs were discovered from it, so Google has known they exist since July.
I miss Mint. And when I say that, I mean that I miss the old Mint before they got acquired by Intuit and started selling my data to anyone who would buy it. I want more than what my bank offers but this space seems surprisingly quiet unless I am hiding under a rock.
I receive leads from three different partners, but each partner sends them in a different format.
One uses a spreadsheet, another sends them by email, and the third uses a form. It makes it difficult to create a consistent process and keep everything structured in our pipeline.
How do you handle leads coming from several partners in different formats?
Do you standardize how partners submit leads, or do you integrate each format into your existing CRM?
I recently submitted a discussion post (topic: security risk of ecosystem lock-in with password managers) and it got rejected. Went back through the community guidelines afterwards and honestly couldn't pin down which one it violated - no product mention, no promotion, no spam, just a genuine question aimed at makers and users. I am curious how others here dealt with a similar situation:
Did you appeal, and did it actually go anywhere? or Did you just rewrite and resubmit without knowing what was wrong the first time?
I am trying to figure out if this is a broader pattern worth raising with the PH team directly. Thanks for your comments and contributions in advance.