Senior engineers at our previous companies took two weeks to ship their first PR. At GreenStack they ship one before lunch on day one.
I'm Aiko, VP Engineering at GreenStack. We're a pre-seed climate tech startup building software for carbon accounting. We hire senior engineers and we expect them to move fast — which means onboarding has to be ruthless. Logbook took us from a 2-week ramp to a half-day ramp. Here's how, and what nobody told me about doing this right.
“Onboarding used to be a 30-page Google Doc and a prayer. Now its a Logbook checklist that auto-provisions everything. Day-one engineers ship code in the morning. We didnt expect that to be possible at our size.”
Background
I came in with one rule: no two-week onboardings.
Hey — Aiko here, VP Eng at GreenStack. We do carbon accounting software for mid-market manufacturers in Europe. Pre-seed, 14 people, 9 of whom are engineers. We hire seniors only at this stage because we have to ship fast and we don't have the bandwidth to onboard juniors properly. Maybe later, not yet.
Before this role I was a staff engineer at a Series C company. Onboarding was 2 weeks of reading docs, getting access to 14 different systems, asking colleagues for the right Slack channels and discovering on day 9 that you'd been missing access to a critical internal tool. I refused to do that to anyone here.
4 hours
Avg time to first merged PR
From the moment a new hire signs in for the first time. They open Logbook, see a checklist, vault auto-provisions, repo access goes live, they pick up a starter ticket and ship it. Lunch.
92
Onboarding NPS
We survey every new hire 30 days in. Last 12 hires averaged 92. The previous company I worked at hovered around 30 for the same survey. Same population (senior engineers). Different system.
12
Engineers onboarded this way
Every single one shipped a PR on day one. Including one engineer who joined while she was on a different timezone — she did it from a hotel in Lisbon during a personal trip.
Why most onboardings fail
The bottleneck is humans, not technology.
The reason most onboarding sucks is that the work is spread across people. Someone has to manually invite you to GitHub. Someone has to share secrets in 1Password. Someone has to add you to AWS. Someone has to pick a starter ticket. That's 4 humans, each with their own queue, each unaware of the others. Day 1 = waiting on humans.
What I wanted instead was: the system does the provisioning, the system picks the starter ticket, the system tells the new hire what to do. Humans are only involved for the warm welcome. Logbook templates were the closest thing I'd seen to that.
How we built our day-one onboarding
We didn't build something fancy. Just a checklist that the system actually executes.
- 1
Step 1
Built the onboarding template
A Logbook project template called 'Engineer Day 1.' Includes a board with 14 cards (everything from 'sign the laptop policy' to 'merge your first PR'). Vault permissions auto-grant when the template instantiates for a new user.
- 2
Step 2
Pre-seeded a backlog of 'starter tickets'
I keep about 5 starter tickets in our Logbook board at all times — small bug fixes or low-risk improvements that don't require deep context. New hire picks one. By design they get it shipped within hours.
- 3
Step 3
Made the buddy mechanic explicit
Every new hire gets a buddy assigned in the template. Buddy gets a Logbook notification when the hire opens their first PR. They review it that day. No more 'is anyone going to look at my PR?'
- 4
Step 4
Iterated based on the 30-day survey
After every hire we look at the 30-day NPS and adjust the template. We've removed 4 cards and added 6 over 12 hires. The template is a living thing.
What day 1 looks like — old way vs ours.
Same caliber of senior engineer. Different first day.
Before
The old way
- Day 1, 9am: 'who do I ask for the AWS access?'
- Day 1, 11am: still waiting on someone to add you to GitHub org
- Day 1, 2pm: get added to GitHub. Spend afternoon reading codebase
- Day 2-5: more access requests, more reading docs, slowly figuring out who's who
- Day 6-10: pick up a real ticket. Take 2 days to ship because of unfamiliarity
- Day 10-14: feel like you can finally contribute
- 30-day NPS: 'it was fine, took a while'
After
With Logbook
- Day 1, 9am: open Logbook, see your checklist, vault is already provisioned
- Day 1, 10am: tour codebase with your buddy (30 min)
- Day 1, 11am: pick a pre-seeded starter ticket from the board
- Day 1, 12-2pm: actually code
- Day 1, 2pm: open PR. Buddy reviews it. Merged by 4pm
- Day 2 onwards: real work. You're already in the flow
- 30-day NPS: 'shipped on day one. felt useful immediately'
“The thing nobody tells you about onboarding is that the first day sets the tone for the next 90. If they ship something day one, they believe they belong. If they don't, they spend three months wondering if they were the wrong hire. Day 1 is everything.”
Aiko Tanaka
VP Engineering, GreenStack
Things we got wrong first
What we'd warn other eng leaders about.
Honest moment: this didnt work for our first hire. He was hire #8 and we used the v1 template, which had way too many cards (we'd over-engineered it). He spent his morning checking off boxes instead of coding. That's why we trimmed it. The current template has 14 cards, half of which auto-complete. The new hire only really has to engage with 7 of them.
Another thing — we found that the buddy mechanic only works if the buddy is genuinely available that day. We block buddies' calendars on day 1 of any new hire. Sounds dumb but it's the difference between PR merged at 4pm and PR sitting unreviewed for two days.
~$28k
Saved per new hire
Industry estimate is that productive ramp for a senior eng is $20-40k in lost output. We've shaved 9 days off that ramp per hire. 12 hires = something like $280-340k of recovered velocity in year 1. Yes really.
0
Departed for onboarding reasons
Of our last 12 senior hires, 0 have left within 90 days. Industry benchmark for senior ICs at early-stage startups is 8-12% in that window. Onboarding NPS predicts retention.
If you're hiring engineers right now
Day 1 is a contribution day.
If youre an eng leader at an early-stage startup and your onboarding is still 'here's a Google Doc' — fix it before your next hire shows up. Build a template. Pre-stage the starter tickets. Block the buddy's calendar. The tooling matters less than the discipline, but Logbook makes the discipline easy.
Day 1 is not orientation. Day 1 is a contribution. That's the bar. Anything less is leaving money on the table — and worse, leaving talent confused about whether they made the right choice.
Onboard your next engineer in an afternoon.
Logbook templates handle vault, access and starter tickets. Set up your day-1 template in an hour, ship it forever.