Apr 29, 2021 · 19m · top-founders
What Do You Do After You Exit Your First SaaS For More than $9m?
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview with Nathan Latka, serial entrepreneur Jeff Epstein shares how he exited his first SaaS company, recovered from severe founder burnout, and applied key operational lessons to launch his new collaborative onboarding platform, Onboard.io.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Nathan holds 35.6% of the talking time here. How this is scored →
speaking balance: gold is Nathan, purple is the guest (3 minute bins)
When Latka suggests the company itself made him sick, Epstein pushes back slightly on the framing, clarifying that his own work habits and lack of boundaries were the cause.
Hardest push from Nathan ▶ 5:04 Pressing on valuation multiple and employee payoutsLatka presses Epstein on specific valuation multiples and whether the PE acquisition waterfall delivered meaningful equity returns to early employees.
Biggest teaching moment ▶ 16:17 Clarifying company versus user onboardingEpstein educates Latka on the technical distinction between user guidance tools like Pendo and infrastructure onboarding platforms that handle prerequisites before users ever log in.
Nathan holds their own ▶ 14:11 Deconstructing multi-axis SaaS pricing strategyLatka demonstrates deep domain mastery by dissecting Onboard.io's packaging model across per-seat pricing, product tier gating, and enterprise support add-ons.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Nathan as informed peer | Guest teaching | Guest disagreement | Nathan pushing back | Why |
|---|---|---|---|---|---|---|
| The Story Behind Building and Selling Ambassador | 7 | 4 | 1 | 3 | Latka demonstrates detailed recollection of Ambassador's growth and exit metrics, comparing the deal structure to Andrew Gazdeki's acquisition. Epstein gently corrects the fundraising figure from five or six million down to under three million and clarifies the final revenue was around eight million. | |
| Addressing Entrepreneurial Burnout and Restoring Health | 3 | 2 | 1 | 2 | Latka inquires about the physical and mental toll of building the company. Epstein candidly reflects on severe sleep deprivation, weight gain, and taking a full year off in 2019 to recover and reset health habits. | |
| Forming Onboard.io with Co-Founders | 6 | 3 | 1 | 2 | Latka highlights the common founder dilemma of solo ownership versus bringing on co-founders and using seed rounds to gain initial customer distribution. Epstein explains why sharing the emotional burden with co-founders was a priority for his second venture. | |
| Narrowing Market Focus and Approaching Revenue Milestones | 6 | 3 | 1 | 2 | Latka rapidly calculates estimated MRR based on customer counts and typical B2B contract sizes. Epstein explains the discipline required to stay focused on a specific SaaS niche rather than building custom features for every early prospect. | |
| Strategic Pricing Architecture and Feedback Prioritization | 8 | 5 | 1 | 2 | Latka analyzes Onboard.io's multi-tier pricing page, identifying user-based and feature-based upsell levers. Epstein explains the strategic rationale of pricing low for feedback, and clarifies how company-level onboarding differs from user walkthrough tools like Pendo. | |
| Engineering Team Composition and Operating Structure | 4 | 2 | 0 | 1 | Latka breaks down the engineering versus go-to-market split across the five-person team. Epstein outlines how three developers handle code while the two co-founders manage sales, support, and product. |