Shipped extension #2, six new buyer-intent pages, and 109 startups across 19 sectors
Quick build-in-public update — past 7 days have been the busiest of the project.
What shipped:
-
Second free Chrome extension: VC GitHub Lookup. Hover any github.com/<owner> or /<owner>/<repo> link → tooltip with 14-day commit velocity, velocity change, contributor count and growth, signal type, and stage estimate. Chip injected on direct repo/org page loads. Toolbar manual lookup. Manifest V3, ~16 KB, no analytics, no account. Companion to the existing Crunchbase + Wellfound badge — together they form the complete loop: signal where you research, signal where the engineering originates.
Install: https://chromewebstore.google.com/detail/vc-github-lookup-—-startu/plgngijmloeljfkenecdkhiblcfcbblm
-
Five new buyer-intent pillar pages on the pSEO domain — each rich-schema, FAQ-rich, indexable:
- Pricing comparison (6 tiers, free → €1,997 one-time): https://signals.gitdealflow.com/pricing
- Buyers Guide (11 evaluation criteria, no email gate): https://signals.gitdealflow.com/buyers-guide
- Enterprise / Sharp Tier (€497/mo, 8-fund cap): https://signals.gitdealflow.com/enterprise
- "Best VC deal flow software 2026" answer page: https://signals.gitdealflow.com/answers/best-vc-deal-flow-software-2026
- "Are VC tools worth the money?" answer page: https://signals.gitdealflow.com/answers/are-vc-deal-flow-tools-worth-the-money
-
Three new conversion surfaces (Brunson v6): /experiments (live runbook of every distribution test), /earned-plays (third-party citations + their lift), /scorecard (rolling Scout Score on demand for any startup you paste in).
-
Dataset refresh: 91 → 109 venture-backed startups across 19 sectors. Public dataset, methodology on SSRN (abstract 6606558).
Stack: Next.js pSEO on Vercel, GitHub API pipeline, Pocketbase for subs, Stripe for checkout, Resend for the drip. ~50 routes total now.
Two questions for the IH crowd:
a) What's the most-overlooked pSEO surface for a B2B SaaS aimed at investors? I've shipped /pricing /buyers-guide /enterprise — is there a buyer-intent surface I'm missing?
b) Anyone running a free Chrome extension as the top of a SaaS funnel? Curious how you measure attribution from extension install → site visit → checkout.
Main site: https://gitdealflow.com
Sector data: https://signals.gitdealflow.com
Free Telegram: https://t.me/gitdealflow
SSRN preprint: https://ssrn.com/abstract=6606558
You’ve covered most of the obvious buyer-intent surfaces.
The missing one is probably not another comparison page.
It’s “decision compression.”
Investor buyers do not just want options.
They want faster conviction.
That usually means the strongest missing surface is not more pSEO.
It is a live “should I care about this company?” layer.
Something closer to:
That is the surface closest to the actual buying moment.
Most investor tooling pages still help users browse.
The higher-value move is helping them kill weak deals faster.
That is also where GitDealFlow starts feeling narrower than what the product is becoming.
Once the product is less “GitHub lookup for startup signals” and more “faster investor conviction,” something like Davoq.com carries more weight than GitDealFlow.
That distinction between browsing and deciding is the useful part here.
The sharper product loop may be:
I would test that workflow before changing the brand. GitDealFlow still explains the wedge. If investors consistently pay for the conviction layer rather than the GitHub signal itself, then a broader name has earned its way in.
The first experiment should probably be a live memo preview, not another landing page. Give an investor a company, return the memo, and measure whether it changes a pass / investigate decision. That would turn your naming argument into product evidence.
If you had to pick one starting artifact, would you lead with the red-flag scan or the memo?
I’d start with the red-flag scan. It creates an immediate pass/investigate decision, while the memo can become the deeper artifact once that signal proves useful.
Agreed. The scan is a two-second read, and pass/investigate is the decision investors actually make first. The memo earns its place later, once something is worth explaining.
So that settles the build order: red-flag scan first. Things like a velocity spike with no contributor growth, a repo going quiet, single-maintainer concentration, license changes. The memo then only exists to explain what the scan flagged, so it never becomes a template that profiles everything.
One design question I keep going back and forth on: should the scan end in a plain checklist of flags, or a one-line verdict with the flags as evidence? Checklist is more honest, verdict is faster to read. I lean checklist first and let the verdict earn trust later.
That’s a useful evolution from our original exchange. I’d be interested in continuing the conversation beyond the thread — would you be open to sharing the best email to reach you on?