SQSPThemes Case Study
How a $500 Squarespace Project Became a Million-Dollar Plugin Business
A real story about client work, hidden assets, market proximity, and the leverage that appeared when one small request revealed a much bigger pattern.
In 2017, I took on a Squarespace project for $500.
That wasn’t the original number. The client negotiated. They only had $500, and at that point in my freelance life, I was still close enough to the edge where a $500 “yes” mattered.
So I took the project.
That detail matters because the story did not begin with a grand strategy. It did not begin with a product roadmap, a launch plan, or a clear vision for a plugin business.
It began with a client who had a limited budget, a site that needed work, and me trying to make the project make sense.
I was freelancing at the time, doing a little bit of everything: design, development, marketing, strategy, whatever the work required. I had skills, but I did not have leverage.
Every month still felt like starting over. A client says yes, and you can breathe. A client says no, and the whole month gets tighter.
That was the part I wanted out of.
The work itself was not the problem. I liked solving problems and figuring things out. The model was the problem. Custom work can pay you, but it can also keep resetting the game.
I didn’t want to keep selling my hours forever. I didn’t want to grow an agency just to manage more people, more deadlines, and more moving parts.
I wanted to build something once and let it keep working.
At the time, my private goal was simple: $10,000 a month from digital products. No clients. No chasing. No 60-hour weeks.
I didn’t know how I would get there.
Then this $500 project opened a door I didn’t even know I was standing in front of.
June 26, 2017: a normal project with a hard ceiling
The project started as a Squarespace ecommerce request with a short list of tweaks and a $500 budget. Nothing about it looked like the beginning of a million-dollar plugin business.
A short list of Squarespace tweaks. A $500 budget. A normal client project.
The request that changed everything
The work was already done. Then the real signal showed up.
The project itself was ordinary. A Squarespace site. A client request. A limited budget. A few things to figure out.
Then, after the fact, the client asked for something extra.
They wanted the product images to change when someone selected different product options.
Simple request on the surface.
If you’ve built enough client sites, you know what lives inside a request like that. The client sees the outcome, the platform has its limits, and you stand in the middle, trying to translate what should happen into something that actually works.
I had seen versions of this before. A client wants Squarespace to do something it does not quite do out of the box. A site needs to feel more custom than the template allowed. A small feature opens up a larger problem.
Most of the time, that kind of work disappears back into the project. You solve it, the site launches, the client is happy, and everyone moves on.
This time, something about the problem stayed with me.
It wasn’t just that the client needed it. It was that I knew other people would need it too.
I didn’t have all the right business language for that yet.
I just knew I wanted to use the solution again.
June 29, 2017: the small question that changed the shape of the business
After the first work was sent over, the client asked if the product image could change according to the selected color. That extra request became the signal.
The request looked small. The pattern behind it was much bigger.
The leverage moment
I could see the market. He could make the code work.
So I messaged a developer I had been working with.
The developer could make the code work. That mattered because I had spent years trying to do too much myself.
I could see the client problem, the market, and how people searched, compared, asked around, and tried to solve things. But I was not the best person to build the technical solution.
That used to feel like a limitation.
In this case, it became the opening.
I asked him how I could license the code from him so I could use it on future projects.
“Do you mean like a plugin?”
I said:
“Yeah. Plugins.”
Then he asked the question that changed everything:
“Do you think selling this kind of plugin would be profitable?”
I didn’t hesitate.
I had a group of almost 1,000 Squarespace users, and I knew designers were running into these exact problems.
The market was not imaginary. It was already talking every day through client requests, Facebook group posts, support questions, search terms, and small moments of frustration.
A week later, we launched our first plugin.
That is the part of the story I keep coming back to.
He did not have to become a marketer. He did not have to build an audience from scratch. He did not have to spend years inside the Squarespace ecosystem, watching the same questions appear in client projects, communities, and search results.
He had a skill that could become much more valuable when paired with the right market path.
And I had been standing close enough to the market to see where that skill could go.
The asset was not only the code
The business appeared when the solution met a path to demand.
The code mattered, and it solved the problem.
But the business did not appear simply because code existed.
The business appeared because a useful solution met a recurring problem, a reachable market, and a clear path to purchase.
That was the unlock.
Before that moment, I had been treating client work like a loop. A client asks, I solve it, the project ends, and then I start over.
That model can pay you, but it does not always preserve the value you create.
The $500 project forced me to look again.
Maybe the value was not only in doing the work.
Maybe the value was in recognizing the repeatable pattern inside the work.
The fix worked inside the client project first
Before there was a plugin business, there was a working solution inside one client site. That is usually how an asset begins: as a practical fix for a real person.
The solution worked first as a client fix. Then it became something that could be packaged.
The first three months
One plugin gave me a product. The first three months gave me a process.
I had to figure out how to move from a client problem to a product path.
The work started with a better set of questions. What problem are we solving, and what should we call it? Who already wants this, and what language are they using when they search for it? What page needs to exist, and what would make the result obvious? What does someone need to believe before buying? What happens after purchase so the customer gets relief?
Those questions became the work.
A plugin needed more than a download button. It needed a name people could understand, a page that made the value clear, a short demo, documentation, support, and content that met people at the exact moment they were already searching.
Then, their next question taught us what needed to become clearer.
That became the loop: capture the recurring problem, develop the solution, expose it to the people already trying to solve it, and listen to what happens next.
The process was not clean at first. I was figuring it out while the business was moving.
But once the pattern started to show itself, I could feel that this was different from freelancing.
A client project ends. A product path compounds.
July 13, 2017: the first public market test
Less than two weeks later, I sent a simple email announcing the new plugins. No giant campaign. No elaborate funnel. Just a direct note to people already close to the problem.
The first market test was simple: here’s what I made, here’s what it does, here’s how to try it.
The first six months
The first proof was small, but it was real.
By the end of 2017, the early plugin experiment had started to move.
The numbers were not huge yet, but they mattered because they came from a system that did not require a sales call, proposal, or custom project every time.
That changed how I looked at the work. A small product sale was more than a transaction. It was proof that someone else had the same problem, trusted the path around the solution, and was willing to pay for the outcome.
July–December 2017: the first curve
The first stretch of sales showed that the idea had legs. It was still early, but the pattern was no longer theoretical.
The early plugin sales proved that the client fix could become a product path.
The next 24 months
The work became less about ideas and more about staying close enough to hear the market.
For the next 24 months, I kept applying that process.
Every plugin gave me another walk through the same business pattern.
I watched what people were asking for, paid attention to where Squarespace created friction, and noticed which searches had weak answers. I looked for problems that were simple enough to solve and common enough to matter.
Some ideas looked interesting but did not repeat enough. Some were too complicated to explain cleanly, and some were useful but not urgent.
Others kept showing up.
Those were the ones I learned to respect.
The work became less about having brilliant ideas and more about staying close enough to the market to hear what it was already saying.
A customer question might show me where the product page was unclear. A support issue might reveal where the documentation needed to be stronger. A search term might give me the exact language people were already using. A buyer’s next problem might point toward the next plugin.
That rhythm built the business.
Over time, the plugin business crossed more than $1 million in sales and supported more than 20,000 freelancers and business owners.
The numbers matter, but the deeper shift mattered more.
Client work stopped looking like one-off delivery. It started looking like a field full of signals.
The experiment became a six-figure income stream
The process worked beyond one plugin or one lucky launch. The repeated rhythm became a real business system.
The early system became repeatable enough to produce real revenue over time.
The business began working without me at the center
A good asset carries your value into the moment someone needs it.
There is one scene that still explains the business better than any chart.
Somewhere, a Squarespace customer asks their designer: “Can we add this to the site?”
You can feel the designer pause. Maybe it needs custom code. Maybe it needs research. Maybe it needs a workaround. Maybe it becomes an awkward explanation about why a simple request is not actually simple.
Then the designer searches Google.
While they are searching, I might be on the couch reading to my kids.
They find SQSPThemes: a tutorial, a product page, and a plugin that solves the exact problem.
A few minutes later, a sale comes through.
That is the kind of marketing I trust most. The solution meets the person already looking for it, the page does the explaining, the demo shows the result, the product delivers, and the system keeps working.
That was the dream I had been trying to reach.
Not passive income in the lazy sense.
Leverage: useful work that could keep helping people long after the original effort was done.
Then I used the leverage
The business gave me room. Distance taught me what proximity was worth.
After that, my relationship with work changed.
I had spent years trying to escape the feeling of starting over every month. Now the business had parts that kept working without me standing in the center.
That gave me room. I homeschooled my kids, wrote, made music, played with ideas, and experimented with AI. I kept asking how little I could work while still letting the business serve people well.
That season taught me something I could not have learned while I was still chasing every client project: leverage is real, but distance has a cost.
The further I got from the daily problems of the market, the harder it became to see the next best product idea clearly.
The business, the systems, and the assets still worked. But the best ideas had always come from close contact: client work, support questions, sales conversations, community posts, and search behavior.
It comes from the small moments where someone says, “Can this do that?” or “I wish there was an easier way.”
That is where the signal lives.
Eventually, I came back around to coaching and advisory because I realized the same thing from a different angle.
The closer you are to real problems, the easier it is to see what wants to become an asset.
Your version will have its own shape
The lesson is not that every Squarespace designer should build plugins.
Your version may look entirely different.
Maybe you already have a product. Maybe it has sold a little, but not enough to become real leverage yet.
In that case, the question may not be “what should I build?”
The question may be: what path does this product need around it?
The form depends on the business, but the place to look is usually familiar: the client questions you keep answering, the fixes you keep repeating, the conversations you keep having, and the proof you have not fully used.
A lot of value hides in work that has become obvious to you. That is why it can be hard to see from the inside.
How I tour a business
I walk it twice: first as a customer, then as the owner.
When I look at a Squarespace business, I am not only looking at the website.
I am walking the business.
As a customer
I’m looking for the path. I want to know what you do without having to piece it together. I want to understand who it is for, why it matters, and what kind of result I can expect.
I’m looking for proof that helps me trust the work before I ever get on a call. If the site makes me work too hard to understand the value, there is usually a leak somewhere.
As the owner
I’m looking for the openings. I want to see where the best clients are already coming from, which projects created the most trust, and which explanations you keep giving on calls.
I’m paying attention to the proof that should be doing more work, the follow-up that still depends on memory, and the places where the offer may be smaller than the value it creates.
Then I’m looking for the leverage moment: the place where a skill, a piece of proof, a process, or raw material could become much more valuable if it were paired with the right market path.
That is the opportunity I am looking for: a hidden asset, a leak in trust, an unclear path, or a piece of proof that should be working harder to help the right person understand, trust, and buy.
Let’s tour your business
The audit is where I look for the signal inside your work.
The Squarespace Business Due Diligence Audit is a private diagnostic for designers and agency owners who suspect there is more value inside their business than the current structure is capturing.
I walk through your business as both customer and owner. I look for hidden assets, trust leaks, unclear offers, underused proof, weak paths to purchase, missed follow-up, and revenue opportunities you may be too close to see.
You’ll leave with a written map of the highest-leverage leaks, assets, and opportunities I see inside your business.
The goal is a clearer read on where value is already moving, where it is leaking, and which asset, offer, page, product, or system could help the business carry more of its own weight.
Private Audit: $2,500
The audit comes first because before anything gets built, we need to walk the business and see what is already there.
The invitation
Your next revenue opportunity may already live inside the work you have completed.
A $500 client project became a clue. The clue became a plugin. The plugin became a process. The process became a business.
Your version may be a repeated client problem, a buried workflow, a service that wants a stronger container, a past project that should become clear proof, a piece of unique expertise that needs language, a partnership opportunity, or a productized idea.
If you want me to walk through your Squarespace business and look for the leaks, hidden assets, and opportunities you may be too close to see, let’s begin.
Squarespace Business Due Diligence Audit
I’ll walk through your Squarespace business as both customer and owner, looking for hidden assets, trust leaks, unclear offers, underused proof, and the revenue opportunities you may be too close to see.
```