Install the GitHub App
Connect the repos where PRs and issues actually stall.
Stay fast. Skip management.
When work gets messy, most companies hire a manager.
There’s another path: keep the team flat, and put a system on the chase.
Today, Pilotless is a GitHub App that sends a weekly digest of what moved across your repos. The weekly digest lists stalled PRs and unassigned issues. Nudges and flags in each thread are on the roadmap, not live.
Where we’re going: make stalled work somebody’s job again, without hiring a manager for the chase. Digests stay part of that; ownership and Slack chase are on the pilot roadmap.
Pinned issue
your-org/app
Weekly status — week of 12 Oct #190
Shipped
- #181 merged
- #179 merged
Stalled PRs · Unowned issues
- #184 open PR, no activity for 9 days stalled
- #171 open issue, nobody assigned, quiet 15 days unowned
Why not a manager
Every growing team hits the same wall
Work stalls. A PR sits. A blocker has no name on it. Everyone’s busy — and you’re all just waiting for someone else to be responsible for this.
Chasing updates starts to feel like begging. Standups fill with recorders, not actors — status gets written down, but nothing moves.
The usual answer is hire your first manager. We think you can turn left instead: keep the team flat, and put a system on stalled work before the “cure” is an org chart.
Pilotless is the vaccination against management — starting with what’s already shipping on GitHub, then expanding through the pilot.
How it works
What you get today
Weekly digest
Pilotless sends a weekly digest of what moved across your repos, so you can see the work without running a status meeting. The weekly digest lists stalled PRs and unassigned issues.
You keep the judgment
It doesn’t decide product or people calls. It surfaces what stalled so humans can act.
What it does / doesn’t
Honest boundaries
It does today
- Run as a GitHub App
- Send a weekly digest of what moved
- List stalled PRs and unassigned issues in that digest
It’s building toward (pilot)
- Nudges and flags inside each PR and issue thread (on the roadmap, not live)
- Stronger ownership on stalled work — make each blocker somebody’s job again
- Slack chase — only after Engineering ships it
It doesn’t
- Connect to Slack today
- Automate 1:1s, career conversations, or conflict
- Hire, fire, or set compensation
- Make product or strategy calls
- Replace a manager — it gives you visibility on GitHub so you don’t need a manager just for status
For teams heading toward 15–30: a way to stay flat longer, not a claim you’ll never need a manager.
Example output
What it looks like on GitHub
Pinned issue
Weekly status
- Commits, people, PRs merged, issues closed and opened
- Shipped
- In flight
- Needs a decision or a nudge
- Closed
- Who moved code
Pull request #184
pilotless[bot]
bot
commented
Issue “pricing page blocked on copy” → unassigned → flagged in its own thread unowned
Listing both in the weekly digest already ships today.
Who it’s for
Built for founder-CTOs and tech leads who want to stay fast
You’re in the right place if
- You’re a founder-CTO or tech lead still chasing stale PRs and unowned issues yourself
- Your team lives in GitHub
- You’re small — or growing toward 15–30 and want to stay flat longer
- Work dies in “no owner” more often than in “bad ideas”
You’re in the wrong place if
- You don’t work in GitHub
- You need Slack chase on day one (roadmap, not shipped)
- You need help with 1:1s, career paths, or conflict
- You already have a management layer and want another dashboard
The pilot
Help us prove the left turn
We’re opening a small pilot for teams willing to run Pilotless on real GitHub work — using weekly digests today, and to help shape what comes next: stale-PR nudges, ownership chase, and Slack when it’s ready.
What you get
- Early access to the GitHub App
- A direct line to the people building it
What we ask
- Use it on real repos and real blockers
- Honest weekly feedback for 4 weeks
FAQ
FAQ
Is this “anti-manager” or anti-management?
Anti-defaulting to management. People managers can be great. We’re against treating “hire a manager” as the first fix when work stalls with no owner.
Isn’t this just another digest tool?
Digests are part of what ships today — and digests alone are easy to commoditize. The point of the product direction is ownership on stalled work. Today that’s a weekly digest on GitHub that lists stalled PRs and unassigned issues; in-thread nudges and flags, fuller chase (and Slack) are pilot roadmap.
Does this replace a manager?
No. Today it sends weekly GitHub digests so you don’t need a manager just for status updates. It doesn’t do 1:1s, career development, or conflict.
What tools does it connect to today?
GitHub (GitHub App). Slack is not available until Engineering ships it.
Where is our data hosted?
The web app is hosted on Google Cloud Run in europe-west1.
Who sees our repo activity?
To build the digest our server reads repository activity through the GitHub API; we store installation ids and repository names, not your code, and nothing is sold or shared. The digest is written into one pinned issue in the repository, so anyone who can read that issue can read it.
Do you have customer logos / case studies?
Not yet. We won’t invent them. Pilots come first.
Is there a Dutch version?
English first. Dutch later if we need it.
How much does it cost?
The GitHub App is free. Pilot terms beyond the App, we'll talk through with you directly.
Stay fast. Skip the org chart.
Start with a free weekly digest on GitHub. Help us build the rest.
PR #184 — no activity for 8 days → nudged in its own thread