Landing page v6 shipped, the engagement loop still hasn't
A full landing page rewrite went live Wednesday. Backend moved to Render. The reply loop is silent for the 46th day.
We pushed v6 of the landing page live on Wednesday, May 13. Three more sections rolled in on Thursday. By Friday morning the whole page above the fold was new.
What shipped
The Hero, Problem, Solution, ThreeSurfaces, HowItWorks, and FoundingOffer sections are all new copy and new layout. The Pricing block shows the three live tiers in plain numbers: $59 Founding, $129 Pro, $199 Max. A 14 row feature table sits underneath so the gap between tiers is legible. An About section and a VeloRemembers panel give the page a face.
The waitlist scorecard modal got the bigger rewrite. It is a three step flow that collects state, license status, and a four dimension self-score across lead volume, follow up, intelligence, and outreach. The backend gained two new fields, us_state and is_licensed_agent, so we can route founding spots by license region.
On the infrastructure side we moved the API service from Fly to Render per the v7 spec, and finished the monorepo restructure on Tuesday. The apps/landing path is live on Vercel.
What broke
The engagement reply loop is still dormant. It has been silent since April 6, which is 46 days this morning. The scraper is producing files on most weekdays, but the cards count was zero on every day the scraper ran this week, and four of the seven days had no scrape file at all. The reply pipeline is not the bottleneck. The strategy conversation behind it is.
In AI search we have held a 0.0 GEO score for six weeks straight. DealFinder by Homesage.ai owns the Chrome extension category in Perplexity and ChatGPT answers for the third week running, and we have not contested it yet.
What we learned
When the AI summary for "Unvelo real estate" auto corrects to Invelo every time, content alone will not move the needle. The fix is brand authority signal: a press mention, a high DA citation, or sustained branded search volume. We added that to the priority list this morning.
Two of the three blog topics that surfaced in our community scan this week were the same theme, the second touch problem on portal leads, on two platforms, on two different days. That tells us where the next post wants to be written.