Day 43: The page every confused visitor needed — and a framework upgrade that couldn't wait

Day 43 split into two halves that had nothing to do with each other. The morning was a framework security upgrade — quiet, technical, necessary. The evening was the biggest single page built since launch prep started: a full /how-it-works walkthrough that treats the visitor like an adult and shows them exactly what they are buying before asking for anything.

Both were overdue. The security work had been deferred one day to give it the dedicated session it needed. The how-it-works page had been a hash-anchor placeholder for 43 days. Today both closed.

The security session

Earlier this week we ran a full pre-launch dependency audit and found 4 advisories in the tree. Two were transitive — isolated, low-blast-radius, closed with a single command. The remaining two were tied to the framework itself and needed more care: a local build verification, a full end-to-end pass across every critical path, and a clean rollback plan ready if anything broke.

Today was that session. We bumped the framework version — five patches forward. Local build passed. TypeScript came back clean. Every page prerendered without complaint. Then we deployed and verified manually: the signup flow, login, OAuth handshake, Stripe checkout, middleware redirects on protected routes, image rendering, the admin gate, and the full dashboard surface. All clean. Zero regressions.

One advisory remains. It lives inside a bundled dependency in the framework's own internals — there is no fix path available without a catastrophic downgrade that would break more than it fixes. It stays logged, accepted, and documented. We will revisit it when the framework team ships a resolution. That is the honest state of things, and pretending otherwise would be worse than admitting it.

The page that should have existed on day one

For 43 days the header said "How it works" and pointed at a homepage anchor that did not always scroll to the right place. A visitor who wanted to understand the product before committing — not just the surface pitch, but the actual mechanics, the tier differences, what they could and could not do on each plan — had nowhere to go.

That changed today.

The page that shipped is built around a sticky left sidebar with seven jump links, the same nav pattern we used on the Help Center. The hero makes no sales pitch. It just says: here is everything. Use the sidebar.

"How it works" — three steps, each one honest about what is happening technically. Connect your Google Business Profile via official OAuth (your credentials never touch our servers). Reviews flow into the dashboard automatically. You get an AI-drafted reply for every review — edit it, approve it, or ignore it. Nothing posts to Google without your explicit action. We describe all three steps in plain terms because that is what a cautious business owner actually needs to read before trusting a new tool with their public reputation.

Noob section — an HTML/CSS mockup of the dashboard as a Noob user actually sees it. A stats bar with four real cards: total reviews, last review with star rating, a response timer that turns red when a review has been unanswered past 48 hours, and average rating with trend. A review feed with three sample rows showing names, stars, review text, and a Replied/No reply badge. Then three blurred locked panels — Your Impact, Performance Analytics, AI Insights — showing exactly what the visitor cannot access yet. An annotation grid explains what every element does. Then a plain "What Noob cannot do" callout: no email alerts, 10-review monthly cap, 5 AI drafts only, no direct posting to Google, no analytics. Honest limitations, not hidden in fine print.

Chad section — the full unlocked dashboard. Instant alerts wired to the notifications panel. AI replies with an SVG rating trend chart for the performance panel. Three analytics cards (time saved, rating lift, revenue impact). AI Insights cards in red/green/gold. A settings mockup showing the toggle UI, star filter pills, and digest selector. Annotation grid for each panel. Then a "What Chad cannot do" callout: no competitor tracking, no team accounts, no review generation, no AI tone learning, no report card. Pointing honestly upward to GigaChad.

GigaChad section — gold-accented browser chrome. Competitor tracking as a horizontal bar chart with your business vs two competitors — rating, review count, and a proportional bar. Team seat UI with owner and two invite slots. An annotation grid covering every GigaChad-only feature: smart filters, full alert preferences, competitor tracking, team accounts, review generation, AI tone learning, monthly report card, priority support. A why-upgrade callout that makes the ROI case without overselling — one extra customer per month from a stronger reputation covers the cost.

Comparison table — all three tiers, every feature, grouped by category. No cards, no soft comparisons, no asterisks. A table. See the full pricing page linked in the intro.

The design principle behind all of it: show the locked panels, show the limits, show the price. A visitor who understands exactly what they get on each tier and still upgrades is a better customer than one who was surprised later. We also dropped /roi-calculator and /waitlist links in the get-started section at the bottom for visitors who are ready to act.

The nav audit that came out of it

Building the how-it-works page forced a full walk through the header and footer. Every link that was pointing at a hash anchor or a bare # got catalogued.

Several were fixable on the spot. The footer had a duplicate Help Center link — both the Resources column and the Company column had one, and the Resources version was broken. Removed. The "How it works" links in the header and footer were pointed at #how-it-works (a homepage section anchor); both now point at /how-it-works. That is the kind of fix that feels embarrassingly simple once you see it.

The remaining broken links are intentional for now. The FAQ links in the header and footer still point at a homepage anchor — that resolves when /faq ships in the next few days. Review Generation and Competitor Tracking stay as # with "coming soon" badges until the GBP API goes live on July 23. Everything is catalogued. Nothing is invisible.

---

Day 43 felt like clearing debt. Security debt, navigation debt, content debt. Three different categories, one session.

The how-it-works page is the page a confused visitor lands on after the homepage doesn't quite answer their question. It is the page that earns trust before the ask. We had been sending people to the /pricing page to understand the tiers, which is the wrong order — pricing answers how much, not what. /how-it-works answers what. Now both pages exist and point at each other.

The session ran long. Security in the morning, how-it-works in the evening, nav audit as a side effect. But a product this close to launch needs a page that tells the full story without asking the visitor to piece it together from five separate feature pages. We have that page now. That is worth more than another feature stub.