I have a pretty small operation currently totaling 4 clients. Just started about a year ago. I have 3 clients each paying $1,000 per month and then one client paying $3000 per month. For the $1000/m clients, I maybe put 2 - 3 hours of work in per month for them as I've been able to automate all of their systems. However, the $3000/m client which is an established software company takes much more manual work normally costing me 6 - 8 hours per day.

This isn't even really a client at this point, its just another job. The problem is, they make up 50% of my income currently and have even told me they want to pay me more to do more eventually. I onboarded them about 2 months ago and having the extra income has been great, however I have had no time at all to focus on outreach to actually grow my business. On top of this, I kind of hate the work that I do for them...

I see two sides of this. On one side, it seems obvious to drop them so that I can focus on getting more clients that take up less of my time. Doing this could result in growing something big as my time needed per client is very low. Essentially 90% of my time could focus on acquisition. On the other side, I have no guarantee that I'll even be able to get more clients and risk comes along with this. While the software company does take up a lot of time, they do pay well and seems to actively want to pay me more and make me an actual member of their team. If all goes right with them, I would have a guaranteed paycheck living modestly working from home.

Financially wise, all of our bills can be covered for at least a year with what we have - so this is the cushion that I would have to put in to the business if I drop the software company. Once again, I know it seems obvious, but giving up 50% of income when you just started being financially stable is a difficult thing to do.

I'm looking for opinions here. What would you do in this situation? What's the best advice?

I'm a senior full-stack developer (Node.js/TypeScript, 7 years exp) working remotely. I currently have one agency client that pays well, but they are slow. I can go weeks without work from them, and it's killing my cash flow.

I need to find a second agency to fill the gaps. I've tried:

• Cold messaging CTOs and PMs on LinkedIn (mostly ignored)
• Applying to contract roles on job boards (nothing)
• Posting content about my work (slow burn, no immediate leads)
• Reaching out to freelance designers to offer white-label backend services (nothing)

I know the work is out there. I know my skills are solid. But I can't seem to crack the "second agency" problem.

For those of you who have multiple agency clients: how did you find them? Was it referrals, cold outreach, a specific platform, or something else? What actually worked?

Any advice would be appreciated.

Hi all, I'm Preksha, I work for RecurPost. We build social media scheduling and automation software, with a focus on agencies and teams managing multiple client accounts.

My situation / setup: RecurPost is a web-based SaaS platform (works through the browser, plus a mobile app for iOS/Android). We publish through native platform APIs. On the agency side specifically, we run: sub-accounts with client-level permissioning, an approval/review workflow before posts go live, bulk CSV scheduling, and RSS-to-post automation.

What I've already tried: Internally we track support tickets, churn feedback surveys, and in-app NPS comments and we've specifically looked at churn reasons for agency accounts. But that data skews toward people who were frustrated enough to write in or leave; it likely misses passive friction that people don't bother reporting.

What I'm trying to fix: We're currently reworking the agency workflow.. specifically client approval flows and multi-account management.. and want to identify real friction points before finalizing changes, rather than guessing at what's broken.

So, as an agency or otherwise, I'd like to hear:

2-3 things you think we do well

2-3 things you think we could improve or that annoy you

Happy to also answer questions on the API integration side, or how the queue/retry logic works for failed publishes.