Doc 1 of 6 · Chapter 1 War Room

🔥 The Urgency List

Things that cost real money or create genuinely uncomfortable situations if not done. Fires first, then people waiting on you. Sources: your Gmail (Jun 22 – Jul 13), post-its, the Jul 12 coach call, Claude Code session history.

⚡ 30-second read

2 fires burn actual money right now (Google Ads billing rejected → client ads pause; Google Cloud at 150% of budget). 1 fire burns reputation (alovasember live booking bug, you promised follow-up Jul 7). 1 has a hard deadline (Revotec champion leaves the company Friday Jul 18). And 9 people are waiting on a reply from you — the worst is a signed client (Kocsy/MOL) silent for 2 weeks. Everything below fits in one heavy Monday.

🚒 Section A — Fires (stop-loss, do first)

A1 · Google Ads payment REJECTED money bleeding15 min

What: payments-noreply@google.com, Jul 8 — payment rejected on Ads account (ref 967-829-4672). If unfixed, ads stop — and two PPC clients (Balogh, Csupi) are already nervous about performance. An ads outage on a churn-risk account is how you lose a paying client in a week.

Do: open Ads billing → fix the payment method → confirm campaigns still running. Then check which card failed and why (expired? limit?).

A2 · Revotec handover — Árpád leaves Friday Jul 18 hard deadline30 min today

What: Gombás Árpád, your champion at Revotec, leaves the company Jul 19. He wanted a handover call, sent his private contact Jul 7 (arpad.gombas74@gmail.com, +36 20 263 3755). The 2,516-row scored lead list + campaign proposal you built dies with his exit if no successor owns it.

Do: today — email/call Árpád: (1) book the handover call before Thursday, (2) get the successor's name + a warm intro, (3) keep Árpád as a private-network contact.

A3 · alovasember booking bug — LIVE with real payments reputation1.5–2 h

What: Customer paid for a consult, money deducted, no confirmation, no booking recorded (Simon Petra, Jul 7). You told Sanyi "ma írok erről" on Jul 7 — no follow-up went out. A new booking came in Jul 13, so the system keeps taking money with a known bug.

Do: (1) reply to Sanyi today with an honest status + ETA — the silence is worse than the bug; (2) run the debug prompt chain below.

# Claude Code — alovasember booking-bug hunt (paste as one prompt) The alovasember booking system has a live bug: a customer paid (money was deducted) but no booking record was created and no confirmation email sent (Simon Petra, 2026-07-07, 18:30 consult). A later booking (Kata Kocsis, 2026-07-13) appears to have worked. 1. Locate the booking + payment flow in the alovasember project. 2. Trace the path payment-success → booking-record → confirmation-email and list every point where it can break AFTER money is taken (webhook signature fail, race, timeout, unhandled exception, idempotency miss). 3. Pull logs/webhook events around 2026-07-07 for the failed booking and around 2026-07-13 for the successful one; diff the two paths. 4. Report root cause + a minimal fix + how to backfill Petra's booking. Do NOT deploy anything without showing me the diff first.

A4 · Kocsy Gergely (MOL) — signed client, 2 weeks of silence churn before kickoff30 min

What: Contract signed Jul 6. He sent 3 emails (Jun 29–30) with the pipeline copy docx + voice recordings (Jul 2) — zero reply from you. A new client's enthusiasm decays fast; two silent weeks after signing is the classic churn-before-kickoff pattern. Post-it says it yourself: this is the fear-of-client-emails loop, not a time problem.

Do: reply today — thank him for the docx, name 1–2 concrete things you took from it, propose a kickoff call slot this week. Send, don't polish.

A5 · Google Cloud budget at 150% money bleeding20 min

What: Budget alerts escalated 50% (Jul 1) → 90% → 100% → 150% (Jul 4) on project 637200-111808270. Something is burning quota unattended — nine days since the last alert.

Do: open billing → find the top-3 SKUs driving spend → kill or cap the runaway (often a forgotten VM, an API loop, or log ingestion). Set a hard budget cap + alert at 80%.

A6 · Fanni Finance — utalási lista ×2 transfers waiting15 min

What: Two "utalási lista" emails from Fanni (Jul 9) — transfers to execute. Unpaid transfers = late payments to people who notice.

Do: execute the transfers, confirm to Fanni in one line.

This is fine meme
the fires, visualized

📬 Section B — People waiting on you (replies + calls, all Monday)

Order = damage-if-skipped × how long they've waited. Per your call with the coach: open them without the pre-dread — the record shows they're almost never bad news (see the Mirror doc, Question 2).

B1 · Bauart galéria — "call me after July 12" = today hot leadcall · 20 min

Sárközi Zoltán (+36 20 286 2556) said Jul 6 the website topic is current and to call after Jul 12. Every day past "after" cools the lead. Call before lunch. Post-prep: 5-min skim of their site + 3 talking points.

B2 · EGYSE — meeting ask + full comment pass done reply · 10 min

Ádi finished commenting the entire design (Jul 13) and asks for a meeting Sat Jul 18 or Sun Jul 19, 10:00 (they're in Eger). Also reported review-tool bugs (can't delete/edit comment, resize doesn't stick) and asked about self-editable sections.

Do: reply with your slot pick + "comments received, processing this week". Log the Studio bugs — they're already on the Studio backlog (BUG list) from your sessions.

❓ Decision needed — comment your answer on this box
Which EGYSE slot do you take?
A) Sat Jul 18, 10:00 — gets it done, frees Sunday; but it's your beach-with-friends weekend candidate.
B) Sun Jul 19, 10:00 — protects Saturday fun; Sunday morning call is usually painless. ⭐ my guess
C) Neither — propose a weekday evening video call — Eger is a 2h drive each way if they mean in-person; clarify remote vs. in-person first.
⚠️ Their email doesn't say whether they expect you in Eger — worth clarifying in your reply either way.

B3 · Balogh Péter — the post-it with the ALARM churn-riskprep 30 min + call

Your own post-it: "Balogh P.! — prep a report, call him + ALARM". He's the churn-risk client ("megkeresések nullára csökkentek") who still paid Jul 6. The PPC restructure summary went out Jun 25 (Norbi) — he needs to hear results-or-plan from you, proactively, before he asks again.

Do: 30-min report prep (leads volume since restructure, what changed, next 2 moves) → call. If Ads were paused by the billing failure (A1), this jumps to fire status.

B4 · Csupi — CTR question unanswered since Jul 12 reply · 20 min

Csupek Péter asked why Search CTR collapsed (Thu 0.3% → Fri 0%); Norbi cc'd, nobody answered. He's the second nervous PPC client. Also open: Search Console indexing errors he forwarded worried (Jul 3).

Do: short honest reply: what you see in the data, what you'll check, when he'll hear back. Loop Norbi with a direct ask + deadline.

B5 · Beridoor — 2nd nudge, waiting since Jul 9 reply · 10 min

Kőrösi Benedek placed images + comments in Figma, asks if it's OK, wants the rebuilt page + your suggestions. Second nudge already ("mikor egyeztessünk?" Jul 9).

Do: reply: comments received + concrete date for the rebuilt version + 2 of your own suggestions (he explicitly asked for your taste — that's trust, use it).

B6 · Gill & Murry — did the promised plan + quote go out? verify · 10 min

After the Jul 8 meeting (szerződés / ügyfélportál / backend) you promised the detailed plan + quote within 1 day. My mail scan couldn't confirm it was sent — check your Sent folder; if it didn't go out, it's 5 days late to a client who just paid you (Jul 9).

B7 · Fusiontables — 8-point feedback (Jul 10) implement · 1–2 h

Hajós Márta sent precise, actionable feedback (copy edits, correct phone +36 1 426 6504, gallery swaps, remove "zománcozott") + carousel photos. Client paid Jul 5. Nothing blocks this except queue position.

Do: either implement Monday afternoon (it's mechanical — a good Claude Code task while at the lake), or reply with a delivery date. Silence is the only wrong move.

B8 · Sico Complex — possibly dropped since Jun 24 verify · 10 min

Bedő Attila approved the "you build the tables" option + sent detailed corrections Jun 24. No visible reply since. Three weeks of silence on an approved go-ahead reads as "my project got forgotten".

Do: check the thread; send status + next milestone date.

B9 · Quick sweep (batch in 20 min)

Gru's plan meme
the cold-email paradox

🧾 The one-screen checklist

#ItemTypeEst.Deadline pressure
A1Google Ads billing fix💸 fire15 mads pause any day
A2Revotec handover (Árpád)⏰ fire30 mFri Jul 18
A3alovasember bug: reply + debug🛠 fire2 hlive system, 7 days silent
A4Kocsy reply + kickoff slot🤝 fire30 m2 weeks silent, signed client
A5GCloud 150% — cap the burn💸 fire20 m9 days running
A6Fanni transfers💸 fire15 mJul 9 ask
B1Bauart call📞 lead20 m"after Jul 12" = now
B2EGYSE slot + comments note📬 reply10 mmeeting is this weekend
B3Balogh report + call📞 churn-risk1 hyour own ALARM post-it
B4Csupi CTR answer📬 reply20 mnervous client, 2 days
B5Beridoor reply + date📬 reply10 m2nd nudge
B6G&M plan+quote — verify sent🔍 verify10 mpromised "1 day", Jul 8
B7Fusiontables 8 points🛠 build1–2 hpaid Jul 5
B8Sico status ping📬 reply10 m3 weeks quiet
B9Quick sweep (6 items)🧹 batch20 m

Total focused time: ~7 h Of which replies/calls: ~4 h Feasible in one heavy Monday: yes — see the plan →