By Roland van den Hout, co-founder of SQSMODS
We never set out to build a plugin store. We were simply trying to solve a problem for a client.
They needed functionality that wasn't available in Squarespace's native toolkit, so we built it.
Within weeks, a handful of other developers reached out to ask if they could use it. Then more followed.
They weren't reaching out because we'd marketed anything. They were reaching out because they'd hit the exact same wall.
That's when we realised something bigger was happening.
Squarespace had real gaps. Not edge cases or nice-to-haves, but genuine friction points that developers and site owners kept running into. Once we started paying attention, plugin ideas came from everywhere. Client requests. Our own observations while building sites. Things we'd see on other platforms and think, "Why doesn't Squarespace have this?"
One plugin became two. Two became five. Five became dozens.
We never wrote a business plan for any of this. We kept building because limitations kept emerging and people kept asking for solutions.
SQSMODS emerged from that momentum. Not from some grand strategy, but from recognising a genuinely underserved market and having the ability to serve it.
Building Solutions, Not Features
That's still how we work today.
Every plugin we build exists because we, or our clients, encountered real friction while building a website. Every feature solves an actual problem, not one we imagined from a spreadsheet.
We don't start by asking what would look good in a marketplace. We start by asking what's slowing people down, what's frustrating users, or what's missing from a project.
If a solution improves the experience for one client, there's a good chance it will help other Squarespace users too.
Over time, that simple approach has shaped everything we've built.
The Story Behind Expand 2.0
One of the best examples of this approach is Expand 2.0.
We had a client with a large number of service offerings. The traditional approach, creating separate pages for every service, meant visitors were constantly jumping between pages to find the information they needed.
We diagnosed the friction and recommended a different structure.
Instead of sending users from page to page, we kept everything on a single page and organised the content into digestible sections that visitors could expand as needed.
The result was a cleaner user experience, better content organisation, and a more engaging way to explore the content.
The client loved it.
When we released it to the SQSMODS community, they loved it too.
What started as a UX observation on a single project became one of our most popular plugins.
That pattern has repeated itself many times over the years. A challenge appears on a client project, we build a solution, and then discover that many other developers have been facing the exact same issue.
Letting Adoption Prove the Idea
That philosophy sits at the heart of SQSMODS.
We don't chase trends or try to predict what developers might want next. We focus on solving real problems, releasing those solutions to the community, and letting adoption tell us whether we got it right.
Every plugin in our store exists because it solved a problem we encountered.
Every update is shaped by feedback from the community.
Every improvement comes from listening to how people actually use our products in the real world.
That's how SQSMODS started, and it's how we'll continue building in the future.
The best ideas rarely come from brainstorming sessions. More often, they come from paying attention to the frustrations people experience every day and taking the time to solve them properly.
For us, that's where every SQSMODS plugin begins.
---
About the Author
Roland van den Hout is the co-founder of SQSMODS, a growing collection of plugins and enhancements built specifically for Squarespace. His work focuses on solving practical challenges faced by Squarespace designers, developers and website owners through thoughtfully designed tools and features.