Floot lets people build and ship full-stack apps from inside Claude and ChatGPT - you describe the app, our MCP connector builds and hosts it. We have a product people love once they find it. Finding it is the problem you'll own. Our users live inside AI assistants, so when someone asks their AI "how do I build an app," we need to be the answer. That's not a nice-to-have for us - it's the whole distribution problem. Here’s what you will do • Source the outlets. Build and continuously grow the map of where our audience actually reads - AI newsletters, dev and founder communities, comparison sites, podcasts, directories, guest-post venues - and rank them by who's worth our time. • Match ideas to outlets. For each venue, come up with the angle that gets accepted: what this publication's readers want, told with our data and point of view. You'll work with the founders on the core theses; you turn them into a dozen pitchable pieces. • Ship placements at volume. Pitch, follow up, negotiate, deliver, publish. Run it as a pipeline with acceptance rates, not as one-off favors. Produce drafts with AI where it makes sense; you're the editor and the quality bar. • Own AEO end to end. Track where Floot shows up in ChatGPT, Claude, Perplexity and Google AI answers, figure out what moves it, and do those things — on our own site (structure, schema, llms.txt, comparison and listicle pages) and off it (the citations AI answers draw from). • Run launch distribution. When we ship something big, you run the checklist: directories, communities, newsletters, press, social, email - timed to land together. • Be present where our users are. Hacker News, Reddit, Discord, X - as a participant, not a promoter. Bring back what you hear. • Measure what converts, not what clicks. You'll have access to our funnel data and are expected to tie distribution to signups and activation, not impressions. You'll be a great fit if you… • Have personally gotten a company attention with no budget — placed pieces, landed newsletter mentions, made a community take notice — and can tell us exactly how • Already think in AEO terms: you have a working view on how answer engines pick their sources and you've tested it, even informally • Run things as pipelines: prospect lists, pitches out, acceptance rates, follow-ups - and like the volume game • Write clean, fast, and can judge a draft in thirty seconds; you don't need to be a craft writer, you need to know good from embarrassing • Use Claude or ChatGPT heavily yourself and can talk about MCP, connectors, and AI app builders without a cheat sheet • Are data-comfortable enough to pull your own numbers and ask "did this convert?" • Are scrappy, resourceful, and want ownership over a function, not a seat on a team Why join Floot • Direct line to the founders: you'll shape messaging, launches, and product direction, not execute someone else's plan • Real leverage: this is the constraint on our growth right now, and you're the person removing it • A field being invented: AEO is two years old; the people who figure it out now will be the experts of the next decade