If it was profiting @ 75K a year, thats half a designer, half a marketer and half a programmer for a year. Hire them in, and let them do what they like with it for 6 months. Get interns and let them have a play with it if you want to give some kids a chance.
It's usually a bad idea to shut down a profit center, unless it truly is unsustainable. @75K this was doing well and IMO should not have been shut down.
My usual strategy works well here: Hire in @min wage, with a huge bonus linked to new subs.
Depending on the size of the company it might just make a great graduate / junior dev recruitment program. Take them on with a probationary period and watch how well they do with the sideline gig. If they turn the code to spaghetti within months then you probably don't want them working on the core business. The last one through the mill becomes supervisor for the next one.
The only potential issue with this strategy is damaging the brand name of the consulting company. I'm not entirely convinced that this is really an issue.
"Thanks for commenting. You are spot on, we weren't profitable in many other ways. The time we were spending on Newsberry could, and does, bring more profitability on our other products. In our opinion at Wildbit, half of an anything is not worth something. We don't build half-projects, and we don't put interns to work on them. But for many, it's hard to turn away $75/year."
Great story, guys. Let's see more of these.
Totally doesn't make any sense. Idealist for sure.
Not all good decisions are based in objective reality. Never underestimate a gut feeling.
After all, something like a mailing list service requires lots of ongoing care if it's to be any good (deliverability, etc).
It's not idealist, as you say, to shut down a project that is a time and energy suck. It's idealist to think a busy company with 2 very successful, well-loved projects should "devote a day a week" to a project that isn't nearly as profitable as the others, and which nobody really enjoys working on to boot.
Eventually, a year later, the overtaxed sales staff were punted the job. The sales guys were fantastic at sales and very personable, but there's a direct conflict of interest between sales and support contracts, especially when they don't understand the cost of supplying it.
All because the only things the CEO could see were his pet project, the projected sales figure, and any possible way to vacuum money into his pocket (he owned 2/3rds the company, so its long term health was actually in his interest...)
However, the true way to value profitability is to take a more financial perspective (financial being different than accounting). A financial perspective would value the opportunity cost of working on this application compared to working on another application. If the team spent 10 hours a week on the application, and those 10 hours a week could grow their other products by more than $75,000 a year, then of course the application isn't profitable. It's actually losing money.
Another way to look at its profitability is to look at it from an operational standpoint. The employees on the team would be consider a fixed cost (yes, they could hire more people, but that just changes the fixed cost). The limited resource for this particular fixed cost is time, and from their article I can assume that their time was maximized (working as many hours a week as they wanted to). Operational theory says when a fixed cost is at its maximum utilization, higher marginal profitability items should be prioritized. Basically, they are better off working on other items if they don't want to work more hours.