Hey @eliquid me again
Remember a couple of months back I asked you for some advice on onboarding a shady client.
Well it turned out OK, he signed, refused to pay for ~2 months and just when I thought my gut was right, he paid for a full year. So twists and turns I suppose...
Also we kept the prices as they are, kept developing and we got new clients
Since then we`ve been steadily onboarding 2-3 clients per month and things are starting to get a bit out of hand in terms of developing.
I cant neglect my job since it pays the bills but I also cant devote my full time to the project.
As a result, we`ve started hardcoding features here and there just so we can keep up with the current and new client requests.
Some features we do integrate into the system, but for half lets say, we do them only for the client that wants them.
I`m hearing my gut again.
On one hand I want to improve on the system, clear out the hardcode, streamline and automate.
On the other hand I keep thinking over and over in my head: Its for the clients, its not for you.
My question is, have you dealt with such a scenario?
Can the project fail because of the accumulated tech debt?
What would you be your advice? Should we slow down/stop with clients until we catch up with development, or keep hardcoding and onboarding until the monthly revenue surpases my income so I can devote 100% to the project?
Any insight would be greatly appreciated.
PS. Thank you for your previous advice and your time spent ot writting it.
Remember a couple of months back I asked you for some advice on onboarding a shady client.
Well it turned out OK, he signed, refused to pay for ~2 months and just when I thought my gut was right, he paid for a full year. So twists and turns I suppose...
Also we kept the prices as they are, kept developing and we got new clients
Since then we`ve been steadily onboarding 2-3 clients per month and things are starting to get a bit out of hand in terms of developing.
I cant neglect my job since it pays the bills but I also cant devote my full time to the project.
As a result, we`ve started hardcoding features here and there just so we can keep up with the current and new client requests.
Some features we do integrate into the system, but for half lets say, we do them only for the client that wants them.
I`m hearing my gut again.
On one hand I want to improve on the system, clear out the hardcode, streamline and automate.
On the other hand I keep thinking over and over in my head: Its for the clients, its not for you.
My question is, have you dealt with such a scenario?
Can the project fail because of the accumulated tech debt?
What would you be your advice? Should we slow down/stop with clients until we catch up with development, or keep hardcoding and onboarding until the monthly revenue surpases my income so I can devote 100% to the project?
Any insight would be greatly appreciated.
PS. Thank you for your previous advice and your time spent ot writting it.
Dislike ads? Remove them and support the forum:
Subscribe to Fastlane Insiders.
Last edited: