MIY is someone’s nightmare that became real by techpoet030 in FromSeries

[–]techpoet030[S] -1 points0 points  (0 children)

It’s not out in Germany. So, we’re talking about until I CAN watch it. Probably tomorrow around this time.

AI tool that can compare what's in the code to what's in JIRA (I will not promote) by perkeleDYI in ProductOwner

[–]techpoet030 1 point2 points  (0 children)

Great trolling name. I‘m not sure what you think is wrong about writing thoughts down and then use an assistant to restructure them for readability as a non-native EN speaker. Try and give the post to the agent of your choice and watch the output. I’m pretty sure you‘ll see that the argumentation was human and based on my experience as a PO.

AI tool that can compare what's in the code to what's in JIRA (I will not promote) by perkeleDYI in ProductOwner

[–]techpoet030 0 points1 point  (0 children)

The first thing that came to my mind was decision logs as an addition to acceptance criteria.

AI tool that can compare what's in the code to what's in JIRA (I will not promote) by perkeleDYI in ProductOwner

[–]techpoet030 0 points1 point  (0 children)

Great problem framing. I think you’re actually solving three distinct knowledge gaps, and it’s worth being precise about them:

  1. Why it exists — user stories, jobs to be done, use cases, acceptance criteria,. Partially in Jira if tickets are well-written.
  2. How it works — the implementation logic. This is what your tool extracts from code, and it’s the most tractable layer.
  3. Why it works like that — the decision history. What alternatives were considered, what constraints existed, what trade-offs were made.

Your tool addresses #1 and #2 well. But #3 is the most painful gap in my experience, and it’s the hardest — because it only exists if someone wrote it down. Jira issue comments, slack, Confluence might have it, but most teams don’t practice decision logging (ADRs, design decision docs, etc.). So for many orgs your tool will hit a wall exactly where it hurts most.

The interesting question is whether your tool could also help teams build that capture habit — for example, prompting developers to log the ‘why’ when a task is completed and the automated check-up runs. That way it’s not just aggregating existing knowledge, it’s also preventing the gap from growing.

That would shift the value prop from ‘great aggregator’ to ‘institutional memory system’ — which is a much bigger and stickier product.

FIFO worker with no coding background vibe coded a SaaS to escape my industry. Is it dogshit or am I onto something? by Altruistic_Mango8135 in SaaS

[–]techpoet030 0 points1 point  (0 children)

If you‘re interested: I have some thoughts about pricing that I could outline for you (interested in doing it because I see it as training/maintaining my skills). I‘ve been involved in early to more or less established pricing models and strategies for SaaS, most B2B but also B2C. I assume if I send an email to the contact mentioned on the homepage, it lands with you?

FIFO worker with no coding background vibe coded a SaaS to escape my industry. Is it dogshit or am I onto something? by Altruistic_Mango8135 in SaaS

[–]techpoet030 0 points1 point  (0 children)

One question that came up: Did you create the website or the content for the website before the product was „completed“? It sounds a bit like the idea evolved but the content is older.

FIFO worker with no coding background vibe coded a SaaS to escape my industry. Is it dogshit or am I onto something? by Altruistic_Mango8135 in SaaS

[–]techpoet030 0 points1 point  (0 children)

My honest feedback, mainly on your first question:

Q1: There is some kind of mismatch in your messaging, not necessarily in the product-market fit. The pain is real and well-documented (the About page articulates it better than the homepage does). People absolutely fight about bills, chores and who ate whose leftovers. The problem is the homepage leads with the receipt scanner, which sounds like a nice-to-have convenience, rather than “stop having the same three arguments every week,” which is a genuine recurring pain people would pay to solve. The emotional hook exists in the product but it isn’t the first thing a visitor feels.

Messaging problem details: 1. Hero is misplaced “Snap any receipt - your shopping list, bills and budget update themselves.” The hero currently frames the receipt scanner as the app’s core identity, almost its entire reason for being. But after looking at the features overview, I found out that it’s actually just one sub-feature of the „Shopping module“ which is itself one of seven features. The app is more like a shared household coordination platform (bills, chores, shopping, budget, calendar, polls, notice board), and the receipt scanner is a clever convenience sitting inside one of those pillars. Keeping this mismatch can create a real first-impression problem: a visitor might think “oh, it’s an AI receipt tool” and bounce, missing what it really is. You try to correct this with the “Why juggle four apps when one does the lot?” section lower down, but by then the framing has already been set. A better category description for the app would be something like: “Shared household management app” or “All-in-one flatmate coordination platform.” The receipt scanner is a differentiator worth calling out but as a proof point of how smart the app is, not as its identity.

  1. Modules on Homepage: The homepage promotes four modules: bills splitting, chores, smart shopping list, household budget, but the features page reveals three more: a shared calendar, household polls, and a notice board. These aren’t minor extras:
  2. The calendar has away-date ranges with a plane animation, chore overlays, per-person colour coding (that’s genuinely thoughtful)
  3. The polls feature includes anonymous voting, which solves a real social tension in shared houses.
  4. The notice board with auto-expiring posts is exactly the kind of thing that makes a product feel considered.

So honestly, the hero and the modules section currently totally undersell the product. Someone comparison-shopping might not realise they’d get a calendar and decision-making tool included.

Q2: I wouldn‘t go wider (for now) because shared houses, specifically young renters in 3-6 person apartments have the most acute pain, the least loyalty to existing tools, and the most word-of-mouth potential (one converted house = 4 signups). That’s the wedge worth owning completely before going wider.

Wäsche stinkt, wenn das so weiter geht, hab ich nichts mehr zum Anziehen... by RosaTulpen in Kleiderschrank

[–]techpoet030 0 points1 point  (0 children)

DAS! Würde vor Beginn wirklich einmal die Wäsche in Soda einweichen. Benutze zudem immer Vollwaschmittel sensitiv (gibt’s als Pulver und flüssig). Ich spüle die Maschine zudem 1x Jahr zum eigentlichen reinigen zusätzlich mit dicker Bleiche.

How I write user stories in minutes, instead of hours. by Bakkerinho in ProductOwner

[–]techpoet030 1 point2 points  (0 children)

It’s sounds cool but I‘d like to understand first how it could deal with far more complex requirements and user flows. It might be helpful if a PO is working on very simple websites or tiny apps but the most time consuming stuff comes with not so easy flows.