
Every morning, GoDaddy publishes thousands of expiring domain names. Somewhere in that spreadsheet are names worth buying, but finding them before the auctions end is another story.
After scrolling through thousands of names, I often found myself relying more on instinct than analysis.
So I built Tactical Names to do the heavy lifting: filter the noise, surface the best candidates, and help me decide what to ignore, buy to resell, or build a business around.
- Role
- Product designer, builder and first customer
- Timeline
- August - October 2026
- Models
- Claude (development and research)
- Status
- Live and charging $39/mo and $129/mo (with a 7-day trial)
01 / ORIGIN
Turning domain-buying instincts into a repeatable process
I’d spent years developing my own rules for evaluating domain names. Shorter is generally better. Real words beat invented ones. And a good name should be easy to say and spell.
But when GoDaddy’s daily list arrived with thousands of expiring domains, applying those rules consistently was another matter.
After scanning enough names, I’d start relying on instinct. And a promising name at $500 could be a terrible investment at $15,000.
I wanted something that could help me make better buying decisions, not just find interesting names.
02 / EXPERIENCE
Turning thousands of names into a few good decisions
I didn’t need a language model to evaluate every domain. Most of the initial filtering could be done faster and more cheaply with conventional scoring.
So I divided the work. A scoring engine processes the daily file in about fifteen seconds, and only the top three hundred candidates go through AI for deeper analysis.
Each receives a recommendation to ignore, flip, or build, along with an explanation and pricing guidance when the data supports it.
The experience is designed to help me spot interesting names quickly, then understand why they’re worth considering.
03 / DECISIONS
Knowing when to start over
After two months of iteration, Tactical Names worked, but it had become increasingly complicated.
I experimented with two conversation-first versions. Neither felt right. They looked generic, and I was adding features without necessarily improving the experience.
Rather than keep refining something I wasn’t happy with, I started over.
I preserved the original code, opened a fresh database, and rebuilt the product around a simpler brief.
Two nights later, I had a much cleaner experience. Those two months of learning helped me recognize what belonged in the product and what didn’t.
Tactical Names is live, with paid subscriptions, a daily analysis pipeline, and a trial designed to demonstrate its value.
My biggest challenge now is distribution. I’ve built something that solves a problem I know firsthand. Now I’m working on reaching others who face the same problem.
Ultimately, success isn’t just having a working product. It’s helping people make better buying decisions.
From idea to production, with AI as a collaborator.

Discover
Understand the problem
Step 1: Frame the idea
Problem, audience, desired outcome
Step 2: Explore together
Questions, alternatives, tradeoffs
Step 3: Validate assumptions
Research, feasibility, evidence (AI research - I decide)
Define
Set the direction
Step 4: Define the product
Requirements and success criteria
Step 5: Plan the work
Milestones, tasks, acceptance tests. AI drafts
Step 6: Approve the plan
I revise scope before work begins. My approval.
Deliver
Build, verify, release
Step 7: Build + review loop
Implement, agent audit, fix, recheck (AI and agents)
Step 8: Connect + test
Services, env setup, staging QA
Step 9: Ship + learn
I approve release; we iterate. My approval
I use AI throughout the product development process, from exploring an idea and challenging assumptions to defining requirements, building, and reviewing the implementation.
But I don’t want a model that simply agrees with me. I expect it to question decisions, identify tradeoffs, and provide evidence that the work actually functions.
I review the plan, direct the experience, and use independent agents to help verify the implementation. Before release, I test the product and make the final call.
AI makes it possible to move much faster. My responsibility is making sure we’re moving in the right direction.

