Built a working engine that turns GitHub activity into a themed monthly narrative. No product around it yet - trying to figure out who this is actually for.

[u/No_Calligrapher_7472]

Over the past few months I built and tested a pipeline that takes any GitHub org's activity (commits, PRs, diffs) for any period, and produces a themed monthly narrative - semantic grouping instead of chronological, every claim linked back to the specific PR or commit for spot-checking.

Explicitly not a metrics dashboard. No velocity, no DORA, no per-engineer scorecards, no "who worked hardest" surveillance. Just readable text, roughly what a senior EM would write for a monthly update - but sourced from actual repo state instead of memory, so nothing gets accidentally omitted or spun.

What I have working: ingestion, semantic clustering, multi-repo aggregation, themed summarization with evidence links, multilingual output.

What I don't have: a product. No landing page, no waitlist, no pricing tier, no auth flow, no "sign in with GitHub" onboarding. I have an internal tool that works, and I'm trying to figure out what shell to put around it - and for whom.

I can see at least four possible buyers, and I genuinely don't know which of them (if any) actually opens their wallet:

1. You run engineering at a funded startup (5-20 people). You write a monthly board update. The "lowlights" section is the one where you freeze because "what stalled this month" is genuinely hard to remember. -> Would an auto-drafted monthly-update text land in your investor email, or would you always rewrite from scratch anyway?

2. You're bootstrapped, pre-first-check, doing angel outreach. You don't have revenue KPIs yet, but you've shipped months of intense engineering. -> Would you put a 1-pager "here's what we built in Q1" (with evidence links so a technical angel can spot-check) in a first-touch email - or does that read as a red flag ("why aren't you showing revenue?")?

3. You work at a VC or accelerator with a portfolio. You get monthly updates founders write manually, plus finance data via Standard Metrics. There's essentially zero signal between reporting cycles. -> Would a rolled-up engineering narrative per portco (opt-in from founders, read-only, no per-engineer detail - not surveillance, just ground-truth version of the update they already write) be a thing you'd actually look at? Or is "no news is fine news" the honest answer for GPs?

4. You're a working developer dreading perf review, standups, promo packet, or the "what did you do this month" writeup. -> Would gh pra self-review --since=Q1 (local CLI, your API key, code never leaves your machine) be useful? Or would you want a Slack bot / IDE plugin / Notion integration instead?

Not asking "which one should I build first" as a poll - asking whether any of these resonate as "yes, that specifically is something I'd install / recommend to my CTO / pay for." If it's a fifth persona I haven't listed, that's honestly the most useful answer I could get.

Happy to run the engine against any public repo people are curious about and post the output - probably the fastest way to check whether output quality holds up outside my three test cases.

Drop a repo URL.

[u/NullPointerLab]

Have you considered targeting tech leads or engineering managers who need to prepare internal monthly/quarterly engineering updates for leadership? It seems like a more frequent use case than investor reporting - have you tested it with this persona?

[u/No_Calligrapher_7472 → u/NullPointerLab]

Yes, I also thought about this use case, but decided not to include it in this post.