This is RevOps on steroids. You won't just maintain a CRM—you'll build the automated infrastructure that makes our sales team dramatically more effective. Your work splits into two domains: 1. Bridge Building (Pre-RFP) Government deals are won before the RFP drops. Your job is to build systems that help us get in front of decision-makers early: Signal tracking: Build workflows that detect buying signals—job changes at workforce agencies, budget announcements, policy shifts, leadership transitions, new federal funding Warm outbound plays: When we close a contract in NYC, automatically identify and score similar opportunities in NJ, CT, PA. Build the sequences that get our AEs in the door. Intent scoring: Aggregate signals into lead scores. Push high-intent prospects to reps via Slack or sequencer workflows. Low-intent goes into automated nurture. Personalization at scale: Draft AI-powered outreach that references specific local context—their workforce board's priorities, their state's recidivism data, their recent press coverage 2. RFP Infrastructure When RFPs drop, speed and quality win. You'll build systems that help us respond faster and better: RFP tracking: Monitor government procurement portals, SAM.gov , state bid boards. Surface relevant opportunities before deadlines sneak up. RFP qualification: Build scoring models that help us decide which RFPs to pursue. Not every opportunity is worth the lift. Response automation: Create systems that pre-populate boilerplate, pull relevant case studies, and queue up content for our RFP lead to review—not write from scratch. The Two Buckets of Output Everything you build will flow into one of two buckets: Plays (automated): Sequences that run without human intervention. Job change detected → email drafted → pushed to sequencer. RFP posted → Slack alert → qualification score attached. Rep feeds (human-in-the-loop): High-value signals that need a human touch. You surface the opportunity, draft the email, but the AE takes it the last mile or makes the call. Who You Are You have an engineer's brain and a seller's instincts. You're technical enough to build complex automations, but you think in terms of pipeline and revenue. You ask "will this actually help close deals?" before you build anything. You're scrappy and resourceful. You don't need perfect tools or complete data. You find creative ways to stitch together APIs, scrapers, and AI to solve problems that "shouldn't" be solvable. You're obsessed with AI and automation. You tinker with new tools constantly. You've probably already built something with Clay, n8n, Zapier, or written Python scripts to automate your own workflows. You see AI as a force multiplier, not a toy. You think in systems. You don't just solve one problem—you build infrastructure that solves a category of problems. You see the whole GTM motion as one interconnected system with inputs, outputs, and feedback loops. You're a clear writer. Good GTM engineering is half building, half communicating. You document your systems. You write prompts that work. You can explain complex workflows to non-technical teammates. You care about impact. You could optimize ad tech funnels or build sales automation for enterprise SaaS. But you'd rather use your skills to help people coming out of prison find careers. The mission matters to you.