Really, your desired point on the price/performance tradeoff depends on the specific circumstances of your business.<p>(a) Being able to compete on price means you have to be really hard-nosed about optimizing every part of your operations to stay lean. Good relationships with suppliers and competent execution of your strategy are paramount -- think Walmart.<p>(b) Competing on product means you have to be able to blow away your competition. It's easier the smaller your niche is. It's often about having a talented designer -- Steve Jobs, Shigeru Miyamoto, Notch -- together with a support team.<p>A lot of software is easier to compete on product, because (1) the zero-marginal-cost structure of the industry means that competing on price is a race to the bottom that will ultimately be won by open source, and (2) a lot of software is specialized.<p>Companies that win in (a) tend to be driven by business types who are good at the stuff they teach in MBA school. Companies that win in (b) tend to be driven by creative types and have a culture where the creatives' vision is the core competency, and the business side is seen as more of a support role. The good news for bootstrap-stage startups is, if you're in category (b), your business chops don't matter as much; the product can make up for a lot, if it's good enough.<p>So if your team is thin on business talent but has a ton of technical talent, you should use strategy (b). The reverse should use strategy (a) in theory, but in practice is rare among startups; business types who are good at what they do tend to pull down very good compensation, and mostly hang around companies that can afford it. Of course, if you're in YC or funded, you may have access to business-knowledgeable people; but getting to that point usually means you already have a great product and a lot of technical talent.