An Evidence Audit of the maxpetrusenko.com Homepage

What the 14 October 2026 capture verifies, what rests on the site's word alone, and what to check before a call.

*Image: Coding da Vinci - Der Kultur-Hackathon (13936422198) by Volker Agueras Gäng, licensed under CC BY 2.0.*

This audit works from a single text capture of the maxpetrusenko.com homepage, taken on 14 October 2026 and identified by content hash (10567c3d1133d9c4b777e32b1a50cd0c7cedfd6d244e5399760d2aa36565cbc1).

Only the homepage was captured for this audit. The pages behind its menu, and any source outside the site, were not inspected, so no conclusion here reaches beyond this page and this date. Each claim carries one of three labels: verified by inspection, stated by the site, or unresolved.

The offer as stated

The homepage presents Max Petrusenko as running two practices: AI automation consulting for founders and private somatic work, the second described through breathwork, movement, and hands-on sessions. The homepage's FAQ states that the work "stays clearly separated, with distinct pages and inquiry paths."

For the tech practice, the FAQ answer to "What tech services can I hire Max for?" lists Claude Code setup, n8n workflow automation, ChatGPT and API integrations, and product execution. The service card shows Claude Code, n8n, Make, and custom code as the stack, and its copy describes auditing the current stack, identifying bottlenecks, and building automations which, per the card, "eliminate repetitive ops" and "save real hours every week."

Everything here comes from the site's own account of the offer, and whether the services deliver the stated effects is outside what a homepage capture can show.

Verified by inspection

Some homepage content is verified by inspection alone, because for a menu or a listing the text is the claim itself. Seven lanes appear in both the menu and the footer: Tech, Blog, Links, About, Proof, Identity, and Mindfold. Home appears only in the menu. What that verifies is that the lanes exist as links on the homepage; the pages behind them were not inspected for this audit. One label, Proof, will interest anyone weighing a hire; it sits one click away on the live site, and this audit did not open it.

Under Featured Writing, the page lists three articles, each with a one-line description: "Google's AI Endgame Is the Interface", "AI Infrastructure for Startups: Minimum Stack", and "LLM Serving Architecture: Latency and Cost Controls". The section introduces them as recent articles on "automation systems, product execution, and operator workflows." The listing is fully verified by the capture; the articles' contents, dates, and live addresses were not inspected, so the titles stand here as the topics the practice publishes on, and nothing more.

The three figures the page reports

The homepage states three results in a row: "$253k annual cost savings", "73% fewer production bugs", and "4.9/5 client experience rating". The capture shows no methodology, no sample, no timeframe, and no client attribution for any of the three, and nothing outside the site was consulted to fill that in.

That leaves the figures stated by the site: the capture confirms that the claims exist, and it offers no way to confirm the results themselves. They stay questions until someone supplies the method behind them.

Availability as captured

The availability block states two situations: "Somatic work: by request. Tech consulting: remote worldwide." The two cards underneath separate them further, with "Private sessions paused for now" under Somatic Work and "Remote worldwide; in-person by request while traveling" under Tech Consulting. The FAQ repeats the paused status across four answers, limits WhatsApp to future-fit inquiry, and reports that "no travel-based calendar slots are open." So "by request" here means a future-fit conversation, with somatic sessions paused as of the capture.

The header adds a signal the capture cannot resolve: a badge reading "Open for Q2 projects." The capture falls in the fourth quarter of 2026, and the badge is written for Q2; nothing in the page says whether it is live availability copy or a leftover template string, so the badge settles nothing about what is open now. It stays unresolved until someone confirms its meaning; the availability card and the FAQ remain the homepage's explicit statements about openness. Both date to the capture, and either can change.

How an inquiry starts

Inquiry follows the two lanes. The page offers a lane choice between "Tech consulting and delivery" and the somatic practice, and the tech path runs through a form titled "Send Me Your Stack". The form asks for an email address and a list of the tools used daily, and its copy states the reply: "I'll reply with 3 automation opportunities personalized for your setup. Free. No spam." The FAQ sequences the tech path, with timing and scope confirmed after the stack or project context arrives. A contact line also appears on the page; the captured copy masks the address, so this audit does not reproduce it.

The reply promise went untested here, and it takes one form submission to check: send a stack and read what comes back.

What to verify in a first conversation

What the capture leaves open closes in one of two places: a direct question in a conversation, or a click on the live site.

The figures. Ask which engagements produced the $253k in annual savings and the 73% reduction in production bugs, over what period, by what method, and what survey stands behind the 4.9/5 client rating.

Availability. Confirm the state of both lanes on the day that matters, and ask what "Open for Q2 projects" means now.

The Proof lane. The menu links it, and it is the check on this list that takes one click instead of a question.

One limit covers all of it: this reading is fixed to a single capture, so for anything that changes, the live page is the current source.