If a web dev is going to start rolling their own CRM (maybe without realizing that's what they're doing), there's less perceived friction if they just start bas

If a web dev is going to start rolling their own CRM (maybe without realizing that's what they're doing), there's less perceived friction if they just start bashing out one more web form (with fields that make the user do some of the routing and prioritization work) than if they must first do enough homework to wire something into the org's email server, where prototype-grade code could really screw you over. I think this is a problem Zed Shaw set out to solve with a new framework, though he didn't display the "100.0% of messages must be delivered" attitude that would make me comfortable tinkering with it.