How to sell a website to a business that already has one.

Why you are not selling them a website

You are not selling them a website because they can already type a URL and see a page. The meeting you want is about a gap on that page a stranger can reproduce. Booking, SSL, a service they perform that is missing, a city they serve that has no page, a collect path that is not there.

Selling a website to a shop that has one is how marketers get the we already have a guy speech. The speech is correct. They do have a guy. The guy shipped something. Your job is not to erase that fact. Your job is to show the path that still fails.

The buyer of this guide is the marketer. The owner is tired of vendors who open with your brand deserves. Deserve is not a finding. A finding is: I booked as a new customer on your site Tuesday and there is no path off the homepage except a phone number.

In Nerxus One, Radar names that gap and stamps a fulfillment action. Forge opens the website tool because the action said so, not because you felt like making a site. If you work outside the product, write the gap in a sentence before you open the builder. If you cannot write the sentence, you are about to sell a redesign. Redesigns are long and taste-heavy. Gaps are short.

Lovable and other builders win when the client already exists and you only need pixels. Use them when that is the job. This page is for the job that starts before they are a client, when the DEMO has to justify the email.

If you only remember one sentence from this guide, remember the gap sentence. I opened this URL on this date and this path failed. Everything else in the week is a DEMO and a FEE hung on that sentence. Lose the sentence and you are back to selling websites.

How to name the gap on their live URL

Name the gap as a path a stranger takes, with the URL and the date. I opened your site from the Maps listing, clicked Services, and there is no way to book a cleaning. That is a name. The site feels dated is not a name.

Walk the path on a phone. Most local traffic does. If the desktop site works and the phone number is a tiny footer, the gap is the phone path. If the phone path works and the listing still has no site field, the gap might be the listing, not the page. Sell the surface the customer used.

Write down what still works. Hours, address, a menu, a real photo of the front door. You will need those sentences in the meeting so you do not sound like you want to burn their money. People listen longer when you can see the parts that are fine.

If you model a dollar around the gap, label it modeled and keep the assumption next to it. Missed bookings need their volume. You can say the path is missing. You cannot say they lose a number you guessed. DEV stays off the invoice. FEE is the rebuild or the page.

Two sources that disagree should stay visible. The listing says they do implants. The site never mentions implants. That disagreement is a service-gap, and it is a better pitch than a new color palette. Do not smooth it into a vague SEO issue.

What to do when they already paid someone last year

When they already paid someone last year, you compliment the parts that work and you keep the last vendor’s name out of your mouth unless they bring it up. Insulting the last invoice makes the owner defend it. Defending it is the opposite of clicking your DEMO.

Ask what the last project was supposed to do. Often the answer is we needed to be on Google. That project can succeed as a site and still fail as a booking path. You are not claiming the last project failed. You are claiming a path is still missing.

If the last vendor is still on a retainer for posts, stay out of the posts. Sell the page. Scope fights are how two vendors burn a client and then both get fired. Your SOW should say what you will not touch.

If the last vendor owns the host login and will not share it, your DEMO still matters. Deploy may mean a new host, a cutover, and a weekend. Say that early. A preview that cannot go live without a hostage situation is still worth sending, as long as the email does not pretend deploy is a button you already have.

Do not offer to sue, shame, or replace them as a personality. Offer a page. If they want you to take over the whole site later, that is client-two energy inside the same account. Steward can hold leftover findings. Your first FEE should still match the first gap.

How to put a DEMO next to their live URL

Put the live URL and the DEMO URL in the same email and in the same browser window on the call. Left side current. Right side preview. Talk only about the gap you named. If you start restyling the logo, you have switched to taste, and taste is their cousin’s job.

The DEMO should reuse public facts: name, city, services, phone, hours. It should not reuse a photo you do not have rights to move. Public on their site is not the same as licensed for your host. For a preview, a simple page with their words and a stock-free layout is enough. For deploy, ask.

Make the fix obvious. If the finding was no booking, the book button is above the fold. If the finding was no SSL, do not build a new brand world. Get HTTPS working or show the same page on a secure host. If the finding was a missing service, that service is the page. Extra sections are how a two-hour DEMO becomes a week.

Label the preview. Draft preview. Not live. That label is part of the pitch. Owners relax when they see you are not claiming you already shipped to their domain. DEPLOY stays gated in this product for the same reason. Copy the habit.

If your DEMO is slower, uglier, or missing a menu they love, say so. Honesty about what you did not rebuild is how the gap stays the hero. A prettier-but-empty clone is a redesign pitch again.

When to sell a page instead of a rebuild

Sell a page when the rest of the site already does the job and one path is missing. A city-service page, a booking landing page, a collect page, a financing FAQ, a storm-damage page after a permit wave. Pages close faster than rebuilds and they are easier to DEMO.

Sell a rebuild when the site is the leak: mixed NAP, no HTTPS, a builder the owner cannot log into, a five-page brochure that 404s on three of them, or a mobile layout that hides the phone. Rebuilds need a longer SOW and a longer DEMO. They are still gap-led if you can point at those failures.

Do not sell a rebuild because you want a retainer that looks like a platform. Wanting a platform is your problem. Their problem is the path. If you need the retainer, sell month-two work after the page is live: Muse drafts they approve, Echo replies they approve, Watchtower on the listing.

Web studios fail when they build the rebuild first and hunt the client second. This guide flips that. Finding, preview, letter, then the build that can survive a no. The no should cost you a DEMO, not a month.

If they ask for the rebuild on the call, write the page as phase one on the invoice anyway. Phase two can be the rest. First clients expand. Invoices that expand before deploy are how you work unpaid.

How to talk about booking, SSL, and service pages on a site that exists

Talk about booking as a path, SSL as a browser warning, and service pages as words they already use elsewhere. Three different findings. Three different DEMOS. Do not mash them into digital presence in the first email.

Booking: open the site as a new customer. Count the taps to a confirmed slot. If you never get there, you have the finding. The DEMO is the missing taps. Chair-Hour Loss language is for the memo, with assumptions, not for the subject line.

SSL: open the URL from the listing. If the browser warns, screenshot the warning with the date. The DEMO can be the same content on HTTPS. Do not add a lecture about nation-state attackers. The padlock is enough.

Service pages: compare the listing, the Facebook about, the truck, and the site nav. The missing noun is the page. Answer-first copy on that page is also what an assistant can cite later. You can mention AI-search as a second sentence if you have a probe. Without a probe, stay on the missing noun.

If all three are true, pick the one you can fulfill this week. The others park. A site-that-exists pitch with three headlines is a scan that learned CSS.

What DEMO versus DEPLOY means in the pitch

DEMO means they can click a preview you host. DEPLOY means their domain, their DNS, their analytics, their booking vendor, their approval. Say both words in the meeting so the owner knows the preview is not a hijack.

In this product, deploy is approval-gated. You should copy that even in a freelance stack. Do not push to their host because they said looks good on a text. Looks good is not an approval to cut over DNS.

List the deploy chores in the SOW. Domain access, redirects from old URLs, the book button’s real destination, form destinations, a privacy draft if you added forms, who owns the photos. Chores are unglamorous and they are why rebuilds slip.

Keep a rollback sentence. If we cut over and the book button fails, we point the domain back and fix the preview. Owners have been burned by agencies who disappear into a new theme. A rollback sentence is more adult than a launch party.

Do not call the DEMO a free website. It is a sample. If they take the sample and walk, that is the cost of this motion. If you cannot afford that cost, hunt fewer rows and make fewer previews. Do not claw the sample back with legal theater in the footer.

How to price the work without a fake ROI slide

Price a FEE for the page or the rebuild you will finish, plus a clear optional month-two retainer. Do not price a revenue lift. You do not have their books. Diagnostic dollars in this product are modeled. Health later is Healthy, Watch, or At-risk. Copy both habits in the pitch.

If they ask what it is worth, walk the path again. Customers who hit the listing cannot book. You built the book path. That is the value. A multiplier from a thread is not a source. If you have no source, you have no percentage.

Separate DEV and FEE if you show a memo. DEV is modeled monthly recovery. FEE is your invoice. Forecasts that add them are how marketers lie to themselves about pipeline. The owner does not care about your forecast. They care that the invoice matches the page.

Say what happens if the last vendor still owns the host. Extra hours for a cutover should be a line, not a surprise. Surprises on deploy day are how good DEMOS die.

Do not match a price you saw on a SaaS homepage. This site will not invent a Nerxus floor until policy exists. Your floor is your week and your deliverable. Write it down before the call so gratitude does not cut it in half.

What to say when they tell you the current site is fine

When they tell you the current site is fine, agree with the parts that are fine and ask them to take the stranger path once while you watch. If the path works, you were wrong. Thank them and leave. Being wrong on a finding is cheaper than arguing taste.

If the path fails while they watch, stay quiet for a second. Let them say the sentence. Then show the DEMO. You are not scoring a debate. You are standing next to a broken door with a spare door in the truck.

If they say their nephew handles it, ask for the nephew on the next call or leave a packet the nephew can reject. Fighting a nephew in absentia is a waste of a Thursday. The DEMO and the gap sentence travel without you. A brand speech does not.

If they say they will think about it, park the row with a date and a Watchtower-style reason to come back: rating change, new location, a broken book vendor. Do not send a new personality every week. The site-is-fine objection is often true enough that only a diff will reopen it.

If they are fine and you are bored, the ICP is wrong. Hunt shops where the path fails in public. Quality businesses with perfect sites are a different sport, and Apollo’s cousins already play it on LinkedIn.

How to walk the phone path before you open a builder

Walk the phone path before you open a builder because most local traffic does, and a desktop site that works with a tiny footer number is a different gap than a listing with no site field. Open the site from the Maps listing. Count the taps to a confirmed slot. If you never get there, you have the finding. If they use a vendor that is simply ugly, you have a taste argument. Taste arguments close slower.

Name the gap as a path a stranger takes, with the URL and the date. I opened your site from the Maps listing, clicked Services, and there is no way to book a cleaning. That is a name. The site feels dated is not a name. Write down what still works. Hours, address, a menu, a real photo of the front door. You will need those sentences in the meeting so you do not sound like you want to burn their money.

If you model a dollar around the gap, label it modeled and keep the assumption next to it. Missed bookings need their volume. You can say the path is missing. You cannot say they lose a number you guessed. DEV stays off the invoice. FEE is the rebuild or the page. Two sources that disagree should stay visible. The listing says they do implants. The site never mentions implants. That disagreement is a service-gap, and it is a better pitch than a new color palette.

You do not need Nerxus One to walk the path. Radar names that gap and stamps a fulfillment action. Forge opens the website tool because the action said so. If you work outside the product, write the gap in a sentence before you open the builder. If you cannot write the sentence, you are about to sell a redesign. Redesigns are long and taste-heavy. Gaps are short.

What to inventory on the old site before you talk rebuild

Inventory the live URLs before you talk rebuild, because burning the old tree without a map is how you drop their one good city page. Note the ones that rank, the ones that convert, the ones that 404. Your rebuild does not get to ignore a page that already answers a question just because your DEMO nav is cleaner. Keep the old site in the conversation as the source of redirects, the photo rights, the pages you will not rebuild, and the URL customers already typed.

Sell a page when the rest of the site already does the job and one path is missing. A city-service page, a booking landing page, a collect page, a financing FAQ, a storm-damage page after a permit wave. Pages close faster than rebuilds and they are easier to DEMO. Sell a rebuild when the site is the leak: mixed NAP, no HTTPS, a builder the owner cannot log into, a five-page brochure that 404s on three of them, or a mobile layout that hides the phone.

Do not sell a rebuild because you want a retainer that looks like a platform. Wanting a platform is your problem. Their problem is the path. If you need the retainer, sell month-two work after the page is live: Muse drafts they approve, Echo replies they approve, Watchtower on the listing. If they ask for the rebuild on the call, write the page as phase one on the invoice anyway. Phase two can be the rest. First clients expand.

Date the before on the invoice line if you need to. Rebuild of the booking path that failed on the live URL dated in the SOW. Specific invoices get paid. Redesign invoices get negotiated. Keep the live URL in the SOW as a before. When someone later says the old site was fine, you have the path you walked and the date you walked it. Memory is not a before. The URL is.

How to write the SOW so phase one stays a page

Write the SOW so phase one is the smallest page that fixes the finding, with deploy chores listed and a rollback sentence, because invoices that expand before deploy are how you work unpaid. Domain access, redirects from old URLs, the book button's real destination, form destinations, a privacy draft if you added forms, who owns the photos. Chores are unglamorous and they are why rebuilds slip.

Keep a rollback sentence. If we cut over and the book button fails, we point the domain back and fix the preview. Owners have been burned by agencies who disappear into a new theme. A rollback sentence is more adult than a launch party. Do not call the DEMO a free website. It is a sample. If they take the sample and walk, that is the cost of this motion. If you cannot afford that cost, hunt fewer rows and make fewer previews.

Say what you will not touch. If the last vendor is still on a retainer for posts, stay out of the posts. Scope fights are how two vendors burn a client and then both get fired. If the last vendor owns the host login and will not share it, your DEMO still matters. Deploy may mean a new host, a cutover, and a weekend. Say that early. Extra hours for a cutover should be a line, not a surprise.

DEMO means they can click a preview you host. DEPLOY means their domain, their DNS, their analytics, their booking vendor, their approval. Say both words in the meeting so the owner knows the preview is not a hijack. In this product, deploy is approval-gated. You should copy that even in a freelance stack. Do not push to their host because they said looks good on a text. Looks good is not an approval to cut over DNS.

What to do when they want the DEMO on their domain this week

When they want the DEMO on their domain this week, slow the cutover and keep the preview labeled, because shipping their live domain in the first mail is a different kind of mess than a preview they can click. If your client already paid and is waiting on a URL, a gating deploy will feel like ballast. Use a focused builder. Lovable can still be faster at the isolated publish. That speed is their win. Our slowness on DEPLOY is a decision.

Supervised is the default on deploys the same way it is the default on sends. Overnight magic deploys are not a production claim. List the deploy chores again. If they skip counsel on a privacy draft to save a week, the email they send you is the record. You still do not strip the label. You still do not add a certified badge.

If the last vendor still owns the host, say the hostage situation early. A preview that cannot go live without access is still worth sending, as long as the email does not pretend deploy is a button you already have. Do not offer to sue, shame, or replace them as a personality. Offer a page. If they want you to take over the whole site later, that is client-two energy inside the same account.

One Free Fix, on this site, means the DEMO asset, not a magic button we cannot show. Auto-generation as a fully hands-off spec is not what we market. We market the preview you can open in the same sitting as the finding and put in the first email. If a walkthrough cannot click it, do not promise it. You can generate in Lovable and attach the URL by hand. Their host is their host. Do not tell a client we deployed a site we did not.

How leftover findings become month two without a surprise invoice

Leftover findings become month two without a surprise invoice when you write the list they already saw and you wait, because Radar often leaves more than you sold and springing a collect page on a site job they already paid for is a bait-and-switch unless the SOW said so. Service-gap pages, collect page, inbound voice, a privacy draft. Steward is the home of that list after close. If you do not have Steward, a single client doc with leftover findings is enough. The rule is they saw the list.

Give them a view of progress that is not your Figma comments. A portal or a weekly note: what is still preview, what is waiting on their login, what is live. Plain language. No internal jokes about the old theme. They paid for that theme. Health later is Healthy, Watch, or At-risk. Diagnostic dollars stay modeled. Copy both habits in the pitch.

If they say they will think about it, park the row with a date and a Watchtower-style reason to come back: rating change, new location, a broken book vendor. Do not send a new personality every week. The site-is-fine objection is often true enough that only a diff will reopen it. If they are fine and you are bored, the ICP is wrong. Hunt shops where the path fails in public.

You can run this whole motion with a builder, a notes file, and a sending domain. Nerxus One is the version where the finding, the DEMO, the letter, and the client record share an id. Useful if you buy. Not required to stop selling websites to people who already have one, and start selling the gap. If the owner asks for a mood board anyway, do it after the gap DEMO, as a paid extra, or do not do it.

When Lovable is the right tool after they pay

Lovable is the right tool after they pay when the account exists and the job is the page, because focused, fast generation is their win in isolation. You can stay inside a builder. You can iterate. You do not have to learn Scout or Relay. The object is the site. The job is ship. Web studios live in that object. If your calendar is already full of paying builds, a loop that starts at a directory search will feel like a second company. It is a second company.

We will not claim Forge is the faster isolated generator. Forge is the builder that opens from a finding. Conversion widgets, booking, and an inbound line can sit on the same preview because those leaks were detectors too. Speed in a vacuum is still their sport. Pick Lovable when the client is waiting on a page. Pick us when you do not have the client, or when the page has to be the reason they become one.

You can generate in Lovable and attach the URL in Nerxus One. Hand-carry is honest. DEPLOY gates on our side only apply to what Forge deploys. Their host is their host. The cost of two builders is two previews and a chance to send the wrong link. Pulse and the business uuid exist so the right link sits on the right row. If you paste into a notes app, you opted out of that.

Stay if you are evaluating AI site tools as a designer. This product will feel like extra company around a preview. Extra company is the point for a marketer. It is ballast for a designer on a deadline. A focused builder is allowed to win isolation. This page exists so a studio stops generating unpaid pages and calling that a pipeline.

How to keep the old site in the conversation after they say yes

Keep the old site in the conversation as the source of redirects, the photo rights, the pages you will not rebuild, and the URL customers already typed. Burning the old tree without a map is how you drop their one good city page.

Inventory the live URLs before you deploy. Note the ones that rank, the ones that convert, the ones that 404. Your rebuild does not get to ignore a page that already answers a question just because your DEMO nav is cleaner.

Give them a view of progress that is not your Figma comments. A portal or a weekly note: what is still preview, what is waiting on their login, what is live. Plain language. No internal jokes about the old theme. They paid for that theme.

Park leftover findings as a written list, not as surprise tickets. Service-gap pages, collect page, inbound voice, a privacy draft. Steward is the home of that list after close. If you do not have Steward, a single client doc with leftover findings is enough. The rule is they saw the list.

You can run this whole motion with a builder, a notes file, and a sending domain. Nerxus One is the version where the finding, the DEMO, the letter, and the client record share an id. Useful if you buy. Not required to stop selling websites to people who already have one, and start selling the gap.

If the owner asks for a mood board anyway, do it after the gap DEMO, as a paid extra, or do not do it. Mood boards are how this meeting becomes last year’s vendor meeting. Last year’s vendor already won that meeting. You are here for the path that still fails.

Keep the live URL in the SOW as a before. When someone later says the old site was fine, you have the path you walked and the date you walked it. Memory is not a before. The URL is.

Date the before on the invoice line if you need to. Rebuild of the booking path that failed on the live URL dated in the SOW. Specific invoices get paid. Redesign invoices get negotiated.