showed the onboarding to an HR rep with 200 employees. she had 4 minutes between meetings. if she couldn't figure it out in 4 minutes, it wasn't simple enough.
@starter_story spent years as an engineer thinking building was the hard part. marketing and customer discovery is 10x harder emotionally when starting from zero imo.
@charlesordo 100% truth. until a stranger actually pulls out a card or pays an invoice, everything else is just practice reps imo. customer cash changes everything.
@auren product speed matters but regulatory compliance and audit logs are still pretty sticky moats imo. once legal/hr relies on a system of record for state mandates, switching is a headache.
@sophie_launch building https://t.co/a2r9D5vHT8 to help growing california teams handle mandatory sexual harassment prevention training and export audit-ready records with zero spreadsheet mess. appreciate you doing this!
@dharmesh the part about not spending sunday night updating a crm is huge. solo operators just want things recorded and tracked automatically without extra admin friction imo. congrats on shipping.
@nicochristie huge respect for this. building 0 to 1 is brutal on family and health, especially when early prototypes dont stick. congrats on everything you built and excited to see whats next.
@jonathan_wilke haha until you cross 5 employees in california and suddenly realize state training rules and compliance records are legally mandated. state audits are no joke imo.
@Keanaalabre ops and gtm hiring in the bay is crazy right now. everyone wants early generalists who can wear 4 hats before specialized roles get carved out imo.
@annajmalayan the 0 to 1 engineering market in sf right now is wild. so many founders looking for people who can handle full-stack plus ops ambiguity without needing hand holding imo.
designed the onboarding to look clean and minimal. first HR rep who tested it said "where do i click." hand-holding is the product right now. pretty can wait.
@jasonfried ran into this when building our first prototype. had 4 complex approval steps before realizing customers just needed one button and an export link. simpler is almost always harder to ship but easier to sell.
@rauchg@X shipping small features directly from user DMs within 48 hours builds more customer loyalty than a 6 month roadmap ever could. speed is the best retention mechanism.
@shreyas the fastest way to lose someone is sounding like a corporate-ey slide deck. in b2b, people do not want a philosophical explanation, imo they just want to know if the button solves their immediate headache.
@amasad spawning 100 agents is the easy part. tracking which one executed what action and keeping the audit trail defensible is where the real plumbing work begins.
@sama most small teams treat defense like insurance until an auditor or breach forces the issue. the shift is moving from static annual checklists to continuous verification that takes zero manual hours.
@rauchg autonomous exploit agents mean audit readiness can no longer be a quarterly fire drill. if you cannot export defensible logs and verify permissions continuously, you are basically operating blind.
@dhh the speed trap is real. when momentum hits before the operational rails exist, half your day becomes triage instead of building. setting up the durable boring systems early is what keeps the rocket from shaking apart.
@paulg the hardest cut i made was an entire backend module my engineer friends loved. customers did not care about the architecture, they just wanted a clean completion certificate. killed 3 weeks of work in 10 seconds.
@gregisenberg testing this in cold outreach right now. generic templates die immediately, but naming the exact line item they failed on an audit still gets opened in 2 minutes. specificity bypasses the filter whether it is human or an agent.