Proof of Work

Before ENPITS: One Refusal and One Failure

The full list of what I tried, what I lost, and what I'm running now. No polished origin story. Specific numbers where they exist, honest gaps where they do not.

Published 2026-04-21

Why This Page Exists

Most agency founders hide their failures. They call the missing years "pivoting" or "learning" and move on, because a polished origin story sells better than a messy one.

I am going the other way, because I have to. I am the founder who is behind. I do not have the three-year track record a senior agency would have. I do not have the seven-failure résumé that makes a Silicon Valley origin story sound inevitable. If I want to earn the right to run anyone's outbound pipeline, pretending those gaps away is the worst move I could make.

So this page documents the single product I tried to build before ENPITS, the one decision I made that looked reckless at the time, and the live numbers of the pipeline I am running right now. Not as a confession. As the data that explains how ENPITS is set up today, and why the founder behind it shows up the way he does.

If you are considering hiring me, this is what you should know before we talk.


The Archive, Compressed

I do not have the classic founder-failure résumé. I was not fired four times. I did not burn through tens of thousands of dollars of personal savings on seven startups in a row. My archive is smaller, more specific, and less flattering than that.

Two entries, in total.

Refusal #1. I stepped off the Korean "correct path" (정답) before ever entering it. No formal employment history. Only military service, which every Korean man completes.

Failure #1. I attempted one product before ENPITS. A Korean B2C AI SaaS for job-seekers, built during university. It did not work. I lost real money I could not afford to lose, and months of my life I will never get back, on a product no one ended up paying for.

That is the full archive. No inflation, no quiet drafts I am pretending did not exist. Two entries, both open for inspection.


The Refusal

I wrote about this in detail on LinkedIn in my "Origin" post, so I will keep it short here.

The Korean default path is well-defined. Study hard in school. Get into a university other people recognize. Complete two years of military service. Graduate. Get hired at a company other people recognize. Spend the next ten, twenty, thirty years building someone else's product.

I was walking that path. I believed I was walking it correctly. Then one question stopped me.

"I am willing to spend ten or more years studying so I can earn money for someone who already built their company. But I am not willing to invest one year in my own?"

That sentence stayed with me for weeks. No mentor, no book, no grand framework. Just the arithmetic of how my time was being spent versus who was receiving the return.

So I stopped walking. That is the refusal. Everything that came after, including the one failure below, was downstream of it.


The Failure

The product was an AI SaaS that generated personalized answers to the four most common questions asked in Korean job interviews: the one-minute self-introduction, strengths and weaknesses, the book-and-role-model question, and the industry-or-social-issue question tied to the target role. The output was a PDF the candidate could rehearse from.

The engineering problem was not the AI. The engineering problem was making the generated sentences sound like the candidate instead of like a chatbot. Interviewers in Korea are trained to detect scripted language in the first ten seconds. The product had to produce hooks and sentence structures that were psychologically anchored in each user's actual background, not filled in from templates. Getting that right, in the AI tooling available at the time, took most of the build.

Three things I got wrong, in order of cost.

I underestimated the Korean B2C market. Korea has a university-enrollment rate near 80 percent. More than 40 percent of the adult population holds a degree. The end customers were, on average, extremely informed and price-sensitive, and they had already seen the previous generation of interview-prep tools. As a solo founder trying to charge for a polished product in that environment, I was not positioned to win.

I optimized for the product before validating the market. I spent the bulk of the build refining the psychology layer of the prompt engine. That part worked. What did not work was whether anyone wanted to pay for it at the price I needed. I built the difficult thing first and left the easier, more important question for last.

I tried to learn everything alone. I did not have an engineering background. I was a business-major university student with zero technical foundation, and I was teaching myself backend, web, API, database, payment gateway integration, and sole-proprietor registration in parallel. There was no one to ask. Today, with the current state of AI tooling, I believe the same product could be built with one-tenth of that effort. But from where I stood then, it felt like hitting a wall every morning.

Total cost: more money than a student without an income can afford to lose, months of time I cannot get back, and an opportunity cost I cannot even measure, because there was no next opportunity queued up.


What the Failure Actually Taught Me

The shipped lesson, the one most founders claim, is "ship at 80 percent and improve the rest after launch." That is true. It is also the most generic lesson a failed founder can claim, and I am not going to pretend it is my original insight.

The real lesson was more specific and more uncomfortable. I learned the shape of my own perfectionism.

On the upside, my personal quality bar is high enough that when something meets my internal standard, market acceptance usually follows. That is the asset.

On the downside, the same perfectionism makes me optimize the deepest technical layer first and leave the distribution question for last. For an agency business, where distribution is the business, that ordering is fatal. Left alone, I would always choose to tune the tenth prompt variant over sending the first cold email.

Knowing that about myself is the only reason ENPITS operates the way it does now.


The Structural Fix in ENPITS

When I set ENPITS up, I wrote a single operating rule for myself, because I knew what I would do otherwise.

Build 20. Sales 80.

Before ENPITS, my time allocation was approximately 100 percent build, zero percent sales. Now it is enforced the other way: no more than 20 percent of any working day on building and improving the system, at least 80 percent on outbound, proposals, conversations, and follow-ups.

That ratio is not a preference. It is a forced inversion, because the previous ratio is what killed the first product. If I catch myself tuning a workflow instead of sending a message, the rule wins.

This is the single operational difference between the founder who lost money and months on the interview-prep product and the founder running ENPITS today. It is not a different personality. It is a different rule.


Current Receipts

These are the receipts of a founder still behind. They are not impressive numbers yet. They are specific, dated, and not rounded, which is the only thing a founder in my position can offer that the polished vendors usually will not.

Below are the actual numbers for the pipeline I am running right now, through the week I published this page.

Metric Value
Week of the build Week 17, Day 12 (since launch)
Cold email messages sent to date 77
LinkedIn posts published to date 8
Hard bounces to date 0
Spam complaints to date 0
Opt-outs to date 1
Paid clients to date 0
Founding Pilot clients to date 0

There is no case study at the bottom of this page. There is no client logo bar. I have not hidden that. The receipts are what they are, as of today.

If you think "a founder with zero paid clients is not qualified to run my pipeline," that is a reasonable position, and you should not hire me. I am not going to argue with the math.

What I will point out is this. In the solo-outbound playbooks that actually worked for other operators, the distance between a founder with zero paid clients and a founder with one was almost always measured in days of consistent outbound, not in additional product work. The rough industry benchmark for that crossing is about ninety days. I am inside that window right now, in public, with receipts.


The Next Ninety Days, in Public

Public studies of solo-outbound timelines converge on roughly the same number. Most solo operators do not generate inbound signal until about post #31 on LinkedIn, after a deliberately unglamorous build-up that almost everyone quits before finishing. I am at post #8. That puts me just past a quarter of the way through the window most founders abandon.

I am behind by that measure. I am publishing anyway. The next ninety days of this page is a commitment made in front of strangers, which is the only kind of commitment that actually binds a solo founder.

Month 1, through mid-May. LinkedIn cadence to 50 cumulative posts. Outbound cadence to 150 cumulative first-touch emails. No paid clients expected yet, by design.

Month 2, through mid-June. First paid pilot secured, at the Founding Pilot $0 for 30-day slot or the Growth $997 monthly tier. First public case-study kernel published, even if thin.

Month 3, through mid-July. First Growth-tier paying client converted from the pilot. Case-study expanded. $997 tier activated as the main price anchor.

If the plan breaks, the break will also be published on this page. The reason a receipts section exists at all is to make it expensive for me to hide later.


Why I Am Publishing This

Most agency founders will never publish a page like this. The polished version sells better in the short term, and the polished version is also easier to defend when a prospect asks hard questions. I understand the trade.

ENPITS is built for the opposite reader. The agency owner who has already tried outbound, been burned by a vendor, and is now skeptical to the point of exhaustion does not want another pitch. That person wants to see that the founder running the pipeline has actually stood on their side of the table, has lost money on his own bad decisions, and has since built rules to stop those decisions from repeating.

I am an underdog by the numbers. I am fine saying that out loud, because the alternative is to pretend otherwise, and prospects in this market smell pretending from a mile away. I am publishing the receipts on the same page as the refusal and the failure for one reason: it makes it expensive for me to drift later, and it makes it cheap for you to check.

If any of this resembles a decision you are sitting with right now, my LinkedIn DMs are open. No pitch. Just a conversation.

Brooks Jeong, Founder, ENPITS. 2026-04-21


This document is part of an ongoing series. See also: The Sniper Formula · The Pipeline Architecture · The Suppression 3-Gate.

Your pipeline, engineered to the same standard.

Managed AI outbound for 1-20 person B2B agencies. Founder-operated, not outsourced.

See how it works →