Skip to content

FIELD NOTES

How the hard parts got built.

Anonymized notes from HubSpot systems running in production: what was broken, what we built, and what it does now.

  1. FIG. 01NIGHTLY CLERK SYNC19:30 CTSample run log of the nightly county clerk sync: file downloaded, filings loaded, heartbeat written, trustee roster refreshed an hour later.
    Field note 01 / 04

    Nightly public-records pipeline

    Public records, loaded every night

    A nightly pipeline that keeps 35.7 million county filings and four appraisal rolls current in one database, and scores every property for distress.

    • Python
    • PostgreSQL 17
    • Docker
    • SFTP
    • +1
  2. FIG. 02DEAL MOMENTUM06:00 CTSample board of deals grouped by momentum: Advancing, Engaged, Slipping, Cold and Never contacted, with the time since last contact on each.
    Field note 02 / 04

    Deal momentum on Cloudflare Workers

    Deal momentum that actually decays

    A HubSpot field that showed stalled deals as healthy, rebuilt as a Worker that recomputes on every activity, schedules its own decay and links contacts to new deals in two seconds.

    • HubSpot webhooks
    • HubSpot Automation API
    • Cloudflare Workers
    • Durable Objects
    • +2
  3. FIG. 03PROPERTY CARDS10:15 CTSample HubSpot deal record for a retail property with four sidebar cards: property overview, valuation and tax, sale history and area snapshot.
    Field note 03 / 04

    Property data cards in HubSpot

    Property data on every record

    Fifteen custom cards that put property, valuation, sale history, area and map data on HubSpot deal and company records, with the property data behind a signed, cached Worker.

    • HubSpot UI extensions
    • React
    • TypeScript
    • Cloudflare Workers
    • +2
  4. FIG. 04REPLY TO DEAL11:48 CTSample log of one positive reply: verified, matched to a contact, duplicate guards passed, deal created for the owner, owner emailed, event key stored.
    Field note 04 / 04

    Email-to-deal automation with AI drafts

    From reply to deal, with agents in the loop

    Every send and reply logged to the right HubSpot contact, every positive reply turned into a deal for its owner, and follow-ups drafted by Claude inside a workflow action with a send guard.

    • HubSpot CRM v3 API
    • Custom workflow actions
    • Cloudflare Workers
    • Workers KV
    • +4

Client names, people, addresses and identifiers are withheld. Figures show invented sample data; the numbers in the text come from the systems themselves.

Your system could be the next note.

Bring the part of your business the CRM can't see yet. We'll show you how we build it.