domain vapoholic .co .uk

[AJ77]

1. Acquisition Reason: Been operating ecommerce business on domain, partner now wants to buy my share of business, so would like guidance on how to fairly value the domain.

2. Markets: ecig / vaping eliquids & ejuice
3. Research:
4. End-User Value:
5. Reseller Value:
6. Traffic: averages between 20 and 30 users per day
7. Revenue:around £200 in sales per day
8. Age: domain age 2 years, operating as ecommerce site for 12 months
9. Miscellaneous: website has gone down since 29th december, database has been corrupted and would take lot of work to get back online

 

[james haw]

If the site is really making £200 per day in sales that's £70K a year. The site and business is worth a fair bit and it's that package you are surely selling on to your partner? Not just the domain name.

It's hard to say what the domain name alone is worth, as it's branded with that site. Do you value it based on its value and requirement to stay with that site/brand, or as a stand alone name?
With the site and brand not factored in, it's just a generic name. As it's a brandable it's what someone would pay for it - eg hard to evaluate.
It could be worth anything from low to high 3 figures - but that's entirely speculation. It could sell for anything and you'd only know exactly what it would sell for by actually selling it.

So it's hard to give a value for your particular scenario.

Incidently, an aside, if it's making £200 a day I'd be sorting out those DB issues pretty promptly

 

[DomainGist]

If the site is really making £200 per day in sales that's £70K a year.

Incidently, an aside, if it's making £200 a day I'd be sorting out those DB issues pretty promptly

Profit and revenue are two entirely different things.

A business can have revenue of £200 a day and costs of £250 a day.... and would in effect be worthless.

I'd say "making" = net profit, in any business, not revenue.

 

[james haw]

Profit and revenue are two entirely different things.

Well, yeah, I get basic business 101

A business can have revenue of £200 a day and costs of £250 a day.... and would in effect be worthless.

This is not necessarily true. The revenue alone can make a business valuable and have a high resale value due to the potential it may have.
There's often plenty of scope to make some changes to start generating profit as long as there is enough revenue. Not always, but often.

 

[dhaupin]

This is a unique brand identity that is an obvious and highly desirable phrase for a vape/ejuice company. Albeit co.UK, its still better than many other choices There is obvious buyout value there, and the traffic could be pumped massively.

Whats up with your DB? You could pay a good developer your revenue for one day, and they could prob sort that DB fairly quickly. For example, a serialization end of space (varchar) in a column could corrupt your site -- but it would take like 10 minutes to grab what data is there, delete that field, and restore the site. Just saying.....don't undermine the value in repairing the DB, especially if you have lost £3000 of your revenue stream since the 29th.

 

[james haw]

a serialization end of space (varchar) in a column could corrupt your site

0_o

delete that field

0_o
0_o

 

[dhaupin]

Hah sorry, my bad for the tech speak. I have experience with corrupted DB's and these guys should def repair theirs to add a TON of value to the changeover.

To clarify the serialization thing above: Imagine you are hired for a job, and you always need to hear full sentences that make sense and end in periods. But the boss telling you has to say it in 100 words or less, and end it in a period, or else you stop listening and everything hits the fan, you melt down, throw a fit, kick and scream, walk out the door, etc. That's sorta what DB errors are like lol

 

[james haw]

To clarify the serialization thing above: Imagine you are hired for a job, and you always need to hear full sentences that make sense and end in periods. But the boss telling you has to say it in 100 words or less, and end it in a period, or else you stop listening and everything hits the fan, you melt down, throw a fit, kick and scream, walk out the door, etc. That's sorta what DB errors are like lol

I just wondered what sort of corruption something at the end of a varchar could be that would bring down the site. I guess it depends on the data really and how it's being stored.

I'd be checking how it happened, in case something is incorrectly serialising or only part serialising, or not being unserialised correctly before use. So likely a bug in the code. Not fixing this could mean the issues would re-occur even if you fixed the corruption issue. So I wouldn't just do a backup and restore without at least trying to ascertain the cause in the first place. Nor just delete the field as that data could be salvageable

Also, maybe something should be validating the serialised data if it's so critical to the app.
All this said, DB corruption could be anything at all, and we're off topic lol

 

[dhaupin]

Yes def off topic but kinda not considering their DB is down and they are asking about value of having the site online.

I agree with everything you are saying brother I was highlighting the fragile-ness of serialization, and technically an incompletely stored string, whether capped length or whatever else, is corrupted. Varchar is a hard limit that i have def seen capped -- especially on platforms where plugin/addon/module devs rely on the settings engine to store their stuff instead of making their own new tables. its pretty common to see a somedev_settings for an addon with a ton of fields stored as 1, and they dont consider that maybe some description goes on for 8 paragraphs. Save and dead.

From the original post I take it that the whole site is down. A product or topic corruption would not do this -- its most likely settings or settings table, that are very likely to be serialized in one way or another. It was def a shortform sentence for a hugely more complex thing. Considering how frequently its called, in broad parts of platforms (ie Wordpress, Opencart, + devs introducing single field storage) it seems to be a common error/corruption point.

PS I am not trying to be off topic -- please consider the topics James and I are talking about to be a starting point for your site repair