SimplyCodes, our coupon site, tests promo codes at real checkouts and knows which ones work. Its agent server is live: developers sign up on the SimplyCodes developer site, get a key, and call it from the agents they build. A free key returns what we know about a merchant's codes with the proof attached; paid tiers return the codes themselves. What we do not have is the developers' side: who they are, what they would build with verified promo code data, and what they would pay for. We want to hear it from them, in their own words.

You find and interview 10 developers who build shopping agents. For each one you write down what they would build with verified promo code data, which tools they would call first, what they would pay for, and what would stop them. You are paid per completed interview. This mission is interviews only; nobody connects to the server during it. A separate mission covers sitting with developers while they connect.

Our goals for this mission

We do not know who the developer is. Indie agent builders, AI startup teams, and platform teams each need something different from the server, and we cannot tell from the inside what to build first. Ten conversations written down in the developers' own words tell us what to build first and what to fix. They also give us a list of developers who want to hear from us as the server grows.

What you would do

  • Finding them. You find 10 developers who build shopping agents and who work for neither Product.ai nor SimplyCodes. Finding them is part of the work; we can suggest places to look.
  • The interview. Each conversation runs 30 to 45 minutes, in person or on a call, with the developer's consent to be quoted. You ask what they are building, where they get product and price data today, what they would do with verified promo code data, which tools they would call first, what they would pay for, and what would make them stop calling.
  • The write-up. Each interview becomes a one-page note in the developer's own words, dated, with what they build, what they want first, and what would stop them.
  • The synthesis. When the 10 are done, you write one page: who these developers are, what they would build, what they need first, what would stop them, and which of them want to hear from us again.

What success looks like

  • 10 completed interviews, each with a dated one-page note the developer has agreed can be quoted internally.
  • The synthesis names the three things developers ask for first and the three things that would stop them, each traced to the notes.
  • A list of the developers who want to hear from us again, with what each said they would build.
  • A result you did not expect is reported as it is. If most of them would not call the server, you say so and show the notes.

Ground rules

  • The developers are outsiders. Nobody employed by Product.ai or SimplyCodes counts toward the 10.
  • You record a conversation only with the developer's consent, and a developer who asks to stay anonymous in the notes stays anonymous.
  • You describe the server as it is at kickoff and promise no dates about what comes next. Our engineers own the timeline.
  • The notes are internal. Nothing a developer says is published without their written yes.
  • Pay is per completed interview, at the rate set in the contractor agreement.

What happens after you send a proposal

3 steps, and a person reads every proposal.

  1. You send a short written proposal. It covers how you understand this mission and how you would approach it, and you attach your resume or a LinkedIn profile.
  2. We read it and reach out with questions. There is no test and no exercise.
  3. If there’s a fit, the mission begins under a contractor agreement and an NDA, paid at your stated rate, with kickoff in Santa Monica.