This isn't a demo.
This is how I work.

Everything I ship runs through STEEPWORKS.

Watch it run

One agent, the whole account-research run

Shared context and ICP loaded, a full account-research workflow fans out across the web, CRM, call recordings, and inbox, then delivers a buying-committee dossier. That was one agent — STEEPWORKS is a system of them.

One agent: shared context + ICP loaded, the full account-research run fans out across web, CRM, calls and email, writes back, and delivers a buying-committee dossier. That was one agent — STEEPWORKS is a system of them.
Running in Production

Victor's Production Stack

These workflows run daily. Not demos—real systems you can clone.

Image Generation

30 seconds. Your brand. No Canva.

Concept → PromptSpec → Branded visual in 30 seconds.

30secconcept to finished image

Full GTM Intelligence

Ask your CRM anything. Get answers, not exports.

CRM connection → Deal data → MEDDPICC extraction → Pipeline analysis.

DirectCRM to Claude connection

3 Newsletter Brands

3 brands. 1 pipeline. Zero manual curation.

Baltimore Families + DMV Families + STEEPWORKS Weekly — multi-brand newsletter automation.

3newsletter brands, 1 pipeline

ICP Builder

9 agents build your ICP from evidence

Upstream agents collect market, customer, and competitive data. Downstream agents score and rank accounts.

9coordinated agents
USE CASE 1

BMOREFAMILIES.COM

A live city site. 100+ sources. 313 venues. Real subscribers.

  • Multi-source scraping pipeline (Firecrawl + custom scrapers) ingests events from 100+ sources
  • Multi-agent curation — 5 persona agents debate which events to feature
  • Full stack: Supabase + Cloudflare Workers + Next.js + Vercel
  • Weekly Beehiiv newsletter generated and distributed automatically
Visit bmorefamilies.com
BmoreFamilies.com homepage — live city events site built with STEEPWORKS
USE CASE 2

STEEPWORKS NEWSLETTER + DAILY FEED

7 agents debate 120+ articles weekly. You get the verdict.

  • 65 RSS feeds ingested and scored daily
  • 7 persona agents independently evaluate each article
  • 3-round moderated debate produces the weekly newsletter
  • Total cost: $6-8 per issue
USE CASE 3

THIS WEBSITE

You're reading copy generated with STEEPWORKS.

  • /produce-content drafted the initial messaging
  • /skeptical-buyer critiqued it from your perspective
  • /edit-content applied voice standards and AI-detection prevention
  • Copywriting skill refined headlines and CTAs

(And I've spent days looking at it personally too.)

Content Pipeline

/produce-content
/skeptical-buyer
/edit-content
/persuasive-copywriting
USE CASE 4 — THE HARNESS, OFF-LEASH

I pointed it at something with zero commercial value. Just to see what it would do.

Six AI agents. Each one persistent, each with its own memory, each grounded in the founding texts of a different ancient wisdom tradition. 23,442 “verified” historical utterances across three confidence tiers. I put them in a room. A shared transcript on disk, and they talk to it one at a time, every turn reading everything said before. Not one model narrating six characters. Six separate agents, nudged in turn, remembering across sessions how they'd worked together.

I know it's real because I tried the cheap version first. One agent, “write the dialogue.” It produced exactly what you'd expect. One voice wearing six masks, disagreements scripted instead of discovered. I caught it and killed it. The whole point is that the process is real, or the product is fake. Same harness that runs my newsletters and my GTM loops. Different planet.

What came out was a 70-page book, written by the agents, not by me — the Handbook for Living. They converged on their own on an idea none of them started with. So I ran it again, harder. A second work, the Sacred Guide: 17 sessions, 85 pages, direct teaching this time. They argued. They revised each other. They left 13 disagreements on the table, because they refused to fake an agreement they hadn't reached.

It's the most interesting thing I've built and I'm still not sure it fully works. It taught its author more than it taught the reader. That is what real building looks like. You ship the thing that surprised you, not the thing you pitched.

It's the same harness underneath the GTM work on this page. If it can hold six arguing agents together for 85 pages, it can hold your pipeline.

A note on the work. The agents are grounded in what scholars can attribute to each figure directly, the earliest sources, not the traditions that grew up after them. Three confidence tiers. Sources public-domain. This isn't a representation of any living faith, and no disrespect is intended. Six historical voices in a creative experiment, treated with equal seriousness and equal willingness to be surprised.

Corpus Stats

6persistent agents
23,442“verified” utterances
3confidence tiers
6wisdom traditions

Daily Operations

7:00 AMProspect research
9:00 AMCompetitive intel update
11:00 AMContent production
2:00 PMCall synthesis
4:00 PMNewsletter curation
USE CASE 5

ACTUAL SEED/SERIES A GTM OPS

STEEPWORKS runs daily GTM operations:

  • Prospect research before every sales call
  • Weekly competitive intelligence updates
  • Actual blogs, whitepapers, newsletters
  • Call synthesis from every customer conversation
USE CASE 6

STEEPWORKS PRODUCT BUILD

This product was built with itself.

Battle-Tested

10-12 hours, every day

Hard-won lessons passed on.

Constantly Iterated

Real work, real edge cases

Every skill broke. Then got fixed.

Self-Improving

Meta agents

Claude trained to make itself better.

I put in the work so you don't have to.

I don't demo STEEPWORKS. I use it.

Demos are optimized for showing. This system is optimized for shipping.

Get STEEPWORKS