Jonathan Stark

If people out there are listening, have running a SaaS or something, you probably pay a team or you have an outsource, some sort of outsource, a dev shop or something where they are writing code. They are implementing new features. They are squashing bugs. And it's the coal mining of the software business. It's the typing semicolons.

If people out there are listening, have running a SaaS or something, you probably pay a team or you have an outsource, some sort of outsource, a dev shop or something where they are writing code. They are implementing new features. They are squashing bugs. And it's the coal mining of the software business. It's the typing semicolons.

And if that's what if you're a dev shop and that's what you do, especially as a soloist, but even as a dev shop, if that's what you do and you like it and it's profitable, then great. Keep doing that. That's fine.

And if that's what if you're a dev shop and that's what you do, especially as a soloist, but even as a dev shop, if that's what you do and you like it and it's profitable, then great. Keep doing that. That's fine.

And if that's what if you're a dev shop and that's what you do, especially as a soloist, but even as a dev shop, if that's what you do and you like it and it's profitable, then great. Keep doing that. That's fine.

But your path to scaling without hiring or without growing the team would be to increase your altitude of involvement so that you are doing more high level strategic types of engagements with your clients and not so much the implementation or the execution of the plan.

But your path to scaling without hiring or without growing the team would be to increase your altitude of involvement so that you are doing more high level strategic types of engagements with your clients and not so much the implementation or the execution of the plan.

But your path to scaling without hiring or without growing the team would be to increase your altitude of involvement so that you are doing more high level strategic types of engagements with your clients and not so much the implementation or the execution of the plan.

And I think of it, especially in software, it's really easy to map to kind of building metaphor, physical house type of thing, where you've got these three altitudes of involvement with a client. One that most people operate at is the middle tier, but there's a bottom tier. So the bottom tier are called maintenance. So that's like a support maintenance contract, that sort of thing.

And I think of it, especially in software, it's really easy to map to kind of building metaphor, physical house type of thing, where you've got these three altitudes of involvement with a client. One that most people operate at is the middle tier, but there's a bottom tier. So the bottom tier are called maintenance. So that's like a support maintenance contract, that sort of thing.

And I think of it, especially in software, it's really easy to map to kind of building metaphor, physical house type of thing, where you've got these three altitudes of involvement with a client. One that most people operate at is the middle tier, but there's a bottom tier. So the bottom tier are called maintenance. So that's like a support maintenance contract, that sort of thing.

where somebody's got a software application and they just need someone to keep it from breaking down or when an OS upgrade creates a bug or something, they just need to keep working the way it's working. They're not looking for necessarily for new features. That's the bottom level.

where somebody's got a software application and they just need someone to keep it from breaking down or when an OS upgrade creates a bug or something, they just need to keep working the way it's working. They're not looking for necessarily for new features. That's the bottom level.

where somebody's got a software application and they just need someone to keep it from breaking down or when an OS upgrade creates a bug or something, they just need to keep working the way it's working. They're not looking for necessarily for new features. That's the bottom level.

It's the least profitable, perhaps the most predictable, but it's a very specific kind of business, the volume business. The middle tier where I would call implementation or building or execution is where you're making the new status quo so that if the maintenance level, the bottom level is maintaining the current status quo, the middle level is making a new status quo real.

It's the least profitable, perhaps the most predictable, but it's a very specific kind of business, the volume business. The middle tier where I would call implementation or building or execution is where you're making the new status quo so that if the maintenance level, the bottom level is maintaining the current status quo, the middle level is making a new status quo real.

It's the least profitable, perhaps the most predictable, but it's a very specific kind of business, the volume business. The middle tier where I would call implementation or building or execution is where you're making the new status quo so that if the maintenance level, the bottom level is maintaining the current status quo, the middle level is making a new status quo real.

It's adding a new feature. It's adding a new module. It's building another SaaS, a companion app. It's some new feature development or new product development where you're creating a new status quo, which eventually will fall into the maintenance level, but someone else can do that. And then the top level is helping the client decide what the new status quo should be.

It's adding a new feature. It's adding a new module. It's building another SaaS, a companion app. It's some new feature development or new product development where you're creating a new status quo, which eventually will fall into the maintenance level, but someone else can do that. And then the top level is helping the client decide what the new status quo should be.

It's adding a new feature. It's adding a new module. It's building another SaaS, a companion app. It's some new feature development or new product development where you're creating a new status quo, which eventually will fall into the maintenance level, but someone else can do that. And then the top level is helping the client decide what the new status quo should be.