Thoughts

Dave Tedder uses an ROI-first decision framework for every project and tool decision: (1) Will it make money? (2) Will it save time? (3) What's the implementation cost? (4) What's the payoff timeline? He expects concrete estimates, not vague language. His priority triage: "Do now" if it makes money this week or saves 1+ hours immediately, "Schedule" if clear ROI but needs setup, "Delegate/automate" if repetitive or low-skill, "Kill it" if no clear ROI or maintenance exceeds benefit.