try again

Author: tstromberg

src/index.njk

@@ -6,27 +6,28 @@ description: Transform your 4-day PR cycle into 3 hours. Fast, smooth, conflict-
 
 <section class="hero">
     <h1 style="font-size: 56px; line-height: 0.85;">SHIP<br>94%<br>FASTER</h1>
-    <p style="font-size: 20px; margin-top: 30px;">4.5-day pull request cycle → 3 hours<br>
-    <span style="color: var(--yellow);">STOP WASTING YOUR ENGINEERS' FUCKING TIME</span></p>
+    <p style="font-size: 20px; margin-top: 30px;">Fix your pull request workflow<br>
+    <span style="color: var(--yellow);">4.5-DAY CYCLE → 3 HOURS</span></p>
 </section>
 
 <h2 style="font-size: 24px; letter-spacing: -1px;">THE PROBLEM</h2>
 
 <div class="groove-card">
-    <p style="font-size: 24px; font-weight: bold; margin: 0;">25% OF YOUR TIME</p>
-    <p style="font-size: 18px;">WAITING FOR REVIEWS</p>
+    <p style="font-size: 24px; font-weight: bold; margin: 0;">SLOW PULL REQUESTS</p>
+    <p style="font-size: 18px; margin-top: 12px;">25% of developer time waiting for reviews<br>
+    Context switching disrupts flow state<br>
+    Merge conflicts increase over time</p>
     <p style="font-size: 32px; font-weight: bold; color: var(--grey); margin-top: 20px;">$1M/YEAR</p>
-    <p style="margin: 0;">BURNED ON A 20-PERSON TEAM</p>
+    <p style="margin: 0;">BURNED OPPORTUNITY COST ON A 20-PERSON TEAM</p>
 </div>
 
 <div class="groove-card" style="margin-top: 24px;">
-    <p style="font-size: 20px; font-weight: bold; margin: 0;">THE LONGER PRs SIT...</p>
-    <p style="font-size: 16px; margin-top: 12px;">→ More merge conflicts<br>
-    → More rebase hell<br>
-    → Zero value generated<br>
-    → Lost opportunity cost<br>
-    → More frustrated engineers</p>
-    <p style="font-size: 14px; color: var(--grey); margin-top: 16px;">UNSHIPPED CODE = $0 REVENUE</p>
+    <p style="font-size: 20px; font-weight: bold; margin: 0;">STALE CODE COSTS</p>
+    <p style="font-size: 16px; margin-top: 12px;">→ Merge conflicts increase<br>
+    → Rebase complexity grows<br>
+    → Features sit unshipped<br>
+    → Developer context is lost</p>
+    <p style="font-size: 14px; color: var(--grey); margin-top: 16px;">UNMERGED CODE DELIVERS NO VALUE</p>
 </div>
 
 <h2>Proven Results</h2>
@@ -100,19 +101,19 @@ description: Transform your 4-day PR cycle into 3 hours. Fast, smooth, conflict-
 
 <div class="groove-card">
     <p style="font-size: 24px; font-weight: bold; margin: 0;">TURN-BASED TRACKING</p>
-    <p style="font-size: 18px; margin-top: 20px;">✓ KNOW EXACTLY WHOSE TURN IT IS<br>
-    ✓ ELIMINATE REVIEW BOTTLENECKS<br>
-    ✓ NO MORE FORGOTTEN PRS<br>
-    ✓ PREVENT MERGE CONFLICTS</p>
+    <p style="font-size: 18px; margin-top: 20px;">✓ Clear responsibility handoffs<br>
+    ✓ Automated bottleneck detection<br>
+    ✓ Context-aware notifications<br>
+    ✓ Conflict prevention alerts</p>
     <p style="font-size: 14px; color: var(--grey); margin-top: 20px;">LIKE JAMES BROWN DESIGNED A PR SYSTEM</p>
 </div>
 
 <ul>
     <li><strong>Week 1:</strong> 50% reduction in PR wait time</li>
     <li><strong>Month 1:</strong> 94% faster overall cycle time</li>
-    <li><strong>Zero disruption:</strong> Works with your existing GitHub workflow</li>
-    <li><strong>No merge conflicts:</strong> Fresh code, always in sync</li>
-    <li><strong>Happy engineers:</strong> They ship code, not wait for reviews</li>
+    <li><strong>No workflow changes:</strong> Works with existing GitHub process</li>
+    <li><strong>Less context switching:</strong> Developers stay in flow longer</li>
+    <li><strong>Outship your competition:</strong> They wait days, you ship in hours</li>
 </ul>
 
 <div class="text-center mt-60">