Existing name, clearer expression
Preserve the name, useful colors, domain, customer language, and anything people already recognize. Rework only what is holding the business back.
A patient business workshop
Bring the rough beginning. We’ll develop the useful parts together.
No account. No card. Nothing goes online. Your private concept is built in this browser.
A workshop, not a slot machine
A fast generator gives you one answer and asks for a card. We want to show our work: several directions, honest tradeoffs, names with reasons, brand combinations, page structures, and revisions you can react to.
You make the taste decisions. We keep turning those decisions into something more complete.
Six chapters · one considered result
Both paths arrive at the same place. The questions and options along the way change to fit how you began.
Find the useful truth: what you know, what exists already, who this is for, and what should change for them.
Develop distinct business directions or sharpen your offer. Compare them, borrow pieces, and combine what works.
Keep an established name, carefully rethink it, or explore new naming territories with rationale—not random word soup.
Mix visual mood, voice, palette, and density. See every choice land in a living preview as you make it.
Choose the story, pages, calls to action, and proof. Refine the private build until the whole experience feels right.
Only now do we discuss the domain, managed hosting, safe ongoing editing, and the one monthly price.
New thought or existing company
A company with customers, a name, or an old website needs a different conversation from a brand-new idea. The workshop asks which situation is yours and adapts.
Preserve the name, useful colors, domain, customer language, and anything people already recognize. Rework only what is holding the business back.
Compare “keep,” “evolve,” and “rename” directions side by side. Name and domain checks inform the choice, but they are never presented as legal clearance.
Build naming territories from the audience, promise, place, personality, and words you care about—then edit or combine them yourself.
Develop, compare, combine
A direction is a starting point, not a verdict. Borrow the warmth from one, the clarity from another, and the structure from a third. The preview follows your choices.
Clear decisions, useful plans, and a home that finally works the way you do.
After you approve the private design
One available standard domain registration and renewal while subscribed, or connection of a domain you already own. Premium and aftermarket names are outside the plan.
HTTPS, deployment, monitoring, backups, and routine infrastructure care. You should not have to become a server administrator.
The approved pages, responsive presentation, essential forms, and content—built as a real site, not trapped in a screenshot.
A Claude-powered website editor scoped to structured pages, copy, styles, images, and forms for your site—controlled in plain language.
A useful boundary is a feature
The in-app Claude-powered editor is intended to operate only through structured website controls. It is not a shell, a code repository, or an administrative console.
Domain, DNS, billing, account, and hosting requests use a separate verified support path. They are never website-editor commands.
Price comes last
Explore, name, design, preview, and revise privately without paying. If you decide the finished direction deserves a real home, publishing is one plan.
Prototype boundary: this V2 workshop currently stops at a private concept. It does not take payment, register a domain, or publish anything.
Starts only when you approve publishing.
Plain answers
No. “I’ve got nothing” begins with your interests, preferred pace, people you understand, work preferences, and useful clues already around you. It develops several directions so you can choose and combine—not accept a random idea.
The idea path asks what already exists. Keep the current name and brand equity, explore a careful evolution, or rethink them. If you already own a domain, it can be connected without placing DNS controls inside the editor.
No. Early names are creative directions. Before publication, domain availability and obvious conflicts should be checked again. That research is useful, but it is not trademark or legal clearance.
Only after you approve the private website for publication and explicitly confirm the plan. The current V2 workshop is a non-charging prototype, so it cannot begin a subscription.
No. The proposed in-app Claude-powered editor is limited to structured controls for your website. It has no shell or repository access. Domain registration, DNS, billing, account access, hosting settings, and other projects are outside its permissions.
Premium or aftermarket domains, paid third-party services, custom commerce systems, and major application development would need a separate, explicit scope. Nothing should be added or charged without your approval.
No polished pitch required
Both are enough to begin.