Pallyy: A Former Locksmith Taught Himself to Code and Hit $74K MRR Solo — the “Agency-Focused, Lowest Price” One-Person SaaS

(Yen conversions in this article use an approximate rate of ¥150/$1.)

Why this case is worth reading

Social media management tools are one of the most competitive markets in all of SaaS. Buffer, Hootsuite, Later — well-funded giants piling on features across every angle, blocking the entrance with free plans. Into that market stepped Tim Bennetto: no degree, no coding experience, a decade working as a locksmith. Alone, he built up to $74K MRR (about ¥11.1M/month). The growth record he wrote up on Indie Hackers reads less like a triumphant success story and more like an inventory of failures and stalls. That’s exactly what makes it useful material for tracing, in numbers, a path for a solo founder to survive in a red ocean.

The published numbers

A timeline that includes the stalls

What he was actually doing

Pallyy is a scheduling, analytics, and comment-management tool for social media. The playbook boils down to three things: (1) specializing in social media agencies as the customer segment, (2) pricing near the market’s floor, and (3) the kind of rapid, solo-only development speed that comes from responding instantly to user requests. Rather than competing head-on with giants on feature breadth, it’s designed to win on specific variables for a specific customer segment.

An inventory of what didn’t work

What’s most informative in his own account is actually the failure side. The “share your analytics data” feature that was supposed to be the flagship turned out that nobody wanted it, so he deleted it. The Product Hunt launch, attempted without an audience, fizzled. And the longest stretch was roughly two years of stagnation caused by Instagram’s API restrictions, an external wall, entirely outside his control, blocking the thing users actually wanted (scheduled posting). On marketing, he himself admits it’s “always been my weak point, and I’m only just starting to figure it out.”

What stands out is that he got through those two stalled years not by “retreating” but by “waiting.” A structure with zero outside funding and just one person is at a disadvantage for growth speed, but with no burning fixed costs, he could afford to wait for the market or the rules to change. When the external event, the API opening up, finally arrived, the fact that he was still standing there, product and existing customers in hand, was itself the precondition for the pivot to happen at all.

The basis for the pivot decision: “which feature is actually used”

Following the actual usage pattern, scheduled posting was being used more than analytics, he swapped the product’s core focus, and MRR doubled around the $2.5K mark. Steering the product toward what the data points to, rather than toward attachment to the original vision, is the same pattern seen in MENTA’s specialization and Bannerbear’s positioning shift. Including the removal of the sharing feature, Pallyy’s product history is less a story of “adding things” and more a continuous process of “cutting what isn’t used.”

The mechanism behind “agency focus × lowest price”

What makes the social media agency customer segment special is that a single agency signs up in bulk for accounts covering 5 to 20 clients at once. Revenue per acquisition ends up many times higher than for an individual user, and an agency using the tool for its daily operations is much harder to churn. While Buffer and Hootsuite piled on features to cover everyone from individuals to enterprises, Pallyy sharpened only what matters for an agency’s daily workflow, managing clients separately, approval flows.

Pricing works on the same structure. Because the lowest-in-market price point gets multiplied by “number of clients × number of seats” for an agency, a $3 difference becomes a difference of hundreds of dollars a month. In fact, that modest $3 increase from $15 to $18 added over $10K in revenue, because he controlled a variable that gets multiplied, even a small price change swings hard. Find the “variable that gets multiplied” for your specialized customer segment, and win there. That’s why a one-person SaaS, which can’t win on total feature count against giants, was able to work.

The reality of acquisition: from borrowed traffic to an SEO asset

The first roughly 100 customers came via traffic from a friend’s free Instagram analytics tool, not acquisition from zero, but a funnel from a place that already had traffic, and that’s what carried the early days. What drove growth after that was investment in content and SEO: he hired a writer and built out a blog, feature-specific pages, competitor-comparison landing pages, and an affiliate program, and only after that did the roughly 10x annual growth kick in. The “if you build it, they will come” stage plateaued at around 100 people, and beyond that he had to separately construct an acquisition engine, a two-stage progression that’s suggestive, given it was followed by someone with no developer background who says marketing is his weak point.

The design for running $74K solo — and its end

Bennetto’s development style is “listen to a user request, implement it in a few days, and ship it back.” A cycle that would take large companies months of internal approval, he ran daily, using being solo as a weapon. Being the whole of support, development, and marketing himself created a tight loop of request → implementation → gratitude → word of mouth, which became a competitive edge.

But there’s a sequel to this record. In October 2023, the same month he reported hitting $74K MRR, he wrote that he’d hired his first employee, a senior developer, and was also planning to hire for support and marketing. “Solo at $74K” was both an achievement and, at the same time, the limit of the solo structure itself. Rather than resolving the weakness of being a single point of dependency through a sale, he chose to resolve it through hiring, a different way of extending the exit than ScrapingBee’s “a state where you don’t have to sell”.

Conditions and limits for replication

What generalizes: the entry path from zero experience (six months of free materials → an MVP in 30 days), the method of pulling early customers from a place that already has traffic, and the design of targeting the “variable that gets multiplied” for a specialized customer segment. That understanding and persistence in a customer’s workflow beats raw coding skill overlaps with a former teacher who built an education app.

On the other hand, there are clear conditions that don’t replicate. The initial traffic source, a friend’s free tool, was a unique stroke of luck, and the timing of Instagram’s API opening up, the turning point, was outside his control. Enduring roughly two years of stagnation required both a light fixed-cost structure and his personal life circumstances. Also, since the depth of the custom of outsourcing social media management to external agencies differs between Japan and English-speaking markets, whether the “agency specialization” approach to choosing a customer segment can be carried over as-is to Japan needs verification.

Related cases

• Carrd — the same “cut to win in a giants’ market” pattern
• An education app — a domestic version built by a non-engineer