Release notes from merged work
Lift drafts notes from the pull requests that merged this week. You edit them. You do not start from a blank page.
Launch on
Lift keeps your launch checklist, release notes and rollout plan in one list. A team of four can ship without a war room. Early access opens to the first 500 teams.
Launch in
Doors open 09:00 UTC on Wednesday 18 November 2026.
Every task has an owner, a status and a deadline. Lift counts what is left and tells you on Monday, not on the Wednesday night you were hoping to ship.
Mon 16 Nov
Lock the list. Anything not done by Monday moves to week two, with no argument.
Tue 17 Nov
Review the drafted release notes and the status page copy. Sign off the rollback steps.
Wed 18 Nov
Rollout starts at 10%. Lift shows each check as it passes and flags the one that does not.
Thu 19 Nov
Move to 50%, then everyone, once the error rate and the support queue look quiet.
Fri 20 Nov
Lift keeps what slipped and why, so the next launch starts with a shorter list.
We shipped two products from a shared spreadsheet and a group chat called "do not push yet". The spreadsheet always lost a row.
Lift is the list we wished we had: scope, notes, rollout and rollback in one place, showing what is still open before anyone presses the button.
Early access is small on purpose. Every team that joins gets a call with one of us in the first week.
Ines Varenne, co-founder
Yes. Early access teams use Lift free for six months from launch day. We email before anything changes.
Read access to merged pull requests, so release notes can be drafted. Lift does not write to your code.
Teams of two to twenty who ship every week or two and have no release manager. Solo builders are welcome too.
The first 500 teams get Pro free for six months. We reply within two working days with your invite.
Email hello@example.com with your team size and what you are launching, and we will send your invite.