Sean Keegan

Hot take - customer relationships in education aren’t built on swag, webinars, or 200-person panels. We don’t fly superintendents out to fancy events. We don’t send branded swag in the mail and expect that to mean something. That kind of thing might work in other industries, but not here. At Subject, we compete with memories. Specifically, memories that stick - and that stamp our presence in a way no branded coffee mug ever could. Instead of sending gifts or event tickets, we actually show up at someone’s front door (without forcing them to rework their schedule). We give districts an experience where they can put a face to the name and trust we’ll give them the support they really need. Instead of trying to impress them, we simplify and say: “Don’t worry. We’ll come to you, so we can solve your problems together.” And it works. When people reflect on what they like about Subject, they often talk about the relationship. They feel like they’re building something with us, not buying something from us. Because relationships that last are built on trust, not swag or flash.

12

1 Comment

Quick implementation field note: identity/residency verification sounds simple until you're doing it at scale in a regulated program. I put together this short walkthrough to help families get through the Plaid step without getting stuck (and to reduce avoidable support load).

1

Teachers shouldn't have to decode great curriculum on their own. So we built the first AI that helps them unlock it and deliver it their way 🚀

4

One quiet shift in EdTech is the move from tools to workflows. Working with schools, I’ve learned that teachers don’t want more features. They want fewer steps. The best conversations I’ve been part of weren’t about what was possible. They were about what fit into a real school day. As an SE, success here comes from designing around classroom reality, not demos. #EdTech #SolutionsEngineering #Deployment #TechStrategy

1

🤖 "What if creating eLearning was as easy as having a conversation?" That's the question I'm answering in this month's Learning Lab Live! I'm diving deep into MicroBuilder's AI magic—where you can generate scenarios, analogies, and step-by-step content in literal seconds. Plus, I'll show you how 150+ diverse AI avatars turn boring content into dynamic experiences that actually engage learners. Ready to see authoring tools that feel like the future? Register here: https://lnkd.in/gcSi_Uyu #LearningLabLive #AIAuthoring #eLearningInnovation

13

2 Comments

Just witnessed something powerful at Disability:IN – Kurt Iobst, CPACC took the stage and absolutely delivered. Speaking on a panel about neurodiversity in the workplace, Kurt brought sharp insight and real vulnerability. He shared the journey of launching NeuroForce – Salesforce first BRG (Business Resource Group) focused on neurodivergent employees – and the impact it’s already having on culture, hiring, and innovation. To hear someone openly talk about being neurodivergent, while also leading change at the intersection of tech and inclusion – that’s leadership. Full stop. We need more of this. More visibility. More support. More force. #Neurodiversity #DisabilityIn #NeuroForce #Salesforce #InclusionMatters #DisabilityPride #RepresentationMatters #BRGLeadership

123

5 Comments

I sat down with Camela Thompson from RevOps Co-op on RevOpsAF (The Podcast) to unpack GTM Engineering. Why we built it at Easygenerator, what it is (and isn’t), and how it complements core RevOps. We get into: - The split: RevOps = stability & scale; GTME = experimentation & innovation - How we test ideas (and what actually “ships” to RevOps) - The metrics that matter (experiment velocity, success rate, impact on pipeline) “GTM Engineering is the R&D arm for RevOps. RevOps keeps the trains running; GTM Engineering experiments with how to build faster trains.” Give it a listen: https://lnkd.in/djy_EKEf If you’ve tried carving out a GTME function (or you’re skeptical!), I’d love to hear how you’re approaching it. If this resonates, I go deeper in my book on GTM Engineering: https://lnkd.in/dSiGZky6 #RevOps #GTMEngineering #OpsLedGrowth #B2B

30

4 Comments

Lesson 2 of Clay Cohort 19: Waterfalls. This exercise revolved around finding work email addresses. Pre-Clay I would've created multiple fields in Salesforce for work email addresses that an enrichment provider can populate. Then create a flow that would compare those fields with the standard Work Email field and update accordingly. I can neither confirm nor deny the fact that our Salesforce org might have a lot of those extra fields (created pre-me) 🤭. With Clay instead of adding tech debt to your Salesforce org with a lot of enrichment provider specific fields, you set up a waterfall with a lot of providers within a Clay table. If the first provider finds the email address then the rest don't run and you're only charged for the provider that finds the answer. The 1 thing that tripped me up a bit is that each provider might have different requirements for input. Basic requirements include Contact Name, Company Name, and Domain. Some also required LinkedIn profile. Others have optional inputs that would help as well. Since I missed some of the required inputs for a couple of the providers they didn't run. Once I realized that I went back and added them in and got the remaining results. Such a time saver and it will help us reduce our tech debt!

13

3 Comments