Forum Moderators: buckworks & webwork

Message Too Old, No Replies

Providing Domain Name Registration as a Part of Website Development Services

Best and worst approaches for handling the issue of domain name registration?

         

vincevincevince

8:33 am on May 3, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I'm looking for advice about how to provide domain name registration to web-development customers. I don't want to provide domain name registration to those not purchasing web development, and I want to handle the billing and renewal myself.

Being able to search for available domains is essential, as is having the service reasonably white-labelled. The price isn't a maximum priority as it can be absorbed into the much-larger web-development budget.

What approaches would work for that? The less work on my part the better!

Note, please do not give links/names of specific services here.

[edited by: Webwork at 11:56 am (utc) on May 3, 2007]
[edit reason] WebmasterWorld TOS [/edit]

Webwork

12:01 pm on May 3, 2007 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



VVV, given the almost universal eschewing of the practice of web developers registering the domain names for client websites I think you may be setting yourself up for trouble.

For example, if someone is seeking quotes and learns that your practice is to handle the domain registration don't you think that competitors might direct the person to a few threads here at WebmasterWorld to prove what a bad idea it is for a company to turn over their web identity to a web developer's control?

I'd consult with the client - for a fee - about branding, etc. and then turn them loose to chose and register their own domain with the advice that they should register it for 10 years if they plan to stay in business.

There are myriad domain registrar websites that offer name-variation or name-suggestion tools. Almost all the major players have some version of this free service. Mostly they're junk producers and I'd tell the prospective client that's my opinion. It's all a matter of any client's willingness to pay for valuable services. It is easy to argue that website naming assistance is a valuable service, though it's equally easy for the average Joe/Jane to reject the argument.

Offer name selection guidance as a value added service for a price. Otherwise, I'd let the client "have fun". At a minimum make name selection and registration and safe domain pratices guidance a 1/2 hour part of your basic package and make it non-optional.

[edited by: Webwork at 12:34 pm (utc) on May 3, 2007]

jtara

6:59 pm on May 3, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I agree 1000% with webwork.

Doing this is going to raise a red flag with savvy customers who will run the other way as soon as they hear this, without hearing the rest of your pitch.

It won't help to then tell them that they can register the domain name(s) themselves if they wish - just knowing that you prefer to do it yourself is all they have to hear to send them packing.

In fact, I'd suggest the OPPOSITE. Take the time to explain to your customers - and your potential customers - why they should not allow a web designer to register domains on their behalf. It just might be the key factor in establishing customer trust and loyalty, and the most productive 5 minutes you ever spent with the customer.

If you still insist, many of the large domain registrars have APIs that will allow you to incorporate registration services into your website and/or your internal administration and billing systems.

vincevincevince

4:21 am on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks for the advice and discouragement!

The only reason I want to provide a service is so that I can provide an all-in service by reducing the barriers. Having to buy a domain name elsewhere first doesn't really sound very professional to me. Nor does discussing domain name choice and then being sent elsewhere to go and buy the domain.

I would prefer to have some way of doing this through an established and reputable registrar so that the customer can have ownership of the domain name through them. Difficult problem!

jtara

4:46 am on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The problem is that some disreputable and even reputable website developers and web hosting companies put customer website registrations in the OWN name. Then, when some dispute arises, or when/if the customer simply wants to change service providers, they "hold the customer hostage", preventing them from switching to another service, because they control the customer's domain name.

Now, surely this isn't your intent. :) And you've stated it's your intention to register the sites in the customer's names. But even if you are pure as snow, there is a taint to the practice due to the actions of less scrupulous individuals, and so it is best to avoid it.

For many websites, their domain name can become their most important asset. It would be foolish to allow somebody else to put it in their own name, or even allow another party to take responsibility for yearly renewal. It is too important to shift the responsibility to sombody else. You will be giving your customers great advice if you tell them this.

Suggest a good registrar, walk them through the process, make sure they understand how to do it and what registration represents. Impress upon them the importance of keeping their registration current, and keeping their registration information current and accurate.

vincevincevince

8:09 am on May 4, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I really do agree with you about the negative points. On the other hand, I really do think that I need to integrate domain name purchase to the maximum extent that doesn't cause a negative slur, for the sake of those new to the web, and to be able to provide a one-stop-shop.

From what you've said above, it seems that integrating it fully is a big no. I guess that my new plan will be to find a domain name registrar who can provide an availability checker on my site but then take the customer off to deal with the purchase and not engage in cross-selling of competing products (e.g. hosting).

I still have major reservations though! I'm worried that a certain percentage of customers will buy the domain and then not come back to me for the development part.

I've dropped the idea of paying for the domain ... instead I reckon I can give a credit of equal value to their first development bill. Perhaps that will help persuade them to stick around.

It's difficult. I feel like not being able to provide the domain service as part of the customer flow is going to really disrupt things.