The *Four Materials* a Strong TIPS Application Has — Accumulated Six Months Earlier
The moment you *write* a TIPS application is too late. The four pieces of material that go into a strong application are *generated six months earlier*. What to accumulate up front.
The moment you write a TIPS application is too late. The four pieces of material that go into a strong application are generated six months before you start writing.
This post is those four pieces — what Korean founders should accumulate six months in advance of TIPS or similar programs.
(Context: TIPS is Korea's flagship deep-tech startup investment program. Acceptance brings ~$2M in matched funding plus mentor-network access.)
Material 1 — a number for the customer segment
Reviewers don't look at market size. They look at who you'll catch.
Weak: "Every enterprise that needs DevOps tooling"
Strong: "Korean public-sector and financial institutions with on-prem operations
as a mandate, 1,000+ employees — about 173 institutions"When 173 with evidence shows up, the reviewer sees the outline of the market.
That number doesn't appear at the time of writing. It's the result of six months of customer meetings + market research.
Material 2 — depth on one feature
One feature explained as why competitors can't easily build it beats eight features listed.
For CollabOps — the permission graph in the Execution Layer. We go deep on the technical reason. If a reviewer is convinced on that one, the other seven are accepted as byproducts.
That depth doesn't appear at writing time. It's the result of six months of building and operating that feature.
Material 3 — past-tense facts
Past-tense facts beat future predictions.
Weak: "Year-3 revenue $X million projected"
Strong: "Past 6 months: N institutional meetings, M PoCs in progress, K LoIs received"Every application has predictions. What actually happened is only your data.
These facts come from six months of sales activity. Cold-emailing for one week doesn't produce them.
Material 4 — direct signals that the team can pull it off
The question reviewers ultimately answer — can this team do this. Code, docs, talks, prior employers are the signals that answer.
Signal types:
- Member backgrounds (prior employers, education, talk history)
- Open-source contributions
- Conference talks
- Papers or technical blog
- Measurable outcomes of prior projects
These don't appear in the week before writing. They're years of accumulation.
When to start accumulating
Six months before application is the minimum. Twelve months is recommended.
12 months out: Team formed, first customer interviews
9 months out: First PoC, blog publishing starts
6 months out: Customer-segment number locked, feature-1 depth crystallized
3 months out: LoI conversations open
1 month out: Application drafted (materials already in hand)Without this pace, materials are missing at writing time, forcing predictions to fill the gaps — the most-frequent rejection pattern.
What happens with missing materials
Common pattern — applying with only 2–3 of the 4 materials. Predictions, hypotheses, and marketing language fill the gap.
Reviewers spot it immediately. Prediction-heavy language is a missing-material signal. Rejection.
When all four are strong
When the four materials are in hand, writing is fast. The materials answer for you. The writer arranges them concisely.
If application drafting takes 4 weeks, materials are thin. Within one week signals strong materials. A good signal.
Should you still apply with fewer than two of the four materials?
No — with fewer than two of the four materials in hand, delaying a TIPS application six months is shorter than rushing it. A submission that fills the gaps with prediction language gets rejected, and waiting out the next round costs more time than the delay would have. If you're preparing TIPS or a similar Korean startup program 6–12 months out, the work right now isn't writing — it's auditing which of the four materials you've accumulated.
Related posts
After Leaving Google, My Definition of Good Work Changed
I was a software engineer at Salesforce and Google before founding a company in July 2024. The standard for good code stayed the same. What changed is that the questions in front of the code became mine: which customer problem, and why now. Notes on how the definition of good work shifted from engineer to founder.
John Baek
Will Hiring More Senior Engineers Actually Make the Team Faster?
Expecting a team to speed up after hiring experienced engineers is natural. But there is something to check before opening the role: can you describe why work is slow as a concrete scene? Notes on separating work time from elapsed time, writing down the expected outcome, and how to judge a senior hire.
John Baek
Korea Had PC Bangs. What Kind of Environment Do Developers Need?
A question that started in a StarCraft lobby, where saying I was Korean was enough to make opponents leave. Where does skill actually come from? Move the practice-and-feedback loop of a PC bang into a developer day and you get an environment where you can see what happens after every change.
John Baek