Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

NO SOFTWARE FOR YOUR WEIRD PROCESS? BUILD IT. every company has one process nobody sells software for, and everyone works around it. ERP AI lets you build that software from a prompt, and proto is the agent that does the building. → describe the process to proto → it...

41,386 görüntüleme • 12 gün önce •via X (Twitter)

7 Yorum

matt profil fotoğrafı
matt12 gün önce

try it and judge the result yourself:

fred profil fotoğrafı
fred12 gün önce

love that the agent drafts in a private workspace first

luca profil fotoğrafı
luca12 gün önce

warehouse and payroll are the ones i'd try first. so much duct tape in those

berni profil fotoğrafı
berni12 gün önce

crm, payroll, warehouse all from a prompt is a big deal for smaller companies

Geloria profil fotoğrafı
Geloria12 gün önce

the agent working the records and not just generating a ui is the real unlock

natt profil fotoğrafı
natt12 gün önce

super clean flow. describe, draft, approve

billy profil fotoğrafı
billy12 gün önce

finally someone going after the boring stuff that actually runs the business

Benzer Videolar

WHAT IS AN AI "SOFTWARE FACTORY" AND IS IT HYPE (31 MINUTE BREAKDOWN) I think it's a silly name for a genuinely USEFUL idea! A software factory is 5-6 markdown files that sit next to your code and tell your agents how you like to work, so you can build high quality apps 24/7. It's going viral because AI coding has a trust problem. The model can build the feature, but with no structure around it you end up babysitting the agent, wondering what changed and hoping it didn't break something important. So you build with agents the same way a factory builds physical products! 1. Each feature gets its own station, which in software means its own branch, so multiple agents can work at the same time without stepping on each other. 2. The build station gives the agent rules for how to write the code, because "it works" is very different from "a developer could open this repo next month and understand what happened." 3. The proof station makes the agent show evidence. Screenshots, videos, speed numbers, before-and-after states. It has to prove the thing works instead of saying it works. 4. The review station runs the work through a code review agent, and if it doesn't clear the bar, it goes back through the line. 5. Then you show up at the end to merge. For a 100+ years people have run production this way, and it worked because the structure is good. The full episode on what’s a software factory is NOW live on The Startup Ideas Podcast (SIP) 🧃 with the wonderful Micky Watch: So is it hype?!? I don't think it is, because of what it does to your output! WITHOUT a factory, you build ONE feature at a time and you're the bottleneck at every step, prompting, checking the diff, testing it yourself, hoping nothing else broke (spoiler alert it often does). WITH a factory, EACH feature runs in its own isolated copy of the app, so you can have 10+ of them going at once, and each agent has to prove its own work and pass a code review before it ever reaches you. Instead of supervising the work, you're APPROVING finished work that already has evidence attached. REALLY interesting to see how work with agents is evolving to be….well, similar to working with people!

GREG ISENBERG

32,056 görüntüleme • 1 ay önce