Forward Deployed Engineer, Agent Commerce

You go to the customer, write the integration with them until it works, and make sure Product.ai gets paid when a machine does the shopping. I'm Michael, founder and CEO of Product.ai. I want to explain what a forward deployed engineer means here, because it's a specific job, not a title we borrowed. A forward deployed engineer goes to the customer and builds the integration with them until it works and pays. Here the customers are the teams building AI shopping agents and assistants, and the developers who buy verified commerce data through our keyed API and MCP, the protocol AI assistants use to call outside tools like ours. You write the integration code with the customer yourself. You price the access. You close the first paying accounts. You bring what you learn back into the product, every time, not once at the end of a quarter. We run this company on Cortex, a written internal system of rules for what we sell and how. You open it every morning through Claude Code, and you read it before you sell, not once during onboarding and never again. That habit doesn't end after the first integration ships. I've spent 17 years building commerce technology, bootstrapped, 100% founder-owned since 2009, profitable, no outside investors, no board. We're the verified truth layer for shopping. We work out what's actually true about a product and a price, for human shoppers and for the AI agents shopping for them. SimplyCodes is our first proof at scale: codes that actually work at checkout, roughly $22M in revenue, profitable, fewer than twenty operators outbuilding companies 10x our size. Why This Role Exists I opened this seat once already this year under a commercial title, and the framing was wrong. A commercial title asks someone to run a pipeline. This work asks someone to build, in code, at the customer's desk, until the thing they bought actually works. AI agents are starting to do the shopping. When one needs to know whether a discount is real, it reaches for a data source. I intend that source to be us, and paid when it happens. That means writing real integrations with real engineering teams, not just proposing them. I own the strategy. But I can't also sit at the customer's desk and write the integration while I build the company, so that part is yours. You'd be the first forward deployed engineer here, the person who turns "agents should pay us" into working code, signed accounts, and priced access. This seat goes out to the customer, builds the integration, and owns the revenue number. Until a second commercial seat opens, the demos, onboarding and support for the developers and agent teams who come through that door are yours too. The System You'll Need to Model • Cortex, and the discipline that comes with it. Every day starts inside it. Before your first integration call, you read the internal rule documents that state what we will and won't sell. • The rules aren't handed down from me. Any operator here can propose a change to how Cortex works, and since August those changes go live the same day, without waiting on my approval. The system is written by the people running it. • A two-sided market that pays for certainty. Shoppers and the AI agents shopping for them consume verified codes, proof a discount is real before checkout; merchants pay to protect their brand. Price both sides without breaking either. • The agent-commerce shift. The buyer is turning from a human into a machine. AI agents are starting to choose their data sources the way search engines once chose which pages to rank. • The keyed API lane, now the only door. Anonymous API access ended in August, and the free legacy codes close behind it. The paid, keyed door is the one that's left, and you inherit it live, not a blank page. • The affiliate engine, and the second line forming behind it. Affiliate networks fund the business today, concentrated among a handful of major networks. A second line is forming too: verified research, sold as a product. If reading that energizes you, keep going. If it feels overwhelming or underspecified, this isn't the right fit. What You Will Own • The integration, written with the customer. You sit down with the engineers building an AI shopping agent or assistant, or the developer buying our keyed data, and you write the code that makes the connection work. No proposal substitutes for a working integration; you build it yourself, in the room or on the call, until it runs. • Pricing and packaging for keyed access. You price the API and MCP access you just integrated, prototyping the pricing pages and account flows yourself before anything reaches an engineer. Fill the paid door with paying, keyed accounts now that the legacy free door is closing. • The first paying accounts, closed by you. You own turning a working integration into a signed, paying account, then bringing what you learned about the customer's real needs back into how we package and price the next one. • A co-signed charter and a first-q