Andrew Lodwig

Which accounts should sales prioritize? Headcount narrows the list, but plenty of right-sized companies aren't hiring engineers. We needed a sharper filter.

An account scoring model in HubSpot, built with Sales Ops. It filters to Revelo's ICP (50 to 5,000 employees), then layers on a hiring signal: it scans sample engineering job posts from Apollo for the keywords that show a company is actively building its team. A hit is a high-confidence buying signal. The data's directional: it refreshes quarterly and sample posts miss some roles, so a hit means go and a miss just means the sample didn't catch it yet. Scores live at the account level today, and I'm driving the extension to the contact level so a rep gets a read on each person.

ICP filter + hiring signal, scored in HubSpot

We argued for 45 minutes about whether Austin or Denver was the better market. Nobody had data.

Evaluates potential T3 Live markets across 8 dimensions: ICP density, panelist pipeline, venue feasibility, competitive white space, sales alignment, and more. Scores each city on a 40-point scale and recommends where to invest next. Replaced subjective debates with a defensible framework.

8-dimension, 40-point scoring model

Reps spend 30 minutes per prospect researching before an event. This does it in seconds.

Produces a research brief from the guest list. Generates an ICP score against a 5-point rubric, company size and funding stage, open engineering roles, mutual connections, something humanizing to break the ice, and a 2-sentence recommended approach that names which business line to lead with, what to say first, and what not to say. Sends to the rep going to the event.

1 page per prospect, scored and ready

Leadership asks 'where are we on X?' because the answer lives in 6 different tools.

Bidirectional sync agent that reconciles event data and progress across every system I work in: Notion, local files, Luma, Figma, HubSpot, Google Suite, and Claude Code. Compares both sides, decides which is newer, auto-resolves conflicts, and flags what it can't. Leadership sees current status without asking, because the system keeps itself current.

events calendar is up to date with key details and progress updates 24/7

40 inboxes, 8 groups, one-sequence-at-a-time rules. I was managing it in a spreadsheet until I wasn't.

Automated outbound at scale. The brain behind Revelo's 40-inbox sending engine, built so the team runs sequenced campaigns instead of sending marketing emails one at a time. It reads which inboxes are free, calculates batch timing, flags conflicts between overlapping sequences, and recommends enrollment windows, all while holding every inbox under 25 sends/day to protect deliverability. Outbound runs as a system, so no one's babysitting a spreadsheet.

40 inboxes, 625 contacts/day max throughput, consistent 30% open rates and 10-15% reply rates

6 events in flight, 30 open tasks, and 2 hours free. What actually moves pipeline right now?

Pulls active tasks, calendar commitments, and event deadlines, then prioritizes what to work on right now. Accounts for urgency, dependencies, and what actually creates revenue (not just due dates). Turns task paralysis into a clear next action.

Friday forecast meetings were 30 minutes of everyone guessing. Now they're 10 minutes of reviewing evidence.

Every Friday, pulls evidence from Notion tasks, HubSpot pipeline, Slack activity, and event configs to propose forecast numbers for active quarterly KPIs and initiatives. Computes confidence scores against quarterly targets, surfaces what moved since last week, and pushes approved forecasts to Notion. Turned a 30-minute guessing game into a 10-minute formulaic review-and-confirm loop.

12 projects forecasted weekly, auto-scored

I was pulling Luma data, updating a spreadsheet, and posting to Slack every morning. That's busywork a script should own.

Pulls live RSVP data from Luma every weekday morning, calculates pacing against goal curves, writes to Google Sheets, and posts a summary to Slack. Runs autonomously on GitHub Actions. I see whether an event is on track before I open my laptop.

~45 min/day saved

Registration data in Luma, working notes in Sheets. One stale export and the nametags are wrong.

Syncs approved guest data from Luma to Google Sheets with email-based deduplication. Preserves manually-entered columns (Role, Status, Notes) while keeping registration data current. Replaced a token-heavy AI tool with a standalone script.

Runs 2x daily

Nametags look simple until you're formatting 80 of them the night before the event.

Takes an attendee CSV and template PNGs, routes each person to the correct template by role (ICP Attendee, Panelist, Revelo staff, etc.), samples background colors automatically, and produces print-ready multi-page PDFs sized for nametags. Creates a subtle, but easy way for reps to differentiate ICP vs non-ICP attendees.

CSV in, print-ready PDF out

Homebot

Customer Stories

Prospected for, wrote, and produced customer stories from scratch: finding the story, getting the customer to tell it, and turning it into a sales asset. Content marketing built from the ground up.

Revelo

Tech Teams Today Podcast

Built the pipeline engine that fuels the T3 podcast. Guest recruitment is account-based: every guest is an engineering leader who fits Revelo's ICP, so booking a guest and opening a sales conversation are the same motion. The outbound and enrollment infrastructure sustains ~1 recording per week. The podcast is a content machine. I built the machine that feeds it.