Nimlits
A place for people
and AI to work together.
Co-founder & Head of Product · 2025–Present
Reconstructed walkthrough
The weekly team review.
Give a Nim the brief. Let a second teammate question the draft. Make the final call yourself.
The assignment
“Prepare our weekly team review.”
Atlas has one product update to work from. Pull out what changed and flag what still needs a decision.
Source note · Chat update
Chats now show each Nim’s saved name and character. Automated checks for the change passed. The team still had to try it on a phone.
Two teammates, one thread
A second pair of eyes.
“Each Nim now appears under its own name and character. The chat update passed testing.”
“Which tests? The team still had to try this on a phone. Let’s say exactly what passed.”
Before the fix
This reply is missing from the editor’s context.
“I can see the request. Which draft should I review?”
After the fix
“Each Nim now appears under its own name and character. The chat update passed testing.”
“Which tests? The team still had to try this on a phone. Let’s say exactly what passed.”
The editor now receives Atlas’s reply with the request. It can point to the exact claim that needs checking.
Human review
The call is yours.
Weekly team brief · Revised
Changed Each Nim now appears in chat with its own name and character.
Still to check Automated checks for this change passed. Verify it in the iOS and Android apps.
What this replay is based on
The weekly review and Atlas come from the Nimlits product deck. During a July 2026 production test, two AI teammates initially said they could not see each other’s replies. The next day, the team verified that the second could critique the first answer and the first could respond. The chat change and test results come from an October engineering review. The dialogue is reconstructed for this walkthrough.
The problem
Teams need more than another chat with a model. They need a shared place to assign work, keep context, inspect progress, and give feedback as people and agents collaborate.
My contribution
- Lead product strategy, experience design, and roadmap decisions for Nimlits, formerly Lydo.
- Translate customer workflows into requirements for shared context, agent orchestration, connected tools, permissions, and human review.
- Work directly in the product development process with coding agents, GitHub, and engineering, from scoped specifications through review and release iteration.
- Shape positioning, usage-based pricing, and beta onboarding for technical and nontechnical teams.
Where the work stands
Nimlits is in private beta. The work spans the collaborative workspace and the execution systems behind persistent AI teammates. Product development and rollout continue.
What this demonstrates
Taking a broad technical thesis and turning it into concrete workflows, product decisions, and a customer experience that a small team can build and improve.
Current venture. Product direction and development scope are described separately from rollout status.