I'm James. I build with AI. Finance degree, then an operations leadership role running a family Mercedes-Benz dealership group, where I implemented company-wide software systems to improve operations and drive revenue, and helped guide the group through a successful exit. Then enterprise SaaS at the customer-vendor seam, as a GTM strategy, ops, and internal solutions consultant. Now independent AI builds. Everything below is live. Every item links to a working tool, a deployed app, or a real artifact.
The pattern behind modern business-process automation: unstructured edge data, a structured enterprise store, AI synthesis. A person talks into a phone; seconds later it's queryable knowledge. Zero database, zero hosting cost, lives entirely inside Google Workspace.
A React 18 PWA captures voice (Web Speech API) or text on a phone and fires it at a Google Apps Script webhook. The script appends each capture to a Google Doc acting as a data lake, which NotebookLM indexes as a retrieval layer. Talk on Monday, query the synthesized knowledge on Friday.
NotebookLM is Google's source-grounded research tool. It answers only from the documents you give it, which is what makes it safe as a synthesis layer over the data lake.
The same pattern transfers to anything that starts as a person talking and needs to end as queryable knowledge: client field notes, sales-call captures, inspection logs, customer voice intake, internal SOP queries. The plumbing is identical; only the front end changes.
This is the v1 of a Workspace-native operating system I can stand up for a client engagement in days, not months.


A note captured on a phone, then queried and synthesized in NotebookLM.
I build the public-facing intelligence asset and the operational machine that uses it to source conversations, end to end. The same shape transfers to any vertical: build the deep-research artifact, wrap a contact pipeline around it, run the cadence.
A P&C broker briefing hub: a research-grade intelligence page built to open conversations, not to sell. It's the thing the outreach points to.
Behind it, an Apollo saved search feeds a CRM pipeline, a daily ten-DM LinkedIn cadence works the queue, and replies are handled against a written runbook so the motion is repeatable rather than dependent on me being clever each morning. Infrastructure is live; the Wave 1 list of 150 mid-market commercial P&C brokers is populating now.
Three deployed apps. A thin layer on top of the AI tools that codifies my build process and makes it portable. The same thinking transfers to any client where the bottleneck is how to brief work to an AI tool.
Turns messy voice dumps into structured prompts across 12 frameworks: voice-dump cleanup, strategy-partner mode, build briefs for Codex and Claude Code, project setup, agent mission briefs, deep-research decision memos, product-signal extractors. The frameworks are a PRD methodology made interactive.
A browser-based agentic workflow builder. Rough task in, mission brief out: objective, deliverable, recommended skills and plugins, agent vs. subagent split, execution steps, verification standard, acceptance criteria. It's how a vague ask becomes something an agent can actually run.
A no-API, fully local prompt transformer for strategy, code, creative, data, and execution tasks. Built to need zero login and zero backend, the kind of friction-free tool you can hand a client without provisioning anything.
Taking a business, researching its market, and packaging a clear-eyed recommendation a decision-maker can act on. Built with AI tools end to end: research, scoring, and the deliverable itself.
The research-grade intelligence asset behind the Wave 1 motion (Section 02). Built to open conversations in the commercial insurance vertical.
A structured audit of digital-retail tooling in the automotive dealership space, the same diagnose-and-recommend pattern applied to a software category rather than a single business.
A self-initiated, value-led diagnostic POC for a real 100-year-old family funeral home. I ran a full competitive digital audit, market research across the local competitors, and a client-ready set of recommendations, end to end with AI tools, on spec. The audit scorecard and the recommendations are linked below.
Patterns that drive real APIs and real workflows. Each one transfers to a SaaS a client already runs.
I run Claude Code as a customized agentic environment, not stock. Custom slash commands I built auto-load into every session (two are below). A claude-mem plugin carries memory across sessions. I direct Claude Code and Codex to build new agents, subagents, skills, commands, and plugins on demand, and I run automated code review inside my own build loop.
Loads Claude Code workflow patterns from the tool's creator, Boris Cherny, so every session starts with the best-practice playbook already in context: parallel sessions, plan mode, verification, subagents, hooks, and more.
Routes any task to the right skill or chain of skills from the live session catalog, with visible reasoning before it acts. Returns a numbered chain with a one-line rationale per skill, then asks whether to run it or just list it.


Two of my custom slash commands, auto-loaded into every Claude Code session.
Python CLI: Google Maps lead source, website-quality scoring, ownership classification, Sheets export. Early build, working MVP, and the pattern that transferred straight into the Wave 1 broker pipeline.
A five-agent system. Build complete; market entry paused due to former-employer adjacency. Included here purely as agentic-architecture proof, not a product I'm pushing.
A request-file workflow plus Python CLI that drives Notion CRUD via API. The agentic pattern transfers to any SaaS with an API: GoHighLevel, HubSpot, Airtable, Salesforce.
Smaller finished builds, live and usable.
A tool for pressure-testing a niche or business idea before committing time to it. Deployed and usable.
A communication and signal utility. Still very much an MVP.
The enablement side: onboarding material, lab work, and structured reporting that turns AI capability into something a team can adopt.
Personalized AI onboarding built for one business at a time, delivered as a working web app, not a deck. The first edition is for private credit: five core principles, a copy-paste prompt library, an interactive 30-day program, and real deal workflows. The same framework rebuilds for any industry, down to a single SMB, and takes a non-technical team from skeptical to confident inside the tools they already use.
My working lab for Claude Code patterns: skills, agents, and workflows. The bench the rest of this portfolio is built on.
Structured research and reporting work: turning model capability into something a decision-maker reads and acts on.
I pick whatever gets to a working result fastest, and I pick up new tools in an afternoon. No traditional engineering background. The range below is the modern AI build stack, plus the judgment for when to use which.
Finance, then consulting at SullivanCotter, then operations leadership at a family Mercedes-Benz dealership group (grew 2 to 4 dealerships, $1,900 PVR above industry, led a successful exit to Fields), then Solutions Consultant at CCC Intelligent Solutions (Salesforce, Asana, and Power BI implementations, doubled NPS response rates, cut GTM cycles 25%). The AI work sits on top of all of it.
Reach me here.
james@intersectionstrategies.co →