The 120-Day Logbook: My Public Experiment to Tame Founder Chaos with AI Systems

Saulius - visitor profile
Jun 15
3 min read

If you're interested in exploring and trying to adapt to the AI revolution or early-stage founder, you know the feeling. Or you are the CEO, the lead developer, the head of sales, the entire support team, and the person who remembers to buy more coffee. It's a state of beautiful, productive chaos.

But it's also a trap. The more successful you become, the more the operational chaos pulls you away from the one thing that matters: building your product or adapting in the AI developments world.

I'm fascinated by this problem. I'm not a developer or a "10x engineer." My background is in seeing how businesses work—or don't. And I've become obsessed with a single question:

How can we use the new wave of simple, no-code AI tools to build operational systems that give founders their focus back?

So, I'm running a public experiment!

For the next 120 days, I'm on a public journey to become a sought-after AI Systems Architect.

This website and blog will be my Public Logbook. No guru-speak. No polished case studies (yet!). Just a transparent, real-time account of my process. You’ll see:

My notes on the specific operational bottlenecks I see in B2B SaaS.
The simple Miro boards where I sketch out systems to fix them.
The no-code automations I build using tools like Make.com, Zapier, and various AI models.
The inevitable failures, the frustrating roadblocks, and the "aha!" moments.
Prompt engineering experiments: https://docs.google.com/spreadsheets/d/15RfWAwSJj8pl13p4jmqWagvq99AFgiZWHtne4OP-0gw/edit?usp=sharing
Public videos: https://www.youtube.com/@WorkTravel.Agency/featured
Live streams: https://www.youtube.com/@WorkTravel.Agency/streams

My goal isn't to become a coder. It's to become an architect—someone who understands a founder's operational pain so deeply that they can design a simple, robust system to make it go away. I'm starting this journey with a deep focus on helping early-stage B2B SaaS founders and building product distribution partnerships and a local representative/ambassadors network globally.

This isn't a one-way broadcast. It's the start of a conversation. I'm building this in public because the collective wisdom of those in the trenches is worth more than any textbook. I'll be sharing my learnings, and I hope you'll share your challenges.

Let's kick this off with the first entry in the logbook.

My first question to everyone reading this is: What's the one repetitive, non-productive task that you wish a robot would just handle for you?

Drop a comment below. Seriously. Let's start mapping out the chaos together.

Talk soon,Saulius

Master 120-Day Strategic Plan: Overview

Phase 1: Preparation & Foundation (Days 1-30)

Objective: To "sharpen the axe" before the first swing. This phase is internal-facing. We will build the operational backbone, brand assets, and a content backlog to ensure the public launch is smooth, professional, and sustainable. No public content will be released in this phase.

Week 1 (Days 1-7): Strategic Alignment & Niche Immersion
Week 2 (Days 8-14): Brand & Operations Setup
Week 3 (Days 15-21): Content Systemisation & Backlog
Week 4 (Days 22-30): Final Checks & "Go/No-Go" Review

Phase 2: Self-Education in Public (Days 31-120)

Objective: To execute the "Public Logbook" strategy, build trust and authority within the niche, validate the "Strategic Diagnostic" offer, and secure the first paid client. This phase is external-facing.

Month 2 (Days 31-60): Launch & Learn. Focus on consistent content production and engagement. The goal
is to spark conversations and book the first free "Strategic Diagnostic."
Month 3 (Days 61-90): Momentum & Validation. Analyse early data. Double down on what works. Refine the diagnostic process. Actively pursue converting a diagnostic into a paid project.
Month 4 (Days 91-120): Optimisation & First Revenue. Systematise client delivery. Focus business development efforts on the most promising leads. The goal is to have a signed retainer or paid project by Day 120.