breathingCode
Will Vowell, founder of breathingCode

Will Vowell

Point Loma, San Diego

I help you breathe life into the AI that is already everywhere.

I run breathingCode from Point Loma. This page is for hiring and for client trust. First person, same person.

I studied music and computer science at USC. I work from Point Loma.

Now

This month I am running the breathingCode shop from Point Loma, San Diego. The site is live. New sites, automations, and consulting are the three offers on it.

Alexander Realty & Construction is built and waiting on final wording. It is not launched. I do not have other client names or metrics to publish.

Why I started breathingCode

There are more AI tools than anyone can try in a month. The first week is noise. The harder part comes after: making the thing run, and keeping it yours instead of a generic copy.

I started breathingCode because I like this work, and because I like sitting with someone until the solution fits them. The cards below are that practice.

Enterprise SaaS · Past

Specright

Implementation through TAM and AI Solution Architect, 2020-2026. Not current.

Problem
Fortune 500 and other enterprise customers in regulated industries needed Salesforce implementations they could run, release discipline they could trust, enablement their people could keep, and later an AI assistant they could actually roll out.
Challenge
I arrived knowing no Salesforce. The work still had to ship in production. I do not name those customers here.
Solution
I became the go-to. Implementation Engineer to Senior to Lead, then Technical Account Manager / AI Solution Architect. I introduced Copado release management into an org that shipped in production. I built internal agentic tooling for delivery. I implemented IDP and named-credential PDF mapping. I did not build those products. I led the customer rollout of the company AI Assistant.
Users
About 200 internal users and about 2,000 external partner users. Fortune 500 and enterprise customers in regulated industries.
System
Salesforce: Experience Cloud, Service Cloud, Apex, LWC, and Aura. Copado for releases.
Mechanisms
Copado in a production-shipping org. IDP and named-credential PDF mapping, implemented not built. Customer rollout of the company AI Assistant. Internal agentic tooling for delivery.
Outcomes
1,000+ Flows. 20+ implementations. I ran the annual user-summit session that certified 75+ customer admins. I ran the session. I did not design the cert. Enablement for 40-50 people inside the company.
  • Role Lead Implementation Engineer, 2020-2025. Technical Account Manager / AI Solution Architect, 2025-2026.
  • Timeline 2020-2026. Past. Not present.
  • Scale 20+ implementations. About 200 internal and 2,000 partner users.
  • Tools Salesforce, Copado, Flows, Experience Cloud, Service Cloud, Apex, LWC, Aura

This site · Live

breathingCode.com

The shop. A live demo of the three offers.

Problem
A shop needs a site that can take a call, a quote, or a booking, and follow-up that actually goes out. Most of that work comes out generic.
Challenge
Keep the offers equal and honest. One real client card. No invented proof.
Solution
I built this site. New website or rebuild. Missed-call and lead follow-up, intake forms, and online booking on a calendar you already own. A one-hour workflow audit and a written plan. You own the accounts. This page is the work.
Users
Owner-operators who want a site, follow-up, or a one-hour plan.
System
This site, Calendly for the discovery call, and a quote form that branches.
Mechanisms
Three priced offers on the first screen. A quote path that asks what you need before it asks for a message.
Outcomes
Live. Starting prices on the page: websites from $1,500, automations from $500, consulting $250.
  • Role Founder
  • Timeline Live
  • Scale One-person studio. Point Loma, San Diego
  • Tools This site, Calendly, quote form
Open the site

Client work

Alexander Realty & Construction

Built. Not launched.

Problem
A general contractor needed service pages and a quote path that used their own photos and reviews.
Challenge
The build is ready. Final client wording is not. I do not treat an unlaunched site as a live case study, and I do not link a domain that is not our work.
Solution
I built pages for custom homes, remodels, and decks, with their project photos and Google reviews, and a quote form with the phone number on it.
Users
The contractor and the people asking for custom homes, remodels, and decks. Not live yet.
System
Service pages, project galleries, Google-review integration, quote capture.
Mechanisms
Phone number on the quote form. Their photos and reviews, not stock.
Outcomes
Built. Waiting on their final wording. No launch date to publish. No traffic or lead numbers.
  • Role Builder
  • Timeline Built, not launched
  • Scale One client build. York County, South Carolina
  • Tools Custom site, quote form, Google reviews
Client Work on the homepage

Shipped

Approval gate

A person has to say yes before an irreversible write.

Problem
An agent can write or delete something you cannot undo, with no person to approve it first.
Challenge
Keep a human decision in front of the write. Do not hide that behind a dashboard claim.
Solution
An MCP server that requires human approval before irreversible writes. Public repo. I wrote it.
Users
Anyone running agents that can change real systems.
System
MCP. A gate in front of irreversible writes.
Mechanisms
Human approval before the write goes through.
Outcomes
Public at github.com/WillyV347/approval-gate-mcp. I do not publish user counts I cannot attest.
  • Role Author
  • Timeline Shipped, public
  • Scale Not published
  • Tools MCP
github.com/WillyV347/approval-gate-mcp

Shipped

VPS ops

Monitor and control a long-running process over SSH.

Problem
A long-running process on a VPS needs eyes and a hand without sitting on the box.
Challenge
Talk about the process honestly. This is not a trading story.
Solution
An MCP server that monitors and controls that process over SSH. Public repo. I wrote it.
Users
Operators who need to watch and steer a process that stays up.
System
A VPS, SSH, and an MCP server in front of the process.
Mechanisms
Monitor and control over SSH. Autonomous, long-running. Not a market bot story.
Outcomes
Public at github.com/WillyV347/vps-ops-mcp. I do not publish venue or volume numbers.
  • Role Author
  • Timeline Shipped, public
  • Scale Not published
  • Tools SSH, MCP
github.com/WillyV347/vps-ops-mcp

Also shipped

  • Multi-agent web toolkit: 20 subagents and 42 skills.
  • Opportunity intelligence pipeline.
  • Weather bot: developing. Not built and deployed.
  • Wedding agent: drafts only. Never auto-sends.

Selected previous work

  • Specright. Implementation Engineer to Senior to Lead. Lead Implementation Engineer, 2020-2025. Technical Account Manager / AI Solution Architect, 2025-2026. Past.
  • Foodbuy USA. Compliance Analyst, 2019, Charlotte. Automated reporting in Excel, Access, Power BI, Python, and SQL. Weekly database work of about two days.
  • University of Southern California. B.A. Music, Computer Science minor, 2018.

Seven-plus years: Foodbuy 2019, Specright 2020-2026.

Also studying Not the current story, and not finished: Airtable Agentic Systems Design, Aug 2026-Sep 2028, ID bd2hf6cwavps. Airtable Builder (optional), ID xeh3juikqnfg. Salesforce Platform App Builder. AWS Cloud Practitioner.

Contact

pulse@breathingcode.com

LinkedIn · breathingCode on LinkedIn · GitHub

Book a Discovery Call