Pendi is [one-line description of what it does]. If you’ve ever [the moment of pain it targets — e.g. “lost track of X” / “had to do Y by hand”], that’s the itch it scratches.
The problem
[Describe the problem in one short paragraph. What were people — or you — doing before Pendi? Why was that annoying, slow, or error-prone?]
The frustrating part: [the specific failure mode that pushed you to build something].
What it does
At its core, Pendi [the single most important thing it does]. Around that:
- [Feature one] — [what it does for the user].
- [Feature two] — [what it does for the user].
- [Feature three] — [what it does for the user].
It explicitly does not try to [non-goal / thing you deliberately left out], because [reason].
Who it’s for
| Audience | Why they’d use it |
|---|---|
| [Primary audience] | [their main reason] |
| [Secondary audience] | [their main reason] |
| [Maybe-later audience] | [stretch use case] |
In one screen
Here’s roughly the shape of using it:
[paste a real example — a command, a config snippet,
a sample input/output, or a flow of screens][One sentence on what just happened in that example and why it’s the “aha” moment.]
Where it lives
- Try it: [link to demo / hosted app]
- Code: [link to repo]
- Status: [alpha / beta / shipped / side-project], built [solo / with whom].
Code walkthrough: Watch on YouTube — placeholder; replace with the real video link.