What Entrepreneurs Can Learn from Topgrading
Priya had bootstrapped her packaging startup for two years when a polished stranger approached her booth at a trade show and pitched himself as the VP of Sales she needed. He spoke fluently about "pipeline velocity," name-dropped a fast-growing company he'd supposedly built from nothing, and predicted he could triple her revenue in a year. She hired him on the spot, skipping any call to that company. Three months in, she learned he had been a mid-level account manager there, not its architect, and his pipeline was mostly recycled contacts from his last job. Priya had judged him the way she judged a sales pitch: on delivery, not on what he had actually done. The cost wasn't just his salary — it was the quarter her company lost believing a story instead of checking it.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
The founder's gut-check trap
Many entrepreneurs treat their instincts about people as an extension of the instincts that let them spot a market opportunity. But reading a market and reading a person's competence are different skills, and confidence in one does not transfer to the other. The founder who trusts a hire because "the idea felt right too" is applying a good instinct to the wrong problem.
A founder hires a technical cofounder after an exciting whiteboard session, never asking to see code the person actually shipped, and later discovers the cofounder has never finished a project alone.
Before extending any offer, require one specific, checkable example of a finished result the person personally produced, and follow up with someone who watched them produce it.
Verifying the track record behind the pitch
A candidate's résumé or pitch tells you what they want you to see; their history of finished, verifiable work tells you what they're capable of. For an entrepreneur, this means treating claims about past companies or revenue numbers as starting points for verification, not conclusions.
A founder takes a freelancer's portfolio at face value, never asking which parts of a listed project they personally built, and later learns they subcontracted the hardest work.
Ask a major hire or partner to walk through one project in detail — what they decided, what went wrong, what they'd change — and compare the honesty of the answer to the polish of the pitch.
Asking questions that surface the real story
Generic questions invite generic, rehearsed answers. Founders get better information by asking about specific outcomes and inviting honest self-assessment, since a willingness to admit a real misstep is often more revealing than any success story volunteered unprompted.
A founder asks a candidate about their "biggest weakness" and accepts a rehearsed, harmless answer instead of asking about a specific project that failed and what they learned.
Replace broad questions with ones anchored to a specific past situation, and push once more when an answer sounds smooth rather than specific.
The compounding cost of a bad call
A mismatched hire rarely announces itself immediately. In a small company the cost compounds quietly — a wrong VP of Sales burns through the customer list, a wrong cofounder poisons decisions, and every week of delay multiplies the damage across the team, not just one role.
Speed and verification pull against each other in a startup. A founder chasing a hire before a funding deadline may feel a week spent verifying is a week the company can't afford. But skipping it to save a week routinely costs months once a mismatch surfaces — a tension worth weighing deliberately, not by default.
Name one thing, honestly
Think of the last person you brought into your business on a strong first impression — what specific, checkable evidence did you actually have about their past results before you decided?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Replace broad questions with ones anchored to a specific past situation, and push once more when an answer sounds smooth rather than specific.