For people who run more than one company
See who's waiting on you — everywhere you work.
Reviews you owe, follow-ups you promised, calendar clashes — ranked across every Linear workspace, GitHub account and calendar you answer for.
Invite-only. Every account is set up by hand.
- Kestrel Studio
- Meridian Clinic
- Personal
It isn't that you're disorganised. It's that nothing sees all of it.
A normal Monday for someone who runs more than one thing:
At the studio
A pull request has waited three days for your review. The developer has stopped asking.
At the clinic
You promised to chase the lab for the results export. That was last Tuesday.
In your own calendar
Your 2pm supplier call clashes with a portfolio review — in a calendar you didn't open.
Each tool is fine on its own. None of them knows you run all three.
One queue. Every company. Ranked by who's waiting.
This is the real console, running on sample data. Click anything — it resets when you reload.
- What someone is blocked on comes first.A review you owe holds up another person, so it outranks your own overdue work.
- Every item says whose it is.Each company keeps its colour in every view — you know which hat you're wearing before you read the title.
- Found for you, not remembered by you.Follow-ups you owe and calendar clashes surface on their own, pulled from the tools you already use.
Three steps. The first one we do with you.
- 01Connect what you already use
Add each Linear workspace, GitHub account and Google Calendar once. Keys are sealed to your account and never shown again.
- 02Say which company is which
Group each workspace, repository and calendar under the company it belongs to. Every item takes that company’s colour from then on.
- 03Clear what's owed
Open one queue each morning. Complete, snooze, reschedule or block time — and the change goes back to Linear and your calendar.
Step one happens on a short call when your access is approved — no setup guide to wade through.
In daily use — not a mockup.
One working Sightline console, counted on 15 September 2026:
- 3organisations
- 34projects
- 199open issues
- 11pull requests waiting for review
Counts only, from a live snapshot. No names or titles leave the console.
Questions people ask before they request access.
Is it safe to give Sightline my keys?
Every key is sealed with AES-256-GCM under a key that belongs to your account alone, is never sent back to a browser, and can make only the handful of changes the console needs. How keys are kept →
What does it connect to today?
Linear for issues, projects and updates. GitHub for pull requests waiting on your review. Google Calendar for your day, your clashes and blocking time. Slack for notifications — the console does not read Slack messages.
Can my team use it with me?
Not yet. Today Sightline is single-player: one account, your own connections, your own data. Shared organisations and per-member state are on the roadmap.
What does it cost?
A custom plan, agreed with you when your account is set up. Standard prices are coming.
How do I get in once I'm approved?
You get a reply at the address you gave, your tools are connected with you on a short call, and you sign in with a six-digit code emailed to you — there is no password to set or remember.
What's coming next?
Shared organisations and per-member state; connecting tools without pasting keys; and a morning digest in Slack for your own account.
Stop being the one everyone waits on.
Tell us what you run. A person reads every request.