FOUNDER • CREATOR • TECHNICAL OPERATOR
I turn complicated ideas and operational problems into products, content, and working systems across AI-assisted creative production, SaaS, technical operations, automation, fintech, and the infrastructure that connects them.
Creator before AI. Systems builder because of it.
FLAGSHIP SYSTEMS
I tend to build when the existing workflow gets in the way. Some of these became public products. Others exist only because I needed a better way to work.
Research becomes content.
An AI-native research and editorial system that turns sourced research into podcast scripts, human-toned blog posts, technical articles, social content, executive talking points, and other editorial formats.
RESEARCH • SOURCING • EDITORIAL • LLM ORCHESTRATION
EXPLORE →The studio I wanted didn’t exist, so I built it.
A private podcast production environment. It reads ScriptForge’s cues, matches sound effects, and lays out the production timeline before I ever record.
RECORDING • TIMELINE • SFX • PRODUCTION
EXPLORE →Creator tools built around ownership and speed.
Browser-based recording and rendering for creators who want to record, edit, finish, and move without building their workflow around platform storage.
RECORD • EDIT • RENDER • PUBLISH
VISIT RCRDME.COM →Turn finished media into usable content faster.
Subtitle and short-form video processing with mobile ingest, media normalization, and creator-focused post-production workflows.
CAPTIONS • SHORT-FORM • VIDEO PROCESSING
VISIT SUBFORGE →My likeness. My infrastructure. Kept inside the box.
A private GPU-backed synthetic media environment built around my own likeness, deliberately kept private rather than exposed as a public product.
GPU COMPUTE • SYNTHETIC MEDIA • PRIVATE
VIEW THE WORKFLOW →PROVEN CREATOR
Before I built creator tools, I was already doing the work.
For The Epoxy Resin Store, I created commercial YouTube content end to end: originating the concepts, producing and recording the videos, appearing on camera, editing the finished pieces, writing the SEO-focused titles and descriptions, packaging the content, and publishing it to the channel. Several became some of the channel’s strongest-performing content.
The significance to me isn’t only the view count. I know how to take an idea that does not exist yet and carry it all the way to something an audience actually watches.
I know how to make the work. I also know how to build the system around it.
THE PRODUCTION PIPELINE
FROM IDEA TO AUDIENCE.
For these productions, I wasn’t one step in a handoff chain. I originated the idea. I developed the concept. I produced it. I presented it. I recorded it. I edited it. I wrote the title and SEO copy. I uploaded it and shipped the finished asset. Then the audience decided whether it worked.
I didn’t start by building tools for creators. I started by creating. Working through the entire production process made the friction obvious: research scattered across tools, scripting separated from production, editing disconnected from distribution, repetitive tasks everywhere. ScriptForge, pdcst, rcrdme, and SubForge came later. They are systems built around workflows I had already experienced firsthand.
CREATE
→ EXPERIENCE THE FRICTION
→ BUILD THE TOOL
→ CONNECT THE WORKFLOW
→ CREATE WITH MORE LEVERAGE
I BUILT THE TOOLS AFTER I KNEW THE PROBLEM.
WHAT I DO
I build systems where research, creative judgment, production, and automation work together.
Complex ideas don’t need to be dumbed down. They need structure. I find the actual story inside technical subjects without stripping away the substance.
I’m most useful when the line between strategy and execution disappears: define, specify, decide, review, operate, and stay responsible for what happens afterward.
AI isn’t a replacement for creative judgment. It’s leverage around judgment. Research becomes a common editorial foundation across formats, and the human stays responsible for argument, taste, voice, and final output.
If I repeat something enough times, a system ends up doing the repeatable part, leaving people to do what machines are still bad at: making decisions.
PROOF OF WORK
The best explanation of how I work is usually something I already made.
BEYOND THE CREATOR STACK
Creative systems are one part of what I build. The broader portfolio includes production SaaS, fintech infrastructure, underwriting systems, communications tools, intelligence platforms, and internal operating software.
07 SYSTEMS
Document provenance, broker CRM, deal rooms, outbound comms, AI bank-statement analysis, virtual PBX. Systems that began as problems I hit firsthand.
VeriMark • BrokerBase • FundFriend • FundingRoom • EzDial • VeriBank • ONLYnumber
VIEW FINTECH SYSTEMS →07 SYSTEMS
A connected toolset built around the way I actually create: recording, rendering, subtitles, video delivery, memes, screenplays, podcast production, synthetic media.
rcrdme • SubForge • wtchme • MemeForge • ScriptForge • pdcst • GPU Studio
VIEW CREATOR SYSTEMS →05 SYSTEMS
Some of my most useful systems were never intended to become products. Not everything needs to become SaaS. Sometimes the correct product has one user.
OIP • Data Repo • WeSign • BFF Outreach • GymGames / FitTrack Pro
VIEW INTERNAL SYSTEMS →ABOUT
I’ve spent most of my career building businesses and solving problems where the person making the decision is also responsible for what happens next.
My operating background is in alternative finance. That led me into software. Software led me deeper into infrastructure, automation, security, and AI. And eventually those systems connected back to something I’d been doing long before generative AI existed: creating.
I’ve built an audience-facing creator brand, taught, produced video, and spoken onstage. Long before I was building AI-native production systems, I was creating and publishing content myself, including end-to-end commercial YouTube production. The creative side didn’t start with AI. AI simply gave me a new set of tools to build around. It didn’t make me a creator; it gave new tools to a workflow I already understood.
I approach software as a product builder and systems operator. I identify the problem, define the product and workflow, establish the constraints and standards, and use AI-assisted development to turn those specifications into working software. Then I test it, direct the iterations, deploy it, and operate what ships.
My value is not writing code. It is knowing what should be built, understanding how the pieces need to work together, and staying responsible for the result.
Identify the bottleneck.
Understand the system around it.
Build a better way to operate.
Own the outcome.
HOW I THINK
A good idea trapped inside a bad workflow eventually becomes a bad product.
Automate repetition. Do not automate responsibility.
What works in a pitch deck and what survives contact with production are rarely identical.
I work best where authority and accountability live in the same place.
NOTES & IDEAS
01
Why AI infrastructure is becoming the product.
02
Why ScriptForge and pdcst exist.
03
Where automation belongs in creative work.
04
Why some of my best software will never become SaaS.
LET’S BUILD
I’m most interested in ambitious work at the intersection of AI, software, media, infrastructure, and operations, especially when the system hasn’t been completely figured out yet.
