# Private website demos that help sell a specific improvement

Research checked October 17, 2026. This is a proposed operating method, not a measured claim about conversion rates, time savings, token use, or Lovable credit costs.

## Recommended workflow

**Qualify first, then build a small but convincing demonstration.** Keep the full lead list, but rank demo effort separately. A tired website does not establish budget, buying intent, available capacity, or weak search performance. Establish the real service, customer, public contact location, and an observable website problem before spending on a concept.

1. **One evidence packet per prospect:** business facts with sources; actual logo and 3–5 usable photos; one concrete website gap; unknowns; one conversion action; visual direction. Keep research outside the build conversation. Give the builder the distilled packet rather than a long transcript or entire websites.
2. **Choose the visual concept before generating:** a headline using the real service, a buyer-specific hero composition, photo crops, typography pairing, section order, and an inquiry action. Start with the hero and one proof section. Review those at phone and desktop sizes before extending the design. Lovable's own advice supports real content, deliberate design direction, scoped components, and precise edits. [Prompting guidance](https://docs.lovable.dev/prompting/prompting-one)
3. **Build a self-contained sales demo:** one excellent homepage plus one useful interaction, such as a project filter or illustrative inquiry drawer. Do not spend pre-sale effort on accounts, databases, chatbots, live scheduling or email sending. Label it “Private website concept — prepared for discussion.” Keep it local or access-controlled. `noindex` reduces indexing; it is not privacy protection. [Google developer guidance](https://developers.google.com/search/docs/fundamentals/get-started-developers)
4. **Make one bounded visual correction pass:** capture phone and desktop screenshots and correct actual issues—crop, contrast, overflow, navigation, tap targets and broken actions. Preserve working sections rather than re-generating the whole site each time. Inspect the page after any edit that affects layout.
5. **Sell the next conversation:** the demo demonstrates presentation and a clearer inquiry path. Ask whether the owner wants more of a particular type of work and whether the team can take it. Confirm content, scope and terms before turning a speculative mockup into an official site. Keep follow-up messages drafted until sending is authorized.

## Reuse code without repeating the design

Reuse the invisible foundations: responsive image helper, accessible menu behavior, form validation, contact field data, metadata scaffolding and measurement events. Keep them independent of the page composition. Change the hero geometry, editorial rhythm, typography, image treatment, content order and CTA journey per business. A change of color on an identical card layout is not a bespoke concept.

Lovable supports referencing code and assets from another accessible project within the same workspace; the referenced project is read-only. That supports a small tested foundation project. It does not establish that copying a whole site's visual structure is right for this sales strategy. [Cross-project references](https://docs.lovable.dev/features/cross-project-referencing)

Use concise shared knowledge for durable engineering conventions, and project knowledge for the current prospect's verified facts and design. Knowledge is included in context; it is not documented as a free-token cache. Keep it short. [Knowledge documentation](https://docs.lovable.dev/features/knowledge)

## Three distinct customer journeys

These are design recommendations based on the buying tasks, not empirical conversion claims.

| Prospect | What the customer needs to decide | Useful demo direction | Best first action |
|---|---|---|---|
| Quick website sale: local storefront or appointment service | What do they offer, is it near me, what does it cost if published, and when can I go? | Friendly brand-led opening, real staff/place photos, readable menu/services, hours and contact high on the page | Call, request appointment, or see directions; only use verified hours |
| High-value projects: builders, outdoor construction, refinishing | Can this team deliver my particular project and style? What is the process? | Editorial project gallery with strong images; individual project context where verified; service/process detail; restrained typography | Discuss project type, location, timing and scope |
| HVAC | Can someone solve my problem, serve my area, and explain the next step? | Direct service-first layout, readable phone action, repair/install/maintenance split, real team proof | Request service; separate office hours from emergency availability |
| Tyler Fabricators | Can this shop support a contractor's structural steel/aluminum scope from drawings to installation? | Industrial editorial layout: original wordmark, masonry/steel geometry, close reading of real project photos, capabilities and drawing-to-installation process | Discuss a fabrication project; a plan-upload interaction may be illustrated but must not upload or send in the private demo |

For Tyler, do not pitch it as a custom-home builder. Its stated market is commercial and residential contractors. Its homepage portfolio is authentic but thinly captioned. The opportunity is clearer capability and project context, plus a visible project inquiry journey—not an unsupported claim that it has no SEO.

## What the Lovable documentation actually establishes about cost

Current documentation says Plan mode costs one credit per message plus any subagent research. Build charges depend on work performed; the example credit figures are illustrative, not quotations for our project. Long-running goals can cost more. Actual message costs are visible in the response menu and usage reporting. We have not run a billed Lovable test here, so there is no measured cost per demo and no proven savings percentage. [Credits and usage](https://docs.lovable.dev/introduction/credits-and-usage)

The current preview toolbar replaces older “Visual edits.” Selecting elements and requesting changes consumes build credits. Inline text edits have a documented free allowance (100 per account with a rolling 24-hour return, subject to a 2,000-per-workspace daily limit), then use credits. Do not claim all visual changes are free. [Preview toolbar](https://docs.lovable.dev/features/preview-toolbar)

Practical hypothesis to test: one researched packet, one visual direction, a small demo scope and targeted edits should reduce rework. Measure elapsed minutes, credits/tokens where exposed, revision count, and whether the final concept passes quality checks for the first three demos. Compare total cost per acceptable demo, not prompt count. A 500-dollar sale needs a bounded deliverable; a custom multi-page site with ongoing SEO is a different scope. No purchase is required to begin with the tools already available.

## SEO and AI-search foundations

For an approved production launch, prioritize specific service information, genuine first-hand project proof, text that answers buyers' questions, crawlable internal links, mobile performance and accurate business details. Google says its generative search features rest on core search systems. The current guide says pages must be indexed and snippet-eligible and the site included in generative search features in Search Console. Special AI text files and `llms.txt` are not required by Google and do not improve its rankings. Meeting requirements does not guarantee indexing, appearance or traffic. This guidance is about Google; it does not prove identical rules for every AI answer service. [Google AI optimization guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)

Use appropriate LocalBusiness/Organization markup that matches visible, verified facts, with the most specific suitable business type. Never invent hours, ratings, prices or certifications. Google restricts local-business review markup for self-serving reviews; do not add an aggregate rating simply because the owner's page displays testimonials. Structured data is eligibility and understanding support, not a ranking guarantee. [LocalBusiness documentation](https://developers.google.com/search/docs/appearance/structured-data/local-business)

Do not publish mass-generated city/service variants with no local evidence. Google warns that scaled pages created without user value may violate spam policy. Instead, obtain real project details and owner expertise after engagement. [Google's AI-content guidance](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content)

## Reusable build prompt

> Create a private sales concept for [business] using the attached verified fact packet and original assets. The customer is [specific buyer]; their decision is [job they need done]; the main action is [call/request consultation/book]. The current observed weakness is [evidence, not guessed revenue or rankings].
>
> Design direction: [specific composition, typography, colors, photo treatment, whitespace and content rhythm]. Use the actual logo and supplied project photos. Distinguish visual descriptions from verified project names. Do not fabricate testimonials, ratings, hours, certifications, guarantees or project locations.
>
> First build the responsive navigation, hero and one compelling proof section. The opening should communicate the actual service and make the next action obvious. Use real concise copy from the fact packet. When those are coherent, complete [small defined remaining sections]. Reuse accessible menu, image and form utilities if available, but compose a new page for this business. Avoid repeating the previous concept's hero arrangement and section rhythm.
>
> Include one useful demonstration interaction: [specific behavior]. Forms must explain that this is a concept and neither send nor store submissions. Keep this local/private, label it as an independent concept and add noindex. No backend, login, analytics, payments, outbound email or public deployment.
>
> Check at narrow phone and desktop widths, keyboard navigation, readable contrast, image quality, working navigation and no overflow. Correct observed issues with bounded edits. Return the private preview, two screenshots, remaining fact questions and a short list of what a production version would still need. Do not claim SEO results or leads from this demo.

## Tyler creative brief

Proposed direction: a dark charcoal masthead for the genuine distressed white wordmark, warm off-white reading areas, restrained oxidized-red accents that echo the actual steel photos, large technical typography and strong horizontal rules. Use a wide masonry/steel photograph as a visual anchor, with adjacent compact service copy. Follow with a varied-scale project editorial rather than identical cards. The company’s actual relationship with contractors should organize the content: scope, capability, project proof, conversation. These are creative choices for a concept, not established brand standards.

Available evidence and assets are in `../tyler-assets/provenance.json`; the contact sheet is `../tyler-assets/contact-sheet.jpg`. The public official site provides no verified operating hours on the pages inspected. Present “Contact the shop for availability” rather than inventing hours or declaring Saturday availability. The Delray address is the shop; the Deerfield address is mailing-only.