So what's a good long-term strategy? Well, refactoring your code so that you will still be able to add features in the future, that's a good one. Or spending some extra time putting some polish on your features and UI so that when the product is released, users are actually happy with it. Not adding features that you don't want to maintain, if they're not important enough – that's another one.
Remember that Mozilla (http://www.mozilla.org) did poorly for years, only to finally start gaining dominance in a market that Netscape had lost, because they had a long-term plan. Granted, Mozilla made some decisions early on that caused some things to take longer than they should have, but they still won out in the long term, despite failing in the short term.
Of course, it can be hard to convince people that your long-term plan is right, sometimes, because it takes so long to show results! When I started refactoring Bugzilla (https://www.bugzilla.org/) in 2004 there was pretty...