r2r page optimization

Author: Thomas Stromberg

src/products/ready-to-review.njk

@@ -16,35 +16,50 @@ title: Ready to Review - Eliminate PR coordination overhead
           <img src="/assets/review-goose.png" alt="Review Goose managing pull requests" style="width: 150px; height: 150px; flex-shrink: 0;" />
         </picture>
         <div style="flex: 1; min-width: 250px;">
-          <p style="margin: 0 0 10px 0; font-size: 20px; font-weight: 700; color: #333;">Eliminate PR coordination overhead</p>
-          <p style="margin: 0; font-size: 16px; line-height: 1.5; color: #333;">Ready to Review runs a deterministic state machine over every pull request to automatically determine the optimal next action and the right person to take it. From intelligent reviewer assignment to turn-based clarity, it eliminates the coordination overhead that keeps PRs in limbo.</p>
+          <p style="margin: 0 0 10px 0; font-size: 24px; font-weight: 700; color: #333;">ELIMINATE PR COORDINATION OVERHEAD.</p>
+          <p style="margin: 0; font-size: 18px; line-height: 1.5; color: #666;">Clear accountability. Instant visibility. Zero management overhead.</p>
         </div>
       </div>
     </div>
 
     <div style="background: var(--black); border: 8px solid var(--cyan); border-radius: 20px; padding: 30px; margin: 40px 0; box-shadow: 0 8px 24px rgba(0, 0, 0, 0.4);">
       <h2 style="margin-top: 0;">THE PROBLEM</h2>
-      <p style="font-size: 18px; margin-bottom: 20px;"><strong>Most engineering teams lose 10-15% of throughput to PR coordination overhead.</strong> For a 20-person team, that's roughly <strong>$1M annually</strong> in lost productivity.</p>
+      <p style="font-size: 18px; margin-bottom: 20px;"><strong>Most engineering teams lose 10-15% of throughput to PR coordination overhead.</strong> For a 20-person team, that's <strong>$1M annually</strong> in lost productivity. Or 2-3 engineers worth of capacity just... gone.</p>
 
-      <p><strong>Root cause:</strong> PRs take 4.5 days to merge on average because GitHub's notification system creates ambiguity—nobody knows who's responsible for moving a PR forward at any given moment.</p>
+      <p><strong>Root cause:</strong> GitHub's notification system creates ambiguity. Nobody knows who's responsible for moving a PR forward. So PRs sit for 4.5 days on average.</p>
 
-      <p><strong>The impact:</strong> Ready-to-Review brings merge time down to <strong>under an hour</strong> (20X faster), eliminating coordination overhead and reclaiming that lost throughput.</p>
-
-      <p style="margin-bottom: 0;"><a href="https://cost.github.codegroove.app/?mode=org">Calculate your team's cost savings →</a></p>
+      <p style="margin-bottom: 0;"><strong>The real cost:</strong> Frustrated engineers. Constant context switching. Endless status questions in stand-ups and Slack. Nobody's happy.</p>
     </div>
 
     <div style="background: var(--black); border: 8px solid var(--cyan); border-radius: 20px; padding: 30px; margin: 40px 0; box-shadow: 0 8px 24px rgba(0, 0, 0, 0.4);">
       <h2 style="margin-top: 0;">OUR SOLUTION</h2>
+      <p style="font-size: 18px; margin-bottom: 20px;">Ready-to-Review <strong>actively manages your PR workflow</strong>. Merge time drops from 4.5 days to <strong>under an hour</strong>. That's 20X faster. Get that 2-3 engineers worth of capacity back—without hiring.</p>
       <ul style="font-size: 16px; line-height: 1.8;">
-        <li><strong>Intelligent reviewer assignment</strong>: Analyzes your diff to find engineers who last modified the specific lines you're changing, balanced by current workload. No more random assignments or hunting for context.</li>
-        <li><strong>Turn-based clarity</strong>: Always knows whose turn it is (author or reviewer) and what needs to happen next. Review it, fix tests, respond to feedback, or merge. No guessing, no ping spam.</li>
-        <li><strong>Multi-channel notifications</strong>: Native desktop alerts via <a href="https://github.com/codeGROOVE-dev/goose">Goose</a> (macOS, Linux, Windows) that auto-open PRs when you're needed, plus Slack integration for team coordination. Get notified at the right moment, not constantly.</li>
-        <li><strong>Full lifecycle tracking</strong>: Manages PRs from creation through merge, identifying bottlenecks and nudging the right people at the right time. Complete visibility across your entire organization without configuration.</li>
+        <li><strong>Intelligent reviewer assignment</strong>: Routes PRs to engineers who actually touched the code. Balanced by workload. Better reviews. Faster merges.</li>
+        <li><strong>Turn-based clarity</strong>: Always knows whose turn it is. What needs to happen next. No more status meetings. No more Slack ping-pong.</li>
+        <li><strong>Multi-channel notifications</strong>: Native desktop alerts via <a href="https://github.com/codeGROOVE-dev/goose">Goose</a> (macOS, Linux, Windows) and Slack. Get notified at the right moment. Not constantly.</li>
+        <li><strong>Org-wide visibility</strong>: Track every PR across your entire organization. Zero configuration. Spot bottlenecks. Recognize contributors. Measure improvement.</li>
       </ul>
+      <p style="margin-top: 20px; margin-bottom: 0;"><a href="https://cost.github.codegroove.app/?mode=org">Calculate your team's cost savings →</a></p>
+    </div>
+
+    <div style="background: linear-gradient(135deg, var(--yellow) 0%, #ffd700 100%); border: 8px solid var(--black); border-radius: 20px; padding: 40px; margin: 40px 0; box-shadow: 0 8px 32px rgba(255, 215, 0, 0.5); text-align: center;">
+      <p style="font-size: 32px; font-weight: 900; margin: 0 0 15px 0; color: var(--black); text-transform: uppercase; letter-spacing: 1px;">🚀 SHIPPING NOVEMBER 17, 2025</p>
+      <p style="font-size: 20px; margin: 0; color: var(--black); font-weight: 600;">For engineering teams and open-source projects worldwide.</p>
     </div>
 
-    <h2>VIDEO</h2>
-    <p>Coming soon!</p>
+    <h2>HOW IT WORKS</h2>
+    <div style="background: var(--black); border: 8px solid var(--cyan); border-radius: 20px; padding: 30px; margin: 40px 0; box-shadow: 0 8px 24px rgba(0, 0, 0, 0.4);">
+      <p style="font-size: 18px; margin-bottom: 20px;">A <strong>deterministic state machine</strong> tracks every PR in your organization. Knows who should act next. Knows what needs to happen. Clear accountability. Zero manual coordination.</p>
+
+      <h3 style="color: var(--yellow); margin-top: 30px; margin-bottom: 15px;">BUILT FOR SCALE</h3>
+      <ul style="margin: 0; padding-left: 20px;">
+        <li style="margin-bottom: 12px;"><strong>Global teams</strong>: Timezone-aware. Assigns reviewers during their active hours. Works for distributed teams.</li>
+        <li style="margin-bottom: 12px;"><strong>Analytics</strong>: Team leaderboards. Contributor recognition. Bottleneck identification. Track velocity improvements.</li>
+        <li style="margin-bottom: 12px;"><strong>Zero config</strong>: Works with your existing GitHub workflow. No training. No process changes. Install and go.</li>
+        <li style="margin-bottom: 0;"><strong>Security-first</strong>: Minimal GitHub permissions. Choose which repos to monitor. No code access required.</li>
+      </ul>
+    </div>
 
     <h2>SCREENSHOTS</h2>
     <div class="screenshot-grid">
@@ -86,26 +101,6 @@ title: Ready to Review - Eliminate PR coordination overhead
       </figure>
     </div>
 
-    <div style="background: var(--black); border: 8px solid var(--yellow); border-radius: 20px; padding: 30px; margin: 40px 0; box-shadow: 0 8px 24px rgba(0, 0, 0, 0.4);">
-      <h2 style="margin-top: 0; color: var(--yellow);">WHAT MAKES THIS DIFFERENT</h2>
-      <p style="font-size: 18px; line-height: 1.6;">Unlike analytics dashboards that just show you the problem, Ready-to-Review <strong>actively manages your PR workflow</strong>. It makes intelligent decisions about who should act next and ensures they know about it — without overwhelming anyone.</p>
-      <p style="margin-bottom: 0; font-size: 18px; line-height: 1.6;">Built by engineers who got tired of watching PRs sit idle while everyone assumes someone else is handling it.</p>
-    </div>
-
-    <h2>HOW IT WORKS</h2>
-    <div style="background: var(--black); border: 8px solid var(--cyan); border-radius: 20px; padding: 30px; margin: 40px 0; box-shadow: 0 8px 24px rgba(0, 0, 0, 0.4);">
-      <p>At the core of Ready to Review is a <strong>deterministic state machine</strong> that constantly analyzes every PR to determine who should act next and what they should do. It understands the full PR lifecycle — from initial assignment through reviews, change requests, updates, approvals, and merge.</p>
-
-      <h3 style="color: var(--yellow); margin-top: 30px; margin-bottom: 15px;">Additional Capabilities</h3>
-      <ul style="margin: 0; padding-left: 20px;">
-        <li style="margin-bottom: 12px;"><strong>Timezone intelligence</strong> - Assigns reviewers during their active hours and adjusts notifications based on work patterns</li>
-        <li style="margin-bottom: 12px;"><strong>Team analytics</strong> - Identify patterns, celebrate contributors, measure real improvement with leaderboards and insights</li>
-        <li style="margin-bottom: 0;"><strong>Security-conscious</strong> - Minimal permissions required, select just the GitHub repos you want to enable access to</li>
-      </ul>
-
-      <p style="margin-top: 30px; margin-bottom: 0;"><strong>Result: 20X faster code reviews — but don't take our word for it, <a href="https://cost.github.codegroove.app/?mode=org">measure your own improvement</a></strong></p>
-    </div>
-
     <h2 id="pricing-section">PRICING</h2>
     <div class="pricing-grid" role="list" aria-labelledby="pricing-section">
       <article class="pricing-tier" role="listitem" aria-labelledby="tier-grassroots">
@@ -181,15 +176,15 @@ title: Ready to Review - Eliminate PR coordination overhead
 
     <div class="info-box" style="margin-top: 40px;">
       <p class="info-box-highlight">All plans are billed through the GitHub Marketplace</p>
-      <p>Start with Community (free forever) and upgrade anytime. Paid plans include a 2-week free trial. No credit card required to get started.</p>
+      <p>Start with Grass Roots (free forever) and upgrade anytime. Paid plans include a 2-week free trial. No credit card required.</p>
     </div>
 
     <h2>GET STARTED</h2>
     <div class="groove-card groove-card--yellow" style="text-align: center; padding: 40px;">
-      <p style="font-size: 24px; font-weight: 700; margin-bottom: 20px; color: var(--white);">Ready to merge 20X faster?</p>
-      <p style="margin-bottom: 30px; font-size: 18px; color: var(--white);">Sign up takes 30 seconds. Free for open source projects, forever.</p>
-      <a href="https://github.com/apps/ready-to-review-beta" role="button" aria-label="Install Ready to Review GitHub App" style="display: inline-block; background: var(--cyan); color: var(--black); padding: 16px 32px; border-radius: 8px; text-decoration: none; font-weight: 700; font-size: 18px; transition: transform 0.2s, box-shadow 0.2s; box-shadow: 0 4px 12px rgba(92, 225, 230, 0.4);">Start Now →</a>
-      <p style="margin-top: 30px; font-size: 16px; color: var(--white);">Questions? Email <a href="mailto:go-faster@codegroove.dev" style="color: var(--cyan); text-decoration: underline;">go-faster@codegroove.dev</a></p>
+      <p style="font-size: 24px; font-weight: 700; margin-bottom: 20px; color: var(--white);">RECLAIM 10-15% OF YOUR TEAM'S THROUGHPUT.</p>
+      <p style="margin-bottom: 30px; font-size: 18px; color: var(--white);">Start with one team. Or your entire org. No training. Works with your existing workflow. Free for open-source projects.</p>
+      <a href="https://github.com/apps/ready-to-review-beta" role="button" aria-label="Install Ready to Review GitHub App" style="display: inline-block; background: var(--cyan); color: var(--black); padding: 16px 32px; border-radius: 8px; text-decoration: none; font-weight: 700; font-size: 18px; transition: transform 0.2s, box-shadow 0.2s; box-shadow: 0 4px 12px rgba(92, 225, 230, 0.4);">Install on GitHub →</a>
+      <p style="margin-top: 30px; font-size: 16px; color: var(--white);">Questions? Want a demo? <a href="mailto:go-faster@codegroove.dev" style="color: var(--cyan); text-decoration: underline;">go-faster@codegroove.dev</a></p>
     </div>
   </div>
 </section>