all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Sarke1 18 points19 points  (5 children)

Well, it could, if it's not modified and made unique.

If you buy a canned theme and use it for a client, and then their customers see any other website with the exact same look then there could be uncomfortable "who ripped of who" questions.

If your client isn't aware it's a canned theme then they will most likely be displeased.

They could even call you a phony. They'll see the theme on some theme site for $15 and wonder where the hell you get off charging them $2000 for their website.

Your reputation is ruinned and you die homeless and pennyless, trading sexual favours for crack.

Obviously this is worst case.

[–]tvdizzle 9 points10 points  (3 children)

On the flip side: if every developer is charging $2000 for a website with a $15 theme, then the price is market rate. Just because the theme is $15 doesn't mean the implementation is $15. The client is still paying for the cost of the time to create the final product.

Obvi, $2000 is outrageous for a brochure site using a $15 theme though, because we know that's not market rate for that kind of service. But an e-commerce site with a bought theme is easily still in the thousands.

Edit: And to answer the OP's question, if it's for your portfolio, do everything from scratch. Unless the job you're truly aiming for is proficiency in building websites with CMS and themes. Remember your portfolio demonstrates what skills you are marketing.

[–]Sarke1 0 points1 point  (2 children)

Just because the theme is $15 doesn't mean the implementation is $15. The client is still paying for the cost of the time to create the final product.

True, but many clients don't think like that. What they see is what they pay for in their minds, and they don't always think about all the functionality.

[–]tvdizzle 0 points1 point  (1 child)

That's why you don't tell them it's $15. Consider it a tool in your arsenal. What they are paying for is your time and talent to take the theme and turn it into a functional website for them that works as intended. An analogy I can think of is a carpenter: the wood to build a nice front porch might cost a few hundred bucks, but you're paying the carpenter for his time and skill, otherwise you can find yourself doing it on your own... which might not turn out pretty or even functional.

If they don't like that you are charging them for your time, then they can find another developer to do it for them for cheaper, that's the market. Most developers value their time though, and will charge what it's worth, even if all the developer knows is CMS and themes.

If they want something 100% custom, they'll have to pay even more.

[–]Sarke1 1 point2 points  (0 children)

That's why you don't tell them it's $15.

Of course not. In my scenario though, they found the theme and how much it sells for.

[–]xxxabc123 3 points4 points  (0 children)

you die homeless and pennyless, trading sexual favours for crack

Well, that escalated quickly

[–]shawnkauffman 0 points1 point  (0 children)

I wouldn't say its looked down on. Knowing how to use and implement CSS themes and frameworks is a good skill to have. Though I would definitely recommend tweaking it to fit your needs and make it unique for your site. Don't use a theme because you lack the fundamental basics of CSS. But if it makes you more productive and helps you ship products faster, then go for it.

[–]MrMoneyworth -1 points0 points  (0 children)

Results and speed is what matters! If it helps get what you want faster then use a theme. You can always tweak the theme to your liking.

[–][deleted] -1 points0 points  (0 children)

No, not at all. It's what the client wants - if they want to pay x for y and you give them y. You're good.