Open Channels FM
Open Channels FM
One Person, One Plugin, and a Business That Works
Loading
/

In today’s episode Marcus and Katie chat with Mark Westguard from WS Form. Mark returns to our podcast but this time he dives into his life as a solopreneur building a plugin business.

He shares his journey, how he manages customer support while staying profitable. Someday there may be team growth, but for now he loves running his business himself. So let’s tune in.

Our sponsors keeps our network independent and actively publishing.

Since 2005, Automattic has built tools for the open web including WordPress.com, WooCommerce, and Jetpack that are used by millions of people to create, sell, and publish online. They believe in ownership, flexibility, and open source and we’re grateful for their support. Learn more at automattic.com.


Logo of Omnisend featuring a stylized 'i' icon and the brand name in lowercase letters.

In five days, Omnisend moves every flow, list, and template off your current platform, and you could be paying up to 35% less without lifting a finger. You just show up when it’s done. We’re glad to have them supporting the show and the community we’re building around it. Use the code OpenChannels and get 30% off your first 3 months of any paid plan.

Highlights

The Journey of WS Form: Mark Westguard shared the origin story of WS Form, a WordPress form plugin. He described his transition from an agency background to creating a product that has been continually developed over six years. Mark emphasized the importance of community involvement and listening to customer feedback in driving the product’s evolution.

Balancing Work and Family: Both Mark and Katie discussed the challenges of balancing work with family life, especially when working from home. Mark mentioned the seasonal changes in his schedule with his kids out of school, and how he manages to maintain a balance despite a demanding work schedule.

Importance of Documentation and Support: Mark highlighted the critical role of documentation and customer support in running a successful plugin business. He has built an extensive knowledge base to streamline support and reduce the need for direct assistance, allowing users to find answers quickly.

Customer-Driven Development: Mark talked about how WS Form’s development is heavily influenced by customer feedback. The plugin’s features are often built in response to direct customer requests, making it highly adaptable and relevant to user needs.

Strategic Feature Additions: An interesting discussion revolved around the decision-making process for adding new features. Mark shared examples of being reactive to customer needs, such as developing a Google Sheets integration based on user requests, and how these additions also serve as marketing opportunities.

Solopreneur Efficiency: Katie and Mark exchanged tips on how to achieve more as a solopreneur. Mark shared his strategies for automating tasks, using macros in support responses, and efficiently managing multiple roles within the business to maintain high productivity without sacrificing profitability.

Growth and Expansion Decisions: The conversation explored the dilemmas faced when considering expanding the team. Mark is cautious about impacting profitability but recognizes the eventual need for additional support staff. Katie shared her experiences of team expansion and its effects on profitability, providing valuable insights into the trade-offs involved.

Diversifying Product Portfolio: Both Katie and Mark discussed the benefits and challenges of diversifying product offerings. Katie emphasized the reduced risk and increased security of having multiple products, while Mark expressed his interest in developing complementary products to WS Form in the future.

Learning from the Community: Mark expressed his appreciation for the WordPress community and the valuable feedback he receives from users. He acknowledged how community involvement has been crucial to the success of WS Form and how he aims to give back by sponsoring WordCamps and supporting key industry names.

Advice for Aspiring Plugin Developers: The episode concluded with advice for aspiring plugin developers. Mark stressed the importance of listening to customers, staying present in the community, and being prepared for the extensive work involved in documentation and support. Katie added the value of focusing on complementary products to leverage existing customer bases and enhance market stability.

Episode Transcript

Marcus:
Hey everyone. Welcome to another Woo BizChat here on Do the Woo. My name is Marcus Burnett, and I’m a community marketer with GoDaddy. I am joined as always by my wonderful co-host from Barn2 Plugins, Katie Keith. How are you doing today, Katie?

Katie:
Great, thanks. How are you, Marcus?

Marcus:
Pretty good. We’re recording on a Friday this time and I am ready for the weekend. My children are out of school. The summertime is starting. Our extracurriculars come to a minimum, so kind of just coasting now. Get to relax a little bit.

Katie:
That seems early. I didn’t know summer started in May in the US for school.

Marcus:
Yeah, their last day was yesterday. Our lives are so much simpler in the summertime. We’ll have some things going on, but without last-minute homework due and all of that stuff, it’s just nice to be able to relax a little bit.

Katie:
Wow. Three months is a lot of time off. I remember getting five or six weeks off in the UK when I was at school, if we were lucky. It is a very long time, but it’s good to have them home and have some fun for the summer. Looking forward to it.

Marcus:
Yeah, I was saying that it’s easier on our schedule, but I’m curious for you, is it easy, we all work from home. Is it easier for you having them home or having them out of the home?

Mark:
I think it’s easier for my wife. She does a lot of the school runs and the extracurriculars because I’m working. For me, I work from home, so it can be a little bit difficult with the kids screaming around everywhere. I’m kind of used to it now, so it’s nice to have them home. When they go to school, you miss them, that’s for sure.

Marcus:
Yeah, my schedule is definitely different in the summertime, but some things are easier, some things a little harder. Well, for folks that may not know who you are, why don’t you catch them up? What is WS Form and how did WS Form come to be?

Mark:
WS Form is a WordPress Form plugin. We’ve been around now for, I want to say six years. Time flies, right? You forget how long you’ve been running your business for. I traditionally come from an agency background. I started my first agency when I was 19 years old, back in, I want to say 96. We used to run the UK’s second fastest growing agency back in the day. I went through the whole dot-com boom and bust and have stayed in the agency game for quite a while.

About ten years ago, my staff introduced me to WordPress. They were going to WordCamps and being part of the community, I was kind of sat in the office, oblivious to it all initially, and then became more and more involved. We decided we wanted to build a plugin of sorts. We decided, I don’t know whether it was wise or not, to build a form plugin. We thought it would take a few months to build, and here we are still building it to this day. It’s continually developing, as I’m sure Katie can attest to. You’re always adding features and improving your product and keeping it up to date. That’s what I do. I build the plugin, manage pretty much everything around it, and I love it. It’s probably the most rewarding and fun part of my career to date.

Katie:
Our topic for today is how you manage to do so much as a solopreneur and talk more widely about at what point people might want to start getting help and move beyond that. What is the limit? WS Form is very well known now and is not thought to be a tiny plugin. You have a respectable place in all the pie charts of the market share of the form plugins. You must be very, very busy. Do you know how many hours you work a week?

Mark:
A lot. It’s like having two jobs. I’m a workaholic by heart. I’ve always run my own business, so I’m familiar with having to run a lot of different parts of it. Although I’m an indie developer, you’re kind of a one-man band building a WordPress plugin, there are a lot of plugins out there, quite significant plugins that are one-man band companies. I wouldn’t be able to do it without the network of people I work with. Although I do the development and support and stuff like that, there are a lot of third-party companies I rely on. There are a lot of people in the community that have helped me get to where I am. I absolutely wouldn’t have been able to do this on my own had I not gotten involved in the WordPress community.

I try to give back as much as I can. I try to sponsor all the flagship WordCamps events. I like to sponsor people to come to WordCamps as much as I can and try to sponsor key names within the industry as much as possible. Being part of that community is what has enabled me to get where I am. Had I not done that, I would’ve just been a storefront with the shutters closed down. I wouldn’t have been as successful as I have been with WS Form. I’m very fortunate and thankful for everyone that’s helped me out, including my wife. She’s part of the team. Without her, I wouldn’t be writing people’s names down at WordCamps properly. When she can come, she’s a great help. It is a lot of work. I probably work sometimes 16 hours a day. You wake up in the morning, start working, spend some time with the family, and then I’m back on the computer developing the next big thing for WS Form. I’m very lucky that I have a job I enjoy. It’s almost like a hobby to me.

Katie:
At what point do you think that would become too much? You are a family man, you’ve got a wife, kids, presumably you have some kind of life outside of that. At what point do you think it’s too much and what would make you consider hiring people for different tasks?

Mark:
I have worked very hard on making the business as profitable and as automated as possible. When somebody sends me a support ticket, I give that my full attention, but I have built quite an extensive knowledge base that helps people with most questions they have. If I get asked a question more than once, I’ll write an article about it so people can refer to that. A lot of my support is really, at this stage, when you’ve got those plugins built, you’re really a support business. You are supporting people most of the time and you are doing product development, but most of the time it’s really support. You become a support business. I have focused on streamlining and making that part of the business efficient.

When somebody fills out our support form, it’s analyzing what they type in and we recommend knowledge base articles back to them to try and prevent that support ticket from even having to come through to us. That gives the user the information they need much quicker. At the moment, my support level is very much within the bounds of me being able to handle it. If I were to hire somebody, it would be someone in support to handle a lot of those tickets. Most of the tickets are “how do I do this?” and then me responding with, “here’s a knowledge base article that you need to be able to do that.” A lot of the time, it’s pointing people in the right direction. Part of my job is to try and point people in the right direction without them needing to ask me for that in the first place.

Katie:
I think that’s an excellent point about reducing the need for support by allowing customers to help themselves. That gives them an instant answer, so it benefits the customer while benefiting you as well. I think that’s a really good thing for people to do from the outset. When you are smaller, you can actually spend time analyzing every ticket and think how could I have stopped this ticket from coming? Whereas when you’ve got hundreds of tickets a day as we do now, we can’t do that. I feel really sad that we can’t put that level of analysis in and it’s still needed because we release new products periodically. For those, we could be analyzing the documentation and we do that a bit, but you cannot do that at such a volume. I think that’s really important and it does allow you to delay hiring a support person for as long as possible. Although there does come a point where that will probably be your first hire because you can’t control the volume beyond that preventative stuff.

Mark:
Anybody thinking about developing a plugin underestimates the amount of documentation and support time involved, depending on what type of plugin you’re building. WS Form is quite a complex product. It has to be able to be applied to so many different use cases. We get asked in support tickets, can it do this? Sometimes if I get that support ticket and I say no, it makes me want to build that and make it do that. That in itself becomes a nice little marketable piece. I spoke to somebody early in the days of building WS Form and their focus was around talking about the benefits of WS Form and not so much the functionality. What I’ve found is that talking about the functionality is what people want with WS Form. They want to know what it can do. They want to know it can do more than other form plugins. They want that one-stop shop for a form plugin.

WS Form is not one plugin. We actually have 46 plugins now as part of the actual that we manage because there’s the core plugin and all the add-ons. Each of those add-ons is a plugin unto itself and those have to be managed and updated. It’s quite a job keeping everything up to date,

especially when a third party suddenly comes out with version three of an API and you’ve got to rewrite everything to make it work with that. The support aspect is definitely the biggest part of running the plugin for us. It’s a lot of work.

Katie:
I love what you said about benefits rather than features. Everybody always says you talk about benefits and not features, but that doesn’t work for me either. Our plugins do very specific things and people need to know that that’s what they’re going to achieve. Marketing philosophy would say you need to focus on the feelings that using the plugin will give them. Well, no, they want a form that does something very specific. So long as your website is professional, that gives them the feeling that you are competent and will make their life easier. For very specific plugins, it is actually features and not benefits, whatever the marketing people say.

Mark:
A classic example is yesterday, somebody on our Facebook group asked if our Google Sheets add-on could add one row per repeater on the form. They wanted it to create a row per repeater. I went, you know what? It can’t do that but I’m going to make it do that. I wrote that last night and it’s a great new feature. I’ve been asked a few times and now that support ticket has disappeared because people will know it can do that. I don’t have to say no to it. It may sound crazy being reactive like that, but it actually works for us. We tend to go with waves of requests from customers. For example, when AI suddenly became all the rage and OpenAI came out, everyone was saying, can I use OpenAI on the form? We built an OpenAI add-on and wrote a press release about it. Because we were the first ones to really do it with all of the API endpoints that OpenAI offers, it was a great little news piece for us. That has now become quite a popular plugin.

The most popular part of WS Form is integrations with custom field plugins like ACF, ACP, meta box tool set, etc. Working on those and developing those has been one of the key selling points of WS Form. We’ve had to differentiate ourselves from the rest of the pack. Focusing on site builders such as Bricks and Oxygen has also been key. We certainly had to find a niche.

Marcus:
You mentioned that you have 46 or so add-ons to WS Form. With almost 50 add-ons, how do you keep track of updates? How do you prioritize your time? Is a lot of it reactive, looking to see if a new API has come out, or do you spend time trying to figure out how to add more features to each of those add-ons? Is it revenue-driven? How do you prioritize what’s important to building new ones versus keeping the ones that you have updated or working on the core plugin itself?

Mark:
On the add-ons, we are usually contacted by those integration partners letting us know there’s going to be a new version of an API coming out so we can get ahead of that fairly quickly. Surprisingly, some of them don’t actually, you just hear from a customer that something’s been changed and then you have to jump in and change it, but there is a little bit of reactivity there for sure. On the core, we are very much a customer-driven plugin. When the product was first launched, it was a core product, fully mobile responsive, and had some quite intuitive and revolutionary stuff. Then it was a case of listening to the customers and what they wanted. We have a features page where people can submit new features for WS Form, and those can be voted on. Honestly, we have more feature requests than we could possibly ever build, even with a team of 20 people.

Certain things shine and get a lot of votes, so we focus on those and build them. We are customer-focused but also business-focused. There are things we want to launch because we know we can reach out to a new audience by doing that. For example, we’ve recently introduced an integration with ACPT, a newer custom field plugin. We are now fully bi-directionally integrated with ACPT. As a result, the developer has shouted to his customer base about WS Form, and we’ve done the same for him on our end. That mutual marketing effort really helps grow the product. It is business-driven and customer-driven, primarily customer-driven. That’s how I roll. I pick what’s next, build it, document it, make a video about it, and push it out to the masses.

Marcus:
You have a feature request page you said. How do you decide when not to build something? You’re going to get hundreds if not thousands of feature requests, and people will vote on them. Maybe something rises to the top that you decide doesn’t make sense for your product. How do you decide that? How do you know when to say no to a feature request?

Mark:
Some feature requests we get are very niche, specific to certain customer requirements. In that case, they usually aren’t built. If it’s a feature where multiple people can take advantage of it, it’s more likely to be built. We do get some customers with very specific use cases. I’m sure Katie comes across that with her plugins as well. We basically just say, look, you could do it with some custom coding, maybe with a hook or something. We work with Codeable as well. If a customer has specific development needs, they can go through Codeable, and maybe they’ll develop it for them. We tend to steer away from developing custom stuff for payment because it pulls us away from supporting people and developing the product the way we want to. There are things that come across the table that are a no, and it’s usually those niche use cases. Sometimes it’s just impossible. We literally get requests that cannot be done. Some use cases are amazing and quite complex. That’s where we focus the product, to build pretty much an app builder, not just a form builder. We have integration with WooCommerce as well, so you can put forms on products. We sometimes collaborate with others to use their products in conjunction with WS Form, like showing form submissions on a website. Sometimes we recommend a third-party product to do that. If somebody wants to build a store with stock levels and multiple payment methods, I’ll say, use WooCommerce, not this form. I won’t try to get every sale. I’ll always recommend something appropriate.

Katie:
Those are all good ways of allowing your company to stay small and not expand the team while being just as successful. You are meeting that customer’s need by telling them to use a third-party plugin with your plugin. You still make the sale, but you’re keeping within scope, staying small. That works. I know I’ve made a lot of mistakes which have forced us to grow more team-wise more than we otherwise would’ve done. Customers use your product in a way you never anticipated. I get excited when that happens because it’s an SEO opportunity to produce new content and get sales. But many times, I’ve been guilty of doing that when perhaps there were compromises involved. It wasn’t what we intended when we built the plugin. There might be something a little hacky about the way you achieve that, but I’ll still go ahead and use it as a marketing opportunity. That generates more support and feature requests. If I hadn’t done that, we could’ve stayed smaller for longer, but then we would’ve had a smaller market. I don’t know what’s best, but mistakes were made.

Mark:
Katie is someone I look up to as a plugin developer. We had the chance to talk at WordCamp US. We had the opportunity to sit down in a coffee shop and chat together. It’s great to learn from others and how they’ve approached things. Katie is quite open about mistakes she’s made and successes she’s had, and we can all learn from that. Thank you for all that. It’s been really, really helpful.

Katie:
Nice. That is helpful. I’m sure we are bigger than we need to be and I do worry about that. We’ve got something like eight support engineers now full-time. I feel that’s because of extra complexity I might have built into the products. Many companies just focus on one product. That’s where I made a mistake. We’ve grown more team-wise because of the extra complexity.

Mark:
When I hit my 10,000th support ticket, I reflected on what I’ve done over those last 10,000 support tickets and how I’ve handled them. I find ways of keeping the conversation great for the customer but also keeping it short and sweet, not prolonging it longer than needed. There are ways of making support more efficient. I almost want to write a blog post on how to run a support department. We use a lot of macros for responses. When a support ticket comes in, we make sure they’re a genuine customer by doing license key lookups on their domain names. There are ways that can be automated to speed things up. It’s quite a science. That’s a large part of how I’m still able to run it as a one-man band. Hopefully, there will come a day when I can’t do that anymore. I’m hoping to grow and get to that point. We are growing between 25-40% year on year, which has been pretty good and still managed to do it.

Katie:
That is more than nearly all plugin companies are at the moment.

Mark:
I’m quite proud of the growth we’ve had. That’s through a lot of hard work. Being present as much as possible is important. It’s very easy to build a plugin and think people are going to use your product. It doesn’t work like that. You’ve got to get out there, tell people the benefits, talk to people, do podcasts. It’s a lot of pushing stuff in the pipe

and hoping stuff comes out the other end. Fortunately, it has done.

Marcus:
That’s a product of you being out in front of folks and showing them what your form can do. It’s also a product of the relationships you’ve formed within WordPress. I’m wearing the WS Form hat right now and happy to share WS Form with anyone who needs a form solution for their WordPress site. It’s a testament to the product itself and the relationships you’ve formed within the community. The question I have is, you said you want to grow and expand your team at some point. Do you have a formula as a workaholic? How do you know when that time is? Is it when you’ve hit that 24th hour of the day and need a 25th hour, or do you have a way of knowing when it’s too much and you need to offload some of it to someone else?

Mark:
It is too much now, to be honest. I’m a stickler for keeping profitability as high as I can. That’s my weak point. It’s a big change from being an indie one-man developer to taking staff on because it impacts the business quite significantly. I think it will come down to when I just cannot do it anymore. Finding support staff who can really understand WS Form and give answers like I do is going to be a challenge. They may take on the simpler support tickets, pointing people in the right direction and taking that load off. If I hire someone, it’s going to be a multifaceted role. It’s not just going to be support. They will be involved in other stuff, standing at the booth at WordCamps. That’s small business nature. Even when I had 40 people, everyone had multiple roles within the business. I’m enjoying the single-man life for the moment, working with third parties to make everything happen. When I find I’m losing too much sleep, I will find that support person.

For now, I’m happy, really pleased with how things are going with the business. I love being part of the WordPress community, really enjoying life. It’s not impacting my time with my family. I can still sit down, have dinner with them, do stuff on weekends, and get involved with the kids. When that starts getting impacted too much, that’ll be the time to find some resource to take that off my shoulders.

Katie:
Makes sense. I understand the dilemma about profitability. Before we started taking on team members, we were always at 91% profit. It’s just gone down and down since then. While it’s still plenty profitable, we did make $20,000 less last year than the previous year. Revenue was higher, but that had entirely been eaten up by increased team costs. We made a conscious decision. Andy and I sat down and thought, shall we hire this extra developer at the expense of this amount of profitability? We decided yes, it’s an investment in the future. But when you see it happen and do your end-of-year numbers and you made $20,000 less, and every team member has had a raise, it’s kind of demotivating. I can see wanting to hold onto that for as long as possible. You, Mark, will always be more efficient than anybody you hire. That’s just how it works with founders versus team members. You’ll hire people, and they will do a fraction of your productivity, but you have to sometimes.

Mark:
When I moved to the States in 2005, got married, and started another agency in New Orleans, it was just me doing consultancy. It was great. I had a great contract with a few companies. I got to a point where I needed some people, started building a team, and got to seven or eight. I found myself doing the same thing. I was spending all my time finding work for those people and managing them, doing business development, and just kind of doing HR. I sat down with my wife at dinner and said, you know what? I’m making less money doing this, keeping people employed. As much as I loved keeping people employed, I was just not doing what I wanted to do, which was development. I love building things. I’m a coder at heart. I’m useless in marketing.

Katie:
You’ve done a very good job at marketing.

Mark:
It was an eye-opener. I realized I didn’t really want to do that anymore. The web game, particularly in New Orleans, was not what it was in London. It’s a very different market. I had been running a wedding company called Wed Simple, which was online wedding websites and planning. I used to white label that to Conde Nast for Brides magazine, Vanity Fair, and things like that. That was a license-based model. I realized that I like this licensing game. It’s more stable. The agency game for me was quite a risk. We had significant contracts, and when those ended, you had to find the next big contract. It was the classic agency stress lifecycle. You see agencies laying off tens of people when they lose these big contracts. Software licensing is thousands of customers with small amounts of money. When you lose one of them, it’s less of an impact on the business. I just kind of needed the change in my career. I got to a point where I couldn’t build another website. That’s probably why my website is so terrible. I need Marcus’s help.

Marcus:
I have been on the other side of that. I worked at an agency where 50% of our income was from one client that went away. I was on the list of folks who were not able to be paid anymore. I had to move on. That’s how I ended up at Sky Verge, which then got acquired by GoDaddy. I wouldn’t recommend putting all your eggs in one basket. Having the majority of your income coming from one or two clients on the agency side can dry up, and that’s no fun.

Mark:
That’s what happened to me with my wedding business. I had five clients, including BBC magazines. I was on vacation in Florida with my family and Pinterest suddenly popped out of nowhere. Brides started looking at Pinterest for wedding stuff and were no longer reading bridal magazines. I lost three clients during my vacation. That’s that done then. Even when you’re running a business, there are certain things you don’t even think about that could impact you. On the whole, from all the plugin developers I’ve spoken to, generally, once they get to a certain stage, it’s fairly stable. As long as you keep developing that product and staying present in the community, people keep coming back for more. Fingers crossed, we’ll keep growing and developing. I’m thoroughly enjoying it. I love working with our customers. They’re pleasant to work with. A lot of them give valuable feedback about the product. Listening to customers is critical to success. If you’re not listening to your customers and adapting your product to their needs, you’re going to fall flat on your face. Being conscious of their needs and listening is very important.

Marcus:
You’ve compared your size to Katie’s Barn2 Plugins a couple of times. One of the big differences is the number of products Katie has versus WS Form. I’m curious if you’ve ever thought about creating another product. Has something come across your plate that you’ve thought, this is not in the realm of WS Form but seems interesting to tackle? Has that ever happened?

Mark:
It has happened. I have some ideas. Whatever I decide to do in terms of an additional product in the future, it’s going to complement WS Form because I would then have a captive audience for that product. If I were to suddenly decide to build an e-commerce platform, it would be a mistake. I’d be starting at the bottom rung of the ladder trying to market that. In a way, the add-ons I have are sometimes new products I can promote and shout about. The reason I have so many is because I need to cater to all the different needs out there. In terms of building an entirely new product, I have some ideas. I don’t want to do it until I’m happy to take my foot off WS Form. To Katie’s point, that’s probably another reason I’m going to need some staff. I’ve made a point over the last six years of not doing that. I knew if I did that, I would spread myself too thin, which I’ve been guilty of in the past with other businesses. Watch this space, there will be stuff coming. We’ve got some exciting stuff in the pipeline, hopefully for this year or early next year.

Marcus:
Katie, you’ve had to step from one to multiple products. Do you have any advice for Mark in having to think about that? What if Mark had another product he wanted to build? Any advice?

Katie:
I think Mark touched on the two key points: not spreading yourself too thin and making sure new products are a good fit. For example, we released our WooCommerce product options plugin partly as a companion for our existing WooCommerce product table plugin. A lot of our product table users were creating one-page order forms and wanted extra options in the order form like tick boxes and things. We integrated with the official WooCommerce product add-ons plugin, but it’s pretty basic. We built our own to scratch the itch of our customers. Now that is a really successful plugin in its own right. We can promote those two products to each other. In contrast, we have a document library plugin, which has nothing to do with WooCommerce. There’s no crossover between the two really.

Speaking more generally, I like having multiple products because it decreases the risk. If something goes wrong with one market, like if there’s a major new competitor or people’s needs change, I’ve still got all my WooCommerce add-ons. I feel more secure having multiple ones.

Mark:
That’s a good point. Diversifying the portfolio gives more

stability down the line. It’s a huge amount of work, but that’s the end goal. It’s been surprising how much work it’s taken to get WS Form to this point. There are easier ways for me to make money. I could still be building websites and systems for people and be making a lot more money, but I don’t think it would be as rewarding. By having a plugin, you have an asset. With an agency, you typically don’t have an asset, just people and computers. Maybe 10 years from now, I’ll be offered some money for WS Form, and that’s something I wouldn’t have had with just an agency. I love the challenge. Being the workaholic I am, I quite enjoy what I do.

Katie:
Excellent. Thank you so much for coming on Do the Woo to talk to us. I think you’ve given us some really good advice about how to be more efficient and achieve more on your own, as well as when maybe it becomes too much. Thank you for coming on.

Mark:
Thank you. I’ll be calling on you again, Katie, in the future I’m sure.

Marcus:
Thanks as well, Mark. I appreciate it.

Mark:
Yeah, thanks.

Sponsors
Open Makers (archived)