How does everyone generally deal with the issue of client domain purchasing? Say my client wants xyz.com and it's available. Is the generally accepted way purchasing (and thereby owning) the domain through my company and incorporating that cost into my bill? Or maybe just giving them directions on how to buy it and getting the passwords from them?
I can see merits in either scenario, but am wondering what is "industry standard". I would think some clients would be leery of letting me own their corporate website, but equally so, some people are horribly internet illiterate and probably aren't able to purchase their own domain.
Depends per client really, as TheDoc says the domain should be in their name. But some clients prefer (lazy / cant be arsed) that you buy it and dont mind that it's on your name.
i'd have to agree with @TheDoc on this one. it's always best to make them get it themselves. should they want ownership of the domain later on, domain transfers are a pain.
Yeah I always make them buy the domain. The trouble of switching it the first time teaches you really quickly to never buy it yourself.
How I handle it is if they have not already bought the one they want and I'm with the client, I just pull up Godaddy and walk them through the purchase. Takes 5 minutes and you can also get any of the usernames and passwords you need in case you have to redirect it. Easier all around.
If you purchase the domain name on their behalf, you're enabling them to be even more hands off than they already are. The best client is an educated client, and while I'm not suggesting you teach them your craft, I think it's much better to factor in an hour of "domain training" into you cost to walk them through it and get them comfortable with interacting with their own account.
Also, when I first started freelancing, I would purchase domain names for clients and completely forget to ever change the contact info -- in one instance a site was deleted because the client never got the renewal notices and I no longer had the email address I used to purchase the domain name. So, if not for any other reason, have your clients purchase their own domains so that once the project is done you can wash your hands of that sort of liability.
Cool! I think I know which way this is going...and it makes a lot of sense to me. Either create some sort of instruction manual or as JoshWhite said, walk them through it.
I normally make my clients get their own domains. Although there have been a few situations where they have wanted me to do it. I think in the long run its easier to get them to do it themselves as others have pointed out.
I can see merits in either scenario, but am wondering what is "industry standard". I would think some clients would be leery of letting me own their corporate website, but equally so, some people are horribly internet illiterate and probably aren't able to purchase their own domain.
Anyway, any insight is most gratefully accepted.
Thanks!
Brian
How I handle it is if they have not already bought the one they want and I'm with the client, I just pull up Godaddy and walk them through the purchase. Takes 5 minutes and you can also get any of the usernames and passwords you need in case you have to redirect it. Easier all around.
Also, when I first started freelancing, I would purchase domain names for clients and completely forget to ever change the contact info -- in one instance a site was deleted because the client never got the renewal notices and I no longer had the email address I used to purchase the domain name. So, if not for any other reason, have your clients purchase their own domains so that once the project is done you can wash your hands of that sort of liability.
Thanks guys!