From a local lead
to a website you can hand over.

1. Open Lead Finder and choose a business type and location.
2. Review the search mode, filters, and credit cost before starting. Search credits are separate from AI credits.
3. Inspect the website, contact information, and available business details for each result.
4. Choose prospects with a specific website need you can explain.

Verify the listing before reaching out. A rating or lead score is a research aid, not proof that the owner wants a website.

1. Open the business details and save the lead with the bookmark control.
2. Find it in your CRM or Saved Leads view.
3. Record what you noticed, the contact details you checked, and why a website might help.
4. Keep the pipeline stage current as the conversation progresses.

Work with a list small enough to follow up on. Record when an owner asks you to stop contacting them.

1. Open the lead’s call guide in the business details.
2. Generate or refresh it if needed, checking your available AI credits.
3. Verify every business-specific claim and remove anything you cannot support.
4. Prepare an opening, a question about the business, and a clear next step.

Use the guide to prepare. Listen to the owner instead of reading a script line by line.

1. Contact the business through an appropriate channel and introduce yourself.
2. Explain the specific issue you noticed and ask whether it matters to them.
3. Discuss the pages, services, contact details, and business goals the site should cover.
4. If they want a preview, confirm where to send it and when you can realistically deliver it.
5. Record the conversation and the next action in your CRM.

Answer pricing questions directly. Separate the website work from any recurring hosting or maintenance you may offer.

1. Check your AI credit balance before you start. Website generation and later edits spend AI credits.
2. Open the lead and choose Generate website. SiteSeeker saves an unsaved lead before starting the build.
3. Use the builder conversation to describe the business, pages, style, and required content.
4. Review the generated website and ask for specific changes in chat.
5. Check the mobile layout, service details, images, phone links, and forms. Confirm that any form has a working destination.

Do not invent testimonials, certifications, business results, or contact details. A generated draft needs your review before it represents a client.

1. Open the project associated with your generated website.
2. If you are bringing an existing website, use Create project from the lead or create one in Projects.
3. Check the business information and add the agreed scope and next action.
4. Keep the project status consistent with what has actually happened.

Check for an existing project before creating another one for the same engagement.

1. For a builder site, choose Publish, review the subdomain, and confirm. Later edits reach the public site when you publish them.
2. For an existing site, open Hosting or Setup website in the project. Choose Upload ZIP or GitHub.
3. For GitHub, authorize access, select the repository and branch, and review the deployment settings. Enable automatic deploys only if you want pushes to publish changes.
4. For ZIP, supply the supported website source or export. A hosted-only service may not provide an export that SiteSeeker can run.
5. Watch the build status and logs. Build time varies; open the live address only after the deployment succeeds.

Keep secrets out of browser code and ZIP exports. Test the public site, including mobile layout and forms, before you share it.

1. Open the project and check its Website section.
2. If the site is already linked, open it and confirm that it belongs to this business.
3. If no site is linked, choose Link existing site and select the correct site, or use Setup website.
4. Review the project’s preview and conversion-bar settings before sharing the public URL.

A live website, a project preview URL, and a purchase link serve different purposes. Open each link you plan to use.

1. Copy the Preview URL from the project’s Website section and open it as the client would.
2. Review the conversion bar so its message and action match your offer.
3. When you are ready to sell, open Sell Website and choose Create listing.
4. Complete any seller agreement and Stripe Connect setup, then set the website price and any optional monthly maintenance.
5. Review the fees and terms, publish the listing, and check the purchase link before sharing it.

Publishing the website does not automatically publish a sale listing. Explain the one-time price and any recurring charge separately.

1. Write to the contact who agreed to review the site.
2. Remind them what you discussed and explain one or two choices you made for their business.
3. Include the preview link and ask for specific feedback.
4. If you agreed on an offer, include its scope, price, and the purchase link.
5. Record the message in your notes and use Mark Preview as Sent when you have sent it.

Mark Preview as Sent updates project tracking. It does not replace sending the message through your email or other communication channel.

1. Follow up at the time you agreed and answer questions about the website or offer.
2. Confirm the deliverables, domain, launch timing, and any ongoing maintenance in writing.
3. Direct the buyer to the published listing’s checkout when using SiteSeeker’s sale flow.
4. Check the recorded payment and purchase status before treating the sale as complete.
5. Confirm client access and the website’s ownership or transfer status, then record any remaining work.

A viewed preview, a verbal yes, or a CRM stage change is not proof of payment. Check the transaction record.

1. Review which prospects replied and which offers became paid work.
2. Compare the time and credit costs of searches, builds, revisions, and follow-ups.
3. Track paid website work separately from recurring maintenance or hosting revenue.
4. Choose a next batch you can support, and keep existing client commitments visible.
5. Update your brief and outreach based on what you learned.

Set your own activity goals. A playbook cannot guarantee a client, conversion rate, or amount of revenue.