The Founder's Log: A Look Inside Beyondspace Studio
Hi everyone, I'm the founder of Beyondspace Studio and the creator of Squarespace tools like Lightbox Studio, Synced Blocks, and our newest project, Ground Control.
A question I get asked surprisingly often is, "What do you actually do all day?" It's not always glamorous, but it’s a process I love. For anyone curious about the nitty-gritty of building software for the Squarespace community, here’s a typical day for me.
9:30 AM: The Morning Triage & Intelligence Gathering
My day doesn't start with a sprint. It begins with a coffee and a methodical check-in. The first stop is our Boldesk app, where I handle all user support tickets. I categorize them by priority: simple "how-to" questions get answered first, then feature requests, and finally, potential bugs that need investigation.
Next, and this is a crucial habit, I check the logs on our DocsBot. This is my secret weapon. Seeing the questions users ask our documentation bot tells me two things:
Content opportunities: If a question is asked frequently, I know our documentation isn't clear enough. I'll immediately turn that query into a short, public Q&A post. It's great for SEO and helps other users with the same problem.
Product friction: It shows me where users are getting stuck in the real world, highlighting potential issues with our products or documentation that need fixing.
11:00 AM: Proactive Support & Community Pulse
With the inbox clear, I shift to proactive community work. I spend about an hour on the Squarespace Community Forum. I don't just lurk; I actively join discussions. Answering questions and seeing the challenges real users face keeps my work relevant. It’s the best way to understand the "burning questions" that can inspire my next blog post or even a new feature.
This is also when I'll check Trustpilot for new reviews. Good or bad, the feedback is a gift. I make sure to respond to them to show that there’s a real person here who cares.
12:30 PM: Deep Work, Part 1: Bug Squashing & Stability
My rule is simple: bugs get fixed first. Before I write a single line of new code, I address any critical issues that have been reported or that I've identified. I believe a stable, reliable tool is far more valuable than one with a dozen features that are half-baked. A smooth user experience is everything.
2:00 PM: Break & Recharge
This is my non-negotiable break. I step away from the screen completely. I’ll cook a proper meal, maybe go for a short walk. Trying to solve a complex coding problem when you're hungry or burnt out is a waste of time. This break ensures my afternoon is productive.
3:00 PM: Deep Work, Part 2: Building the Future (Ground Control)
This is when I do my most focused work. With bugs out of the way, my entire development focus right now is on Ground Control. This is the "head down, headphones on" part of the day where I'm architecting new features, refactoring code, and chipping away at our product roadmap. It's a slow and steady process of bringing a big idea to life, one line of code at a time.
5:00 PM: Marketing & Content Creation
I switch from a developer mindset to a creator mindset. My marketing is all about education and adding value. Based on the insights I gathered in the morning from Boldesk, DocsBot, and the community forums, I'll start creating content. This usually involves:
Writing a detailed blog post that answers a common user struggle.
Creating short-form video tutorials or GIFs.
Sometimes, I'll do a bit of market research, looking for inspiring websites built on Squarespace to see how top-tier brands use the platform. It's part inspiration, part competitive analysis.
6:30 PM: Winding Down
I do a final check of the support inbox to make sure no urgent issues have come up. After that, I close the laptop. It's important to have a hard stop to prevent burnout. The evening is for personal time—family, exercise, reading, and completely disconnecting from the world of code.
And that’s it. Rinse and repeat. It’s a constant cycle of listening, fixing, building, and sharing. Thank you for being a part of the journey.
What does your typical workday look like? I'd love to hear in the comments below!
