Alec SnowCustomer Success · Strategic AccountsLet’s talk
← Back to home

A PROJECT NOTEBOOK / ALEC SNOW

Things I build

You can't keep what you can't see.

I build practical tools when something important is hard to see. At work, that has meant mapping project relationships, turning order information into a daily report, and researching changing regulations. At home, I use the same habit to make everyday tasks easier.

01 / AT WORK · Westlake Royal Stone Solutions

The map nobody had

Workflow illustration · Project relationships lead to manufacturing and stocking conversations.

  1. What I noticed

    After COVID, long lead times meant availability could outweigh the architect's specification. Contractors could swap our product late, and we lost volume without visibility into those decisions.

  2. What I needed to understand

    Who was working with whom on which project, and what was being specified months ahead.

  3. What I built

    An Excel model with an LLM doing the reading, using ConstructConnect project and specification data to map relationships between architects, builders and contractors.

  4. What changed

    I took the map to manufacturing. With a clearer view of upcoming projects and relationships, we also worked with distributors to keep builder-specific stock on hand.

ExcelLLM-assisted readingConstructConnect

02 / AT WORK · SiteOne Landscape Supply

The report the system couldn't give them

Workflow illustration · Three information streams come together in a daily report for the customer.

  1. What I noticed

    A contractor needed a report the existing system could not provide.

  2. What I needed to understand

    A clear view of open orders, outstanding materials and truck-scheduling information.

  3. What I built

    I used AI to build an automated report and made sure the customer received it daily.

  4. What changed

    The customer had better visibility, handled things more efficiently, and needed less back-and-forth with the branch.

AI-assisted reportDaily customer report

03 / AT WORK · Oldcastle Infrastructure

Keeping up with the code

Workflow illustration · Source documentation and AI-assisted research pass through in-house engineering validation before customer guidance.

  1. What I noticed

    Stormwater specifications and local requirements change by jurisdiction.

  2. What I needed to understand

    What had changed in the source documentation and what that meant for plan and specification review.

  3. What I built

    I set up an LLM over county code and regulatory documentation and kept it current to support plan and spec review and identify where a system upgrade might fit.

  4. Why it matters

    The point was to understand a change before it became an account problem. Every answer was validated against our in-house engineers before it reached a customer.

County codeRegulatory documentationIn-house engineering validation

04 / FOR MYSELF

Same habit, pointed at my own life.

Personal tools I built with AI and use every day.

Concept illustration · Tenant service, invoices and books connected to rental management.
01 / PERSONAL BUILD

The tenant app

A Gmail-authenticated app I built to manage tenant service, invoices and the books for my rental property. I use it every day.

Concept illustration · Data APIs feed four-judge scoring and stock information.
02 / PERSONAL BUILD

Trading research

A trading analysis app that pulls from 20+ data APIs, with a four-judge system that scores stocks.

Concept illustration · Plaid feeds Zapier, then a to-do list.
03 / PERSONAL BUILD

A to-do list that builds itself

A Plaid app that feeds my to-do list through Zapier.

Read my public project post ↗ (opens in a new tab)
LET’S TALK

Pick one account you'd hand a new CSM and think hard about. I'll come to the call with a short account plan on it: where the risk is, what I'd do in the first ninety days, and what I'd measure.

alecsnow8@gmail.comLinkedIn ↗Full background ↗

Want to see how I approach a review? Try the fictional account review ↗