Peter Baumgardner

Contact

Send the real problem, not a polished brief.

A URL, the behavior you expected, what happened instead, and what changed recently is enough to start.

01 / Best routes

  • Website problem
    Use the website intake

    This captures the URL, urgency, relationship to the site, and the failure in one place.

  • Backend or AI system
    Email the technical context

    Include the current stack, user-visible failure, relevant constraints, and what a successful outcome would change.

  • Role or collaboration
    Email Peter directly

    I am interested in practical AI infrastructure, developer support, reliability, backend, solutions engineering, and systems work where the failure path matters.

02 / Sensitive access

Do not send secrets in the first message.

Do not email passwords, API keys, private keys, recovery codes, database exports, customer records, or payment credentials. After the scope is agreed, access should be granted through the provider’s normal invitation or restricted credential process.

For website lead data, read the privacy notice.