Closing the code to impact gap

Tl;DR

Thoughts after this theo video, shipping a micro-saas in front of people and doing some tech talks.

Intro

Everything can be done with code and llms/agents are pretty good with that.

So…why arent we?

Product, how’s and features matter.

But so that’s the packaging.

The UI/X, the presentation, the how easily is to understand what you do or you dont do.

Lets get better and close the gap.

Some Context

One more time, a series of unconnected chaotic events.

And some questions: that thing that happens when you create

1. What are my products missing?
2. If the features are so great, why dont people want them?
3. How could my tech talk generate more engagement?

Create a sth sth sth like... a Landing Page based on NextJS with a cool and modern UI

Include a `dockerfile` and `docker-compose.yml` that will control the title, description, open-graph image, favicon location and other global website variables via environment variables.

Add also a docker-compose.portainer.yml to use assuming that the image has been built already.

Create also a makefile with the following commands:

* `make help` - Show available commands
* `make install` - Prepare the dependencies for local development
* `make dev` - Run development server
* `make container` - Build and Run in Docker container

Create the `z-development-plan.md` with independent and testable phases that can be completed sequentially.

When it is completed, create a `z-walkthrough.md` with the steps to deploy the application and what each part of the tech stack does on a high level to bring the features to life.

Consider adding a Terms of Service / **terms and conditions and privacy policy** to the website, which will be governed by two separated markdown files.

Add also a faq section, that instead of been controlled via a json, lets have it controlled as per the frontmatter and content of separated markdown files inside the folder `faq`. 

The logic should read them in order as per their file name and show them in the right component of the UI.

> When these change, consider sending an email to your existing clients!

Consider adding **Umami web analytics capabilities** to the WebApp when using the container, by adding the possibility to feed the PUBLIC_UMAMI_SCRIPT_URL and PUBLIC_UMAMI_WEBSITE_ID to be used via <script defer src="" data-website-id=""></script>

If you are using Python, design proper functions with docstrings, so that the codebase is understandable, scalable and self-documenting.

#sudo apt install gh
gh auth login
#gh repo create make-xyz --private --source=. --remote=origin --push
    
git init && git add . && git commit -m "Initial commit: simple landing website" && gh repo create make-xyz --private --source=. --remote=origin --push
###du -sh .
#docker stop $(docker ps -a -q) #stop all
#docker system df

So…wait.

To improve all that, I need to get the psychologycal stack at the same level than the technical one.

Because both are coupled.

Landing pages must haves are coupled with psychology.

From the example of one of my last tech talks, here is what it came out: mermaidjs powered here

As you can imagine, this goes as: can we now have a community chat slack alert the date before alert and the 1h before?

mindmap
  root((Presentation
Psychology))
    Emotional Hook
      Problem Amplification
        Shared Enemy
        Slack DM Pain Point
      Limbic Engagement
        The Why first
        Purpose over Logic
      Contrast Theory
        The Sparkline
        What Is vs What Could Be
    Attention Control
      Zeigarnik Effect
        Open Loops
        Unresolved Mystery
      Self-Generation
        Socratic Questions
        Audit vs Statement
      Primacy & Recency
        Power Openings
        Action-Oriented Closings
    Cognitive Clarity
      Dual Coding
        Visual + Verbal
        Mermaid Diagrams
      Rule of Three
        Pattern Recognition
        Bronze-Silver-Gold
      Cognitive Load
        Progressive Disclosure
        V-Click Animations
    Professional Trust
      Identity Alignment
        Pragmatic Reframing
        Dynamic ORM vs Chatbot
      Social Proof
        Case Studies
        Time-to-Ship Validation
      Far Transfer
        BA Skills to AI Prompts
        Executable Requirements

Whats the catch?

You are missing parts.

Improving your Presentations

The workflow that I have for this year presentations is:

0. Tinker & be willing to share
1. Mind the brand
2. Prepare the slides.md
3. Make a ppt-review
4. Prepare a mail communication
5. Prepare engaging slack/follow ups notifications

Why to do so?

because you improve your brand: specially if you have the same repo for your consulting landing, that where you store the ppts

#npx slidev build --base /presentations/ba-brd/ --out dist-ba-brd
npm run build
mkdir -p public/presentations && cp -r y2026-tech-talks/2-ba-brd-development/dist public/presentations/ba-brd

Improving your emails

Wondering why not many people are going to your tech talks?

You might need to improve how you coomunicate its value via email.

Get better at conveying what you will do via mail. Like this.

Improving Slack Engagement

Got a centralized repo with your presentations as text?

There is no excuse not to write a psycologycal engaging email and/or slack alert messages to get more people flowing to your funnel.

I mean: assisting to your tech talks.

Improving your Products

Leave them be for a while to get volume/repetitions on their current state.

flowchart LR
    %% Styles
    classDef state fill:#E3F2FD,stroke:#1565C0,stroke-width:2px,color:#0D47A1;
    classDef start fill:#43A047,stroke:#1B5E20,stroke-width:2px,color:white;

    %% Nodes
    Start((Start)):::start --> More
    More(Doing MORE):::state
    Better(Doing BETTER):::state
    Newer(Doing NEWER):::state

    %% Internal Feedback Loops (The Grind)
    More -- "Scale Up" --> More
    Better -- "Refine" --> Better
    Newer -- "Test" --> Newer

    %% The Progression Journey
    More -- "Capacity Hit" --> Better
    Better -- "Optimized" --> Newer
    
    %% The Upward Spiral
    Newer -- "New Baseline" --> More

Done?

Ok, now lets tweak with some sense of whats going to move into a better direction.

graph LR
    %% 1. The Split
    Start[Define] -->|Why| B[BRD]
    Start -->|What| C[FRD]
    Start -->|How| D[PRD]

    %% 2. The Join
    B & C & D --> E(Clarify)

    %% 3. The Linear Flow
    E --> F[Development Plan]
    F --> G[Finished PoC]

    %% Styling
    style G fill:#f96,stroke:#333,stroke-width:4px
    style Start fill:#bbf
    style F fill:#e1f5fe

The Copy

If you have be smart and make so that your full micro-SaaS copy is in one file, like: copy.md

You can have inmediate feedback from any LLM, like gemini on how and why you can tweak a certain title/cta/whatever.

Become authoritative and articulated.

Product emails

Want to increase LTV?

Make sure that your potential client remembers that you are there to help them.

Such astro components with mailtrap help.

Remember to measure and optimize KPIs: Like CTOR

Conclusion

Im preparing an agentic workflow for those who are interested to close their gap ando get their ideas succed.

In the meantime, you can:

Consulting Services

Consulting - Tier of Service

DIY via ebooks

Distilled knowledge via web/ooks to enable you to create

Have you Plugged PostHog?

See how people really interact and what they want from you.

What they do.

Not what they say.

Not what you think.

This helps: the best product tool

Find the revealed preferences.

Not the announced ones.