Skip to content

Launch readiness

Legal, email, CRM, and testing decisions before paid traffic.

This register tracks the remaining approvals GeoPlus needs before launching ads or scaling the roadshow. Items stay pending until James or Jeremy confirms them; nothing here invents legal or business details.

Legal information

Public pages stay draft until details are confirmed.

Legal business name

Pending confirmation

Current state: Privacy and terms pages use GeoPlus Marketing as public-facing site language with explicit legal TODOs.

Needed: James or Jeremy must confirm the exact legal entity name before paid traffic.

Legal contact email

Pending confirmation

Current state: Public pages currently use the operational contact email already present on the site.

Needed: Confirm whether the legal contact email should match the operational contact or a different approved address.

Business address

Pending confirmation

Current state: No physical business address is published as final legal address.

Needed: Confirm the address format required for privacy, terms, email compliance, and paid-traffic review.

Service area wording

Pending confirmation

Current state: Site uses Cache Valley and Idaho Falls launch language plus expansion scaffolding.

Needed: Confirm final service-area wording for legal pages, ads, and public offers.

Resend sender domain

Decision required

Current: Current notifications send as GeoPlus Intake using [email protected] because that domain is verified.

Needed: Decide whether to keep the current sender for launch or verify geoplusmarketing.com or a mail subdomain before paid traffic.

GeoPlus GHL subaccount decision

Decision required

Current: Current intake workflow uses the New Reward GHL subaccount.

Needed: Decide whether GeoPlus should continue using the current setup for launch or move into a dedicated GeoPlus GHL subaccount before scale.

Controlled live intake test approval

Approval required

Current: Website intake route, GHL webhook path, and Resend notification path are configured.

Needed: Approve one labeled test lead, expected notification recipients, GHL verification steps, and cleanup requirements.

Controlled intake test

Test only after the test lead and cleanup plan are approved.

Step 1

Submit approved test lead

Evidence: Timestamped submission using approved test business/contact details.

Cleanup: Use a clearly labeled test contact so it can be found and removed or archived.

Step 2

Verify GHL contact creation

Evidence: Private screenshot or internal note showing the contact exists in the expected pipeline/account.

Cleanup: Remove or label the test contact according to the approved cleanup plan.

Step 3

Verify automation and notification behavior

Evidence: Private evidence that expected workflow steps and notification email behavior occurred.

Cleanup: Stop any accidental follow-up sequence before it contacts real people.

Step 4

Save private evidence

Evidence: Evidence stored privately, without provider secrets or public GitHub attachments.

Cleanup: Do not paste screenshots containing private values into public issues or docs.

Step 5

Clean up test data

Evidence: Confirmation note that the test lead was deleted, archived, or clearly labeled.

Cleanup: Leave no unlabeled test opportunity in the live sales pipeline.