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
- What are my products missing?
- If the features are so great, why dont people want them?
- How could my tech talk generate more engagement?
After Shipping
When you bring eyes to your saas
You might realize that it needs some improvements.
Psyco
If you have ever wondered about psychology.
So…wait.
To improve all that, I need to get the psychologycal stack at the same level than the technical one.
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
- Tinker & be willing to share
- Mind the brand
- Prepare the
slides.md - Make a ppt-review
- Prepare a mail communication
- 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-brdImproving 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 talk.
Improving your Products
Leave them be for a while to get volume/repetitions on their current state.
Done?
Ok, now lets tweak with some sense that it sgoing 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:#e1f5feThe 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.
Product emails
Want to increase LTV?
Make sure that your potential client remembers that you are there to help them.
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
DIY via ebooksHave you Plugged PostHog?
See how people really interact and what they want from you.
What they do, not what they say.