Reverse-engineering a billion-dollar company in 18 months
by @myfirstmillion
ABOUT THIS BRAIN
Ramp co-founder Eric Glyman recounts how he and Kareem Atalaya set the audacious goal of reaching a $1B valuation in under two years, then systematically de-risked and accelerated every step of the process to actually hit an $8.1B valuation in 24 months.
TECHNIQUES
KEY PRINCIPLES (10)
Set an impossible timeline first, then reverse-engineer the milestones.
Eric and Kareem literally asked “Can we be a billion-dollar company in 18 months?” before they had a product or even a name. They then worked backward to hit network approval in 45 days, bank approval in 60, first live transaction in 70, and 10 % weekly growth thereafter.
Why: Compressing the timeline forces ruthless prioritization and exposes every hidden dependency early.
"We wanted to go and make this company big, and either make it huge quickly or fail really quickly."
Pick markets where incumbents are still running on 30-year-old software.
Ramp targeted corporate cards where the largest competitors (Chase, Amex, Wells Fargo) had barely changed their products since the 1980s. Glyman compares using their parents’ bank vs. using their parents’ cell phone—one still works, one is unusable.
Why: Legacy infrastructure plus huge TAM equals an opportunity for 100× efficiency gains.
"Imagine that you wake up one day and you have to use the computer or the cell phone technology or the tools that your parents used when they were your age… but if you woke up and you had to use their bank account or their credit card or debit card, you probably could."
Monetize via interchange, not interest, to align incentives with customers.
Ramp earns ~1.4 % of every swipe (interchange) instead of charging interest or annual fees. Because customers spend more to earn more rewards, both sides win; Ramp’s revenue grows only when customers’ spend grows.
Why: Removes the adversarial relationship typical in credit cards (issuer profits when customer fails).
"It was crazy that the largest credit card companies on the planet were working really hard to get customers to spend a little bit more than they thought… and then devalue them in the background."
Design the entire company for shipping speed, not for comfort.
From day one they counted days since incorporation (2,310 at time of recording), set 10 % weekly growth targets, and built internal tooling so that 40-50 new hires can start in a single two-week cohort without slowing releases.
Why: In financial services, regulatory lead times are measured in months; product velocity becomes the only edge.
"We designed the company explicitly around velocity… Today we're 2,310 days old."
Pre-mortem every metric three to six months ahead and fight about it internally.
After losing 75 % of revenue overnight at their first startup, the founders instituted weekly “beat the shit out of each other” sessions to surface risks long before they appear in the numbers.
Why: Fast growth hides problems; forcing early conflict prevents later existential crises.
"We resolved to… beat the shit out of each other all the time, worrying about problems that are three to six months to a year out in the future."
Hire for operational triage, not for founder genius.
Glyman admits he naturally ignores 90 % of tasks; he therefore surrounds himself with operators who excel at cascading and finishing the long tail.
Why: Founders who scale learn to architect teams that compensate for their cognitive blind spots.
"It's actually totally fine to have huge flaws… I surround myself with people who are operationally unbelievable."
Audit your calendar weekly to spend time on the craft that energizes you.
Glyman blocks Saturdays completely off and regularly “blows up” his calendar to ensure he’s doing the product and design work he loves instead of defaulting to meetings.
Why: Founders who stop doing what they’re great at burn out faster than those who delegate everything.
"I pretty regularly try to go and blow up my calendar and be like, all right, I actually love doing this thing. Am I spending any time on it?"
Treat emotions as data, not directives.
Childhood experience watching medication change his brother’s moods taught Glyman to ask, “Does being mad help me or not?” before acting.
Why: Separating stimulus from response prevents bad decisions during high-stress growth phases.
"Maybe I could not be mad. Does being mad help me or not?"
WHAT YOU GET
This brain captures how an expert actually thinks. Your AI retrieves their decision principles semantically and applies their reasoning to your situation.
Use this brain with your AI · OpenClaw · Claude · ChatGPT
principles · semantic retrieval · per-use pricing
Free during beta · Pay per use soon