u/Logical_Musician8096

I worked with EDIs in the past and got tired of two things: every decent viewer is either paid enterprise software, or it wants you to upload your file to some server. Uploading real trading-partner data to a random website never sat right with me. So I built EdiPeek (edipeek.com). You paste raw EDI and it breaks down every segment and element in plain English. It also gives you a business summary of what the transaction actually means, so for an 850 it'll tell you who's ordering what from whom, for how much. It handles both X12 (850, 810, 856, 837, 835, etc.) and EDIFACT (ORDERS, INVOIC, DESADV, etc.). Everything runs locally in your browser, so nothing ever leaves your machine. That was the whole point for me, since a lot of what I look at is confidential. It's completely free, no signup. I also wrote up some guides on reading the common transaction types if that's useful to anyone. Would genuinely appreciate feedback from people who deal with this stuff daily. If there's a transaction type or segment I'm not handling well, let me know and I'll fix it.

https://edipeek.com/x12/

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.

userstoryforge.app

Background: I've worked about 8 years as a business systems analyst - the person who sits between business teams and developers, turning "just make it user-friendly" into something a developer can actually build.

The problem I kept hitting: a vague requirement almost never blows up immediately. It comes back weeks later as rework, after a dev already built the wrong thing. Every other team has tools (devs have linters and code review, marketing has CRMs, data teams have their stack), but the people writing requirements mostly get a blank page.

So I built StoryForge (userstoryforge.app). You paste a messy requirement, and it:

• Scores it against INVEST (a common agile quality framework)
• Flags every ambiguous word with the specific question you should ask the stakeholder
• Generates a clean ticket + a UAT test pack (Gherkin-style Given/When/Then)

Example: you paste "make the dashboard load fast and support lots of users." It flags "fast" (asking: max load time, at which percentile?) and "lots of users" (asking: peak concurrent count?), then rewrites it into something testable like "load within 2s under 3,000 concurrent users." Basically a quality gate that catches unclear requirements before they reach a developer.

Things I'd genuinely love feedback on:

1. The landing page - does the value land in the first 5 seconds, or is it confusing?
2. The free tier (5 reviews total) - does that feel fair before asking for money, or too stingy?
3. The actual output quality - if you paste a real requirement, does the rewrite hold up?

This is my first time taking something all the way to live payments, so I'm learning as I go. Happy to answer anything about the build.