Founding Operations Lead

Every restaurant we work with is owed a number of visits and a level of reach each month. Your job is making sure that happens across every account, every cycle. You'll know which restaurants are on track and which aren't before anyone tells you, and why. When something goes sideways you handle it. Then you make sure it doesn't come back. The AI handles the volume, but it only gets better because someone is paying attention to where it falls short. You'll spot the patterns, figure out what needs to change, and often build the first version of the fix yourself. This is an operations role for someone who thinks like a product owner. If your instinct after fixing something twice is to make sure there's no third time, you'll do well here. What you'll own The numbers. Every account has targets. You own hitting them. The booking engine. Our matching and booking runs on AI. You're the owner behind it. You watch what it gets right, you catch what it gets wrong before a customer notices, and you make it better every week. The relationships. Owners talk to you. Creators rely on you. When something needs a person instead of a system, that's you. Building for scale. Whatever you build has to work at 150 accounts and at 1,500 accounts. We want the version of this operation that works in every city we expand to, and you're the one building it. What we're looking for Required

• 3+ years in operations, customer success, or account management, somewhere you owned an outcome and not just a queue
• Good with people and escalation management. You've dealt with someone upset and been the reason they stuck around
• Good with numbers. Hand you a list of accounts and targets and you can see what's off
• Scrappy. There's no playbook here and most of the time the answer is that you figure it out
• Actually interested in building. You don't need to be an engineer, but if you've never opened Replit or Claude and made something ugly that worked, this probably isn't the right role for you
• Based or willing to relocate to Orange County and able to work onsite and on the move, with some travel
• This isn't a 9-to-5. Restaurants and creators are active at night and on weekends

Nice to have

• Vibe coding. You've built something that worked with Replit, Claude Code, Codex, Lovable, Cursor or similar
• Restaurant industry or creator economy experience
• Early ops hire at a startup before
• SQL, or enough interest to pick up what you need
• A second language