Sightline for funds, accelerators and venture studios

One check across every company in the portfolio.

Before a raise, before demo day and after each release, Sightline reads each company's public pages across three lenses: the interface (broken links and forms, unclear claims, pages that fail on a phone), search visibility and the technical setup. The same method for every company.

See a sample report Request an invitation

Example Medium Interface /pricing

The pricing page and the homepage name different numbers of customers.

Evidence: The homepage says "Trusted by 400+ teams"; the pricing page says "Join 250 teams".
Why it matters: An investor who clicks through before a call notices the mismatch, and asks which number is in the deck.
Fix: Pick one figure, use it on both pages and date it.

Evidence

/ (homepage heading): "Trusted by 400+ teams"/pricing (intro line): "Join 250 teams"

Fix for your developer

replace both strings with the one current figure

Example finding.

What Sightline checks

Three lenses, one report.

Each finding lands on a to-do list for the page it belongs to.

Interface

UX, forms, accessibility

Links that lead nowhere and forms a visitor can't get through; a price on one page and a different one on another; layouts that scroll sideways or controls too small to tap on a phone. Each one is pinned to the page and the element where it happens.

Search visibility

SEO, metadata, structured data

Page titles and descriptions that are missing, too long or the same on every page; headings out of order; structured data search engines can't read; pages a crawler can't reach. Each one names the page and the tag where it happens.

Technical

headers, cookies, HTTPS

Missing security headers, sign-in cookies without the protections browsers look for, certificate and HTTPS gaps and responses that give away more than they should. All read from what the site already returns to any visitor.

When to run it

The moments a company's site gets read hardest.

Before a raise

Investors click through the site before the first call. A broken sign-up form or a claim that contradicts the deck is better found by the team first.

Before demo day

The week a cohort presents is the week its sites get read by the most people. Run the check early enough to fix what it finds.

After each release

New pages break old links. Run it again after a company ships, or turn on the weekly re-scan for its domain.

How it works

From a list of companies to a report for each team.

Agree the list of companies

Write to us with the portfolio or cohort you want covered, and how each report should reach its team.
Each company verifies its domain

One DNS record per domain, added by the company itself. That record is its agreement to the check, and nothing runs on a company that has not added it.
The same check runs on every site

Every company gets the same method and the same report structure, with the evidence behind each finding and a to-do list for each page.
Repeat after each release

Run it again when a company ships, so the next report shows what's still open.

How it runs

Reads public pages the way a visitor does, on domains verified by their owner. It never changes anything on the site.

Verification: whoever manages the domain's DNS adds one record we give them. It shows the site's owner agreed, and Sightline reads nothing until the record is in place.

Pricing

Portfolio coverage is a subscription for each company domain, billed monthly. For a whole portfolio or cohort, write to us first. Prices aren't published yet: ask us and we'll tell you.