Lula โ€” Active work

What Gemma is currently delivering to Lula. Update weekly. This is the anchor doc for every conversation โ€” read first to know current state without re-deriving from chat.

Roadmap source: ../strategy/icp-traffic-roadmap-2026-Q2-Q3.md.

๐Ÿ”” Pending Nate verification

Items awaiting Nate sign-off before shipping. Surface in weekly Friday check-ins until resolved.

ItemBlocked onSentStatusNext action
Cluster 1 lead-magnet popup improvementsLula dev resource (popup template) + Kaytlynn replyFlagged 2026-04-27 in Slack to Kaytlynn โ€” no reply sinceCluster 1 (Work Order Chaos) lead magnet IS LIVE; popup UX needs work per Gemma's note to Kaytlynn. Silent for 2+ weeks.Nudge Kaytlynn (or surface on Friday Nate/Gemma sync). Identify which popup library / template Lula's WP uses; spec the better-popup behaviour (trigger, fields, design); decide whether to handle in-skill or as a dev request. Could potentially fold into the broader popup pattern rollout across all 3 cluster lead magnets.
Cluster 2 (Scheduling) lead magnet โ€” final approval + placement on 5 URLsNate sign-off (final asset approval AND placement format)Rebuilt as "Maintenance Scheduler's Efficiency Toolkit"; final approval + placement asks sent to Nate via Slack 2026-05-12Awaiting Nate's reply on BOTH the final asset approval AND placement format. Placement target: 5 Cluster 2 articles (/articles/maintenance-scheduling-software, /articles/how-scheduling-maintenance-saves-time-and-money, /articles/technician-scheduling-software, /articles/sla-tracking, /articles/foresight-vs-manual-processes). Copy (Option 1, Gemma preferred): headline Stop losing hours to scheduling friction / subhead Free toolkit: checklist, KPI tracker, ROI calculator. / button Get the toolkit.Once Nate replies with final approval + placement format (popup vs inline CTA), deploy across the 5 URLs. Closes Cluster 2 lead-magnet substream loop.
Trello card ayCC5XKP (https://trello.com/c/ayCC5XKP) โ€” closes 3rd Foresight cluster loopNate approval + implementationAsked Nate 2026-05-12 via Slack alongside Cluster 2 placement asksPer Gemma's Slack framing: approval + implementation of this card closes the third (and final) Foresight cluster loop. Card content lives in Trello.Await Nate's approval; once approved, implement per card scope. Closes all three Foresight cluster loops (Cluster 1 + Cluster 2 + Cluster 4 lead-magnet/placement workstream).
/foresight customer quote for trust blockNate (he is checking what's available)Asked 2026-04-27 PMNate replied: "Yes โ€” that's a great question I'll see about." Pending.Once Nate returns a usable customer / pilot quote (Renters Warehouse, MMG, Open Door, or other), add a trust block to /foresight between the FAQ and final CTA. Block includes: customer logo, quote, and the 350,000+ properties served stat.
LuMi launch packageNate positioning sign-off2026-04-10 (package built)Awaiting replyLula Day May 8 deadline. Hard external date. Push by 2026-05-01 or ship without.
Property-maintenance-software listicle โ€” performance metricsNate confirmationSent 2026-06-03LuMi-focused rewrite of the Lula section sent to Nate. Three performance metrics (average turnaround, coordination-start time, maintenance time saved) need client confirmation before they go in the published copy. Verified scale numbers (9,000+ network, 50+ markets, 350,000+ properties, 125,000+ work orders in 2025) are in place meanwhile.On Nate's confirmation, add the three metrics and publish the section; otherwise ship the verified-only version.
Core / Core Boost / Core Premium naming finalizationNate decisionOpen since 2026-02-12In fluxConfirm what tier names are current. Affects all product page content.
Make Ready takeaway form (lead magnet)VP of Make Ready sign-offSent prior to 2026-04-24Awaiting reply (Nate following up)Per 2026-04-24 meeting: Nate to push VP again. Blocks lead capture for entire Make Ready cluster.
Help center subdomain SEO fixesLula dev resource (subdomain owner)Spec sent months agoStale, never actionedResend sharper dated nudge to whoever owns the subdomain. Per 2026-04-24 meeting: ~1 day of dev work; site audit health stuck at 79 partly because of these.
/articles blog archive intro copy โ€” WP-edit investigation needed + master style files permission askWP-edit-method discovery (possible Lula dev resource if theme template) + Nate permission to use master style files in ClaudeInvestigation flagged 2026-04-30; permission ask to be raised at Friday 2026-05-15 Nate/Gemma sync/articles archive page is losing rankings. New intro copy locked: Practical guides for property managers running maintenance at scale. From work orders and scheduling to predictive maintenance, software comparisons, make-ready cycles, and vendor management. Written by the Lula team, grounded in what we see across 350K+ properties. Below: latest posts, most-read guides, and our most popular topics. Replaces an Agent A draft that mis-cited topics ("NTE workflows," "SFR portfolio scaling") and used banned voice ("9,000+ contractor network"). Three possible WP-edit paths to investigate: (1) /articles is a Page with a Posts/Query Loop block โ€” paste a Paragraph block at the top; (2) it's a theme-generated archive โ€” edit the Category description in WP admin โ†’ Posts โ†’ Categories; (3) it's a hardcoded template (archive.php/category.php) โ€” needs dev work. Open question carried over from earlier turn (not resolved): intro uses "vendor management" to match published article titles (Vendor Scorecard / Vendor Onboarding / Vendor Compliance Checklist) at the cost of breaking the brand voice rule that says "Pros" not "vendors." Decided to use "vendor management" for page-coherence with article cards. Voice-rule exception logged.(1) Ask Nate at Friday meeting for permission to use the master style files in Claude (blocks the ship if approval needed). (2) Identify which of the three WP cases applies โ€” quickest test is loading /articles/ on the live site and checking whether the WP admin bar offers "Edit Page" or "Edit Category" or nothing. If editable directly: paste copy + ship. If theme-template: spec for dev resource.

Active delivery streams

1. Make-Ready cluster expansion โ€” HIGHEST PRIORITY โ€” IN PRODUCTION (updated 2026-05-21)

Compounding on the only proven flagship (/articles/what-is-a-make-ready โ€” 273 visits/mo May 2026, 33 keywords, ranks #1 on 10+ commercial-adjacent variants). Cluster strategic plan locked 2026-05-14 via Ahrefs Agent A trial.

  • 6 spokes + money-page rewrite + hub light optimization. Spokes: (1) Checklist, (2) Cost, (3) Timeline, (4) vs Apartment Turnover, (5) Technician (backlink magnet), (6) Reduce Days Vacant (highest commercial intent).
  • Money page rewrite /make-ready-service repositions around commercial intent. Page bled 53 โ†’ 19 visits/mo over 12 months as the hub cannibalized informational queries; needs distinct commercial angle ("near me" / metro / SLA / pricing).
  • Hub link-out edits: add contextual links from existing hub copy to all 6 spokes + new H2 stub pointing at the Checklist spoke.
  • Projected ~1,300 net new visits/mo at 12 months (conservative; assumes pos #3-5 average for spokes; upside if the Checklist PDF-gap is won).
  • Downloadable PDF lead magnet mirrors the Checklist spoke (test gated vs ungated).
  • Status (2026-05-27): Spoke 1 (Checklist) taken through a full brief and article production pass via the Lula skill stack: verified ~2,650-word draft, pending Gemma final read and publish. Money-page rewrite completed by Gemma and signed off. Lead magnet locked: existing "Make-Ready Operations Toolkit" Google Sheet, gated week 1. Hub patch document produced: 9 find-and-replace patches for the live hub article (stale Multifamily Dive citation swapped for NAA 2025 data, the 3-day vs 72-hour inconsistency fixed, 9 to 11 metros, 4 voice hard-stops removed, Spoke 1 cluster-activation link added, fallback anchors reserved for the other 5 spokes), ready to apply in WordPress. Remaining spokes, revised production order with Spoke 5 deferred 2-3 weeks to absorb the Cluster 6 centralized-maintenance spoke pull-forward: 4 (vs Apartment Turnover), 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician) following the Cluster 6 ship. Update (2026-06-01): Spoke 4 (vs Apartment Turnover) is drafted and now in editing. Remaining production order: 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician). Update (2026-06-16, per editorial board): Spoke 2 (Cost โ€” "How Much Does a Make-Ready Cost?") and Spoke 4 (vs Apartment Turnover) are now PUBLISHED. Spoke 1 (Checklist) and Spoke 6 (Reduce Days Vacant โ€” "How to Reduce Days Vacant on Rental Properties") are drafted and sitting in Ready-for-editing. Make-ready lead magnet is queued for WP. Update (2026-06-16, end of day): Spoke 3 (Timeline โ€” "How Long Does a Make-Ready Take?") is now drafted and in Ready-for-editing. Update (2026-06-17): Spoke 5 (Technician โ€” "What Is a Make-Ready Technician?") is now drafted, the backlink-magnet piece with salary benchmarks and a copy-pasteable job description. All six spokes are now published or in editing; the cluster is fully drafted. Remaining: editing passes on Spokes 1, 3, 5, and 6, the make-ready lead-magnet WP load, and the hub light-optimization patch.
  • Canonical metro count: 11 (Atlanta, Cincinnati, Columbus, Dallas, Houston, Indianapolis, Kansas City, Minneapolis, Oklahoma City, Phoenix, St. Louis) โ€” confirmed against the live /make-ready-service page. Hub article + earlier Spoke 1 drafts said 9; Spoke 1 patched to 11. Hub still says 9 (in the hub-optimization scope below).

2. Hub landings ship + activate โ€” LIVE (2026-05-12)

All three Foresight landings now LIVE. Published 2026-05-12 after Nate sign-off at:

  • /predictive-maintenance-software (Cluster 4 โ€” Reactive vs. Predictive Maintenance) โ€” KD 4 / SV 2,600 target.
  • /ai-work-order-software-for-property-managers (Cluster 1 โ€” Work Order Chaos & Triage Bottlenecks).
  • /ai-scheduling-software-for-property-maintenance (Cluster 2 โ€” Scheduling Inefficiency & Technician Burnout).
  • Strategic frame (per Gemma's Slack note): "the idea is to create a number of these types of pages targeting different keywords / entry points to see what sticks." Multi-cluster Foresight surface area, not a single hub.
  • Post-publish wiring verified COMPLETE 2026-05-18: All Cluster 1 + 2 + 4 spokes link to the correct live hub URLs (curl-verified across 8 spokes + 4 Cluster 4 spokes). The 2026-05-15 /blog/property-management-work-order-system buyer's guide also links correctly. /foresight has 2 reciprocal links to each of the 3 new hubs. Live HTML snapshots of all 3 hubs archived to content/drafts/2026-05-18-*-live-snapshot.html.
  • Post-publish work remaining: rewrite brand-led titles on existing spokes (where not already done); resolve open product-team flags (/ai-scheduling-software-for-property-maintenance 5 flags + Smart NTE on work-order page) via surgical edits when product team returns.
  • Nate priority signal (2026-04-24): confirmed Foresight is "front of the line" โ€” landing page + supporting assets need to go deeper. Foresight cluster needs lead magnets + nurture-ready landing pages so leads from each pain point have a pathway. Kaytlynn owns email/nurture downstream; Gemma's scope is the assets.

Lead-magnet substream (closes the loop on each cluster):

  • Cluster 1 (Work Order Chaos): lead magnet IS LIVE. Popup UX needs work โ€” flagged to Kaytlynn 2026-04-27.
  • Cluster 2 (Scheduling): Canva first-pass created over the weekend (pre-Claude). Worth a Claude rebuild to lift design quality before external share.
  • Cluster 4 (Reactive vs Predictive): in-flight today (2026-04-27) โ€” Gemma working on the lead magnet to close the cluster loop.

3. Sitewide "Lula" entity disambiguation

Foundational fix per Apr 4 Google NLP discovery (Lula tagged as PERSON not BRAND).

  • Top 5 pages Week 1.
  • Top 15 pages by Week 4.
  • Pattern: meta + H1 + first body mention as "Lula, the property maintenance software for..." or equivalent.

4. PMS integration page refresh โ€” THESIS NEEDS REVISION (2026-05-18 diagnostic)

Original plan: refresh /buildium, /appfolio, /rentvine, /rentmanager, /propertymeld Weeks 5-8 to capture high-intent commercial demand per Apr 16 traffic analysis ("/buildium punches above its weight"). Buildium diagnostic (2026-05-18) falsifies the SEO premise:

  • /buildium has 0 ranking organic keywords (Ahrefs). 22 weeks of GSC: 84 imp / 0 clicks. Half of those impressions are site-operator/typo noise.
  • All buildium maintenance/work-order/integration query variants return volume 0 in Ahrefs Keywords Explorer. Only buildium integration(s) (vol 50-70, KD 0-1) and buildium api (vol 200, dev intent) have measurable demand.
  • SERP for buildium integrations: Buildium owns 8 of 11 ranked URLs (marketplace, partners, help, blog, customer stories, staging). Only LeadSimple (DR 61) ranks as a true third-party. Lula's realistic organic ceiling is ~40-80 visits/mo even at perfect ranking.
  • The "highest converting PMS integration page" claim from Apr 16 HubSpot analysis is almost certainly measuring direct/branded traffic, not organic search. Lula doesn't use HubSpot โ€” provenance of the claim is itself an open question for Nate.
  • Re-scope direction: treat /buildium (and likely the other 4 PMS pages) as conversion landing pages for direct/branded arrivals, not organic acquisition pages. Run the same 1-hour diagnostic on the other 4 PMS pages before Phase 2 Week 5 to confirm the pattern. If it holds, kill the SEO refresh, reframe as a 5-page conversion-rate-optimization batch + Buildium Marketplace partnership push (out of Gemma scope โ€” partnerships hand-off).
  • Quick wins regardless of Phase 2 direction: fix the /buildium meta description typo ("power" โ†’ "powerful"), add H2s (currently zero), bump dateModified from 2026-01-08 (4 months stale), submit to GSC re-index. ~30 min CMS work.
  • Full diagnostic + refresh spec at work/artifacts/2026-05-18-buildium-diagnostic.md.

5. Geo programmatic SEO (Phase 3) โ€” 16 OF 17 PAGES IN WORDPRESS, READY TO GO (updated 2026-06-16)

17 Lula markets get local make-ready pages from the existing /make-ready/ hub. 16 of 17 are built and loaded into WordPress as preview pages, ready to publish: Atlanta, Cincinnati, Cleveland, Columbus, Dallas-Fort Worth, Dayton, Houston, Indianapolis, Kansas City, Memphis, Minneapolis, Oklahoma City, Orlando, Phoenix, Tampa, and Tulsa. Each page features the market's local W-2 field manager (photo, bio, direct contact), market-specific make-ready content (seasonality, climate, neighborhoods, county coverage, and ZIP-code service area), and a "Talk to a Field Manager" CTA. Counties, neighborhoods, employers, climate, and every ZIP code were fact-checked against public sources and the master coverage sheet. Only St. Louis remains, pending its field-manager details.

  • Atlanta sample page built โ€” full local-SEO city-page template at clients/lula/work/make-ready-city-pages/atlanta.html. Includes on-brand dark statement block, Service + LocalBusiness + FAQPage + BreadcrumbList JSON-LD schema, NAP block, embedded Google Map, county/state variation, 10 city-specific FAQs, and ~50% unique-per-city content target. Iterated to match Nate-call framing (the W-2 field manager coordinates the work; vetted Pros execute it).
  • 17-city data spreadsheet built at clients/lula/work/make-ready-city-pages/city-data-spreadsheet.csv. 13 [LULA] columns for the team to fill (FM name + photo + bio + years, turns YTD per city, vetted Pros count, local phone, GBP URL, customer testimonial, real cost range, lead-paint handling specifics). 11 [RESEARCH] columns pre-populated for every city (avg SFR rent, daily vacancy cost, peak SFR turnover season, days to lease, counties, neighborhoods, ZIPs, climate factors, pre-1978 stock notes, employer/school patterns, Google Maps embed URL).
  • GBP setup note: Each metro needs its own Service-Area Business listing (one per city, FM home address used for verification only, hidden from public profile). 17 listings to claim or create.
  • Markets section wired to city pages (2026-06-17): the make-ready service page now links each of the 16 live-ready metros to its own city page as a button, and every city page links back to the service page. St. Louis shows as a matching placeholder button until its page is built.
  • Structured data written for all 16 pages (2026-06-17): per-city JSON-LD (Service markup with county-level coverage, FAQ, and breadcrumb) is complete and has been passed to Nate to deploy via Google Tag Manager. Worth a quick verification of the phone numbers and the few unconfirmed cost figures before pages and markup go live together.
  • Next: publish the 16 ready pages from WordPress preview to live; Nate to deploy the per-city schema via GTM; build St. Louis once its field-manager details arrive; confirm a local phone line for the few markets still showing a shared number; then Yoast config per city.

7. Cluster 6 pull-forward โ€” centralized maintenance spoke โ€” LIVE (2026-05-29)

Single-spoke pull-forward from Cluster 6 (Disconnected Systems & Visibility Gaps), targeted at portfolio operators across SFR, multifamily, and mixed books. Argues that team-and-software centralization is incomplete without vendor-network centralization, and frames the hidden cost the decentralized vendor layer carries across a portfolio.

  • Published: https://lula.life/articles/centralized-maintenance (2026-05-29).
  • Keyword target: centralized maintenance (KD 0, vol 30, AI Overview present). The "hidden cost of decentralized maintenance" framing sits inside the article rather than in the URL or title.
  • SERP read: active multifamily category conversation (Multifamily Dive, Happy.co guide + podcast, IrisCX LinkedIn) plus industrial-CMMS noise. Lula has zero current presence. Wedge nobody in the SERP makes: vendor-layer centralization is the missing piece. Same structural advantage mapped in the agentic-maintenance synthesis, applied to the current Core services + Foresight + LuMi product line.
  • Scope swap: Make-Ready Spoke 5 (Technician) deferred 2-3 weeks to absorb this work. Logged at work/decisions/2026-05-27-cluster-6-spoke-pull-forward.md.
  • Lead-magnet seed: 5-question "Centralization Gap" assessment inside the article. Candidate for a downloadable scorecard PDF as the Cluster 6 lead magnet.
  • Next: 30-day measurement window 2026-06-28 (rankings, impressions, AI Overview presence on centralized maintenance and related variants).

8. PM-partner PDF backlink program โ€” PDF DRAFTED + DESIGNED, 87 PROSPECTS SOURCED (2026-06-01)

PM-partner outreach campaign locked with Nate 2026-05-28: brand-neutral 2-4 page owner-facing make-ready research PDF distributed to PM companies, who host it as a lead-gen asset for their owner-investor audience. In exchange they place a contextual "learn more about make readies" text link or embed pointing to /articles/what-is-a-make-ready. Expected yield ~10% (Nate's estimate) = ~10 contextual editorial links per 100 PMs pitched.

  • Cluster order: Make Ready (Phase 1, now) โ†’ Foresight (Phase 2) โ†’ Core Services (Phase 3). 100 PMs per cluster.
  • Sender: Nate, outside of sales, additional touchpoint. Does not step on Kaytlynn email/nurture scope.
  • Asset: brand-neutral 5-page owner-forward make-ready research brief (the benefit of a professionally managed make-ready and what it means for owner wealth), repurposed from /articles/what-is-a-make-ready. Drafted + designed 2026-06-01, pending Nate review. Sourcing resolved: cites the 2025 US median single-family rent ($2,100, Rentometer 2025 Annual SFR Report); the Peter Lohmann reference was dropped (latest is a 2024 report with no make-ready/turn data), and the portfolio-wealth math is framed as illustrative on the owner's own turn numbers rather than a claimed national benchmark. Draft at clients/lula/work/backlinks/pdf-draft-makeready-owner-brief-v1.md, spec at pdf-asset-spec.md.
  • Sourcing (2026-06-01): six PMS-vendor ecosystems mined for referring domains (AppFolio, Buildium, Rentvine, DoorLoop, Yardi, Propertyware). Candidates verified individually before listing; brokerages, owner-operators, software vendors, and non-US firms screened out.
  • Master prospect tracker live: Google Sheet with 87 verified US property-management companies in tiers: A (18 with explicit make-ready language on their site, pitch first), B (69 confirmed PMs without explicit make-ready language). Top of Tier A: utopiamanagement.com (multi-state west US, explicit make-ready), cloverleafpropertymanagement.com (San Antonio), managementone.com (SoCal).
  • Sourcing method note: referring-domain mining has reached diminishing returns; each additional vendor now surfaces only a handful of new PMs. The final stretch to 100 will come from vendor customer/case-study pages and the NARPM member directory, which name PMs directly.
  • Revisit 2026-09-28. Kill threshold: fewer than 3 confirmed links by then.
  • Next: Nate review of the PDF (owner-audience tone + factual check), source the remaining ~13 prospects from case-study pages + NARPM, hosting URL slug, and Nate-voiced outreach email draft.

6. Foresight-light competitive intelligence โ€” READY FOR NATE REVIEW (2026-05-25)

Cross-competitor synthesis for the 90-day Foresight-light / autonomous-coordination product build per the 2026-05-22 call.

  • Three competitor deep-dives at clients/lula/competitive/agentic-maintenance/: Vendoroo, Mason (thisismason.com), Haven (usehaven.ai). Each covers product + positioning + pricing + GTM + team, with marketing-usable language banks (verbatim hero copy, taglines, customer testimonials with attribution, voice/tone analysis).
  • Cross-cutting synthesis at _synthesis.md. Like-for-like wedge stack ranked: vendor-network-included as primary (the only structural advantage no competitor can copy in V1), data scale (200K+ work orders) and voice-AI category capture as supporting, multi-language and PM-native team as tactical.
  • Next: cross-reference the named competitor customers against the Lula book to identify at-risk accounts; wedge-stack confirmation with Nate; pricing-model decision (per-door vs per-work-order vs free-software + network-commitment); draft V1 site spec.

Recently completed (last 7 days)

  • 2026-06-23: Apartment-turnover guide tuned for benchmark queries (quick win shipped). Made small on-page search edits to /articles/best-ways-to-cut-down-on-apartment-turnover-time to capture a cluster of low-difficulty benchmark queries sitting one position off page 1: "apartment turnover rate" (volume 200, position 9), "unit turnover" (position 6), and "average tenant turnover rate" (position 8), roughly 370 combined monthly searches at low difficulty. The page already ranks well on its core terms, so these were light surface-the-query edits, not a rewrite, and the published date was intentionally left unchanged. First of the three 2026-06-22 quick wins to land. Next: 30-day measurement window 2026-07-23, re-pull positions on the three benchmark queries; entity-disambiguation pass and /articles archive recovery still to come.

  • 2026-06-23: llms.txt file drafted for lula.life and handed to Nate. Created a curated llms.txt for the site, the emerging standard file that tells AI answer engines what a company is, what it offers, and which pages to trust. It opens with a plain-language description of Lula (the maintenance platform: the 9,000+ Pro network, Foresight software, and the LuMi intelligence layer) and what Lula is not, then points to the key services, software, integration, guide, and company pages. Hand-written rather than auto-generated, so the positioning, page selection, and category framing are deliberate rather than a raw page dump. Every linked page was checked live. Came with a short implementation guide covering exactly where the file has to live and the cleanest way to publish it on WordPress. Next: Nate / dev to host it at lula.life/llms.txt, then confirm it loads.

  • 2026-06-23: Integrations page structured-data error diagnosed, fix handed to Nate. A validation check flagged one remaining issue on the Integrations page: a parsing error in the page's structured data ("Missing '}' or object member name"), which makes the affected items invalid and ineligible for Google's rich results. Traced to a single malformed spot in the schema where one object was never closed before the next began. The fix is a one-line correction (close the open object and add the separating comma). Pinned the exact location and change in the Trello card. Next: apply the one-line schema fix, then re-validate to confirm the page is rich-results eligible.

  • 2026-06-22: Maintenance Budget Calculator landing page built. A new interactive tool for property managers: enter your monthly work-order volume, average invoice, and how much a job's cost tends to swing, and see the annual maintenance budget range that variable pricing leaves you forecasting against, the spread you cannot plan around. It carries the Flat-Rate predictability story, with a plain-language readout of what the number means, a short note on how it is calculated, a clear disclaimer, and a book-a-demo path. Styled to the Lula site with a new hero illustration and supporting card icons. Next: publish at /flat-rate-maintenance-calculator, then connect the lead-capture form so each result becomes a qualified lead with its portfolio numbers attached.

  • 2026-06-22: Three quick-win search optimizations surfaced and underway. A scan of pages sitting just off page 1 surfaced three low-effort, high-leverage moves. (1) Add a benchmark-rate block to the apartment-turnover guide to capture "apartment turnover rate" and "unit turnover," both one position off page 1 (about 370 combined monthly searches). (2) Resume the sitewide "Lula" brand-entity fix on the top pages, where the homepage still ranks only around 12th for the brand name itself. (3) Recover the /articles blog archive, which is slipping on "property management blog" and "property managers blog" (positions 5 and 7). Next: ship the turnover block, run the entity pass on the top five pages, and confirm the archive edit path.

  • 2026-06-18: Flat-Rate Handyman launch content produced. A full content set for the Flat-Rate Handyman push: a content program brief that gives blog, social, and email one shared positioning and messaging foundation; a blog announcement; a conversion landing page built in the make-ready page style (hero catalog visual, a three-step walkthrough with custom step graphics, and the customer-success image in the closing call to action); and a press release. Grounded in fresh property-manager research, with the through-line that predictable, transparent, catalog-based pricing turns maintenance from a churn risk into a retention win. Next: finalize against Nate's edits, confirm the demo form and a couple of open product details, then publish to land with the launch.

  • 2026-06-17: Broken-link audit reviewed and handed to Nate. A site audit flagged broken outbound links across ~36 pages. Diagnosed down to a single real issue: a dead Google Play app-badge link living in a footer block that is hidden from view, so no visitor ever sees or clicks it. Cleanest fix is removing that hidden block from the footer template, which clears every flagged page at once. The AppFolio badge links also flagged but are false positives (AppFolio blocks the audit crawler; the links return 200 for real visitors and for Google). Info passed to Nate. Next: Nate / dev to remove the hidden footer block, then re-run the audit to confirm the flags clear.

  • 2026-06-16: Three on-page optimizations shipped across the article library. Surgical edits to three ranking articles to push high-intent queries sitting just off page 1. (1) /articles/deferred-maintenance gained three internal links from related maintenance articles to build topical authority behind "what is deferred maintenance in real estate" (position 7, already position 2 on the core term). (2) /articles/best-property-management-software had its intro, a section heading, and an FAQ reworded to capture "property management software ratings" and "most popular property management software" (positions 11-12, roughly 400 combined monthly searches). (3) /articles/rental-inspection-checklist had a section heading and a sentence updated to target the "routine" and "quarterly" rental inspection checklist queries (positions 7-10). Next: 30-day measurement window 2026-07-16.

  • 2026-06-16: 16 of 17 local make-ready market pages built and loaded into WordPress, ready to publish. Atlanta, Cincinnati, Cleveland, Columbus, Dallas-Fort Worth, Dayton, Houston, Indianapolis, Kansas City, Memphis, Minneapolis, Oklahoma City, Orlando, Phoenix, Tampa, and Tulsa each have a full local market page: the market's W-2 field manager front and center (photo, bio, direct contact), make-ready content tailored to that metro (seasonality, climate, neighborhoods, county coverage, and ZIP service area), and a "Talk to a Field Manager" call to action. Every page's counties, neighborhoods, employers, climate, and ZIP codes were fact-checked against public sources and the master coverage sheet before load-in. Next: publish from preview to live, link them from the main /make-ready/ markets section, and build St. Louis once its field-manager details arrive (the only market still outstanding).

  • 2026-06-09: Bing crawl throttle cleared. Bing Webmaster Tools flagged a High-severity "limited crawl capacity" recommendation. Root cause was a crawl-rate setting in Webmaster Tools held at the slow band across every hour of the day, capping how much Bing would crawl. Lifted it to full crawl rate around the clock. robots.txt and the sitemaps were already clean (no parameter sprawl or low-value URLs to exclude), so this was the only lever. The recommendation clears on Bing's next crawl pass. Next: confirm it drops off the Webmaster Tools recommendations within a week.

  • 2026-06-08: Maintenance performance claims corrected across the content set. Removed the unverified "80% one-trip resolution rate" stat (an industry-benchmark figure from the Vendor Performance Scorecard lead magnet, not a Lula performance metric) along with the unsupported "3.8-day turnaround," "coordination within 10 minutes," and "60 to 65% reduction in coordination time" claims wherever they appeared in body copy. Each was reframed onto verified scale proof (9,000+ maintenance Pros, 350,000+ properties served) while keeping the original benefit framing intact: fewer repeat visits, less resident disruption, freed coordinator capacity for renewals. Affected the LuMi landing, the maintenance-scheduling, AI-work-order, AI-scheduling, and predictive-maintenance hub surfaces, plus the lease-renewal retention and downtime/repair-delay pieces. Next: the three performance metrics Nate is confirming (average turnaround, coordination-start time, maintenance time saved โ€” see Pending) can drop back in once verified.

  • 2026-06-05: Source7 partnership announcement article published at https://lula.life/articles/source7-foresight-integration. The partner-supportive piece for Source7 (the appliance-data company integrated into Lula) went live alongside Source7's PR Newswire press release. Predictive-maintenance / repair-vs-replace angle, dropping into the preventive-maintenance cluster and reinforcing the 200,000+ work orders data-volume story. Strengthens the Foresight narrative through the Source7 integration and gives Lula a citable asset on the partnership. Next: monitor for citation pickup; 30-day measurement window 2026-07-05.

  • 2026-06-02: AI property management software comparison article drafted (competitive response to Vendoroo's organic surge). Nate flagged a competitor's sudden organic increase on AI-property-management queries; analyzed their ranking page + AEO visibility and built a sharper version, Best AI Property Management Software in 2026 (target keyword ai property management software), ranking Lula first for AI maintenance coordination (LuMi + Foresight) on the "automate your costliest workflow first" thesis. Ready for editing, not yet live. Next: editing pass, then publish.

  • 2026-06-05: LuMi announcement article revised and aligned to the approved positioning. Reworked the product announcement article (/articles/lumi-ai-maintenance-intake) against the May 2026 LuMi Positioning Brief. LuMi now leads as Lula Maintenance Intelligence, the AI behind every maintenance experience, with intake framed as how it shows up here rather than as a standalone product. Added the approved data-credibility block (7 years, 500K+ work orders, 50+ markets, always learning) and swapped in approved proof points (70% fewer re-calls, 9,000+ Pros, 3.8-day turnaround). Removed the inaccurate "80% one-trip resolution" claim and tightened the voice (no contrast framing, no em dashes). Next: holds for the launch go/no-go; the 70-80% handle rate and the Brandywine/Truehold/Bridge customer references still need Nate's confirmation before publish.

  • 2026-06-03: Property-maintenance-software listicle updated, Lula section reworked around LuMi. Surgical on-page edits to /articles/best-property-management-maintenance-software (the cluster's top organic workhorse, #1 on best property maintenance software-family queries) to firm up rankings after recent mixed tracking signals. The Lula entry was reworked to center LuMi as the AI layer running maintenance coordination end to end, with Foresight positioned for in-house teams. Section sent back to Nate for review. Next: confirm the flagged performance metrics with Nate (see Pending), then finalize; 30-day measurement window 2026-07-03.

  • 2026-06-01: Make-Ready Spoke 4 (vs Apartment Turnover) drafted and in editing. Full spoke produced distinguishing the apartment-turnover lifecycle from the make-ready subset: a quick-answer summary, side-by-side comparison, the ten-stage turnover process, the KPIs that matter (days vacant, turnover rate, vacancy loss, cost per turn), and reduction levers, all on an owner-facing angle. Now in an editing pass before publish. Next: finalize edits and publish; remaining production order is Spoke 6 (Reduce Days Vacant), 2 (Cost), 3 (Timeline), then 5 (Technician).

  • 2026-06-01: Make-Ready PDF partner prospect list extended to 87 verified PMs. Added two more PMS-vendor ecosystems (Yardi, Propertyware) to the earlier four, taking the sourcing pool to six. After individual verification, with brokerages, owner-operators, software vendors, and non-US firms screened out, the master tracker holds 87 confirmed US property-management companies: 18 with explicit make-ready language and 69 confirmed PMs. Referring-domain sourcing has reached diminishing returns (each added vendor now surfaces only a handful of new PMs), so the final stretch to 100 will come from vendor customer/case-study pages and the NARPM member directory. Next: source the remaining ~13, then hosting URL slug and Nate-voiced outreach email.

  • 2026-06-01: Make-Ready owner-facing PDF drafted and designed. The brand-neutral 5-page research brief for the PM-partner backlink program is written and laid out (cover, what a managed make-ready is, the owner-facing case, the wealth angle, and a five-question checklist for owners to use on any manager). Sourcing was resolved cleanly: the 2025 US median single-family rent is cited from the Rentometer 2025 Annual SFR Report ($2,100/mo), the portfolio-wealth math is presented as illustrative on the owner's own turn numbers, and a planned Peter Lohmann citation was dropped after the latest edition turned out to be a 2024 report with no make-ready data. No CTA, light Lula attribution, reads as research. Next: Nate review for owner-audience tone and any factual corrections, then hosting URL and outreach.

  • 2026-05-29: PM-partner PDF backlink program scoped end-to-end and 85 prospects sourced. Strategic call 2026-05-28 with Nate locked the campaign shape (brand-neutral owner-facing PDF distributed to PM companies as a lead-gen asset, link back to /articles/what-is-a-make-ready in exchange). Built the sourcing pipeline today: four PMS-vendor referring-domain CSVs (AppFolio, Buildium, Rentvine, DoorLoop) processed through a Python filter, 2,893 unique domains classified, top candidates WebFetch-verified via subagent runs. Master tracker live as a Google Sheet (lula-prospect-tracker-makeready-2026-05-29) with 85 prospects in 3 tiers: 18 Tier A (explicit make-ready signal on homepage, pitch first), 64 Tier B (confirmed PMs without explicit make-ready language), 3 Tier C (manual verification needed). Cross-vendor confirmed in 20 cases. Next: one more vendor CSV to clear 100, PDF design ownership decision, hosting URL slug, Nate-voiced outreach email.

  • 2026-05-29: Cluster 6 centralized-maintenance spoke shipped live. Published at https://lula.life/articles/centralized-maintenance. First Cluster 6 surface area for Lula, targeting centralized maintenance (KD 0, vol 30, AI Overview present) with the vendor-network-centralization wedge no competitor in the SERP makes. Next: 30-day measurement window 2026-06-28; consider productizing the in-article "Centralization Gap" assessment as the Cluster 6 lead magnet.

  • 2026-05-25: Make-Ready city-page expansion produced. Atlanta sample page built (full local-SEO city-page template with branded dark statement block, schema, NAP, embedded Google Map, county/state variation, 10 city-specific FAQs). 17-city data-collection spreadsheet built with 13 [LULA] columns for the team to fill and 11 [RESEARCH] columns pre-populated per city (avg SFR rent, daily vacancy cost, peak season, days to lease, counties, neighborhoods, ZIPs, climate factors, pre-1978 stock notes, employer/school patterns, Maps URL). Next: Lula team fills the team-side columns; templated rollout of remaining 16 city pages follows.

  • 2026-05-25: Agentic-maintenance competitive intel + Foresight-light positioning produced. Three competitor deep-dives (Vendoroo, Mason, Haven) plus cross-cutting synthesis with a ranked like-for-like wedge stack led by vendor-network-included. Next: wedge-stack confirmation with Nate, pricing-model decision.

  • 2026-05-21: Make-Ready hub patch produced. Generated the find-and-replace patch set for the live /articles/what-is-a-make-ready hub: 9 patches covering stale-stat swaps to NAA 2025 data, the 3-day vs 72-hour fix, 9 to 11 metros, voice fixes, and the Spoke 1 cluster-activation link. Next: apply the patches in WordPress.

  • 2026-05-20: Make-Ready Spoke 1 (Checklist) brief and article produced, lead magnet and 2 content rules locked. Full Spoke 1 production pass via the Lula skill stack: a zero-ambiguity brief plus a verified ~2,650-word article draft, voice-clean, pending Gemma final read and publish. Lead magnet locked: Gemma's existing Google Sheet repositioned as "The Make-Ready Operations Toolkit," gated week 1, with a printable PDF mirror to design. Money-page rewrite done by Gemma and signed off. Two content rules locked for all future work: 2025-or-newer stats only, and no fabricated operational provenance. Next: hub patch, then Spokes 4, 6, 2, 3, 5.

  • 2026-05-18: /buildium pre-Phase-2 diagnostic and hub-landing wiring verified. Confirmed all 3 Foresight hub landings live and all 12 Cluster 1, 2, and 4 spokes plus the buyer's guide linking correctly. The /buildium diagnostic found near-zero organic search demand, so the page should be reframed as a conversion landing for direct and branded traffic rather than an SEO play. Next: run the same diagnostic on /appfolio, /rentvine, /rentmanager, and /propertymeld before Phase 2 Week 5. Full spec at work/artifacts/2026-05-18-buildium-diagnostic.md.

  • 2026-05-15: Make-Ready cluster execution kicked off. Strategic plan locked 2026-05-14: 6 spokes plus money-page rewrite plus hub optimization, projected ~1,300 net new visits per month at 12 months. 4 of 6 spoke drafts produced as Google Docs (Checklist, Cost, vs Apartment Turnover, Reduce Days Vacant). Next: Spokes 3 and 5, money page, and hub edits over the following weeks.

  • 2026-05-15: Cluster and internal-link map shipped to lula.propsaasgrowth.com/map. New dashboard surface visualizing Lula's topical clusters and internal link graph: 244 indexable pages with URL rating, traffic, and inlink counts, plus orphan and authority-concentration findings. Refresh runbook at operations/cluster-map-refresh.md.

  • 2026-05-15: property management work order system buyer's guide shipped live (Cluster 1). Published a 2,157-word buyer's guide at /blog/property-management-work-order-system, built with the full Lula skill stack, voice gates passed. Closes the Cluster 1 buyer's guide loop opened 2026-05-08. Next: 30-day measurement window 2026-06-14, and wire the reciprocal link from the Cluster 1 hub.

Open items pending Nate input

  • LuMi launch go/no-go + customer-name permissions (Brandywine/Truehold/Bridge) + handle-rate confirmation (positioning now signed off)
  • Core / Core Boost / Core Premium naming current state
  • Attribution stack clarity for demo attribution โ€” needed for lagging indicators
  • Per-URL GSC data on 10 priority Foresight-cluster articles (Gemma can pull, but Nate access useful for some)
  • Provider-recruitment geo page duplicate audit โ€” flag and prioritize Q3 if needed

What we're explicitly NOT doing this quarter

(See strategy/icp-traffic-roadmap-2026-Q2-Q3.md for full list.)

  • New blog content on Clusters 5-8 (After-Hours, Disconnected Systems, Inventory/CapEx, Training)
  • More Foresight/predictive blog spokes (existing get title rewrites + link wiring; no new)
  • AEO citation tracker build (defer to Q3)
  • Wikipedia attempts (defer indefinitely)
  • Tangential blog posts (lease renewals, fair housing, landlord-tenant disputes)
  • Help center subdomain SEO

Standing meetings + reporting rhythm

  • Weekly check-in (Fridays, ~30 min): Gemma + Nate. Shipped, blocked, next.
  • Monthly check-in (last Friday of month, ~45 min): Phase vs plan; update this file.
  • Quarterly revisit (2026-07-23, ~90 min): Full scope review; update audit + roadmap.

Tools / infrastructure in use

  • Ahrefs MCP (via Claude) โ€” domain + per-URL data
  • GSC (Gemma access) โ€” URL Inspection + queries
  • Looker Studio โ€” dashboards
  • Surfer SEO โ€” content optimization
  • WordPress + Yoast โ€” CMS
  • Trello โ€” editorial pipeline (Nate edits)
  • Microsoft Clarity โ€” page behavior
  • 27+ Lula-specific Claude Skills โ€” content production stack
  • GitHub repo (nateatlula/Lula-mrktng-Claude-skills) โ€” skills versioning
  • Foresight Master Copy Deck 2026 โ€” source-of-truth for positioning (Bo-approved)

Update cadence for this file

  • Weekly: Update "Pending Nate verification," "Active delivery streams," and "Recently completed." Move any "Recently completed" entry past 7 days into active-work-archive.md so the section stays scannable.
  • Monthly: Roll up and review delivery streams.
  • Quarterly: Full review; update against roadmap; retire/add streams.