We built this because we needed it ourselves.

Ed leads sales, marketing, and go-to-market strategy for Audity. He's also an active AI transformation consultant through rac/AI, running engagements for mid-market companies. He's the one on the podcast, in front of the client, and on the demo call walking through what a real discovery looks like.

That practitioner perspective is why Audity is built around how you actually sell and run discoveries, not how a software team imagines you do. He uses it on real client work every week, so the product stays honest to what wins business. When he's not working, he's skiing, mountain biking, or camping in Tahoe.

Jeremy built Audity. He's the product owner and lead developer, leading the development team and responsible for every feature, integration, and release. He sets the product direction and ships it, so the platform stays tightly aligned with how consultants actually run discoveries.

He's also an active AI transformation consultant, so the features he ships come from real discoveries, not hypothetical use cases. Request something and Jeremy is usually the one building and shipping it within the week, which means the platform keeps pace with the work you actually run.