What to vibe-code
First posted on LinkedIn.
We’ve been running weekly Replit office hours and demos. A few patterns are emerging that can help you decide what to replace with your own vibe-coded tool.
Replacing spreadsheets is a good mental model for what to vibe-code and which internal tools to replace.
A simple heuristic for ease of production deployment: look at where data comes from and where it goes.
- Internal → Internal. Low chance. You’re inside systems of record.
- External → Internal. Hard. Writing into internal systems creates trust and control issues.
- Internal → External. Good chance. You read context, but don’t touch core systems.
- External → External. Best chance. Fastest to build and ship.
Read is easier than write. External is easier than internal.
Our internal tools (including Google Docs) fall into three groups:
Coordination: Who does what, when. Tasks, owners, status. People work separately but stay aligned.
Collaboration: People share context, discuss, and react. Comments, threads, meetings. Work moves forward through exchange.
Co-creation: Multiple people work on the same artifact at the same time. Docs, slides, whiteboards. The output is shaped live together.
My current take: as AI agents become primary builders, coordination and co-creation between humans shrink. Agents handle execution and even draft artifacts. What remains is collaboration — places where human judgment, context gaps, and taste still matter.