--EL BLOGO--
Thursday, September 10, 2026
Tuesday, September 08, 2026
08.09.2026
This is one of those days, that is a turning point in any person's life.
its is just like those days in Freising but now with this.
my thoughts today are:
I do not regret the life I have lived.
I regret :
- Not taking care more of myselft, probably this shouldnt have happend.
- Not staying with my parents more, specially since the last years onwards,
- Not being closed with my daughters
- Not being closed with my systers
and regret and get angry about not being able to contribute more to the community and the world.
Starnberg, 08.09.2026
I hope I can have time to reverse all this.
this is the only thing I ask now.
Sunday, September 06, 2026
1%
1.Remove any crutches
2. Re imagine the Timeline
3. True Freedom
4. Adversity in your life
5.Build a Strong Networking. Problem solver..,
+ meditate,
Sunday, July 26, 2026
Four Loops for validating and measurement robot development
Note: this are generic notes with ChatGPT aid : (26.07.2026)
One of the biggest mistakes robotics startups make is treating every iteration as a technical iteration. In reality, you're trying to reduce uncertainty across several dimensions.
| Loop | What are you validating? | Typical question |
|---|---|---|
| 1. Customer | Problem and market | Are we solving a real problem worth paying for? |
| 2. Technical | Robot capability | Can the robot reliably perform the task? |
| 3. Operational | Deployment and usability | Can customers actually use and maintain it? |
| 4. Business | Business model | Can we build a profitable, scalable company? |
Notice that only Loop 2 is really about robot development. The other three are about turning a capable robot into a successful business.
Think of it as four risks
A robotics startup fails if any one of these is false:
- People want it.
- The robot can do it.
- The customer can operate it.
- The economics work.
Many startups spend years proving #2 while never really testing #1 or #4.
During early development
Suppose you're building an autonomous warehouse inspection robot.
You might run all four loops in parallel:
Customer loop
- Interview 20 warehouse managers.
- Observe current inspection workflows.
- Ask what inspections are missed and what that costs.
Technical loop
- Can the robot navigate a warehouse?
- Can it detect damaged pallets?
- Can it run for an 8-hour shift?
Operational loop
- How long does installation take?
- Can staff recover the robot if it gets stuck?
- How much training is needed?
Business loop
- Would a customer pay €1,000/month?
- How many robots would a typical warehouse need?
- What does deployment cost you?
They influence each other
Imagine you discover:
- Customers only need inspections twice a day (Customer loop).
- That means 99% navigation reliability is unnecessary (Technical loop).
- Simpler hardware reduces maintenance (Operational loop).
- Lower costs improve your margins (Business loop).
One customer insight can change the entire engineering roadmap.
A practical framework
Instead of thinking:
Build → Measure → Learn
For robotics, think:
Hypothesis → Experiment → Evidence → Decision
Every sprint should answer one important question, such as:
- Customer: "Warehouse managers will pay for automated inspections."
- Technical: "The robot can detect pallet damage with >95% accuracy."
- Operational: "A technician can install the system in under 2 hours."
- Business: "We can deploy profitably at our target price."
If the evidence supports the hypothesis, move forward. If not, adjust the product, the market, or the business model.
For robotics founders, this "risk-first" mindset is often more useful than thinking in terms of feature development. It helps ensure that engineering effort is spent reducing the uncertainties that matter most, not just building more capability.
To sum up.
Specifically for robotics
Most robotics founders should think in four loops, not just Build–Measure–Learn.
Loop 1 — Customer learning
Before writing code:
- What problem hurts enough?
- Who pays?
- What is the current workflow?
- What's the ROI?
Metrics:
- interview count
- willingness to pilot
- pilot conversion
- paid commitments
Loop 2 — Technical validation
Can the robot actually perform?
Metrics might include:
- success rate
- localisation error
- navigation uptime
- grasp success
- battery life
- intervention frequency
Loop 3 — Operational validation
Can customers live with it?
Measure:
- installation time
- training time
- maintenance frequency
- mean time between failures
- operator satisfaction
Loop 4 — Business validation
Can this become a company?
Track:
- customer acquisition cost
- gross margin
- deployment cost
- payback period
- annual recurring revenue (if applicable)
Saturday, July 25, 2026
7 Questions that every business must answer
This is an abstract from P. Thiel, book 0 --> `1, I read first in Mexico City in 2016 when working for Huawei Technologies, I didn't understand most of the book. Now I re-read it, in Starnberg 2026, building Isar Subsea Robotics and all makes sense.
1. The engineering question.
Can you create breakthrough technology instead of incremental improvements ? . Here the key is to target 10X improvement from your nearest competitor or competition in general.
2. The Timing question.
Is now the right time to start this particular business?
3. The Monopoly Question.
This referes to two things, one to the 10X in number 1. and are you starting with a big share of a small market ? . Basically this refers to bascially aim to create a Monopoly (i.e the author refers to companies Google, and others).
4. The People Question
Do you have the right team ?
5. The Distribution Question
Do you have a way to not only create but deliver your product ?
6. The Durability Question.
Will your market position be defensible in 10 and 20 years into the future? , this also refers that as long as you take this approach, take your time to enter the market, the company doesnt have to be the first.
7. The Secret Question.
Have you identified a unique opportunity that others don't see ?
25.07.2025
Monday, November 17, 2025
Once Upon a time 1873
Monday, October 27, 2025
Anti Procrastination Tool (AntiPro)
A tool for avoiding Procrastination
it is called, Anti Procrastination. (AntiPro)
- The different axis represent a subject that is important to focus; therefore it can be 2 axis, 3 axis (3D), here are represented 6 subjects as an example to focus.
- This tool is to be used per week.
- The Centric round are used to represent a day of the week.
- Everytime there is something done or executed, it is represented with a dot and a tag or label.
- This can be as a routine used.
Luis Orozco.
