How a JP Morgan Employee Built a Web Hosting Business Nobody Thought Could Win
How Elston went from JP Morgan to 40,000+ MRR — by ignoring the giants, building for the people they forgot, and finding the one distribution channel that compounded into 20 million Google impressions.
- 01 The Setup
- 02 The Idea
- 03 The Business Model
- 04 The Distribution Machine
- 05 The First Sale
- 06 The Traction Framework
- 07 What You Can Apply
- 08 Your Move This Week
Every issue of The Real How follows the same structure. The Setup. The Idea. The Business Model. The Distribution Machine. The First Sale. The Traction Framework. What You Can Apply. And your move for the week.
We do this because most people only ever see the revenue screenshots. The $40k MRR post. The "I quit my job" tweet. Nobody shows you the evenings at JP Morgan when he was still there four years past when he planned to leave. Nobody shows you the first year when the MRR averaged $70 a month and most people would have quietly given up.
I am building RealHow to document these patterns clearly, for myself and for people like us — employed, restless, building something on the side, trying to see the full machine before we commit to it. This issue is about one of the cleanest executions of that machine I have found. Let's get into it.
The Setup: Four Years Longer Than He Planned
Elston joined JP Morgan with a plan. Six months. Get the experience. Leave. Four years later he was still there, not because the money was bad or the work was miserable, but because inertia is the most invisible trap ever designed. It does not feel like a trap. It just feels like another reasonable week.
You probably recognise that season. The job is fine. The salary is fine. There are just these ideas that arrive at 11pm and do not quite leave by morning.
Here is what I want you to understand about this period of Elston's life, because it is the period most people in our audience are in right now: he had more time than he probably felt he had. Not a lot. But enough. Forty-five minutes before the day starts. An hour after dinner. A Sunday morning that belongs entirely to you if you decide it does. You do not need to quit to begin. You need to stop waiting for the right-sized block of time and start treating the imperfect ones as sufficient.
Almost every founder we cover in these playbooks built their first version while employed. Not in spite of the job — because of it. Having a job forces a kind of focused efficiency that people who quit first and build second often have to learn the hard way. Elston learned to build fast and ship under pressure. The constraint shaped the product.
In 2026, the tools available to you compress the timeline even further. AI can write your first draft, generate your landing page copy, answer your customer support, and help you research your market in an evening. The work Elston did over months you can test in days. The question is not whether you have time. The question is whether you have decided to use it.
The Idea: A Crowded Market Is Not a Warning. It Is Confirmation.
Elston did not find a niche no one had touched. He walked into web hosting — the same market as GoDaddy, Bluehost, Namecheap. Companies spending more on a single campaign than most indie founders will see in revenue for years. Companies with brand recognition, infrastructure, and legal teams larger than Elston's total user base at the time.
Most people would have stopped there. Wrong space. Too competitive. No budget to compete. That instinct is understandable and it is also wrong, because it misunderstands what a crowded market actually signals.
A crowded market means the demand is proven. People are already paying. The behaviour already exists. You are not evangelising a new category. You are walking into a room full of buyers and asking whether any of them are being underserved. In web hosting, the answer was obvious once you looked at it clearly.
"If you take something that already exists, make it better, make it more legitimate — you've got a winner on your hands."
He did not try to beat the giants. He found the people the giants were ignoring. That is not a clever marketing positioning. That is a fundamental business decision. And it is the decision that made everything else possible.
Before building anything, Elston validated the gap. The method I use — and the one I will cover in full in a later issue — takes an evening. You are not trying to prove the idea is great. You are trying to find one person with the problem. If you can find one, you can find a hundred. If you cannot find one in a targeted search, the problem may not be as widespread as you think. Validate before you build. Always. That is step one.
The Business Model: Find Who Is Being Ignored. Build Their Version.
GoDaddy was not ignoring people. It was just built for a different person than Elston decided to serve. Built for the person comfortable with a control panel. Who knew what FTP meant. Who could navigate three pages of documentation to get a site live.
On the other side of that split were designers, students, restaurant owners, real estate agents, teachers, freelancers — people who needed a website up and had no interest in learning infrastructure to get there. Not because they were not intelligent. Because it was not their problem to solve. Their problem was something else entirely, and they just needed a website to support it.
Tiiny Host did one thing. You drag. You drop. Your site is live. No panels. No jargon. No account verification hoops before you can see what you are building. A working website, visible to the public, in minutes.
Simple? Yes. Easy to build well? No. And this is the distinction that matters. The best ideas are usually the ones that make you ask: why has nobody done this cleanly for this person yet? When you hear that question in your own head about a specific audience, chase it. It usually means someone has built something for that space — just not for who you are thinking about.
Now here is the move in this section that most builders never think about early enough.
He added a free plan. Not because free users pay the bills. Because every website hosted on Tiiny Host carries a quiet line at the bottom: Powered by Tiiny Host. Every site became a small billboard. Every user became, without being asked, part of the distribution. He built a viral loop directly into the product before he ever thought about marketing.
How does your product spread when nobody is watching? Not when you are posting about it. Not when you are running ads. When a user simply uses it. If you cannot answer that question, you will be doing all the marketing yourself, indefinitely. Elston answered it before he launched. The free plan with the footer link was not an afterthought. It was a distribution strategy embedded in the product architecture itself.
The Distribution Machine: The Part Most Builders Skip Until It Is Too Late
Here is the sequence that kills most products. Build. Launch. Wait. Nothing happens. Blame the product. The product was usually fine. The distribution was missing, and it was never planned. It was hoped for. That is not a strategy.
Weinberg and Mares, in their book Traction, make an argument that changed how I think about building: you should spend 50% of your time on product and 50% on traction from day one. Not after launch. From day one. Most builders treat distribution as a problem for after the product is ready. By then they have lost months of compounding.
Elston did not launch with a splash. He started with SEO.
SEO will not show results in 30 days. It will not even look like it is working at 60. But done consistently, over 6 to 12 months, it compounds into something genuinely hard to take from you. It stops being a marketing channel and starts being infrastructure. And in a world where AI tools can help you identify keywords, write optimised content, and analyse competitor gaps in hours rather than weeks, the time investment required to build a real SEO presence has never been lower. The compounding is the same. The ramp to it is shorter.
He targeted low-competition keywords. Not "web hosting" — that was a fight he could not win on budget. Instead: how to share a PDF as a link. How to host a website without coding. Small searches. Real intent. Real people already looking for exactly what he built. Not people who needed to be convinced. People already raising their hand.
Then YouTube. Not produced. Just screen recordings. Short tutorials answering the exact questions his audience was typing into Google. One video on sharing PDFs as links. Thousands of views. Still bringing in users long after it was recorded. Made once. Works on its own.
Then Reddit. He did not spam. He showed up honestly. Told the story of what he was building. Asked for feedback instead of pitching. Gave early users a discount as a thank you for showing up before the product was ready.
Notice that combination: transparency about what you are building, asking for feedback instead of selling, rewarding the people who showed up early. That combination works consistently. Not because it is a tactic. Because it is how most people prefer to be treated, and because it builds the kind of trust that converts strangers into advocates.
Building the product is maybe 20% of the work. What Elston did here — the SEO, the tutorials, the honest community presence — is the other 80%. This is what every issue of The Real How is built to cover. Not just the idea. The full machine.
The First Sale: Proof Matters More Than Margin
He lowered his prices until people started paying. That is the strategy, stated plainly.
Not because you should always discount. Not because cheap is a sustainable position. But because getting that first sale matters more than margin at the start. The first sale is proof — that someone in the world values what you built enough to give you money for it. That proof changes how you think. It changes the questions you ask. It changes the work from a hobby into something real.
He ran a lifetime deal. Made $1,000 in a couple of days. The money was not the point. The proof was.
Once revenue starts coming in, it must never stop. That is not a business goal. It is a mindset change — from builder to operator. You stop asking whether anyone will pay and start asking how to keep them paying. From then on, every decision runs through that lens. Retention. Sustainment. Keeping the machine running. We will cover this in a dedicated issue. For now: get the first sale fast. Not to get rich. To get proof.
For a year the MRR was low. The feedback was good — users praised it consistently — but the numbers were not impressive from the outside. He held on. Kept shipping. Kept showing up in communities. Kept responding to feedback the same week it arrived.
Then the compounding kicked in. SEO started working. Word of mouth picked up. The business found its rhythm.
That year where nothing looks like much from the outside — I think it is the most important part of this story. Not because patience is a virtue. Because that is the period where most people quit. It usually looks like failure from the outside. It usually isn't. The work you put in during the quiet year is the work that becomes a number people screenshot later.
The Traction Framework: How Elston Found His Channel — And How You Find Yours
Gabriel Weinberg and Justin Mares, in Traction, argue that most businesses fail not because of bad products but because of bad distribution. Peter Thiel said it directly: poor distribution, not product, is the number one cause of failure. The book identifies 19 channels through which any business can get traction. Not all of them work for every business. The goal is to find the one that unlocks your next stage of growth — what Weinberg calls the Bullseye.
Here is how Elston ran this framework, whether he knew it or not.
Here is the full list of the 19 traction channels from Weinberg and Mares, mapped against what Elston used and what is most relevant for a solo builder with the tools available today.
Weinberg's rule: most businesses get zero distribution channels to work. If you can get even one to work, you have a real business. If you try several without nailing one, you are spread too thin to go deep enough on any of them. The Bullseye tells you where to focus.
Elston's channel was SEO backed by content marketing and community. The three worked together. But SEO was the engine. He went deep on that one before anything else mattered. That is the lesson. Not the list of nineteen channels. The discipline to run one of them at real depth until it compounds.
What You Can Apply: Four Principles That Do Not Age
Your Move This Week
- Go to G2 or Trustpilot. Pick any software category that interests you, something you use or understand. Read the one-star reviews for 20 minutes. Use an AI tool to find patterns across 50 reviews if you want to move faster. Write down the three most common complaints. That is your product idea. Not polished. Not validated. A direction worth investigating.
- Run the Bullseye on the idea. Take the list of 19 channels above. For each one, write one sentence about how you could use it to reach the specific audience who has the problem you identified. Do not dismiss any channel in this phase. You are brainstorming, not committing. The goal is one sentence per channel, no more.
- Pick the three channels that feel most promising — not most comfortable. There is a difference. The channel you feel most comfortable with is usually the one you have biased toward before the evidence. The most promising one is the one where the audience is clearest and the signal is most specific. Circle those three.
- For each of those three, design the smallest possible real test you can run this week. Not a plan for a test. The actual test. Post in a relevant subreddit. Publish one piece of SEO-targeted content. Record one screen recording tutorial. The test should tell you within seven days whether the channel has real signal for this audience. That is how Elston built $500k ARR. Not with a launch. With seven days of this, repeated for two years.
Elston did not win because he was the best developer in the room. He won because he understood exactly who was being ignored, found the one channel that could reach them at scale, and then showed up in that channel consistently for two years before the compounding became visible.
Simple product. Specific audience. Patient distribution. That is the whole game.
And in 2026, with AI compressing the time it takes to build, write, research, and distribute, the only remaining question is whether you will decide to start.
Next issue: Minecraft. How Markus Persson built the best-selling video game in history on his lunch breaks — and what his distribution model teaches builders in every industry about the power of community-led growth.
- Elston Baretto, IndieHackers — "Tiiny Host hits $500 MRR" (Feb 2021) and "Bootstrapping Tiiny Host to $6k MRR in 33 Months" (Sep 2022)
- Indie Bites Podcast — Episode 21 (Mar 2021) and Episode 80: "From $0 to $10k MRR in 2 years"
- Starter Story — initial interview (2021) and update: "I Quit My Full-Time Job After My SaaS Grew 8X" (2024)
- Philip Baretto (@_baretto) on X — MRR milestone disclosures 2021 through 2025
- Gaps.com — "Web Hosting: 15 Startups with 2025 Revenues" (Mar 2025) — 2,000+ paying customers, $20k+ MRR
- Getlatka.com — Tiiny Labs Ltd. profile: $387k revenue, 8 employees
- Gabriel Weinberg and Justin Mares — Traction: A Startup Guide to Getting Customers (2015). 19 traction channels and the Bullseye Framework.
- All Tiiny Host figures from Elston's own public disclosures. Nothing estimated or extrapolated.
More Playbooks
View AllHe Was Tired of Formatting Other People's Newsletters. So He Built the Tool. Kept the Monkey.
How Ben Chestnut built Mailchimp as a side project to automate his most annoying freelance work, bootstrapped it for 20 years without answering to a single investor, and sold it to Intuit for $12 billion — the largest acquisition of a bootstrapped company in history.