Founder: Why I Built Deskworks and Lessons I Learned Along the Way

Initially, we–before we were Deskworks–didn’t start with the intention of building software. We started with the intention of solving a problem: the problem of people needing a place to work close to home but not IN their home. We certainly didn’t know the term “coworking” when we began back in 2009. We just knew that people had laptops and cellphones and could work anywhere. Which in many cases meant they were isolated working at home or distracted by the dishes needing washing, or depressed by not talking to anyone all day, or worried about sounding unprofessional on a call with the noise at Starbucks, or struggling with terrible Wi-Fi.

So we started up a company called “The Satellite” and created small coworking spaces in towns and communities. We knew we had to be super-efficient if we were going to make this work. Our workspaces had to be open 24/7,  while staffing only during working hours. We had to offer different types of space on different types of plans. Some people wanted full time, some wanted to just have a “Bucket of Hours.” Some were happy with open space; some only wanted a private enclosed space. We had to offer it all since we had a smaller universe to market to and had to meet the needs of any knowledge worker within a geographical radius if we were going to pay the rent. It was an interesting problem. 

We had to have systems and processes that took care of themselves and were highly automated and totally simple to use because we wanted staff to be engaging with people. (This is before we figured out that “people” were “members.”) Oh, and it had to be fun to use.

So all of these needs inevitably dictated software, since it had to automate processes and track usage without human intervention (or paper) and bill automatically for any kind of plan and severely reduce the possibility of errors or gaming of systems. We knew we were in an infant market that would be growing and changing. We never thought we were developing a product for others. This was to use for ourselves as we created replicable spaces that could be plunked down in the center of any town. 

What I Wish I’d Known When We Started

1. That We Were Creating a Unique Product

What do I wish I’d understood at the time? That we were creating a product from a unique perspective. We were operators with an intimate understanding of what people like us needed.

2. That Flexibility Was Key

Second, that there would be so many different ways to build appropriate spaces for people. Some would want funky, some would want high-end. Some would want 2,500 s.f. places, some would want 50,000 s.f. spaces. Some would want high-touch, some would want unstaffed. Some would be mostly offices and most would eventually be a hybrid mix of offices, desks, open space, meeting rooms, podcast rooms, equipment, therapy studios, recording studios…and even a dog park.

And there was no reason that what was now Deskworks Coworking Management Software couldn’t be designed to be flexible enough to meet any of these needs. The fun was in the logic.

3. That Automation Would Keep Evolving

The other thing I didn’t quite get originally was that the concept of automation would keep growing. People got used to the idea that if they could think it, it could be created. And I love that. It’s an absolute joy to take a statement of “Couldn’t we…” and define a logical rule that works across any requirement and use of the product.

The Continuous Journey of Software Development

There are more learnings, and all of them are important. Software is never completed; there are always new things to incorporate. Some need to be built in; some need to be integrated with other best-in-class products. Ten years ago, software was frequently cumbersome to use—you could break it, and it was sometimes hard to understand. (We worked hard to keep Deskworks out of that category!) Now, it has to be simple, beautiful, intuitive and flexible.

Designing and improving and thinking of the next great feature has only become more fun. I can’t imagine that ever changing. And what will always be there is the need to see software tools from an operator’s perspective, to intimately understand what operators need, and to inherently know how operators will use the software they live with.

The Evolution of Deskworks: A Journey of Innovation and Empowerment

At its core, Deskworks was built out of necessity—a need to solve real-world challenges for coworking space operators and members alike. Over the years, it has evolved into a flexible, intuitive, and ever-improving solution that meets the diverse needs of operators across the globe. What began as a tool to optimize our own spaces has grown into a platform shaped by the experiences, challenges, and ideas of an entire community. As we look ahead, one thing remains clear: the journey of innovation, problem-solving, and connection is far from over. Deskworks will continue to adapt and empower operators to create thriving, inclusive spaces for their communities.