🚀 Pilot programs aren't just about feedback—they're about co-creating the future with your users. At Clarify, this belief helps us build a product that doesn’t just meet your expectations, but exceeds them. And a key ingredient in walking the walk with this worldview is finding ways to uncover all the valuable feedback you, our community, can give. This was the motivation behind the launch of our pilot program three months ago. 🌱 In our recent blog, Austin Hay and Patrick Thompson take a deep dive into the lessons we've learned along the way—and the advice we’d pass on to other early-stage companies looking for PMF. Here are the key CRM-specific takeaways: 🍽️ We won't give you a product we ourselves wouldn't enjoy using: Dogfooding our own CRM helped us refine key features and uncover significant improvements quickly. 🧩 Feature sequencing matters: When we focused on product throughlines for top tasks, we could build more efficiently and deliver features that resonated with users. 🧠 You want your CRM to act as your operating system: Users wanted to integrate their workflows directly into the CRM, reaffirming our belief in CRMs as customizable platforms and integration hubs. 🗺️ Modern sales workflows need structured pipelines: This was another meta lesson. As we built out our sales-ready pipeline, a robust organizational system was crucial for managing the pilot program effectively. We've detailed our four-phased approach to pilot programs—from the initial learning phase to becoming sales-ready—in the full write up. Each stage brought its own challenges and insights, helping us refine both our product and our processes. 🔄 As we continue to grow Clarify, these learnings are shaping the future of how we think about next-gen CRM. We're excited to build a product that truly resonates with how modern teams need to work. 🚀 Want to learn more about how we structured the program and the takeaways we’re folding into the product? You can find the link to the post in the comments. 👇
About us
Next-gen CRM, unifying customer data, automation & analytics.
- Website
-
http://getclarify.ai/
External link for Clarify
- Industry
- Software Development
- Company size
- 1 employee
- Headquarters
- Seattle, Washington
- Type
- Privately Held
- Founded
- 2024
Locations
-
Primary
Seattle, Washington, US
Employees at Clarify
Updates
-
CRMs have come a long way, but the legacy options available to revenue professionals are too often stuck in the past. Our co-founder Austin explores how we got to the present-day CRM, and why it's time to reimagine what we expect of them. 👇
Remember when your boss used to say, "If it's not in Salesforce, it doesn't exist" and you'd resign yourself to setting aside a few hours to update all your data manually? 📊 Well, times are changing, and so should our CRMs. Let's take a quick trip down memory lane to see how we got here: 📇 1980s: Digital rolodexes like ACT! hit the scene 💻 Late 1990s: Modern CRM software emerges ☁️ Early 2000s: Cloud-based CRMs revolutionize access 📚 Mid-2010s: The B2B sales playbook becomes standardized & CRM options multiply Despite all this progress, we're still stuck with CRMs that feel like they're trapped in the past. They promised to streamline our work, but instead, we're wasting time on manual data entry and still not getting a true, unified view of our customers or saving time on day-to-day workflows. Why? Because legacy CRMs haven't kept up with the times due to their: ❌ Rigid structure ❌ Lack of real-time insights ❌ Poor handling of event-based data ❌ Limited analysis capabilities ❌ Creation of new data silos It's 2024. We shouldn't be spending 20% of our time just keeping our CRM up to date. You deserve a CRM that's a force multiplier, not a burden blocking you from doing your best work. 🤖💡 But as we charge toward a RevTech future where modern, AI-native capabilities make this vision a reality, it’s important to understand how we got to the present moment in CRM history, and why we need to reinvent how they work for us. Check out the latest article on the Clarify blog to dive in. Link in the comments 👇
-
Today’s CRM options have come a long way. 🤯 From the days of the the physical rolodex to the age of manual spreadsheets to today's complex ecosystem of options, revenue professionals have used a wide range of tools to manage relationships over the years. But here's the thing: Despite all the technological advancements, we're still stuck in the paradigm of the digital rolodex. 😵💫 Too often, people have to spend hours manually inputting and updating data, wrestling with clunky UI, and trying to extract value from systems that demand more than they give. It's time for a change. At Clarify, we believe that rich context–a blend of informational and personal data–is what truly defines relationships. Which is why we’re building an AI-native CRM that can help you easily find, connect, and nurture relationships with the people who matter most to your business. We’re building this vision for the CRM of the future is built on three key tenets: 1️⃣ Modern: Fast, collaborative, and a joy to use. 2️⃣ Flexible: Event-driven and customizable to grow with your business. 3️⃣ Intelligent: Taking work off your plate to help you learn and execute better and faster. We're moving from a world where CRMs are passive data repos to one where they're active partners in day-to-day work. From pull-based systems that require constant input to push-based systems that continuously provide value with minimal effort. The modern CRM isn't just about storing data–it's about understanding it, deriving insights from it, and using it to build more meaningful, authentic relationships at scale. Want to learn more? Check out the CRM Manifesto from our co-founders, Patrick Thompson, Austin Hay, and Ondrej Hrebicek (linked in comments). 👇
-
Hackathons: Love 'em or hate 'em? At Clarify, we LOVE 'em ❤️ Especially when they lead to 5 new GA'd features (with more to come)! 🎉 Ondrej Hrebicek just published an article on our blog covering all the lessons we learned from planning and executing our hackathon in Seattle a few weeks ago. Hint: It involves crystal trophies, loose end times, and a whole lot of team spirit. 👀 Check out his post below for more insights (and we'll drop the link to the full article in our comments). 👇
I ❤️ hackathons so it was a blast to hold our first one at Clarify recently. 24 hours, 11 people, and 5 GA'd projects later, I jotted down some notes about why this one felt different and what worked so well we will absolutely do it again next time. ⭐ Don’t stress the prep — over-organize and risk turning what should be a fun, spontaneous event into just another company initiative ⭐ Involve everyone — we’re saying no to PD hackathons! Our own Sam Larsen-Disney explains in his The Hackathon Survival Guide how all roles at all levels can make a huge difference ⭐ Productize right away — dedicating the following week for shipping strikes a great balance between ambitious hacks and grounded, realistic projects ⭐ Skip the cash prizes — awards w/ meaning can quickly turn into coveted collector’s items with unlimited incentive potential. In our case: simple, elegant crystal trophies ⭐ Sharp start time, loose end time — keep a level playing field and respect the team’s time, then leave room for late night jam sessions that turn into their own special moments At the end of the day, our first Chrome extension, a Zapier integration, a Raycast plugin, dark mode, and universal record popovers have now GA’d, and the remaining ones are all lurking in prod behind a FF. If any of this sounds interesting and you’d like to join me, Patrick Thompson, Austin Hay, Andrew Kramarev, Michael M., Eugeny Voronin, Ashish Pandhi, John Jiang, Sam Larsen-Disney, and Adam T. on our startup’s journey, let me know! https://lnkd.in/gyyVQAzi
-
-
It’s great to see the CRM + automations category featured a16z's market map of AI applications in sales (and also awesome to be included as an innovator at the forefront of the category ❤️). If you’re a founder or sr. revenue leader, we recommend taking a read through the full write up from Andreessen Horowitz. Here’s what stood out to us from their analysis: 🤖 AI will fundamentally reimagine core sales systems and workflows 🏗️ Future CRMs must handle both structured and unstructured data 📚 Comprehensive, shared context across go-to-market teams is crucial 💲 Common sales activities will be redefined or eliminated These are all trends we’ve seen on the ground as revenue teams are increasingly pushed to generate more value with more data for less overhead. Here’s how we’re approaching building an AI-native CRM that solves for these shifts: 1️⃣ Multi-modal data foundation: We’ve built a flexible custom object system from the ground up to help revenue teams align their CRM to their business model and marry robust structured and unstructured data from sales and marketing use cases. 2️⃣ Unified revenue system: We’re breaking down silos between sales, marketing, and customer success to support seamless collaboration, data sharing, and shared use cases (like attribution). 3️⃣ Intelligent automation: We’re helping customers cut mundane tasks like data entry and follow-up reminders and focus their sales reps on high-value interactions. 4️⃣ AI powered by rich context: We’re combining a structured data enrichment waterfall with comprehensive unstructured data capture to power truly intelligent and meaningful sales workflows. 5️⃣ Flexible GTM Strategies: We’ve built an AI co-pilot right into the CRM to help users answer questions and adapt on the fly without needing to learn a new tool. We firmly believe revenue professionals deserve a CRM purpose-built for the AI era. You shouldn’t have to waste hours manually logging information about customers and routing leads. We can (and should) do better to support the next generation of sales workflows and strategies. As the industry stands on the cusp of an AI revolution, we’re excited to meaningfully contribute to a better future for sales teams everywhere. 🙌 By rethinking how sales teams work in an AI-first world, Clarify is building more than just a CRM – we’re creating the foundation for the future of revenue technology.
-
11 team members. 3 days. 6 customer projects shipped. 1 unforgettable Clarify offsite. ✨ Our recent offsite in Seattle wasn't just about fun (though we had plenty of that). Our team focused on activities to build trust, align on goals, and create excitement around all the awesome work we have planned in coming months. Key takeaways: ❤️ Flexible agendas foster genuine connections 🏗️ Hackathons drive rapid problem-solving and innovation 🧘 Shared adventures (like lake plunges and hot wing challenges) are the fast track to team bonding 💸 You don't need a massive budget for a high-impact offsite Curious about how we balanced heads down work with team bonding? Want some ideas for fun things to do with your team in Seattle? Want to find out how Patrick Thompson’s hot ones challenge with one of our investors went? 👀 Check out the full write up from Austin Hay at the link in the comments. Bonus: We converted a few of our offsite planning docs into templates that you can use to get a head start on your next team trip (linked in the blog).
-
-
Excited to share a collaboration between our co-founder, Austin Hay, and Kyle Poyar in the latest edition of Growth Unhinged! 🚀 This is a great read if you’re an early-stage founder or revenue professional looking for some advice on building and maintaining a flexible, efficient GTM stack that can adapt to your growing needs. Austin dives deep into the evolution of GTM tech stacks, from the early days of sales tech to today's decentralized landscape. He also shares some Frankenstack wrestling tips, too. Key insights ⬇️ 🧘The importance of stack flexibility in modern GTM operations 🥇How redundancy, coupling, interoperability, and focus shape stack effectiveness 📈Real-world examples of GTM stacks at different company stages 🌱The future of CRM and its role in revenue team success You can find the link to the full article at the link in our comments.
Lately, I’ve been thinking a lot about how Martech and Revtech stacks are cut from the same cloth. Many of the lessons learned from martech apply in equal doses to Revtech. That’s why it was fun to collaborate with Kyle Poyar this week and write down some of the lessons I’ve learned about building “good” GTM stacks (and fixing not-so-great ones) for the latest edition of his newsletter, Growth Unhinged. The article covers a good amount of ground for founders or early rev professionals wrestling with their GTM tech, but I wanted to take a second to talk about what “good” means for our stacks. As a reminder, modern GTM stacks are built around four core data components: 1️⃣ Inputs: Where we get customer data from 📥 2️⃣ Storage: Where we keep that precious customer data 🗄️ 3️⃣ Capabilities: Tools that enrich data or act as endpoints (like analytics tools) ➕ 4️⃣ Federation: How data gets moved between the other components 🛣️ A "good" stack isn't about the quality of individual tools. It's about how well they play together as a function of redundancy, coupling, interoperability, and focus. We call this stack flexibility, and it's crucial for all of our work as revenue professionals. Why? 👇 1️⃣ GTM teams need to build audiences and segments quickly. Flexibility lets you create audiences across various tools and stream them to many destinations. (good redundancy) 2️⃣ World-class software requires world-class debugging. Stack flexibility helps you find, assess, debug, and resolve issues quickly. (coupling) 3️⃣ Novel challenges mean moving data easily. If you can't move data because of vendor limitations or system complexity, you're in trouble. (interoperability) 4️⃣ Business needs and tool options change fast. A flexible stack lets you easily onboard and offboard vendors – but more importantly solve the problems at hand quickly with dedicated tools and without confusion. (focus) In short, stack flexibility drives high performance PLG and B2B2C teams by giving them the underlying agility they need to support complex customer journeys and gain insight into user interactions across products and channels. There are more options for GTM tools than ever before, with wildly ranging capabilities and quality. As you build your stack, focus on these principles to create a flexible, efficient system that can adapt to your evolving needs. If you do, you may build the elusive “good” GTM stack, one that lets you grow and pivot easily while delivering deep insights into your users. And if you don’t, well, you’ll be in good company with many other Frankenstacks. 😆 If you want to learn more about this topic (and get a breakdown of GTM stack history and examples), I’ll link the article in my comments.
-
-
Our very own Austin Hay sat down with Pranav Piyush last month to talk Revtech and Martech! Together they cover .. 🤔 What tools should you use at different stages of your company life? ⚙️ How do you build a system of decision making and control around your tools to help them work for you? ✨ What makes for a magical stack? Read the blog and tune into the podcast to get the major 🔑s
Scott Brinker's martech landscape has 14k products. Wut? 😱 As a marketing team scales beyond a few million in spend, the task of designing and maintaining the ideal stack for your needs becomes quite daunting. 😰 I've been there myself. Saw a lot of implementations and build vs. buy decisions at companies like Dropbox, Magento/Adobe, and Invoice2go/BILL. One thing is clear. With so many tools, it's easy to overcomplicate things. So, we spent some time with Austin Hay who is both a MarTech expert (ex Ramp, Runway, mParticle, and Branch) and has recently co-founded Clarify (a new CRM), to create the ultimate guide with tips on must-have tools and how to choose them. 💪 Check out the latest blog post, and the podcast, with Austin! You know where to go but I'll drop the links in comments as well.
-
-
Last week, our co-founder Patrick Thompson joined Adam Fishman on the Startup Dad Podcast to talk about founder work-life balance, early parenthood, and the concept of the “first team.” While you won’t hear too much revtech tool geekery in this interview, Patrick’s insights all orbit a topic near and dear to our team: Building (and maintaining) meaningful relationships. Here are some the stand out tips: 🥇 Prioritize your “first team” relationships (whether that’s with your spouse, with your co-founders, or with your peer leaders). 🗣️ Practice proactive communication. Be open and honest about how you’re feeling. 🧘 Take time to nurture your identity and interests outside of your professional life. 🎯 Build alignment with your team around your core principles and approaches. ⚡ Focus on managing your energy, not just your time. The episode is packed full of great advice and lessons for founders, or anyone looking to find the balance between startup life and early parenting. You can find it on your streaming platform of choice. 🎧
The concept of 'first team' means that managers and leaders should prioritize (and be most loyal) to their peer leadership team over the teams they directly manage. But the concept of first team applies to your household as well. In today's Startup Dad podcast I'm joined by Patrick Thompson -- co-founder of Clarify, three-time founder and former director of product at Amplitude. "My wife and I, we're the first team. We need to be aligned. We need to be a unified front. We need to be on the same page around how we communicate, what are some of the principles we operate around, and what are some of the rituals that we hold dear to each other?" We discussed: 💙 How to manage a young family with starting a company 💙 The differences between his last startup when he wasn’t yet a parent and this one 💙 Having the conversation with your partner about getting back to building 💙 Investing in your relationship with your partner 💙 The concept of “first team” and applying that at work and home 💙 Rituals for quality time with your kids 💙 Recharging his batteries as both a parent and founder 💙 Top tips for airplane travel with an infant 💙 A potty training disaster story Thanks to Austin Hay for suggesting Patrick for the show! You can watch, listen and subscribe everywhere you get your podcasts! Links below.
-
Ending your week with product-led sales on the brain? 🧠 Save your spot for Patrick Thompson's session with our friends at Amplitude next week (10 am PT June 18). He'll dive deep into how he built the PLS models at Atlassian and Iteratively, an Amplitude Company and how you can use your model to: - create a shareable scorecard - rank leads, and - automate workflows. 𝘉𝘰𝘯𝘶𝘴: You'll walk away with tips on how to operationalize your models. Visit the link in the comments to sign up. 👇
-