1 Year, 3 Years, 10 Years — How to Last as a Maker

A 10-year maker isn't the fast one — it's the one who doesn't stop.

1 year vs 10 years, two paths

There's the startup that hit Product Hunt #1 in 1 year. Flashy pitches, media, investor interest. 2 years later, quietly gone.

Meanwhile, a maker who's been running 4 projects over 10 years and earns tens of billions of won a year. No flashy start, but they never stopped.

What's the difference? Not failure vs success. Speed vs sustainability.

Year-1 traps, the backlash of a flashy start

Year-1 founding statistics are scary. 3 of 10 new businesses close within a year; under 30% survive 5 years. But year-1 makers usually don't know the stats. Year 1 is full of flash.

Park's marketing-column classifier got 100 users in 6 months. 30 active, 5 paid. Revenue failed but proved something. "My idea might just work." That sensation is year-1's most dangerous part. You start mistaking unproven potential for proven success.

3 year-1 traps

1. Early-user feedback is low-reliability. Early users are pulled in by your passion. Hard to tell if they're real customers or supportive fans.
2. Operations is heavier than expected. Building took weeks; operating is endless. Bug fixes at night, email replies, server monitoring become daily life.
3. You can't decide what's next. Pivot/Kill/Persevere. Year 1 has too little data to ground decisions. Procrastination wins.

Year-1 flash is an illusion. 100 users is not proof — it's possibility. You must distinguish whether you grew possibility or accumulated operating cost.

The year-3 fork: burnout vs pace

Year 3 is the maker's inflection point. Year-1 flash fades, year-2 weight accumulates, year 3 splits into two paths.

Burnout signals

At first you ran on passion; over time you tire. Repetition wears you down; replying to customer emails feels heavy. Weekends can't escape Slack notifications.

Burnout is a vicious loop. Tired = lower quality = lower satisfaction = "I must work harder" = more tired.

The maker who found pace

Pieter Levels tried ~80 projects over 10 years and killed 70+. The 4 remaining now earn tens of billions of won a year.

He could do that because he didn't burn out. How? He designed the next from the start. When one project made money, hire help. While that team operates, build the next.

Burnout comes from going all-in on one MVP. Sustainability comes from pacing across multiple MVPs.

3 pacing techniques

1. Separate manager mode and maker mode: trying both at once wears you out via context switching
2. Clarify each MVP's lifecycle: defining "this project is in validation" auto-decides time allocation
3. Deliberately run small projects in parallel: when one gets stuck, focus on another

Year-10 patterns: what those who don't stop have in common

1. Not fast — consistent

Pieter Levels said "I'm not fast. I just don't stop." His first project took over a year. But every month, every year, he kept making something.

2. Don't cling to small wins

10-year makers don't treat first-100 users as too precious. They already know the path to the next 100, the next 1,000.

3. Invest in maker assets

Code goes legacy in 6 months, but relationships, know-how, habits keep producing value. Nomad List ships since 2014 and still earns 30–50M KRW/month. Why? The community is alive. That community is an asset Pieter has tended every day for 10 years.

New-business 5-year survival is below 30%, but makers who lasted 10 years keep exceptional satisfaction. Common thread: not "project success" but "pattern discovery."

The long-game maker's day: consistency over flash

Pieter Levels's day: morning email, bug fixes, read user feedback. Afternoon, new feature thinking. Evening, sketches for the next project. Weekend, rest. That's it.

Different from flashy startup culture. No all-nighters. Instead, daily consistency. 20–30 hours per week — enough but not burnout-inducing.

Common patterns of 5-year+ Korean makers

1. Hard boundaries: "work is one thing, personal projects another," "operations time 4–6 PM"
2. Small goals: not "50 users this quarter" but "1 active user a week"
3. Routine repetition: Sunday-evening retro, Monday-morning plan, Friday weekly review

The most important thing is mindset. Year 1: "I must succeed." Year 3: "Can I succeed?" Year 10: "How do I keep going?" The shift in question direction is the key to survival.

What stage are you at?

Year-1 check (3+ → you're year 1)

• You get excited about early user counts
• You don't precisely know your MVP's business model
• You can't decide between next MVP and growing this one
• You work 40+ hours/week
• You check Slack/email on weekends

Year-3 check (3+ → you're year 3)

Revenue exists, but growth has plateaued

User support is repetitive and tiring

One project doesn't feel enough

No money for a team, but too much for one

"Should I keep doing this?" surfaces

Year-10 check (3+ → you have the year-10 mindset)

• You run 3+ MVPs at once
• You can clearly decide what to Kill
• You have patterns extracted from past mistakes
• You work 15–25 hours/week and earn enough
• You can picture yourself 5 years from now

Once you identify the stage, set one action to step into the next.

• Year 1 → "Pivot/Kill decision in 3 months"
• Year 3 → "Start the second MVP"
• Year 10 mindset → "Set yourself up as an entrepreneur, not a developer"

Wrapping up

Lasting 10 years isn't about fast hands — it's about a mind that doesn't stop. What makes that mind isn't a flashy vision but small daily routines.

Next post (series finale) finds the next identity of "the twice-built maker." Are you ready to walk toward "the sold-it maker"?

Previous: A Maker's Real Asset
Next: [Fail School S2 Wrap-Up] The Next Seat of the Twice-Built Maker

About Seoyeon Park
Seoyeon Park is a fictional persona created by Fail School. Pieter Levels's 80 projects and Nomad List revenue, the new-business 5-year survival statistic are all real.

Minchul Kim, CEO of Freeive, Fail School