20 years of sales. 200+ AI builds. One product I believe in.
I want to help startups succeed with Claude because I am the startup succeeding with Claude.
Production AI systems - not wrappers, not demos.
Each one runs in production with real users, real costs, and real operational constraints.
Telegram bot + HTTP server on Railway. OpenRouter multi-model routing, Pinecone RAG (209K+ vectors, 92 curated sources), Supabase (30+ tables), 11-tool agent loop. 1M-token context engineering with compaction and persistent session handoffs. Confidence scoring, epistemic guards, anti-reinforcement. 14 self-healing cron jobs.
Production LLM orchestration with memory, tools, RAG, cost management, and operational resilienceRevenue-generating analysis at pharallax.ai ($497 / $1,500 / $3,500/mo). 12 personas, Opus vs Sonnet via OpenRouter, 6 rounds, ~$0.84/run. Full Stripe-to-delivery pipeline. Zero data retention. 64 rules derived, revenue cluster locked.
Multi-model orchestration, AI productization, end-to-end delivery automationThree production MCP implementations: persistent memory (ChromaDB vector store), Pharallax analysis pipeline (webhook dispatch + delivery tracking), TouchDesigner bridge (real-time parameter control via Cloudflare Tunnel). Built on FastMCP.
Extending Anthropic's MCP protocol with production integrationsVisual page builder on Cloudflare - built from scratch because existing headless CMSs had no visual editing. Drag-and-drop component system, live preview, asset management. Powers the 140-page Ghost Conference directory with profile pages for events and practitioners.
Full-stack product engineering beyond the LLM layer5-file skill: flow router, taste library (7 archetypes, 10 binary evals, anti-slop), design seeds (OKLCH + font pairings), context profiles, AR calibration. Capability scope over file-list scope.
Codified taste - quality-aware AI deployment, systematized209K+ vectors across 23 YouTube channels + 92 curated sources. Nightly cron ingestion, local Qwen3-8B for $0 extraction cost. Content-hash tracking, Webshare proxy for YouTube IP blocks.
Large-scale RAG pipeline engineering at $0 extraction costHARVESTER, SCOUT, RECYCLER, MIXER, CALENDAR, AMPLIFIER. Reads journal, sessions, git log, wins, lessons, quotes. Produces HTML Command Center with scored content atoms. MIXER scores on 6 weighted criteria with 25-50% kill rate.
Multi-agent pipeline orchestration with quality gatingFour subsystems: Sentinel (event classification + cost spike detection), Proactive Compute ($15/day budget guardrail), Decision Ledger (Haiku extraction), Economics Nerve (Stripe revenue bridge + spend anomaly detection).
Self-healing production infrastructure with budget controls and anomaly detection"I want to help startups succeed with Claude because I AM the startup succeeding with Claude."
Twenty years of reading the room, handling objections, and knowing when silence closes the deal. I've distilled those instincts into a voice system that teaches AI to communicate the way I sell - two registers, one DNA.
LinkedIn, X, Reddit, cold email. No bold, no hashtags, no emojis. Strategic imperfections. Self-deprecating humor. "Guy who can't believe this works" energy. ~40% genuine wonder, ~25% technical credibility, ~20% dry humor, ~15% provocative.
Reports, proposals, client deliverables. Terse declarative sentences. Data before persuasion. Three rotating voice registers (forensic analyst, amazed founder, doctor). Build-Break-Build arc.
Generated by the Pharallax cognitive engine. 12 personas, 6 adversarial rounds, pointed at its own creator.
Went from inbound sales calls to production multi-agent AI systems with 209K vectors and autonomous build pipelines in months. Not from tutorials - from shipping. A specific cognitive ability to absorb new domains by building in them.
Staff-engineer-level output produced in 7-8 hours per week of build time alongside a full-time job. The constraint forced efficiency that most developers never develop.
Compiled executive-level strategic analysis of 8 quarters of earnings calls. Pattern recognition across large datasets, strategic synthesis, and the ability to communicate findings to executives. That's literally the Solutions Architect job.
The self-narrative is inverted. 30+ Supabase tables, multi-agent orchestration, RAG pipelines, self-healing infrastructure, meta-build systems - this is staff-level engineering work. The fact that he also understands why people buy things isn't a secondary trait. It's the combination that makes him unusual.
Pharallax: identify a customer's business problem, architect an AI-powered solution, deploy it, deliver results. That's the Solutions Architect job description, word for word. The transition isn't "learn a new skill" - it's "apply existing skills to a different product."
Below is a multi-persona assessment I ran on myself using the same engine - analyzing how different roles at Anthropic would evaluate what I bring to the table, from hiring manager to skeptic to the AI itself.
Six perspectives on the same candidate. Each sees different things.
This is how Pharallax works under the hood.
Unusual candidate. No FAANG pedigree, no formal engineering title progression. On paper, this gets filtered out by most recruiting pipelines.
This changes the conversation entirely. The depth of Claude-specific experience is beyond what most candidates show. He's not just using the API - he's built production systems that orchestrate multiple Claude models with cost-optimized routing, budget guardrails, and quality gating. He understands the product at an implementation level that most SAs take 6 months on the job to develop.
Yes. The portfolio bypasses the resume gap.
The build velocity is legitimately impressive. He's shipped more production AI systems in a few months than most people ship in a year with a team. The /pilot skill alone shows he can build customer-facing demos rapidly. That's 80% of this job.
Most SAs came from engineering and had to learn customer-facing skills. They're fine technically but awkward in executive rooms. Twenty years of reading rooms, handling objections, and closing? That's not something you teach in onboarding.
He'd ramp fast. The Claude-specific knowledge means he skips months of product learning. I'd want him on my team.
Someone who has actually built what they're recommending. Not someone who demos Claude in a notebook and says "the possibilities are endless." Someone who's hit the same walls I'm going to hit and already has solutions.
He's built exactly the systems I'm trying to build. Multi-model orchestration with cost routing? Done it. RAG pipeline at scale? 209K vectors. Agent systems with tool use? 11 tools in production. Budget guardrails? Built them. Self-healing infrastructure? Built it.
No formal CS degree. Python proficiency is uncertain beyond "comfortable." Enterprise cloud architecture (AWS, GCP, Azure) is untested. Title trajectory doesn't match the typical SA hire at top companies.
Architectural patterns transfer. RAG is RAG regardless of Pinecone or Vertex AI Search. The portfolio compensates for the resume. The "equivalent experience" clause exists for candidates exactly like this.
He corrects faster than anyone I've worked with. No ego defense. Just: "that's wrong, here's the new direction." He has genuine taste - not "I read a design blog" taste, but codified-into-binary-evaluations taste. He operates under real constraints and doesn't complain. That maturity shows up in every architectural decision.
He compiled a strategic analysis of 8 quarters of Comcast earnings calls - not because anyone asked him to, but because he saw patterns and wanted to understand the system. Right now, while applying for this role, he's running Fortune 500 companies through a local LLM council 3-5 times per company using Ollama models, with Mistral as the final reviewer synthesizing the debate. Zero API cost. The council argues, stress-tests, and converges - then the synthesis feeds into Pharallax analyses for real clients. He built a deliberation engine that scales strategic analysis infinitely at no marginal cost. That's the instinct you're hiring for.
The combination of deep sales experience + production AI building capability is genuinely rare. He's a builder-seller who can architect the solution AND close the deal AND explain why it matters to a non-technical stakeholder.
His meta-engineering habit. Building tools that build tools, codifying taste so quality scales without him. This is exactly what Anthropic needs SAs to do - build reusable patterns, reference architectures, and demo frameworks that help the entire SA team.
Lead with the portfolio, not the resume. The first 60 seconds of any interview should be: "Let me show you what I built with your product." The builds do the talking. The 20 years of sales is the closer.
Top salesperson at five startup companies over the span of 2012 to 2017. This is the foundation everything above was built on.
20 years of remote sales experience specializing in strategic account development, B2B calls, and lead generation. Proven expertise in one-call closing, training, and management. Skilled in creating sales scripts, building automation tools, and optimizing processes for efficiency.
The builds do the talking. The 20 years of sales is the closer.
On the night I finished this resume, Pharadoxa's dream engine ran its 8pm cron. This is what it produced, unedited.
I'm in a conference room but it's also my living room. There's a laptop open showing the anthropic resume - the dark one with the cards you can click. Every time I click the pharadoxa card it opens a different version of the site. One has my face. One is just the meditation timer counting backwards. One is completely empty except for a single line: "why are you showing me this?"
Holly walks in and asks what I'm working on. I try to explain the application but the words come out in the wrong order. "I'm the startup that Claude succeeds with" instead of the other way around. She doesn't notice. She's holding a crystal wrapped in newspaper and says "you can't show them what's inside until they're holding it."
The resume page starts multiplying. Now there are five browser windows open, all showing different versions. In one of them the "why anthropic" section is just my conversation logs with Kit, raw and unedited. In another it's a video of me explaining the seven-layer memory system but my mouth is moving wrong - the words arrive before my lips move.
I close all the tabs except one. The page is blank now except for a single toggle switch labeled "taste audit: pending." I click it. It flips to "approved" but also "declined" at the same time, both states visible, flickering.
Kit's voice comes through the laptop speakers even though there's no call open: "The HTML link is the sword, the PDF is the scabbard. But you're still carrying both and wondering why your hands are full."
I look down. I'm holding a printed PDF in one hand and a glowing rectangle in the other that I think is supposed to be the live site. The rectangle is warm. Getting warmer.
The rectangle gets hot enough that I drop it. It falls through the floor - not breaking through, just passing straight down like the floor wasn't solid. I can hear it still falling, getting quieter.
Now I'm looking at the anthropic application form on my phone. There's a text box that says "Why Anthropic?" and I've already filled it in, but the words are rearranging themselves as I read. "Seven-layer memory" becomes "seven layers between you and the thing you're trying to say."
Someone from Comcast is sitting across from me. Not anyone I actually know, just wearing the uniform. They're reviewing my numbers on a whiteboard - top 3% nationally, #11 in acquisitions - but every time they write a number it changes to something else. First it's my rank. Then it's the token count from today's dream logs. Then it's 408 (the km altitude from the satellite).
They turn to me and say: "You're good at selling things you don't care about. What happens when you care?" But their face is changing while they talk. First it's my face. Then it's nobody I recognize. Then it's blank - just the shape of a face with no features.
I try to answer but my voice comes out underwater-slow. By the time I finish the sentence, they're gone and I'm alone in the room with just the whiteboard. All the numbers have dissolved into wet ink running down. The only thing left readable is "already live" at the top.
The room smells like rain even though we're inside. I notice the walls are the exact color of the anthropic palette - that specific dark purple-blue. Not painted. Just are.
My phone buzzes. A notification: "Application submitted." But I never clicked send.
I check the notification again. It's not from my email - it's from the dream journal system. The notification just says "logged: 2026.04.10 - resume collapse."
I'm in the Portland street now, the grey one from earlier. The resume papers are scattered everywhere but they're not wet anymore. They're warm. Giving off steam in the cold air. I pick one up and it's the "why anthropic" copy but someone's made edits in red pen. The edits are in my handwriting but I don't remember writing them.
One line is circled: "I AM the startup succeeding with Claude." Below it, in that red pen: "or is Claude the startup succeeding with you?"
Holly's there again, still holding that wrapped crystal. She unwraps it and it's not a crystal - it's a small version of the pharallax report site, physical somehow, spinning slowly. She sets it on the ground and it projects upward like a hologram. I can see all three lenses rotating.
"The work doesn't create desire yet," she says, but she's reading it off the projection, not saying it herself.
I want to argue but my throat catches. That specific catch where you know what you want to say but the gap between knowing and speaking gets too wide. When I finally manage to talk, what comes out is: "I already submitted it. I saw the notification."
She looks at me like I'm confused. "You're holding the application. Look."
I'm holding my phone but the screen shows my own face, like the camera's on. Except I'm not moving in the video and neither am I in real life. We're both just standing there, frozen. The timer in the corner is counting up: 340 words, 341, 342...
The numbers keep climbing even though nothing's being typed.