Revenue Engine Operator

A Sprint-to-Seat Path at Tangle Venture Studio 14-Day Pipeline Transfer Sprint We are hiring someone to step directly into the engine room. One of our current contractors has begun building the outreach, pipeline, CRM, and project-management systems that will keep Tangle moving. As they transition out soon to focus on other items, your role will be to jump in the driver’s seat with a focused two-week shadowing and systems-transfer sprint. Your first mission is simple: learn the machine before the person who built it leaves. You will shadow the current BD/PM, absorb the outreach engine, document the workflows, clean up the CRM, understand the warm pipeline, track active follow-ups, and help make sure no lead, client item, campaign, or founder decision gets lost in the transition. This is not a closing role. The founders still close all deals. This is not a VA role. We need someone who can think operationally, move quickly, and turn messy founder-led growth into visible systems. This is also not only a pipeline role. The first sprint is focused on learning and preserving the revenue engine: outreach, CRM, warm lead follow-up, pipeline tracking, founder-call preparation, and sales-system documentation. After the sprint, the person who wins this seat will also take on the project-management layer for Tangle’s next client. That means the role you are aiming to earn is dual: Revenue Operations + Project Management. On the revenue side, you will help keep the pipeline clean, visible, and moving toward qualified founder conversations. On the project side, you will help manage the client-facing execution layer: Asana boards, delivery timelines, contractor assignments, client handoff dashboards, milestone tracking, open requests, internal blockers, founder decisions needed, and weekly project-status reporting. The founders still own strategy, pricing, closing, and high-level client trust. You own the operating flow that keeps growth and delivery from falling through the cracks. This is a sprint-to-seat opportunity. If you complete the transfer well, prove you can run the engine, and earn trust quickly, you will be first in line for the next internal operating role as Tangle grows — a dual Revenue Operations + Project Management seat that may evolve into Growth Ops, Studio Ops, Revenue Ops, or Chief of Staff over time. No inflated promises. No fake corporate ladder. Just a real shot at earning the next seat by proving you can keep the machine moving. Operating Stack You Should Know You do not need to be a software engineer, but you cannot be intimidated by AI tools, build tools, dashboards, documentation, or messy operating systems. You should be highly comfortable with: Asana — building project boards, assigning owners, tracking deadlines, creating dashboards, managing dependencies, and keeping work visible. Loom — recording walkthroughs, documenting processes, creating async updates, and turning shadowing sessions into reusable training assets. Claude — summarizing calls, drafting SOPs, organizing messy notes, creating workflows, turning founder direction into structured execution plans, and supporting research or documentation. Codex / AI coding assistants — understanding how AI-assisted build workflows move, tracking what is being built, documenting issues, and helping founders/developers organize next steps. Replit — navigating live builds, tracking feature requests, documenting bugs, coordinating updates, and understanding enough of the environment to communicate clearly with builders. Lovable — understanding no-code/AI-assisted app and dashboard builds, tracking client-facing product progress, documenting build requirements, and helping move prototypes toward usable handoff assets. Notion or Google Drive — building a clean SOP library, organizing process documentation, storing templates, housing handoff docs, and making sure operating knowledge does not live only in someone’s head. Google Workspace — Docs, Sheets, Drive, Calendar, and shared files for operational documentation, reporting, tracking, and collaboration. CRM tools — tracking leads, warm relationships, next steps, follow-ups, deal stages, qualification notes, founder-call readiness, and pipeline movement. Slack / WhatsApp — keeping fast-moving communication organized without letting important decisions disappear inside chat threads. Bonus if you are comfortable with Airtable, Zapier, Make, HubSpot, Pipedrive, Close, GitHub, Figma, or other tools used to connect operations, sales, delivery, automation, and documentation. The real requirement is not tool memorization. The real requirement is that you can turn scattered activity into a visible operating system.