A lot of people from here shared their experiences with me in my last post, when I asked about the problem of self hosting n8n within a VPS. Hetzner and Railways stood out as 2 incredible options to me and I went ahead with hetzner and today, I can literally create events from my phone, without my laptop running on any quick tunnel or cloudflare or etc. and I am just so happy that I have done what I really thought would take me longer than this to achieve! I can now add people to my config that I am using right now, and ask their experience on event creation with my whatsapp bot. Too happy :) Please share any leads you have for any small businesses requiring this kind of aid. I am happy to connect with any person, arrange a meeting or answer any of the question your network brings! Onwards and upwards!! 🔥 🚀🚀

Just over an hour on video, recorded, with his store admin open on screen. I went in with a list of numbers I wasn't allowed to leave without. I also went in with a favourite answer, and that turned out to be the problem. After discovery I was sure the bottleneck was content. He'd told me he had loads of footage that never got published, so I'd basically written the report in my head: a system to get the backlog out. So I asked him to walk me through the last clip he'd filmed that never got posted. He thought about it and said there isn't one. Everything he films goes up. Idea to published takes him about 20–30 minutes, and he edits it without friction. The real issue sits earlier. Nothing tells him what to film or when, and all his raw material lives unsorted in his camera roll. He isn't stuck on publishing. He's stuck on starting. The second surprise was bigger. In discovery he'd said he wanted to spend less time chasing retailers, so I'd put retail outreach under "not recommending." Then we talked about what would actually let him go full-time, and almost all of that math ran through winning new stores. The thing I'd written off moved to the top of my list. He's already half-built his outreach with AI, but he still sends every email by hand, and he dropped his daily target the day after he set it. Third: the business can't see its own split between online and wholesale. Wholesale invoices live in a different system from the shop, so the split is his best guess. He works with business processes in his day job. His own words about his own company: "we run on paper." I don't see that as a criticism. I think it's the most common pattern there is, because expertise doesn't carry over into your own business when you have no time left for it. The finding I was proudest of, a technical email problem I'd verified before the call, he parked. Not a priority right now. That's fair. Pushing it would have been about me, not him. I also told him I'm still in school. Nothing changed.

As you may know I was hired at Nuvex Nova as Content Strategist I pitched the CEO of Nuvex Nova on something that has nothing to do with the content I'm actually hired to do for the company. I told him, straight up, this ones not about Nuvex Nova. This ones about him, personally. And honestly, about me too. Here's the idea. People trust people way faster than they trust a company page. If he just documents what he's actually doing, building the company, the decisions, the stuff thats genuinely hard people start to feel like they know him. And once they trust him, that trust extends to the company too. Its a completely different kind of credibility than any company account can build on its own. (I wasn't asking him to become a content creator. I was asking him to let a few real moments get captured as they happen. A voice note after a hard call. A thought mid-decision. Something that actually happened that day. I'd take the raw material and shape it from there.) We'd already talked about a podcast idea once before. I pitched it again, but as its own separate thing, running outside the regular content pipeline. Relaxed. Recurring. Documenting the journey as it happens. Not scripted, not polished. I told him the truth too, Im not just pitching something I have no stake in. I've been getting into personal branding and content strategy on my own, so this is a genuine two-way thing. He documents his side of building the company. I help shape it, and probably learn a ton doing it. And it helps me build something for myself at the same time. Not me asking him for extra work. Just a real collaboration. He said yes almost immediately. I can absolutely do that, small documentations here and there. We should do a raw podcast. Then he said he'd been thinking the same thing, and wanted to collab properly. We're starting with the podcast. I'm planning it, and I'm hosting it. Two personal brands, one real conversation, starting now. (Repost this ♻️) P.S. if you pitched your boss on something that had nothing to do with your actual job, would you expect a yes?

From a single sentence to a fully branded newsletter in my inbox. Here is the breakdown of the AI newsletter system I built, how it works under the hood, and the technical hurdles solved along the way. The Architecture: Workflows, Agent, Tools The system separates logic, orchestration, and execution into three distinct layers: 1. Workflows: Markdown SOPs outlining explicit execution instructions, guardrails, and known pitfalls for the agent. 2. Agent: Claude Code acts as the orchestrator, deciding which tools to call and evaluating output quality. 3. Tools: Three focused Python scripts handling image generation, HTML compilation, and email delivery. When an edge case or error occurs, the fix is documented directly back into the workflow instructions, preventing repeat failures. Step-by-Step Pipeline 1. Primary-Source Research 2. The agent queries the web and filters strictly for primary research data (e.g., AMA, JAMA Network Open, Menlo Ventures, Oliver Wyman), automatically discarding secondary vendor-blog claims. 3. Structured Content Generation 4. The draft is emitted as structured JSON containing the subject line, preheader, hook, three verified metrics, three core sections, an Effort vs. Impact matrix, key takeaways, and source citations. 5. Parallel Infographic Generation 6. Using the Gemini API (Nano Banana 2), four visuals are generated concurrently (one hero banner and three infographics) aligned with custom brand colors. 7. Email-Safe HTML Assembly 8. A Python build script converts the JSON and assets into inline-CSS, table-based HTML optimized for Gmail rendering, including custom stat cards and styled matrix blocks. 9. Human-in-the-Loop Gate 10. A local preview file is generated for manual review. No email is dispatched without explicit approval. 11. Multipart SMTP Delivery 12. The approved email is transmitted via Gmail SMTP with embedded CID images so assets display reliably without being blocked or clipped. Key Engineering Challenges and Fixes

I have been in enormous debt for a long time and it obliterated the relationship with the love of my life and broke her heart. It put me under the gun to finally figure out how to get my AI business working. Now I see how easy it is - it's just giving value to people that need it, derisking it appropriately for them, and then it all snowballs. Now I've got conversations this week for deals over $100k. if you need help just getting started please shoot me a message, I don't want anyone to have to go through what I did.