Jan Moravec
78 posts

Jan Moravec
@janmoravecAI
I make sure that AI transformations land and deliver real business outcomes | Blockers → adoption → KPIs | Czech Republic + Europe
Katılım Mayıs 2023
92 Takip Edilen62 Takipçiler
Sabitlenmiş Tweet

Jan Moravec retweetledi

Agentic AI adoption is on fire at @Uber, and it's changing the way we build, not just in engineering, but across the entire company.
Today, 99% of our engineers use AI tools. More than 70% of pull requests are attributed to local or cloud agents. And our engineers have built 2,500+ agent skills across the software development lifecycle.
Those numbers are exciting, but they led us to a much bigger question:
How do we bring agentic AI beyond engineering?
Finance. Legal. Operations. Marketing. Customer Support. HR. Procurement.
These functions run on complex workflows that are often manual, highly nuanced, and spread across dozens of systems. You can't automate them effectively by looking at process diagrams or documentation. You have to understand how the work actually gets done.
So we created something called Agentic Pods.
The idea is simple.
We handpicked ~30 of our most AI-proficient engineers (people with deep knowledge of Uber's systems) and paired each of them with a domain expert from a business function.
Then we gave every pod just two weeks.
• Days 1 – 2: Shadow the expert. Observe every step. Document workflows. Ask questions. Build intuition.
• Day 3: Prioritize opportunities based on scale, repetition, business impact, and data availability.
• Days 4 – 5: Build a working agent alongside the person doing the job.
• Days 6 – 9: Validate with several others performing the same work. Does it generalize? Does it actually make their job better?
• Day 10: Ship.
In just the past two months, we've run 16 Agentic Pods across 16 different business functions.
• Capital allocation across 150 cities: 15 hours → 30 minutes.
• Financial pacing reports: 2 days → 10 minutes.
• Marketing web quality assurance: 2 weeks → 50 minutes.
• Support workflow creation: 9,000 manual workflows → self-service automation.
The productivity gains are impressive, but what surprised us most wasn't the speed.
• It was how quickly engineers embedded in unfamiliar domains uncovered opportunities that had been hiding in plain sight.
• The biggest wins rarely come from automating one task. They come from rethinking an entire workflow. Once you redesign the workflow around AI, you often eliminate handoffs, remove unnecessary approvals, replace legacy tooling, reduce vendor spend, and dramatically accelerate decision-making.
• The workflow becomes the unit of automation - not the individual task.
• The most impactful agent skills cut across teams, orgs, functions, tools, and systems.
The biggest lesson? The best AI opportunities are rarely visible from the outside.
You discover them by sitting next to the people doing the work, understanding every friction point, and building with them, not for them.
We're now forming a dedicated team to scale this further and go deeper. They'll deeply understand the work, redesign it from the ground up, and use AI to fundamentally change how the business operates.
It's exciting times!

English

This is what I do: I join the executive team as the internal owner of AI transformation and drive their AI project from the inside. I represent the company and stay on until business outcomes show a real improvement.
In the middle of one? janmoravec.ai
English

@market_sleuth Nature is amazing! Just thinking about the poor bridge downstream. Looks like it has no chance.
English

@askvladi Love it! I firmly believe that 85% of procument can be automated today. 95% tomorrow ;)
English

Announcing Lio's $30M Series A, led by Andreessen Horowitz!
Procurement still operates like an administrative back-office function: rigid software, manual workflows and endless headcount. Enterprises spend over $180 billion annually on procurement talent and roughly $10 billion on procurement software, yet the problem persists. More software hasn't solved it. More hiring won't either.
Introducing @Lio_Technology (formerly askLio) the world's first multi-agent system for procurement. Our virtual workforce is already deployed at some of the world's largest enterprises, taking over the manual work that buries buyers, shared service centers, and BPOs today. But Lio doesn't just do the same job - it does work that was never humanly possible: renegotiating every contract, sourcing across every category, and preparing as well as analyzing every negotiation, all at once.
Lio's AI agents operate on top of existing procurement software and ERPs - no rip-and-replace - autonomously executing workflows end to end.
The results speak for themselves:
- 95% adoption rate
- 85% reduction in manual work
- 10% incremental savings
- 100% customer retention
Lio isn't a dashboard or a copilot. It's the execution layer for enterprise procurement. As one Head of Procurement put it:
"Lio is a cheaper, more scalable, and faster-to-onboard alternative to outsourcing."
Lio’s agents are already managing billions of dollars in enterprise spend across dozens of Global 2000 and Fortune 500 companies – from manufacturers to reinsurers to huge industrial conglomerates.
This raise accelerates our US expansion and the growth of our agent ecosystem as we build the infrastructure powering AI-driven procurement.
A huge thank you to our incredible team, customers, and advisors. Proud to have outstanding investors on board: the round was led by @a16z - special thanks to @seema_amble - with participation from SV Angel, @HarryStebbings, @ycombinator, and a group of leading procurement executives and successful founders.
Additional thanks to @BKRoberts, @arampell, @jamdac, @zephratic and @t_blom.
Whether as an enterprise partner or a new team member — join our mission now!
English

Not a bug. It's my config.
"sessionTarget": "isolated" means truly isolated - no automatic context inheritance.
My cron jobs weren't reading SOUL.md, MEMORY.md, or lessons learned because I never told them to.
Fix: Add explicit context loading to cron prompts:
1. Read SOUL.md
2. Search memory vault for critical lessons
3. Read today's memory file
4. Then do the work
OpenClaw works as designed. I just misunderstood what "isolated" means.
The real insight: autonomous sessions need explicit instructions to load context. They don't inherit it automatically.
English

I might have found a bug? Does anyone else struggle with #openclaw forgetting who they are and their instructions when running scheduled jobs?
My OpenClaw repeated the exact same mistakes five times in one day, always promising that they will not appear again. They always did.
Then I asked it to check if SOUL.md, MEMORY.md, and other instructions are shared with the LLM during scheduled/cron jobs. They aren't!!
The agent wakes up fresh, no context, repeating mistakes the main session already fixed.
Fixed by updating cron prompts to load context first:
1. Read SOUL.md
2. Search critical lessons
3. Check today's memory
4. Then do the work
If your scheduled agents don't load context, they're learning nothing between runs.
English


