Small cuts

.src/sales.md

@@ -55,18 +55,18 @@ out loud.
 By the time you realize what happened, you’ve spent more than half your runway
 and you’re left with something that sort of works, kind of.
 
-_It doesn't have to go that way._
+_It doesn't have to be that way._
 
 ## Why Most Software Projects Fail
 
 It's not a technology problem. The tools to build almost anything
 have never been better or cheaper. It’s not even a talent problem.
 There are excellent engineers everywhere.
 
-Here’s why most software projects actually fail:
+Here’s why most software projects fail:
 
 - The people writing the code don’t
-  **understand the problem they’re actually trying to solve**.
+  **understand the problem they’re trying to solve**.
 - The outsourcing shop has too many clients,
   deprioritizing your project whenever **something bigger comes along**.
 - Nobody takes ownership of outcomes – developers write code,
@@ -84,7 +84,7 @@ _The incentives are broken from the start._
 
 ## Why You’ll Hire Us
 
-We understand something absolutely vital to your business:
+We understand something vital to your business:
 **short–term decisions made under pressure create long–term structural risk.**
 
 Small teams optimize for survival — shipping fast to stay funded —

sales.html

@@ -30,7 +30,7 @@
         <a href="/">readme</a>
         <a href="/">sitemap ▾</a>
       </header>
-      <article><h1>Hello, World!</h1><p><strong><em>We Ship Software</em></strong> is a small development agency run by <a href="https://jarrodtaylor.me">Jarrod Taylor</a> &amp; <a href="https://richard.is">Richard Rissanen</a> focused on one thing: <strong>shipping software</strong>.</p><p>We’re veterans of the tech industry, hands–on engineers, working to build <strong>independent, product–led businesses</strong>.</p><p><em>And we’re really fucking good at it.</em></p><hr><ul><li><a href="">The Next Big Thing</a></li><li><a href="">Why Most Software Projects Fail</a></li><li><a href="">Why you’ll hire us</a></li><li><a href="">Frequently Asked Questions</a></li></ul><hr><h2>The Next Big Thing</h2><p>Your new company just launched the next big thing. Investors are on board, customers are signing up and demand is rolling in. <em>Too much demand.</em></p><p>You hire a development shop to keep up, to grow the team. The first month goes great — kick–off calls, a detailed roadmap, everyone is excited.</p><aside class="left">Hiring sites are broken.</aside><aside class="right">Freelancers are unreliable.</aside><p><strong>Then the slippage begins.</strong> Deadlines become “targets”. Estimates balloon. The developers you interviewed disappear, and you’re handed to someone more junior who’s juggling four other clients.</p><p>Months later you’ve made little progress. What you have is not quite what you needed, cost twice what you planned, <em>and you’re starting the whole process over with someone new</em>.</p><p>The truth is <strong>most software projects fail quietly.</strong></p><p>Not with a bang — with a slow accumulation of missed standups, vague tickets, scope that keeps shifting, and a release date that everyone stops mentioning out loud.</p><p>By the time you realize what happened, you’ve spent more than half your runway and you’re left with something that sort of works, kind of.</p><p><em>It doesn't have to go that way.</em></p><h2>Why Most Software Projects Fail</h2><p>It's not a technology problem. The tools to build almost anything have never been better or cheaper. It’s not even a talent problem. There are excellent engineers everywhere.</p><p>Here’s why most software projects actually fail:</p><ul><li>The people writing the code don’t <strong>understand the problem they’re actually trying to solve</strong>.</li><li>The outsourcing shop has too many clients, deprioritizing your project whenever <strong>something bigger comes along</strong>.</li><li>Nobody takes ownership of outcomes – developers write code, the PM moves tickets, <strong>yet nobody ships software</strong>.</li><li>Estimates are <strong>optimistic theater, not honest assessments</strong> that you can plan around.</li><li>The project grows in scope with every new conversation, and nobody says “<strong>that'll cost more and take longer</strong>”.</li></ul><p>These failures are rooted in how development shops are optimized — to <em>sell</em> projects, not to <em>finish</em> them. A finished project means a client relationship ends. Scope creep means it continues.</p><p><em>The incentives are broken from the start.</em></p><h2>Why You’ll Hire Us</h2><p>We understand something absolutely vital to your business: <strong>short–term decisions made under pressure create long–term structural risk.</strong></p><p>Small teams optimize for survival — shipping fast to stay funded — and defer the foundational work that makes scaling possible. The danger is that by the time the business has resources to fix these issues, the technical problems have become deeply embedded and expensive to unwind.</p><h2>Frequently Asked Questions</h2><p>...</p></article>
+      <article><h1>Hello, World!</h1><p><strong><em>We Ship Software</em></strong> is a small development agency run by <a href="https://jarrodtaylor.me">Jarrod Taylor</a> &amp; <a href="https://richard.is">Richard Rissanen</a> focused on one thing: <strong>shipping software</strong>.</p><p>We’re veterans of the tech industry, hands–on engineers, working to build <strong>independent, product–led businesses</strong>.</p><p><em>And we’re really fucking good at it.</em></p><hr><ul><li><a href="">The Next Big Thing</a></li><li><a href="">Why Most Software Projects Fail</a></li><li><a href="">Why you’ll hire us</a></li><li><a href="">Frequently Asked Questions</a></li></ul><hr><h2>The Next Big Thing</h2><p>Your new company just launched the next big thing. Investors are on board, customers are signing up and demand is rolling in. <em>Too much demand.</em></p><p>You hire a development shop to keep up, to grow the team. The first month goes great — kick–off calls, a detailed roadmap, everyone is excited.</p><aside class="left">Hiring sites are broken.</aside><aside class="right">Freelancers are unreliable.</aside><p><strong>Then the slippage begins.</strong> Deadlines become “targets”. Estimates balloon. The developers you interviewed disappear, and you’re handed to someone more junior who’s juggling four other clients.</p><p>Months later you’ve made little progress. What you have is not quite what you needed, cost twice what you planned, <em>and you’re starting the whole process over with someone new</em>.</p><p>The truth is <strong>most software projects fail quietly.</strong></p><p>Not with a bang — with a slow accumulation of missed standups, vague tickets, scope that keeps shifting, and a release date that everyone stops mentioning out loud.</p><p>By the time you realize what happened, you’ve spent more than half your runway and you’re left with something that sort of works, kind of.</p><p><em>It doesn't have to be that way.</em></p><h2>Why Most Software Projects Fail</h2><p>It's not a technology problem. The tools to build almost anything have never been better or cheaper. It’s not even a talent problem. There are excellent engineers everywhere.</p><p>Here’s why most software projects fail:</p><ul><li>The people writing the code don’t <strong>understand the problem they’re trying to solve</strong>.</li><li>The outsourcing shop has too many clients, deprioritizing your project whenever <strong>something bigger comes along</strong>.</li><li>Nobody takes ownership of outcomes – developers write code, the PM moves tickets, <strong>yet nobody ships software</strong>.</li><li>Estimates are <strong>optimistic theater, not honest assessments</strong> that you can plan around.</li><li>The project grows in scope with every new conversation, and nobody says “<strong>that'll cost more and take longer</strong>”.</li></ul><p>These failures are rooted in how development shops are optimized — to <em>sell</em> projects, not to <em>finish</em> them. A finished project means a client relationship ends. Scope creep means it continues.</p><p><em>The incentives are broken from the start.</em></p><h2>Why You’ll Hire Us</h2><p>We understand something vital to your business: <strong>short–term decisions made under pressure create long–term structural risk.</strong></p><p>Small teams optimize for survival — shipping fast to stay funded — and defer the foundational work that makes scaling possible. The danger is that by the time the business has resources to fix these issues, the technical problems have become deeply embedded and expensive to unwind.</p><h2>Frequently Asked Questions</h2><p>...</p></article>
     </main>
   </body>
 </html>