AG LUXURY / OUR LAUNCH GAME PLAN

From built to ready. From ready to launched.

Allison + NORTH

Snapshot September 25, 2026 · Working evidence-backed plan, not company-wide doctrine

Proposed sprint

Proposed four-week sprint. Not a commitment and not approved. Gates beat the calendar.

KickoffMonday, September 28, 2026
Soft-review weekWeek of October 12, 2026
Public-launch candidate weekWeek of October 19, 2026
Candidate targetFriday, October 23, 2026

Status vocabulary: Confirmed decision · Exists / needs acceptance · In progress · Blocked · Needs Allison · Not yet audited · Proposed · Verified complete · Later

M1One agreed launch packageIn progressWeek 1 opening (proposed)

Outcome: Evidence, assets, proposition and scope agreed so nobody relitigates settled decisions.
Owner: NORTH + Allison
Next action: NORTH inventories evidence and assets through connected systems and returns unresolved decisions only.
Depends on: Access to existing connected systems. No new accounts.
Done means: Founder decisions recorded or deferred with stated consequence, sources linked, no identity conflict remaining.
Evidence required: Founder decisions recorded or deferred with consequence; sources linked; no identity conflict remaining.
Allison decides: Final email after inventory; Phase 1 scope, capacity and target dates.
NORTH action: Inventory evidence and existing assets before recommending anything.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 1 opening (proposed)

M1.1In progress

Outcome: Asset and evidence inventory
Owner: NORTH
Next action: Link brand guide, logo package, live site, King Ranch story, guides, farming roadmap and flywheel with their approval state.
Depends on: None
Done means: Every asset listed with source and approval state.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 1

M1.2Confirmed decision

Outcome: Reaffirm consumer proposition and primary community
Owner: Allison
Next action: Nothing new unless Allison reopens it.
Depends on: None
Done means: Locked decisions LD5 to LD7 remain unchanged.
Launch impact: Launch blocker
Source: Owner decision · September 25, 2026
Proposed timing: Week 1

M1.3Not yet audited

Outcome: Settle delivery email identity
Owner: NORTH, then Allison
Next action: Audit mailboxes, domains and delivery authentication before recommending.
Depends on: Inventory access
Done means: One recommended address with verified delivery; Allison decision recorded (DQ1).
Launch impact: Launch blocker
Source: Owner decision · September 25, 2026
Proposed timing: Week 1

M1.4Needs Allison

Outcome: Reconcile typography record
Owner: NORTH
Next action: Compare owner typography (Aperitif Serif, Neue Swiss) with deployed Manrope and Italiana; verify approval and licenses. No redesign.
Depends on: Brand guide and license records
Done means: One documented answer with license evidence, Allison confirmation recorded.
Launch impact: Improves launch
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Week 1

M1.5Needs Allison

Outcome: Accept scope, capacity and weekly outcomes
Owner: Allison
Next action: Review Phase 1 scope in /launch and this sprint scenario (DQ2).
Depends on: M1.1
Done means: Scope and dates approved, revised or deferred in writing.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 1

Open in /launch

M2A working client journeyBlockedWeeks 1 to 2 (proposed)

Outcome: Licensed search and inquiry delivery genuinely work on the live domain.
Owner: Existing WordPress worker + NORTH acceptance + Allison approvals
Next action: Allison restores normal screen-recording permission so the signed-in Showcase account can be inspected.
Depends on: macOS ScreenCaptureKit -3801 on the worker. No bypass.
Done means: Search and inquiry acceptance tests pass with recorded evidence.
Evidence required: Search acceptance tests pass on the live domain; a controlled end-to-end test inquiry is received in the correct PartnerSync location.
Existing worker: AG Lux Wordpress Build (Lovable To WordPress Conversion)
NORTH action: Prepare copy and delivery acceptance; verify outcomes.
Permission needed: Allison restores normal macOS screen-recording permission so the signed-in Showcase account can be inspected. No bypass.
Launch impact: Launch blocker
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Weeks 1 to 2 (proposed)

WordPress build checkpoint

M2.1Needs Allison

Outcome: Restore screen-recording permission
Owner: Allison
Next action: Restore normal permission on Ember. Do not sign in again or purchase.
Depends on: None
Done means: Worker can inspect the signed-in account.
Launch impact: Launch blocker
Source: User-reported · September 25, 2026
Proposed timing: Week 1

M2.2Blocked

Outcome: Verify Showcase identity and authorized install
Owner: WordPress worker
Next action: Confirm current website, license, domain and MLS association. Historical UUID is not current proof.
Depends on: M2.1
Done means: Account details recorded from the current account view.
Launch impact: Launch blocker
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Week 1

M2.3Proposed

Outcome: Choose search namespace
Owner: WordPress worker + NORTH
Next action: Verify /search candidate; /properties editorial routes block a blind default namespace.
Depends on: M2.2
Done means: Namespace chosen without breaking existing editorial URLs.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 1 to 2

Open in /launch

M2.4Proposed

Outcome: Search acceptance tests
Owner: NORTH
Next action: Test results, map, filters, detail, account and saved searches if exposed, metadata, pagination, sitemap and cache isolation.
Depends on: M2.3
Done means: Test record with pass or fail per item.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M2.5Blocked

Outcome: Contact and valuation delivery
Owner: WordPress worker
Next action: Route into the correct AG Luxury PartnerSync location with notification, dedupe, source, spam, consent and clear success and error states.
Depends on: M1.3 and verified PartnerSync location
Done means: Controlled end-to-end receipt recorded. No parallel CRM, no guessed integration.
Launch impact: Launch blocker
Source: Fresh public page read · September 25, 2026
Proposed timing: Week 1 to 2

M2.6Proposed

Outcome: Response expectation copy
Owner: NORTH, then Allison
Next action: Draft honest response language. No assumed 24/7 promise.
Depends on: Allison service promise
Done means: Approved wording on forms and confirmations.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M3A credible, consistent public presenceExists / needs acceptanceWeek 2 (proposed)

Outcome: The website tells the truth and priority profiles match one identity.
Owner: NORTH + WordPress worker + Allison approvals
Next action: Deliver one decision packet: buyer offer, opening narrative, seller proof, Kingswood reference guide.
Depends on: M1 decisions
Done means: Page approvals recorded in /launch and priority profiles consistent or waiting on a provider.
Evidence required: /launch rows accepted; identity inventory complete with priority corrections done or provider-waiting.
Allison decides: Claims, photos, services and typography reconciliation.
Existing worker: AG Lux Wordpress Build for destination and label repairs
NORTH action: Inventory existing profiles before any duplicate or rename.
Permission needed: Access to existing Google Business Profile and portal accounts.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2 (proposed)

Open in /launch

M3.1Proposed

Outcome: Repair wrong destinations and labels
Owner: WordPress worker
Next action: Fix Bella Cima destinations, sold cards framed as for sale and neighborhood links pointing to contact.
Depends on: Authorized worker session
Done means: Each defect rechecked on the live review site.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

Open in /launch

M3.2Proposed

Outcome: Buyer page and opening narrative
Owner: NORTH
Next action: Draft the buyer page, currently To draft in /launch.
Depends on: M1.2
Done means: Draft linked and approved by Allison.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.3Exists / needs acceptance

Outcome: Kingswood reference guide
Owner: NORTH
Next action: Replace generic media, date all figures, review claims.
Depends on: Allison photo and claim approvals
Done means: Guide approved and used as the pattern for the other five.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

Open Kingswood draft

M3.4Exists / needs acceptance

Outcome: Remaining guides and Frisco and Prosper hubs
Owner: NORTH
Next action: Expand after Kingswood pattern is approved; hubs remain proposed.
Depends on: M3.3
Done means: Each approved in /launch.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2 to 3

M3.5Needs Allison

Outcome: Seller, concierge, marketing, case study and footer documents
Owner: Allison
Next action: Accept or revise with NORTH notes.
Depends on: Decision packet
Done means: Acceptance recorded.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.6Not yet audited

Outcome: Identity inventory
Owner: NORTH
Next action: Inventory real phone, email, business naming, broker, existing GBP (before any duplicate or rename), hours, photos, links, brokerage and MLS, Google, Zillow, Realtor, Homes, Bing, Apple, Instagram, Facebook, LinkedIn, YouTube.
Depends on: Connected system access
Done means: Matrix of current values with one recommended correction list.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M3.7Later

Outcome: Secondary portal propagation
Owner: NORTH
Next action: Continue after launch once priority channels match.
Depends on: M3.6
Done means: Secondary portals consistent.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: After launch

M4Ready to win and serve the appointmentNot yet auditedWeeks 2 to 3 (proposed)

Outcome: Allison can run a buyer and a listing consultation with current, usable materials.
Owner: NORTH + Allison + existing presentation lane
Next action: Inventory current buyer and listing presentations before assuming anything is missing.
Depends on: Existing presentation lane access
Done means: One buyer and one seller scenario rehearsed with current materials.
Evidence required: One buyer and one seller scenario rehearsed with current materials and current approved Texas and broker forms.
Allison decides: Service deliverables and consultation approach.
NORTH action: Inventory and improve existing presentations; do not generate legal forms.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Weeks 2 to 3 (proposed)

M4.1Not yet audited

Outcome: Presentation inventory
Owner: NORTH
Next action: Find existing buyer and listing decks.
Depends on: None
Done means: Inventory with gaps named.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M4.2Proposed

Outcome: Minimum usable buyer and listing presentation
Owner: NORTH, then Allison
Next action: Cover discovery, service deliverables, proof or case study, transparent compensation and agreement discussion, objections and follow-up.
Depends on: M4.1
Done means: Allison approves both.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2 to 3

M4.3Proposed

Outcome: Forms
Owner: Allison
Next action: Use current approved Texas and broker forms. NORTH does not generate legal forms.
Depends on: Broker
Done means: Current form set confirmed.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 3

M4.4Proposed

Outcome: Rehearsal
Owner: Allison + NORTH
Next action: Rehearse one buyer and one seller scenario. No promise to close every prospect.
Depends on: M4.2
Done means: Notes captured and fixes applied.
Launch impact: Improves launch
Source: Proposal · September 25, 2026
Proposed timing: Week 3

M5Test, approve, then announceProposedWeek 4, only if hard gates pass (proposed)

Outcome: Soft review passes, then separate explicit approvals for indexing and announcement.
Owner: NORTH + WordPress worker + Allison release approval
Next action: Wait on M2 to M4. Nothing here runs from this planning app.
Depends on: M2, M3, M4
Done means: Soft review closed, release approved, indexing enabled only after that approval.
Evidence required: Soft review completed, technical acceptance recorded, and a separate explicit approval for indexing.
Allison decides: Release approval, indexing and announcement, each separately.
Existing worker: AG Lux Wordpress Build for technical acceptance
Permission needed: Search Console access, only after explicit approval.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4, only if hard gates pass (proposed)

Open in /launch

M5.1Proposed

Outcome: Soft review
Owner: Allison
Next action: About five trusted reviewers across buyer, seller and relocation on mobile and desktop.
Depends on: M2 to M4
Done means: Findings logged and resolved.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week of October 12 (scenario)

M5.2Proposed

Outcome: Technical release checks
Owner: WordPress worker + NORTH
Next action: Fresh backup and recovery, links, redirects, security, accessibility, responsive, performance, metadata, canonical, schema.
Depends on: M5.1
Done means: Checklist recorded with evidence.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4

M5.3Proposed

Outcome: Compliance footer
Owner: Allison
Next action: Current IABS, consumer notice, broker, privacy and consent language.
Depends on: Broker
Done means: Links verified live.
Launch impact: Launch blocker
Source: Official external guidance · September 25, 2026
Proposed timing: Week 4

M5.4Not yet audited

Outcome: Measurement or approved manual fallback
Owner: NORTH
Next action: Check GA and Search Console access and conversions.
Depends on: Access
Done means: Working measurement or written manual fallback.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4

M5.5Later

Outcome: Indexing and Search Console approval
Owner: Allison
Next action: Separate explicit approval. Robots stay unchanged until then.
Depends on: M5.1 to M5.4
Done means: Approval recorded, then indexing and sitemap submission.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week of October 19 (scenario)

M5.6Later

Outcome: Warm-network, email and social rollout
Owner: Allison
Next action: Separately authorized. No sends from here.
Depends on: M5.5
Done means: Authorized rollout completed.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: After release

M6Build authority from real conversationsLaterPost-launch 30 / 60 / 90

Outcome: Authority grows from real client conversations and one excellent guide at a time.
Owner: NORTH + Allison
Next action: Starts after release. Not a launch prerequisite.
Depends on: M5
Done means: Day 90 review completed with observed data.
Evidence required: Observed baseline data from real conversations, not assumptions.
NORTH action: Run focused content cycles from the Kingswood reference guide.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: Post-launch 30 / 60 / 90

M6.1Later

Outcome: First focused content cycle
Owner: NORTH
Next action: Repurpose the Kingswood guide into insight, short video, LinkedIn, Instagram and Facebook cutdowns and consented email.
Depends on: M3.3
Done means: One cycle shipped with approvals.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: Day 30

M6.2Later

Outcome: Genuine review process
Owner: Allison
Next action: Verify real baseline first, then voluntary requests only.
Depends on: M3.6
Done means: Process documented and in use.
Launch impact: After launch
Source: Official external guidance · September 25, 2026
Proposed timing: Day 30

Full plan · Snapshot September 25, 2026 · Working evidence-backed plan, not company-wide doctrine

The foundation exists. We are finishing the client journey and launch acceptance, not starting the brand over.

Critical gates

Licensed search works: Blocked. Showcase identity, license, domain and MLS association not yet verified. Current search is a truthful fallback, not working IDX.
Inquiry delivery tested: Blocked. Fresh public read September 25: contact and valuation forms explicitly not accepting messages.
Content and identity approved: Needs Allison. No page-level final signoff recorded in /launch. Final email and cross-account handle implementation unresolved.
Sales and consultation readiness: Not yet audited. Buyer and listing presentation inventory not audited in this pass.
Explicit indexing and release signoff: Needs Allison. Indexing intentionally off. Release needs a separate explicit approval.

Next three outcomes

A. Make Search + Contact genuinely work. The AG Lux Wordpress Build worker owns technical execution. It is blocked by macOS ScreenCaptureKit error -3801. NORTH prepares acceptance tests and form copy concurrently.
B. Approve the first launch-content batch. NORTH drafts and reconciles the buyer offer and opening narrative, accurate seller proof and the Kingswood reference guide. The worker repairs wrong destinations and active versus sold labels. Broader /launch scope stays.
C. Establish one identity + outreach baseline. NORTH inventories current domains, email, Google Business Profile, portal and social profiles, reviews, CRM and presentations through existing connected systems. No public edits during assessment.

Decision queue

Choose the final usable email address after NORTH inventories mailbox, domain and delivery. (After inventory (M1))
Approve or revise Phase 1 scope, weekly capacity and target dates. (Week 1 opening)
Approve claims, photos, services and the typography discrepancy using current sources. (With decision packet (Outcome B))
Approve release: indexing, Search Console and announcement, each separately. (Later, only after hard gates pass)

Proposed four-week sprint. Not a commitment and not approved. Gates beat the calendar.

M1 One agreed launch package · In progress

Outcome: Evidence, assets, proposition and scope agreed so nobody relitigates settled decisions.
Owner: NORTH + Allison
Next action: NORTH inventories evidence and assets through connected systems and returns unresolved decisions only.
Depends on: Access to existing connected systems. No new accounts.
Done means: Founder decisions recorded or deferred with stated consequence, sources linked, no identity conflict remaining.
Evidence required: Founder decisions recorded or deferred with consequence; sources linked; no identity conflict remaining.
Allison decides: Final email after inventory; Phase 1 scope, capacity and target dates.
NORTH action: Inventory evidence and existing assets before recommending anything.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 1 opening (proposed)

M1.1 · In progress

Outcome: Asset and evidence inventory
Owner: NORTH
Next action: Link brand guide, logo package, live site, King Ranch story, guides, farming roadmap and flywheel with their approval state.
Depends on: None
Done means: Every asset listed with source and approval state.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 1

M1.2 · Confirmed decision

Outcome: Reaffirm consumer proposition and primary community
Owner: Allison
Next action: Nothing new unless Allison reopens it.
Depends on: None
Done means: Locked decisions LD5 to LD7 remain unchanged.
Launch impact: Launch blocker
Source: Owner decision · September 25, 2026
Proposed timing: Week 1

M1.3 · Not yet audited

Outcome: Settle delivery email identity
Owner: NORTH, then Allison
Next action: Audit mailboxes, domains and delivery authentication before recommending.
Depends on: Inventory access
Done means: One recommended address with verified delivery; Allison decision recorded (DQ1).
Launch impact: Launch blocker
Source: Owner decision · September 25, 2026
Proposed timing: Week 1

M1.4 · Needs Allison

Outcome: Reconcile typography record
Owner: NORTH
Next action: Compare owner typography (Aperitif Serif, Neue Swiss) with deployed Manrope and Italiana; verify approval and licenses. No redesign.
Depends on: Brand guide and license records
Done means: One documented answer with license evidence, Allison confirmation recorded.
Launch impact: Improves launch
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Week 1

M1.5 · Needs Allison

Outcome: Accept scope, capacity and weekly outcomes
Owner: Allison
Next action: Review Phase 1 scope in /launch and this sprint scenario (DQ2).
Depends on: M1.1
Done means: Scope and dates approved, revised or deferred in writing.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 1

M2 A working client journey · Blocked

Outcome: Licensed search and inquiry delivery genuinely work on the live domain.
Owner: Existing WordPress worker + NORTH acceptance + Allison approvals
Next action: Allison restores normal screen-recording permission so the signed-in Showcase account can be inspected.
Depends on: macOS ScreenCaptureKit -3801 on the worker. No bypass.
Done means: Search and inquiry acceptance tests pass with recorded evidence.
Evidence required: Search acceptance tests pass on the live domain; a controlled end-to-end test inquiry is received in the correct PartnerSync location.
Existing worker: AG Lux Wordpress Build (Lovable To WordPress Conversion)
NORTH action: Prepare copy and delivery acceptance; verify outcomes.
Permission needed: Allison restores normal macOS screen-recording permission so the signed-in Showcase account can be inspected. No bypass.
Launch impact: Launch blocker
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Weeks 1 to 2 (proposed)

M2.1 · Needs Allison

Outcome: Restore screen-recording permission
Owner: Allison
Next action: Restore normal permission on Ember. Do not sign in again or purchase.
Depends on: None
Done means: Worker can inspect the signed-in account.
Launch impact: Launch blocker
Source: User-reported · September 25, 2026
Proposed timing: Week 1

M2.2 · Blocked

Outcome: Verify Showcase identity and authorized install
Owner: WordPress worker
Next action: Confirm current website, license, domain and MLS association. Historical UUID is not current proof.
Depends on: M2.1
Done means: Account details recorded from the current account view.
Launch impact: Launch blocker
Source: Implementation checkpoint · September 24, 2026
Proposed timing: Week 1

M2.3 · Proposed

Outcome: Choose search namespace
Owner: WordPress worker + NORTH
Next action: Verify /search candidate; /properties editorial routes block a blind default namespace.
Depends on: M2.2
Done means: Namespace chosen without breaking existing editorial URLs.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 1 to 2

M2.4 · Proposed

Outcome: Search acceptance tests
Owner: NORTH
Next action: Test results, map, filters, detail, account and saved searches if exposed, metadata, pagination, sitemap and cache isolation.
Depends on: M2.3
Done means: Test record with pass or fail per item.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M2.5 · Blocked

Outcome: Contact and valuation delivery
Owner: WordPress worker
Next action: Route into the correct AG Luxury PartnerSync location with notification, dedupe, source, spam, consent and clear success and error states.
Depends on: M1.3 and verified PartnerSync location
Done means: Controlled end-to-end receipt recorded. No parallel CRM, no guessed integration.
Launch impact: Launch blocker
Source: Fresh public page read · September 25, 2026
Proposed timing: Week 1 to 2

M2.6 · Proposed

Outcome: Response expectation copy
Owner: NORTH, then Allison
Next action: Draft honest response language. No assumed 24/7 promise.
Depends on: Allison service promise
Done means: Approved wording on forms and confirmations.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M3 A credible, consistent public presence · Exists / needs acceptance

Outcome: The website tells the truth and priority profiles match one identity.
Owner: NORTH + WordPress worker + Allison approvals
Next action: Deliver one decision packet: buyer offer, opening narrative, seller proof, Kingswood reference guide.
Depends on: M1 decisions
Done means: Page approvals recorded in /launch and priority profiles consistent or waiting on a provider.
Evidence required: /launch rows accepted; identity inventory complete with priority corrections done or provider-waiting.
Allison decides: Claims, photos, services and typography reconciliation.
Existing worker: AG Lux Wordpress Build for destination and label repairs
NORTH action: Inventory existing profiles before any duplicate or rename.
Permission needed: Access to existing Google Business Profile and portal accounts.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2 (proposed)

M3.1 · Proposed

Outcome: Repair wrong destinations and labels
Owner: WordPress worker
Next action: Fix Bella Cima destinations, sold cards framed as for sale and neighborhood links pointing to contact.
Depends on: Authorized worker session
Done means: Each defect rechecked on the live review site.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.2 · Proposed

Outcome: Buyer page and opening narrative
Owner: NORTH
Next action: Draft the buyer page, currently To draft in /launch.
Depends on: M1.2
Done means: Draft linked and approved by Allison.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.3 · Exists / needs acceptance

Outcome: Kingswood reference guide
Owner: NORTH
Next action: Replace generic media, date all figures, review claims.
Depends on: Allison photo and claim approvals
Done means: Guide approved and used as the pattern for the other five.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.4 · Exists / needs acceptance

Outcome: Remaining guides and Frisco and Prosper hubs
Owner: NORTH
Next action: Expand after Kingswood pattern is approved; hubs remain proposed.
Depends on: M3.3
Done means: Each approved in /launch.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2 to 3

M3.5 · Needs Allison

Outcome: Seller, concierge, marketing, case study and footer documents
Owner: Allison
Next action: Accept or revise with NORTH notes.
Depends on: Decision packet
Done means: Acceptance recorded.
Launch impact: Launch blocker
Source: Current planning data · September 25, 2026
Proposed timing: Week 2

M3.6 · Not yet audited

Outcome: Identity inventory
Owner: NORTH
Next action: Inventory real phone, email, business naming, broker, existing GBP (before any duplicate or rename), hours, photos, links, brokerage and MLS, Google, Zillow, Realtor, Homes, Bing, Apple, Instagram, Facebook, LinkedIn, YouTube.
Depends on: Connected system access
Done means: Matrix of current values with one recommended correction list.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M3.7 · Later

Outcome: Secondary portal propagation
Owner: NORTH
Next action: Continue after launch once priority channels match.
Depends on: M3.6
Done means: Secondary portals consistent.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: After launch

M4 Ready to win and serve the appointment · Not yet audited

Outcome: Allison can run a buyer and a listing consultation with current, usable materials.
Owner: NORTH + Allison + existing presentation lane
Next action: Inventory current buyer and listing presentations before assuming anything is missing.
Depends on: Existing presentation lane access
Done means: One buyer and one seller scenario rehearsed with current materials.
Evidence required: One buyer and one seller scenario rehearsed with current materials and current approved Texas and broker forms.
Allison decides: Service deliverables and consultation approach.
NORTH action: Inventory and improve existing presentations; do not generate legal forms.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Weeks 2 to 3 (proposed)

M4.1 · Not yet audited

Outcome: Presentation inventory
Owner: NORTH
Next action: Find existing buyer and listing decks.
Depends on: None
Done means: Inventory with gaps named.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2

M4.2 · Proposed

Outcome: Minimum usable buyer and listing presentation
Owner: NORTH, then Allison
Next action: Cover discovery, service deliverables, proof or case study, transparent compensation and agreement discussion, objections and follow-up.
Depends on: M4.1
Done means: Allison approves both.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 2 to 3

M4.3 · Proposed

Outcome: Forms
Owner: Allison
Next action: Use current approved Texas and broker forms. NORTH does not generate legal forms.
Depends on: Broker
Done means: Current form set confirmed.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 3

M4.4 · Proposed

Outcome: Rehearsal
Owner: Allison + NORTH
Next action: Rehearse one buyer and one seller scenario. No promise to close every prospect.
Depends on: M4.2
Done means: Notes captured and fixes applied.
Launch impact: Improves launch
Source: Proposal · September 25, 2026
Proposed timing: Week 3

M5 Test, approve, then announce · Proposed

Outcome: Soft review passes, then separate explicit approvals for indexing and announcement.
Owner: NORTH + WordPress worker + Allison release approval
Next action: Wait on M2 to M4. Nothing here runs from this planning app.
Depends on: M2, M3, M4
Done means: Soft review closed, release approved, indexing enabled only after that approval.
Evidence required: Soft review completed, technical acceptance recorded, and a separate explicit approval for indexing.
Allison decides: Release approval, indexing and announcement, each separately.
Existing worker: AG Lux Wordpress Build for technical acceptance
Permission needed: Search Console access, only after explicit approval.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4, only if hard gates pass (proposed)

M5.1 · Proposed

Outcome: Soft review
Owner: Allison
Next action: About five trusted reviewers across buyer, seller and relocation on mobile and desktop.
Depends on: M2 to M4
Done means: Findings logged and resolved.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week of October 12 (scenario)

M5.2 · Proposed

Outcome: Technical release checks
Owner: WordPress worker + NORTH
Next action: Fresh backup and recovery, links, redirects, security, accessibility, responsive, performance, metadata, canonical, schema.
Depends on: M5.1
Done means: Checklist recorded with evidence.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4

M5.3 · Proposed

Outcome: Compliance footer
Owner: Allison
Next action: Current IABS, consumer notice, broker, privacy and consent language.
Depends on: Broker
Done means: Links verified live.
Launch impact: Launch blocker
Source: Official external guidance · September 25, 2026
Proposed timing: Week 4

M5.4 · Not yet audited

Outcome: Measurement or approved manual fallback
Owner: NORTH
Next action: Check GA and Search Console access and conversions.
Depends on: Access
Done means: Working measurement or written manual fallback.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week 4

M5.5 · Later

Outcome: Indexing and Search Console approval
Owner: Allison
Next action: Separate explicit approval. Robots stay unchanged until then.
Depends on: M5.1 to M5.4
Done means: Approval recorded, then indexing and sitemap submission.
Launch impact: Launch blocker
Source: Proposal · September 25, 2026
Proposed timing: Week of October 19 (scenario)

M5.6 · Later

Outcome: Warm-network, email and social rollout
Owner: Allison
Next action: Separately authorized. No sends from here.
Depends on: M5.5
Done means: Authorized rollout completed.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: After release

M6 Build authority from real conversations · Later

Outcome: Authority grows from real client conversations and one excellent guide at a time.
Owner: NORTH + Allison
Next action: Starts after release. Not a launch prerequisite.
Depends on: M5
Done means: Day 90 review completed with observed data.
Evidence required: Observed baseline data from real conversations, not assumptions.
NORTH action: Run focused content cycles from the Kingswood reference guide.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: Post-launch 30 / 60 / 90

M6.1 · Later

Outcome: First focused content cycle
Owner: NORTH
Next action: Repurpose the Kingswood guide into insight, short video, LinkedIn, Instagram and Facebook cutdowns and consented email.
Depends on: M3.3
Done means: One cycle shipped with approvals.
Launch impact: After launch
Source: Proposal · September 25, 2026
Proposed timing: Day 30

M6.2 · Later

Outcome: Genuine review process
Owner: Allison
Next action: Verify real baseline first, then voluntary requests only.
Depends on: M3.6
Done means: Process documented and in use.
Launch impact: After launch
Source: Official external guidance · September 25, 2026
Proposed timing: Day 30

30 / 60 / 90

Day 30

Every inquiry accounted for with an owned response handoff.
Actual baseline for contacts, conversations and appointments.
Priority identity corrections complete or waiting on a provider.
First focused content cycle and review process running.

Day 60

Use observed source-to-qualified-consultation data to refine channels and content.

Day 90

Evaluate signed buyer and listing clients, client experience and cost and time per qualified appointment.
Choose the next community or campaign.

Scorecard

Tested public inquiry paths / total paths: Baseline pending
Qualified consumer inquiries: Baseline pending
Buyer consultations: Baseline pending
Listing appointments: Baseline pending
Signed agreements: Baseline pending
Median first human response under chosen coverage: Baseline pending
Source attribution: Baseline pending
Key page index and organic visibility: Baseline pending
Authentic review count and recency: Baseline pending
Consistent priority profiles: Baseline pending

Qualified means a consumer need, location, timing and service fit. Agent coaching is not qualified.
Conversion shows N/A until the denominator is above zero.
AI citation spot checks are exploratory only.
No guaranteed closings or profit.

Partnership

Allison owns: Business decisions, Service promises, Taste and factual approvals, Budget, Regulated and vendor agreements, Client relationships.

NORTH: Retrieves existing sources first, Distills and recommends with tradeoffs, Drafts actual assets, Executes authorized work through available tools, Batches work and verifies outcomes, Updates the shared checkpoint.

Existing Codex and Claude workers own their lanes. Technical website execution stays with AG Lux Wordpress Build under Lovable To WordPress Conversion, not a shadow build. Human gates only for real business decisions, authentication, permission or vendor steps.

Monday, 20 minutes: direction, three outcomes maximum.
Midweek: exception check only if needed.
Friday, 20 minutes: proof review.

What we do next

NORTH checks the evidence first.
NORTH returns the three most important outcomes.
NORTH executes what is already authorized.
NORTH routes technical work into the existing worker lanes.
NORTH returns to Allison only with the next genuinely necessary decision or human gate.

Sources and evidence labels

Phase 1 launch checklist · Current planning data · /launch
Website map · Current planning data · /
Guide drafts directory · Current planning data · /guides/directory
Source playbook PDF (Bailey Kemps Group, July 2026, 8 pages) · Proposal · https://drive.google.com/file/d/1kaf841MFa2rjDgsVUUB2rRwKZ0IwA2Gx/view
Live review website · Fresh public page read · https://agluxurytx.com
WordPress build checkpoint · Implementation checkpoint · https://github.com/ExpertPartners/ag-luxury-site/blob/main/intake/2026-09-24-wordpress-build-checkpoint.md
Brand guide · Owner decision · https://lovable.dev/projects/f5fbb131-ff33-4cc5-915a-fca3385d8c0b
Approved visual source · Owner decision · https://lovable.dev/projects/2b3535c2-f353-410d-ac25-ab0792310f4b
Farming roadmap · Current planning data · https://lovable.dev/projects/1b570f02-998e-4f3b-b407-975413471e7a
Content flywheel · Current planning data · https://lovable.dev/projects/82181ff8-10de-4801-a134-bc1933d625ec
King Ranch sold-property story · Fresh public page read · https://259kingranch.agluxurytx.com