Writing in the shell

<p>Aaron,</p>

<p>Thursday morning got eaten by a deploy. Can we move to 2pm the same day? Same link.</p>

<p>If that does not work, throw me two times that do and I will take whichever.</p>

Every line is a <p>. That is the whole trick — the well handles the rest.

<h2>Where the reporting stands</h2>

<p>Short version: the August numbers are in and the sourcing note at the bottom is
the only thing that needs a decision from you.</p>

<h3>What moved</h3>

<ul>
  <li>Lead volume up 31%, third month running</li>
  <li>Cost per booked call down to $41.20</li>
  <li>Two listings live, both Schaumburg</li>
</ul>

<p>The full breakdown is in <a href="https://reports.opscend.net">the live report</a>
if you want to go through it line by line.</p>

<blockquote>The one thing I would change: retargeting is still running on the broad
audience for the commercial list.</blockquote>

<p>Tell me to cut it and I will cut it this week.</p>

<hr>

<p>No rush on any of this &mdash; Monday is fine.</p>

Headings in Instrument Serif, links ink + underline, a hairline blockquote, <hr>, lists. No classes, no inline styles, no <style> block — the shell already styles all of it.

Dana,

Following up on the note from last week. Still happy to send that breakdown
whenever you want it.

No rush.

⚠️ This one is not paste-ready. Dropped into the blank as-is it renders as one run-on paragraph, because the blank is an HTML file and HTML collapses newlines. normalizeBody is what turns it into the paragraphs below.

<p>Dana,</p>
<p>Following up on the note from last week. Still happy to send that breakdown<br>whenever you want it.</p>
<p>No rush.</p>