WEBVTT 00:00:00.000 --> 00:00:06.640 Namegarage Weekly uses AI voices, with a script based on our published posts and reviewed before publication. 00:00:06.640 --> 00:00:13.120 Welcome to the first episode of Namegarage Weekly. This is a show about finding a name for what you're 00:00:13.360 --> 00:00:17.040 building, and about the work behind Namegarage itself. 00:00:17.040 --> 00:00:23.520 So, two ways into the same story. You might be looking for a domain. Or you might be curious about how a small 00:00:23.680 --> 00:00:27.920 business builds the software around its own very real problems. 00:00:27.920 --> 00:00:34.560 Ideally, both. We'll talk about what changed for buyers, the decisions behind those changes, and a few 00:00:34.640 --> 00:00:41.200 names worth a look. We'll also keep an eye on the Dutch auctions, where prices move down in scheduled steps. 00:00:41.200 --> 00:00:46.880 But before we do the weekly update, we should give people a way into the story. What has actually been built so 00:00:46.960 --> 00:00:47.840 far? 00:00:47.840 --> 00:00:54.400 Start with the catalog. Namegarage brings thousands of domains into one place, with search and filters to help 00:00:54.480 --> 00:01:00.400 you narrow the field. Each name has a page of its own, with a price where one is listed and ways to take the 00:01:00.480 --> 00:01:01.600 conversation further. 00:01:01.600 --> 00:01:07.040 Which sounds obvious until you've tried shopping for a name and found yourself wondering whether it's for sale, 00:01:07.080 --> 00:01:11.400 who to contact, or whether the number on the page means anything at all. 00:01:11.400 --> 00:01:18.000 The pages also offer naming ideas and, for some names, a concept logo. Those give you something to react 00:01:18.080 --> 00:01:24.400 to. You can imagine a product instead of looking at a string of letters and hoping inspiration arrives. 00:01:24.400 --> 00:01:30.960 Although you're still buying a domain. A suggested use isn't a ready-made business. I like those ideas best as a 00:01:31.040 --> 00:01:34.400 prompt: does this sound like what I'm trying to build? 00:01:34.400 --> 00:01:40.800 Then there's the price. The pricing process draws on several outside appraisal signals, rather than relying on a 00:01:40.960 --> 00:01:46.480 single estimate. It blends those signals and reduces the influence of extreme results. 00:01:47.000 --> 00:01:53.800 And a price still has to meet a buyer. A careful calculation doesn't turn a domain into a guaranteed investment. 00:01:53.840 --> 00:01:58.200 What it gives the seller is a more consistent way to price a large portfolio. 00:01:58.200 --> 00:02:04.280 For a builder, that distinction is interesting. Software can make a decision repeatable and easier to 00:02:04.760 --> 00:02:07.640 explain. It can't remove all the judgment from it. 00:02:07.640 --> 00:02:14.413 The purchase side has grown too. There's listed-price checkout through Escrow.com, offers and counteroffers, 00:02:14.467 --> 00:02:20.280 and payment plans on eligible names. Monthly card payments through Stripe are another part of that system. 00:02:20.280 --> 00:02:25.560 So if someone likes a name but doesn't want to pay the full amount at once, they can look at the available 00:02:25.640 --> 00:02:30.600 schedule. And if the price isn't right, they can make an offer rather than disappearing. 00:02:30.600 --> 00:02:37.080 With an important difference between payment routes. Escrow.com holds funds under its transaction process. A 00:02:37.280 --> 00:02:43.160 direct card payment plan is an agreement with the seller, with ownership transferring after it's fully paid. The 00:02:43.240 --> 00:02:46.240 site explains the route and terms before you commit. 00:02:46.240 --> 00:02:51.960 There's also been work on the conversation around a purchase. Making a counteroffer, seeing the payment plan 00:02:52.160 --> 00:02:57.520 alongside the price, and keeping the agreed terms clear as the discussion moves back and forth. 00:02:57.520 --> 00:03:03.720 Because a number on its own can hide quite a lot. The same price paid today and spread over a plan are different 00:03:03.800 --> 00:03:07.920 proposals. The software needs to keep that context attached. 00:03:07.920 --> 00:03:14.360 And the catalog has to be pleasant to use before anyone reaches checkout. You can share a filtered view, return 00:03:14.440 --> 00:03:18.960 to it, or browse the plain catalog when interactive controls aren't available. 00:03:18.960 --> 00:03:24.760 That's a recurring theme in the build: make the common task work without asking visitors to understand the whole 00:03:25.200 --> 00:03:30.440 system. Search for a name. Read about it. Compare the options. Keep your place. 00:03:30.560 --> 00:03:36.720 The blog follows those changes as they happen. This podcast will connect them, so you can hear what the week 00:03:36.800 --> 00:03:40.240 adds up to without having to read every release note. 00:03:40.240 --> 00:03:46.560 Including the rough edges and the trade-offs. If an update makes something easier, we'll ask what changed. If a 00:03:46.640 --> 00:03:49.720 result is still uncertain, we can say that too. 00:03:49.720 --> 00:03:54.880 That's the show. For this launch, we're looking at the updates published from October twelfth through 00:03:55.000 --> 00:04:01.440 eighteenth, twenty twenty-six. Let's start just after checkout, when a buyer has chosen a domain and wants to 00:04:01.520 --> 00:04:02.560 get on with using it. 00:04:03.010 --> 00:04:09.170 Say I'm buying through a monthly card payment plan. A payment receipt tells me money went out. It doesn't 00:04:09.383 --> 00:04:12.770 necessarily tell me everything I want to know about the domain. 00:04:12.770 --> 00:04:19.410 Right. How much is left? When does the plan finish? Where do I go to manage it? Namegarage's new My 00:04:19.490 --> 00:04:24.610 Lease link brings its Stripe lease buyers into Namewrench, where those details live together. 00:04:24.610 --> 00:04:28.290 So I can stop treating my inbox like an account dashboard. 00:04:28.290 --> 00:04:34.290 That's the useful change. You sign in through your checkout email, then see the payments, remaining balance, and 00:04:34.370 --> 00:04:37.490 lease end. There isn't another password to remember. 00:04:37.490 --> 00:04:40.370 And can I use the domain while I'm paying for it? 00:04:40.370 --> 00:04:46.370 For supported GoDaddy domains, the portal lets eligible buyers manage the nameservers—the settings that point 00:04:46.450 --> 00:04:52.250 the name toward their website or email provider. Some changes still need help, but routine management has a 00:04:52.290 --> 00:04:53.410 clearer home. 00:04:53.410 --> 00:04:59.330 Nameservers are one of those words that can make a perfectly ordinary task sound like an exam. 00:04:59.330 --> 00:05:05.250 Think of the practical question: “Where should this name send people?” The portal helps with that part. If the 00:05:05.370 --> 00:05:10.450 setup is more complicated, there's a contact route rather than a promise that every possible change is 00:05:10.570 --> 00:05:11.570 self-service. 00:05:11.570 --> 00:05:16.730 That's a useful boundary. A simple screen doesn't mean the thing behind it is simple. 00:05:16.730 --> 00:05:22.370 Especially when a change could affect a website or email. The screen needs to make the common task easier 00:05:22.450 --> 00:05:24.530 without hiding the consequences. 00:05:24.530 --> 00:05:31.170 There's a building lesson there already. A purchase flow doesn't end when payment succeeds. Someone still has to 00:05:31.250 --> 00:05:32.730 live with what they bought. 00:05:32.730 --> 00:05:38.130 And the better that experience is, the less the buyer has to learn about the machinery just to get on with their 00:05:38.530 --> 00:05:38.930 work. 00:05:39.380 --> 00:05:46.020 Now let's rewind. I haven't bought anything yet. I've found a few names, and I'm doing that thing where I keep 00:05:46.220 --> 00:05:49.620 opening the same tabs to see whether the price has changed. 00:05:49.620 --> 00:05:56.100 You can give those tabs a break. Namegarage now offers a weekly selection based on your interests, or updates 00:05:56.180 --> 00:05:58.460 for a particular domain you're following. 00:05:58.460 --> 00:06:04.020 Those are two different shopping moods. “Show me some ideas” and “Tell me about this one.” 00:06:04.020 --> 00:06:10.340 Yes. A category, an extension, a budget—those help when you're exploring. Following a single 00:06:10.500 --> 00:06:12.900 name makes more sense once you have a shortlist. 00:06:12.900 --> 00:06:19.020 And then the email arrives. The important question is whether I can understand it at a glance. 00:06:19.020 --> 00:06:25.620 That's another update this week. Each domain gets its own card, with the price, discount information, deadline, 00:06:25.700 --> 00:06:30.260 and purchase link kept together. Offer replies also make the next action clearer. 00:06:30.260 --> 00:06:36.420 It sounds like a layout change, but pairing the right button with the right price is doing real work. 00:06:36.420 --> 00:06:42.180 Imagine comparing several names on a phone. If the deadline is floating somewhere else in the message, you have 00:06:42.260 --> 00:06:48.420 to work out what belongs to what. Keeping those details together removes a small, avoidable puzzle. 00:06:48.420 --> 00:06:54.660 There's a second piece to that: the weekly Platinum and Gold discounts now start and finish at their scheduled 00:06:54.740 --> 00:06:55.300 times. 00:06:55.300 --> 00:07:01.540 With the regular price returning when the offer ends. So the offer has a clear window, and the email points you 00:07:01.620 --> 00:07:03.900 back to the listing for the current position. 00:07:03.900 --> 00:07:10.180 Which is also our rule for this show. We'll date the prices once, put the links in the notes, and let listeners 00:07:10.260 --> 00:07:11.860 check the listing when they're ready. 00:07:13.430 --> 00:07:19.270 Before we get to the names, there's something a price card can't answer. Why should someone feel comfortable 00:07:19.350 --> 00:07:20.470 buying here? 00:07:20.470 --> 00:07:26.230 That's where the new Trust center comes in. It gathers the purchase process, payment options, transfer 00:07:26.310 --> 00:07:30.790 information, contact details, and website checks in one place. 00:07:30.790 --> 00:07:36.630 Useful because a buyer can have several questions that all sound like “Is this safe?” They might mean the 00:07:36.910 --> 00:07:40.310 website, the payment, or what happens to the domain afterward. 00:07:40.310 --> 00:07:44.550 And one impressive-looking security score can't answer all three. 00:07:44.550 --> 00:07:51.110 Exactly. A website check can tell you something about the website. It doesn't guarantee the transaction. The 00:07:51.230 --> 00:07:55.750 Trust center keeps those distinctions visible and explains the different payment routes. 00:07:55.750 --> 00:08:01.670 For anyone building a product, I think that's the interesting part: give people enough information to judge the 00:08:01.750 --> 00:08:06.550 process, rather than asking one badge to do all the reassuring. 00:08:06.550 --> 00:08:12.470 Also, leave the awkward information in. The performance reporting includes areas that still need work. 00:08:12.590 --> 00:08:17.150 You've improved the site. Why doesn't every score immediately look better? 00:08:17.150 --> 00:08:23.150 Because a test run today and a report covering weeks of real visits are looking at different things. A new 00:08:23.390 --> 00:08:26.750 release doesn't change the experience someone had last Tuesday. 00:08:26.750 --> 00:08:29.310 So what actually changed this week? 00:08:29.310 --> 00:08:35.710 Smaller page styles, less unnecessary work when domain pages load, and fewer stops on the way from typing a 00:08:35.990 --> 00:08:42.590 domain to reaching its listing. The homepage also gives visible content priority over loading the whole catalog. 00:08:42.590 --> 00:08:48.350 A buyer wants something useful on screen. They don't need to wait for every possible search result before they 00:08:48.430 --> 00:08:49.590 can start looking. 00:08:49.590 --> 00:08:55.710 That's the idea. Remove work that isn't needed yet. But there's one piece you still need: checking whether a 00:08:55.830 --> 00:08:57.390 name is available. 00:08:57.390 --> 00:09:01.710 Otherwise you've made it quicker to reach a Buy button for something you can't buy. 00:09:01.710 --> 00:09:07.390 A very efficient disappointment. The published update says those availability checks are preserved. 00:09:07.510 --> 00:09:13.590 That's the trade-off worth discussing. Which work can disappear, and which decision still has to be 00:09:13.670 --> 00:09:14.390 right? 00:09:14.390 --> 00:09:20.710 It applies beyond domain shopping. A page can load quickly and still be wrong. Performance work needs to 00:09:20.910 --> 00:09:24.910 consider what the page is promising, as well as how soon it appears. 00:09:24.910 --> 00:09:31.270 And then measure what real visitors experience after the change, rather than calling the job finished because 00:09:31.430 --> 00:09:32.950 one test looks good. 00:09:32.950 --> 00:09:38.350 The week also brought comments and audio across the blog. People can leave a comment without creating an 00:09:38.390 --> 00:09:41.030 account, and listen to posts that have a recording. 00:09:41.030 --> 00:09:47.110 That feels connected to the rest of the week: fewer obstacles between someone and the thing they came to do. 00:09:47.110 --> 00:09:53.350 With some care around the edges. Comments are reviewed before appearing. Audio is optional. And the Dev blog 00:09:53.430 --> 00:09:56.790 gives people who want the engineering discussion a place to follow it. 00:09:56.790 --> 00:10:03.350 Which is where the detailed explanations belong. Here, we can pull out the decision and why it matters; the 00:10:03.430 --> 00:10:05.270 notes can take listeners deeper. 00:10:06.040 --> 00:10:12.280 Let's use that same approach for the names. We checked these prices on October nineteenth. The listings in the 00:10:12.360 --> 00:10:18.200 notes have the current terms and availability. The weekly Platinum and Gold offers close Saturday, October 00:10:18.280 --> 00:10:21.080 twenty-fourth, at six in the evening Pacific. 00:10:21.080 --> 00:10:27.640 Four picks: two Platinum, two Gold. And an interesting choice between names that suggest a category and 00:10:27.720 --> 00:10:29.320 names you can give your own meaning. 00:10:29.320 --> 00:10:36.040 First, Normo dot com. Platinum, at twenty-seven thousand nine hundred forty dollars at that check. 00:10:36.120 --> 00:10:37.640 What does it suggest to you? 00:10:37.640 --> 00:10:44.200 Norms, standards, things being consistent. My naming idea would be software that helps teams organize a 00:10:44.720 --> 00:10:48.920 process. It's short enough to leave room for a business to define it more broadly, though. 00:10:48.920 --> 00:10:54.840 Compare that with SocialHost dot com, the other Platinum pick, at seventeen thousand nine hundred thirty 00:10:54.920 --> 00:10:58.920 dollars. You get a stronger hint about the category straight away. 00:10:58.920 --> 00:11:05.240 Hosting a community, perhaps, or infrastructure for a social product. That clarity can help if it's the business 00:11:05.280 --> 00:11:09.080 you want to build. It also gives the name a more specific direction. 00:11:09.080 --> 00:11:15.640 So the useful question isn't just “Which name sounds nicer?” It's “How much should the name explain before I've 00:11:15.720 --> 00:11:17.080 said anything else?” 00:11:17.080 --> 00:11:23.080 OnSEO dot com makes that question pretty easy. It's a Gold name at eight thousand six hundred thirty dollars at 00:11:23.160 --> 00:11:26.440 that check, and search marketing is right there in the name. 00:11:26.440 --> 00:11:32.840 An agency or tool in that area wouldn't have to spend much time explaining the subject. Monfy dot com goes the 00:11:32.920 --> 00:11:36.600 other way: another Gold pick, at six thousand dollars. 00:11:36.600 --> 00:11:42.920 Short and more open-ended. It makes me think of money, but that's a naming association, not an existing business 00:11:42.960 --> 00:11:44.120 we're describing. 00:11:44.240 --> 00:11:50.560 If you're making a shortlist, try saying each name in a sentence about your product. Do you like what it makes 00:11:50.600 --> 00:11:54.400 you explain? Does it still fit if the product changes? 00:11:54.400 --> 00:11:59.600 Those questions won't pick a name for you, but they give you something more useful than staring at a list of 00:11:59.680 --> 00:12:04.560 prices. The regular prices, discounts, and offer windows are in the notes. 00:12:05.010 --> 00:12:11.330 The Dutch auctions add a different question: buy at today's price, or wait for the next drop? 00:12:11.330 --> 00:12:17.650 The price falls in scheduled steps while the name is still available. Waiting can save you money. It also gives 00:12:17.810 --> 00:12:19.730 someone else time to buy it first. 00:12:19.730 --> 00:12:26.130 Elastic-Fabric dot com is seven hundred forty-five dollars at our check, with five hundred ninety-five as its 00:12:26.210 --> 00:12:27.650 next listed step. 00:12:27.650 --> 00:12:33.570 VerifySignature dot com is one thousand four hundred ninety-five, with one thousand one hundred ninety-five 00:12:33.730 --> 00:12:39.010 next. That one's quite direct if your project involves document or signature verification. 00:12:39.010 --> 00:12:45.490 And Komposable, with a K, dot com is two thousand six hundred ninety-five, with two thousand 00:12:45.570 --> 00:12:50.770 ninety-five next. I can see why a modular software project might look at that one. 00:12:50.770 --> 00:12:56.530 Those are naming ideas, of course. The decision is still whether the words fit your project, and whether you're 00:12:56.610 --> 00:12:58.210 comfortable with the price now. 00:12:58.210 --> 00:13:04.930 The next listed step for all three is Saturday, October twenty-fourth, at six in the evening Pacific. We've put 00:13:05.010 --> 00:13:07.930 the schedules and minimum prices in the notes, too. 00:13:07.930 --> 00:13:14.570 A displayed minimum is a possible later price, not a reservation. If one of these is the name you really want, 00:13:14.610 --> 00:13:19.250 the trade-off is the saving you're waiting for against the chance that it won't still be there. 00:13:19.250 --> 00:13:22.050 A little harder than watching a number count down. 00:13:22.500 --> 00:13:28.580 What I like about this week's updates is that they follow the buyer beyond the first impression. Finding a deal, 00:13:28.700 --> 00:13:34.340 understanding an email, checking the purchase process, then managing the domain afterward. 00:13:34.340 --> 00:13:40.580 And the engineering discussion gets more interesting when we ask what each change does for that person. Less 00:13:40.660 --> 00:13:45.940 waiting. Fewer unclear steps. A better answer to “What happens next?” 00:13:45.940 --> 00:13:49.140 With room for people to ask questions back through the blog. 00:13:49.140 --> 00:13:55.860 The episode notes link to the stories behind the build, this week's seven posts, and all the names we mentioned. 00:13:56.180 --> 00:14:01.620 This has been the first Namegarage Weekly. We'll be back with another look at what's changed. Thanks for 00:14:01.700 --> 00:14:02.340 listening.