Atom / Atom.com - Marketplace (formerly Squadhelp)

[JudgeMind]

Hey Folks,

I've just started using squadhelp.com to list some of my brandable. So far I have 76 domains listed, there is no fee to list. I've had some decent action so far in the way of interested buyers but no sales as of yet. I've only been with them for 1 week now.

A bit of a summary review of SquadHelp:

PROS

• No Listing fee
• No Logo design fee
• Ability to submit your names to end users holding naming contests
• Ability to chat directly or send a message directly to end users.
• Stats of your marketplace domains are shown in the marketplace dashboard.
• Their customer service and support has been great, 24hr a day chat.
• Ability to increase or decrease the list price of your domains or to show a discount. You can decrease or increase the price yourself by $200. If you want to lower more, you can contact support.
• End users can shortlist your domains before they make a decision on which they want to purchase. The number of shortlists is shown in you marketplace dashboard.
• When you submit your names you get to set the price you wish to get. Because their commissions are high I recommend listing at a higher price to offset the commission costs.
• Their landing pages are fairly basic but they work. Because the marketplace is fairly new, I'm sure we will see style improvements in the future.
• One thing I really like is they accept multiple extensions. I have listed .co and .io along with .com
• Each seller gets a direct link to their marketplace portfolio, HERES MY PORTFOLIO. It is handy if your trying to p[promote your portfolio through social media.
• I like that their marketplace doesn't have tens of thousands domain listings like BB. They are fairly strict on the domains they accept to list and so this helps keep the number of domains in the marketplace down and gets your listings more exposure.

CONS

• Their commissions are very high, depending on the domain name they are usually between 30% and 35%. However, there are no listing fees, no logo design fees, so in the end their commission is very similar to brand buckets.
• Their logos are not top quality, in fact I requested to have some of my logos remade.
• I think they have a big backlog of logos to design, the wait time for logo design has been around 1 week, but your names are still listed while the logos are being designed.
• After your names are accepted you need to agree to their commission rate, at this point you also need to apply your own keywords, descriptions etc. I found this was very time consuming.

 

[Future Sensors]

I can confirm that the NaN domain(s) matched message shows when pasting a list of domains in the portfolio search field.

Thanks @Optimal Names and @DN_Hunter

(I've submitted another ticket for this)

 

[Dane]

Hey guys,

If you feel like I do about the phrase "Make an Offer" and you too would prefer an option to say "Start up a Conversation" instead, please contact Atom to let them know. Below is the email I sent them for their Product Team. Feel free to copy, paste and send.

---------------------

To Atom:

Please share this with your Product Team:

Using the phrase “Make an Offer” sends the wrong message. It implies that the seller is completely open to discounting the BIN price, which lowers the value of the domain name.

I prefer saying something like “Start a Conversation” since it feels more open, more approachable... and helps to open a dialogue between buyer and seller. If someone is truly interested, they WILL make an offer -- but without the assumption that the seller is open to offering a discount.

Just to be clear, I’m not suggesting that you remove Make Offer completely. I’m simply asking for it to be an OPTION for sellers who would prefer it over Make an Offer.

Thanks for your consideration.

---------------------

 

[NameGroove]

Hey guys,

If you feel like I do about the phrase "Make an Offer" and you too would prefer an option to say "Start up a Conversation" instead, please contact Atom to let them know. Below is the email I sent them for their Product Team. Feel free to copy, paste and send.

---------------------

To Atom:

Please share this with your Product Team:

Using the phrase “Make an Offer” sends the wrong message. It implies that the seller is completely open to discounting the BIN price, which lowers the value of the domain name.

I prefer saying something like “Start a Conversation” since it feels more open, more approachable... and helps to open a dialogue between buyer and seller. If someone is truly interested, they WILL make an offer -- but without the assumption that the seller is open to offering a discount.

Just to be clear, I’m not suggesting that you remove Make Offer completely. I’m simply asking for it to be an OPTION for sellers who would prefer it over Make an Offer.

Thanks for your consideration.

---------------------

100%!!! This should be an industry standard
You identified the problem eloquently

 

[Future Sensors]

Atom.com advertisement within Microsoft Copilot.

 

[Future Sensors]

For part of my portfolio, I'm using the "Request Price" lander. Although I can still set a BIN price in my domain settings, it doesn’t appear on the visible lander, because the "Request Price" toggle is active, which is exactly what I want for those domains.

However, I've discovered that the BIN price is still exposed in the lander's HTML source, in two locations ("data-mp-domain-price"). This allows anyone to view the current BIN price, effectively bypassing the Request Price workflow. As a Seller, I need to trust that my hidden BIN values remain inaccessible to lander visitors.

Expected behavior:

Remove all data-mp-domain-price BIN references from the HTML source when a domain is set to "Request Price" lander. Ensure savvy buyers cannot discover the BIN price without submitting a request. Note that Sellers should retain the ability to set a (hidden) BIN price in their Dashboard.

Thank you @Atom.com

<div id ="without-logo-shortlist"
class="short-list"
data-mp-domain-name="Example.com"
data-mp-domain-price="25000"
data-mp-domain-id="1234567"
data-page-type=""
onclick="shortlistOrRemoveDomain(this)">
<div class="icon"></div>
<span class="shortlisted-count">77</span>
</div>

<div id ="with-logo-shortlist"
class="short-list"
data-mp-domain-name="Example.com"
data-mp-domain-price="25000"
data-mp-domain-id="1234567"
data-page-type=""
onclick="shortlistOrRemoveDomain(this)">
<div class="icon"></div>
<span class="shortlisted-count">77</span>
</div>

 

[Future Sensors]

Note that the issue also occurs with WLM landers, not just Atom.com.

Additionally, disable the "Price Tracking" feature on Request Price landers. It doesn't make any sense.

 

[Dane]

Additionally, disable the "Price Tracking" feature on Request Price landers. It doesn't make any sense.

It's the little things, right?

 

[NicTraders]

It's the little things, right?

Sometimes Often, I think Atom just needs to stop introducing new features for a little while, do a stocktake and fix all these little things to get things right before moving forward again.

 

[Future Sensors]

Remove all data-mp-domain-price BIN references from the HTML source when a domain is set to "Request Price" lander.

The same applies to Make Offer landers, where the BIN price is also exposed in the HTML source.

 

[NamesBond]

Additionally, pls don't display auto-generated discounts on MO and PR names on the Premium/Standard domain view lists (Listing a "sale" amount on "make offer" and "price request" domains, where there is no base price to begin with and no modifications on the landing pages, makes no sense to me! )

 

[ran_doank]

Did you know that Atom now has a Whois tool? Regardless of whether the atom listing price is hidden on the domain landing page (e.g., price request), it will still be displayed on the Whois result.

 

[Future Sensors]

Did you know that Atom now has a Whois tool? Regardless of whether the atom listing price is hidden on the domain landing page (e.g., price request), it will still be displayed on the Whois result.

Good catch @ran_doank. Atom should not show the BIN price there for MO or PR landers. I will add this to the current ticket.

 

[Future Sensors]

On Atom's Appraisal page, the BIN price is already properly hidden for domains with MO or PR configured.

 

[King]

Submitting an appeal says

Months later is not "shortly"

Have one pending review since April.

 

[Dane]

Submitting an appeal says

Show attachment 278991

Months later is not "shortly"

Have one pending review since April.

Well, at least they spelled the word "received" correctly. Oh, wait...

 

[Optimal Names]

Submitting an appeal says

Show attachment 278991

Months later is not "shortly"

Have one pending review since April.

I had one waiting since mid-May and finally cancelled it.

 

[Future Sensors]

For part of my portfolio, I'm using the "Request Price" lander. Although I can still set a BIN price in my domain settings, it doesn’t appear on the visible lander, because the "Request Price" toggle is active, which is exactly what I want for those domains.

However, I've discovered that the BIN price is still exposed in the lander's HTML source, in two locations ("data-mp-domain-price"). This allows anyone to view the current BIN price, effectively bypassing the Request Price workflow. As a Seller, I need to trust that my hidden BIN values remain inaccessible to lander visitors.

Expected behavior:

Remove all data-mp-domain-price BIN references from the HTML source when a domain is set to "Request Price" lander. Ensure savvy buyers cannot discover the BIN price without submitting a request. Note that Sellers should retain the ability to set a (hidden) BIN price in their Dashboard.

Thank you @Atom.com


Show attachment 278899

<div id ="without-logo-shortlist"
class="short-list"
data-mp-domain-name="Example.com"
data-mp-domain-price="25000"
data-mp-domain-id="1234567"
data-page-type=""
onclick="shortlistOrRemoveDomain(this)">
<div class="icon"></div>
<span class="shortlisted-count">77</span>
</div>

<div id ="with-logo-shortlist"
class="short-list"
data-mp-domain-name="Example.com"
data-mp-domain-price="25000"
data-mp-domain-id="1234567"
data-page-type=""
onclick="shortlistOrRemoveDomain(this)">
<div class="icon"></div>
<span class="shortlisted-count">77</span>
</div>

Fellow investors -

I've just heard back from @Atom.com, and they've confirmed that all mentioned issues have been resolved.

The HTML source of "Make Offer" (MO) and "Request Price" (PR) landers no longer expose the BIN price that is set for the domain. Instead, it now says in the HTML source:

data-mp-domain-price="Price Request"

and:

data-mp-domain-price="Make Offer"

Also, on Atom's Whois page, when searching for a domain with MO or PR enabled, the BIN is no longer visible.

Finally, on MO/PR landers, the Price Tracking feature has been removed. It didn't make sense.

You may need to clear the page cache for the changes to take effect. Otherwise the changes will be automatically applied across all pages in the next 2-3 days.

 

[draco]

Fellow investors -

I've just heard back from @Atom.com, and they've confirmed that all mentioned issues have been resolved.

Finally, on MO/PR landers, the Price Tracking feature has been removed. It didn't make sense.

You may need to clear the page cache for the changes to take effect. Otherwise the changes will be automatically applied across all pages in the next 2-3 days.

Wouldn't it be a good idea to keep the Price Tracking feature on MO/PR landers? That way it will be available and you'll have potential buyers queued up if a Seller switches from MO/PR to a fixed price.

 

[Dane]

Wouldn't it be a good idea to keep the Price Tracking feature on MO/PR landers? That way it will be available and you'll have potential buyers queued up if a Seller switches from MO/PR to a fixed price.

Maybe it would be better if Price Tracking was changed to "Get updates on this domain" (or something similar). That would still cover price updates.

 

[Future Sensors]

Wouldn't it be a good idea to keep the Price Tracking feature on MO/PR landers? That way it will be available and you'll have potential buyers queued up if a Seller switches from MO/PR to a fixed price.

You'd have to explain all that on the lander, which would be incredibly confusing. The page already contains a huge number of elements.

Moreover, you'd prefer visitors to actively request a price or make an offer. That way, you'd at least be able to connect with potential buyers.