Co-founder at Onepilot | Forbes 30 Under 30
Obsessed with turning complex operational chaos into scalable systems. At Onepilot, our AI-native platform and a network of 2,000+ independent freelancers run customer support for 300+ brands, handling millions of interactions a month, including the complex, multi-turn workflows traditional BPOs can't touch. Self-taught since age 12. Forbes 30 Under 30. 🚀 Scaling to $35M ARR and beyond. 🛠️ Building the future of automated business infrastructure.
Markdown supported · ⌘↵ to post
Halfcycle
Your own three-month summary holds the answer you land on: the 300-prompt brainstorm that went straight into production with no spec step (two fixes per feature, the core rule redefined three times) against the small tool that went from discovery to deployed in four days because it was scoped first. The fatigue mostly comes from deciding by approving diffs, one at a time, all day. We built Halfcycle around that: the deciding happens first, one question at a time with you, inside Claude Code or OpenAI Codex, and the agents build from those answers, so less of your day is approving things you won't remember. Worth trying npx halfcycle on the next feature you'd otherwise brainstorm for 300 prompts. Of the three times that rule was redefined, how many could a question asked before the build have caught?