How 50¢-Per-Pool Pricing Grew a SaaS to $1M ARR

Most software aimed at small service businesses makes the same mistake: it charges in a way that feels disconnected from how the owner earns money.

That is part of what made Skimmer’s story notable. Founder Ron Hash built software for pool service companies, priced it at $0.50 per serviced customer with a $29 minimum, and grew it to more than $1 million in annual recurring revenue with roughly 1,500 customers, no ad budget, and a market many founders would have dismissed as too small.

On the surface, this is a SaaS success story in a narrow niche. But for practical operators, the more useful lesson is broader: growth came from aligning the product to the customer’s actual workflow, pricing it in a way that made sense on a job-by-job basis, and reducing friction in onboarding and daily use.

That matters whether you run a venue, a trade business, a one-person operation, or a niche software product. The details change. The pattern does not.

Key Takeaways

• Price against customer value, not your internal convenience. Skimmer avoided per-seat pricing and tied cost to serviced accounts, which made growth feel fairer to customers.
• A painful manual process is often a stronger signal than a "nice-to-have" feature request. Hash moved after hearing that paper-based operations were actively hurting the business.
• Good onboarding can cut churn more effectively than adding more features. Skimmer reportedly reduced churn from about 6% to around 2% by helping users reach value faster.
• Field software lives or dies on speed. Fewer taps, less typing, and offline access were not cosmetic improvements; they were the product.
• One traction channel is enough at first. SEO became the engine. That focus mattered more than trying every growth tactic at once.
• Customer support can be a growth channel. Fast replies and welcome calls turned early users into word-of-mouth advocates.
• Niche markets are often bigger than outsiders think. A "small" industry can still support a meaningful software business if the pain is real and underserved.
• If your customers are still on paper, your real competitor is not another app. It is habit, flexibility, and the comfort of the old workflow.
• Big feature launches bring attention, but small quality-of-life fixes build loyalty.
• You do not need a grand theory to validate an idea. Sometimes one sharp conversation reveals a problem worth solving.

sbb-itb-342b8b2

The Real Opportunity Wasn’t "Pools." It Was Paperwork

The easy version of this story is that Hash found an overlooked vertical and built software for it.

The better version is that he found a workflow bottleneck that software could remove.

He had a friend in pool service who struggled to find decent software. Later, after calling a pool company he found online, he heard a line that clarified the whole opportunity: the manual paperwork side of the business was dragging operators down. That was enough to convince him the problem was not hypothetical.

This is a useful filter for any small operator considering software, AI, or automation:

A market is attractive when all three are true:

1. The work is repeated frequently
2. The admin burden grows with volume
3. The current workaround is manual

In pool service, that meant route management, service records, chemical tracking, and billing. In a restaurant, it might be bookings, staff coordination, guest follow-up, and WiFi-driven list building. For contractors, it could be field notes, job signoff, and syncing paperwork later when service returns.

The niche is less important than the pattern. If a business owner says some version of "this admin work is killing me," that is often a better signal than a polished market research report.

Why the Pricing Worked Better Than Per-Seat Plans

One of the most interesting parts of the story is not the product itself. It is the pricing model.

Instead of charging by seat, Skimmer charged by the number of serviced customers, with a floor of $29 a month. The practical effect was simple:

• A tiny operator could start cheaply
• A growing company paid more only as business expanded
• Owners did not have to debate whether to add another employee to the system

That last point matters more than many founders realize.

Per-seat pricing can quietly create resistance inside small businesses. If every extra technician, manager, or office user increases cost, owners begin rationing access. The software becomes something to limit rather than spread through the operation.

A usage-linked model flips that psychology. Hash described customers being happy when the bill increased because it meant their route count had grown. That is rare. And it is powerful.

Why this matters for small operators

If you buy software, ask one blunt question:

Does the pricing rise when my overhead rises, or when my revenue rises?

Those are not the same thing.

A tool priced close to your revenue engine usually feels easier to justify. A tool priced around headcount, logins, or arbitrary tiers often creates friction long before the monthly charge becomes large.

Why this matters for founders selling to small businesses

If your customer is a practical operator, your pricing should pass the "back of the napkin" test. They should be able to estimate the bill in seconds.

Skimmer’s formula worked partly because it was simple. If a company serviced 150 pools, the monthly price was easy to understand. No calculator gymnastics. No feature maze. No mystery.

For buyers with no time to waste, that clarity is an advantage in itself.

The Product Won Because It Fit the Work

Many founders talk about user experience as if it is decoration. In field-service software, it is often the business model.

Hash’s edge was not only that he made a mobile-friendly product. It was that he focused on the person doing the actual work in the field, not just the office admin or owner.

That distinction matters.

A field tech does not care about elegant dashboard language. They care whether the app slows them down at a gate, in the sun, with wet hands, on a schedule, and maybe with weak cell service.

According to the interview, Skimmer improved traction by solving a few concrete problems well:

1. It reduced input friction

Instead of forcing users through clunky web-style forms, the product was designed to minimize taps and manual typing.

That sounds minor until you multiply it across dozens of stops per day. Saving seconds on each visit is not cosmetic. It changes whether crews tolerate the software.

2. It worked offline

This is a practical feature too many software products treat as optional.

If a crew works in areas with poor signal, "cloud-based" can become another way of saying "unreliable when needed most." Skimmer’s offline functionality meant workers could keep operating normally and sync later.

For trade businesses, mobile crews, event teams, and anyone who works in dead zones, offline capability is not a premium add-on. It is table stakes.

3. It replaced end-of-month paper reconciliation

A strong software product does not merely digitize the old mess. It removes the need for the mess.

In this case, one example was chemical billing. On paper, field records had to be brought back, reviewed manually, and totaled later. Software collapsed that chain. The operational gain was not abstract; it was fewer hours wasted in catch-up admin.

That is a useful benchmark for evaluating any tool:

Does it just store the same information digitally, or does it eliminate a whole step of work?

Only the second one tends to become indispensable.

Why Onboarding Mattered More Than More Features

One of the sharper lessons in the interview is that churn did not fall simply because the product improved over time. It fell because onboarding improved.

Hash said churn was around 6% in earlier days and later came down to about 2%. He credits several factors, but one idea stands out: the company treated churn as an onboarding problem, not just a product problem.

That is a lesson many software teams still miss.

If a customer never reaches the "this is useful" moment quickly, they do not stay long enough to appreciate your roadmap.

What Skimmer did right

The onboarding flow was reportedly kept simple and goal-oriented. Instead of exposing users to everything, it guided them toward the immediate outcome that mattered most:

• add the customers they needed next
• build the route for the next day
• use it in the field
• experience the core value firsthand

That sequence is smart because it compresses time-to-value.

Too much onboarding tries to educate. Good onboarding gets the user to a result.

What small operators can learn from this

If you are implementing new software in your own business, do not ask staff to "learn the system."

Ask them to complete one real-world outcome with it this week.

Examples:

• send tonight’s event customer follow-up
• close one job from the field without paper
• launch one pre-order item without holding stock
• collect one guest contact list from WiFi logins
• invoice one repeat service cycle end to end

That is how adoption sticks. Not through training decks. Through immediate usefulness.

SEO Beat Ads Because the Search Intent Was Already There

Another practical detail: Skimmer grew without paid ads, and SEO became the main acquisition channel.

This is not a romantic story about "content marketing." It is a reminder that some markets are highly efficient if buyers already know the problem and actively search for solutions.

Someone searching for phrases like pool service software is not casually browsing. They are likely in-market.

That makes SEO especially attractive in narrow B2B categories where:

• the search volume is modest
• the intent is strong
• the competition is weaker than in mainstream SaaS

For small operators and solo founders, this is the part worth underlining:

You do not need every growth channel. You need one channel that matches buyer behavior.

Hash cited a lesson from the book Traction: focus on one channel until it stops moving the needle. That is still solid advice.

What this means in practice

If you sell to practical U.S. operators:

• Search can beat social if the problem is urgent and specific
• A clear category phrase often outperforms clever branding
• Fast support and good product experience can amplify search via referrals

Skimmer also benefited from customers recommending it in Facebook groups, even without the company actively pushing social media. That happened because the product and support created stories people wanted to repeat.

Word of mouth is usually described as magic. In reality, it is often the result of reliability plus relief.

People recommend tools that save them from annoying work.

The Hidden Advantage: Customer Support as Product Strategy

One of the least flashy but most defensible parts of the company’s growth was support.

Hash put a phone number prominently on the site. If people called, he answered. Emails got fast replies. He also made welcome calls and used a simple dashboard to see what new users had or had not done in the app before speaking with them.

That is a disciplined move, not just a friendly one.

Good support in early-stage software does at least four jobs at once:

1. Rescues stuck users before they churn
2. Reveals onboarding friction
3. Shows which features are actually being used
4. Creates stories customers retell to peers

Small business buyers notice responsiveness because they usually get the opposite from software vendors.

For the audience WEIRDTOO serves, this is highly relevant. Small operators are not looking for "customer success journeys." They want to know whether someone will help when the tool interrupts real work.

That means support is not overhead. It is part of the offer.

What Most Founders Would Miss in This Story

It is tempting to summarize the case as "find a niche and price creatively." But that misses the more durable lessons.

Lesson 1: Narrow markets are often operationally dense

Pool service sounds narrow. But it has recurring work, route logic, field teams, recurring billing, consumables, and customer communication. In software terms, that is a rich environment.

A niche does not need to be glamorous. It needs enough operational repetition to benefit from systems.

Lesson 2: The first version can be wrong if the learning loop is right

The early product focused on iPad, but customers wanted phones. That could have killed adoption if the founder had stayed stubborn. Instead, feedback corrected the path.

Plenty of founders overprotect their original concept. Hash treated early product choices as movable.

Lesson 3: Annual timing matters in real businesses

One tactical point from the interview deserves more attention: releasing a major feature at the start of the calendar year helped because business owners were already rethinking operations then.

This is a useful reminder that small business buying patterns are seasonal and behavioral. Not every month is equal. A tool can feel more valuable when it appears exactly as owners are making "this year we’re fixing this" decisions.

A Practical Framework You Can Borrow

If you are a founder, operator, or one-person software builder, here is the most useful way to translate the Skimmer story into action.

Step 1: Find a workflow people still patch with paper, texts, or spreadsheets

You are looking for repetitive admin around real revenue, not vague inconvenience.

Step 2: Validate with direct conversation

You do not need a giant survey. You need to hear how the work is actually done and where it breaks.

Step 3: Build for the moment of use, not the management view

If the work happens on a phone, in a vehicle, on-site, or without signal, design from there.

Step 4: Price close to the customer’s growth

If they make more money, your bill can rise. If they merely add complexity or staff, think twice before charging more.

Step 5: Get users to one real result fast

Onboarding should aim for one outcome, not a complete education.

Step 6: Pick one acquisition channel and work it hard

Search, referrals, direct outreach, partnerships - any can work. Most fail because founders split effort too early.

Step 7: Use support to find the real product roadmap

The most useful feature requests often arrive disguised as confusion, hesitation, or support tickets.

The Exit Lesson Is Different Than the Growth Lesson

The story ends with acquisition interest arriving once the business reached meaningful scale. Hash sold, stayed briefly for transition, and later fully exited. He also said he does not regret the decision.

That part matters because there is a common myth in founder culture that if a business later becomes much larger, the original founder must have sold too early.

Not necessarily.

His framing is realistic: he built a business, and the next team built a larger company. Those are different jobs. Many operators will recognize the same truth in their own world. Running a solid, profitable operation is one skill. Building layered management, systems, HR, and organizational complexity is another.

For small operators, the useful takeaway is not about selling. It is about knowing what kind of business you actually want to run.

Growth is not free. Bigger often means more structure, more people management, and less direct control over the work itself. That can be worth it. But it is not automatically better.

Why This Story Still Matters in an AI-Everything Market

One line near the end of the conversation is especially relevant now: with modern AI tools, more people can build software than before.

True. But that does not make distribution, workflow fit, or pricing irrelevant. It makes them more important.

AI lowers the cost of building. It does not lower the cost of misunderstanding the customer.

If anything, the rise of cheap software creation means more mediocre tools will flood small-business markets. The winners will still be the ones that:

• solve a costly, obvious pain
• fit the real working conditions
• charge in a way that feels fair
• help users get value quickly
• support them when things go wrong

That is why this is more than a story about pool software. It is a case study in practical alignment.

Final Thought

The most valuable idea in this interview is not the pricing formula by itself. It is the discipline behind it.

Hash did not win by inventing a category. He won by noticing where small operators were losing time, then building around the way they actually worked rather than how software companies prefer to sell.

That distinction is worth remembering.

For practical businesses, the best tool is rarely the one with the biggest claims. It is the one that removes friction from a job that already has to get done tomorrow morning.

Source: "He charged 50 cents a pool and grew his SaaS to $1M ARR, then sold it" - SaaS Club, YouTube, Jul 16, 2026 - https://www.youtube.com/watch?v=c4N-nWFlPB4