You Shipped the Site with Codex. Nobody Shipped the Nurture.
It is a quarter past midnight and the landing page is live. You described it to Codex, argued with it about the hero for twenty minutes, added a form, put it on the custom domain, and posted the link. By Thursday there are forty signups in the form’s storage. And the honest answer to “what happened to them” is: nothing. They filled in a form on a page that does not know what a follow-up is.
This is the most common shape of founder-led marketing in 2026, and it is not a failure of the page. It is a failure of the assumption that the agent that built the page knows what happens after the form submits. It does not. This post covers what Codex Sites actually gives you, what the forty people need in the next two weeks, and how to draft that follow-up from the same assistant you built the page with, without rebuilding the page anywhere.
What Codex Sites gave you
OpenAI launched Codex Sites in June 2026 as a way for people who do not write code to build and host a page by describing it, and, per Masset’s write-up for marketers, added custom domains and public sharing in July. For a founder it removes the two things that used to stand between an idea and a live page: a designer and a page builder. You get a page, a form, a domain and hosting, in an evening.
That is real, and the enthusiasm around it is earned. Forbes ran a piece in March on vibe coding your entire marketing engine in a day, and the page half of that promise now holds. The engine half is where the trouble starts.
What the agent that built the page cannot know
Codex knows how to build a page because a page is code, and code is what it is trained to produce. What happens after a visitor submits the form is not code. It is a sequence of decisions about people: who wrote to them, when, saying what, and where the conversation should end up.
Nothing about building the page teaches the agent any of that. It does not know that a signup at 11pm should get a welcome at 8am, not at 11:02pm. It does not know that a signup from a company with two hundred employees should be offered a call, and one from a personal email address should not. It does not know that a second email should go out only if the first was not answered, or that a third should stop the moment someone books. The page’s form stores a row. The row waits.
The people who watch vibe-coded pages in production keep describing the same gap. ScoreApp’s warning not to vibe code your lead generation is about exactly this: the page works, the capture works, and the follow-up does not exist. MarTech’s lessons from letting AI build a landing page reaches the same place from the other side. Replo went as far as publishing how to wire an email tool to a vibe-coded page, which tells you how often people arrive at the page with no plan for after it.
This is a system-of-record problem, not a code problem
The founder’s instinct is to solve the gap the way the page was solved: ask Codex to write the follow-up. And Codex will write three good emails. That is not the problem. The problem is that the emails need a place to live that knows about time, people and state: who has been sent what, who replied, who booked, whose second email is due tomorrow at 8am, and who should never get a third.
That is a marketing system, and it has three parts the page lacks:
- A trigger. Something fires when a new signup lands on the list, and it knows which page they came from.
- An automation with timing. Steps with delays between them, quiet hours so nobody is emailed at midnight, and exit rules so a booking stops the sequence.
- A queue where a person approves the words before they run.
Marqeable holds all three, and the page does not need to move. The form on your Codex Sites page keeps capturing; the automation runs the follow-up. The general case, for any campaign that begins as a chat transcript, is in ChatGPT wrote my campaign, now what?. If the page is also where you want visitors to get an answer before they submit anything, AI website chat is the other half of the front door, and it is a one-snippet install on the same page.
What the forty people need in the first two weeks
Before drafting anything, be concrete about what a good follow-up looks like for a demo-led company with no SDR. Here is the version most founders end up with, once they stop treating “follow-up” as one email.
| Step | When | What it does | Exit |
|---|---|---|---|
| Welcome | Next morning inside quiet hours, not at 11:02pm | Thanks them, says what the product does in two lines, offers one thing to do next: book a 20-minute call | Booking stops the sequence |
| Proof | Day 3 | One customer story or one concrete result, one link | Booking or reply stops the sequence |
| Direct ask | Day 7 | A short note from the founder asking whether a call is worth their time, yes or no | Any reply routes to the founder |
| Quiet close | Day 14 | One line: no hard feelings, here is where to find us when the timing is right | Sequence ends |
Four emails, one booking path, quiet hours throughout, and an exit rule on every step. That table is the specification. What follows is the fastest way to turn it into a draft.
Draft it from where you already are
Marqeable’s MCP server lives at https://app.marqeable.com/mcp. It is a remote server over HTTP with OAuth 2.1, so you sign in with your normal Marqeable login in a browser window and the assistant sees exactly what your account can see. The connector reads your business context (brand, ICP, voice, offers), campaigns, existing content, the content calendar and every automation with its plan, and it writes drafts: campaign drafts, content drafts, suggestions on existing copy, brief updates and automation drafts. There is no send, launch, publish or delete tool. Everything waits for you.
Two ways to connect, as of September 2026. In the Codex desktop app: Settings > MCP servers > Add server, choose the streamable HTTP transport, paste the address and authenticate; from the CLI, codex mcp add marqeable --url https://app.marqeable.com/mcp then codex mcp login marqeable. In ChatGPT: Settings > Connectors, turn on Developer mode under Advanced, create a connector with the address and OAuth, and enable it in the conversation. OpenAI has moved that setting more than once this year, so search Settings for “Developer mode” if the path differs. The fuller Codex setup, including the approval mode that prompts only on writes, is in Codex MCP for marketing.
Here is the session, the same evening the page went live:
You: Run whoami and get_business_context, then read the calendar for the next three weeks.
Codex: Signed in as the founder on the Northwind account. Offer: 30-day pilot. ICP: first controller at a 50 to 200 person company. Voice: direct and specific. Calendar: a nurture email on the 4th and a LinkedIn post on the 18th. No automations are live yet.
You: Draft a welcome automation for signups from the new landing page. Four steps: welcome next morning, proof on day 3, a direct ask from me on day 7, a quiet close on day 14. Quiet hours on. Stop the sequence if they book or reply. Put an approval gate on the day-7 note so I read it before it goes.
Codex: Created an automation draft, “Landing page welcome”, triggered when a new contact arrives on the landing-page list synced from your CRM, with four steps at those intervals inside the 7am to 9pm window, exit on booking or reply, and an approval step on the day-7 note. Each step’s email is a content draft in your voice with the pilot offer, copy only. Nothing is live. Review it here: [link to the automation draft in Marqeable].
You: The proof email should use the finance-team story if we have one.
Codex: I searched your content and found the June finance-team story. I updated the day-3 email’s brief to reference it and added a suggestion on the draft pointing at the paragraph to replace. Both are waiting for your review.
The whole thing took as long as the argument about the hero did. The difference is that this output is not a page. It is an automation with timing, quiet hours, exits and a gate, sitting in a system that will run it once you approve it. The page stays exactly where it is.
The forty existing signups are not lost. Once they are on the list and the automation is approved, it can be activated for them too, with the welcome going out the next morning rather than at the moment you add them. Nobody gets an email at midnight because you finished the setup at midnight.
Keep the page where it is
There is a temptation, once you see the marketing system, to rebuild the page inside it. Resist it for now. The page is done, it is on your domain, and Codex can keep iterating on it. What it needs is the form wired to the CRM you already sync from, such as HubSpot, so each submission becomes a contact on the landing-page list that Marqeable picks up and the automation triggers on. Move the page later if you want the campaign creative and the page in one place. Ship the nurture first, because the nurture is what the forty people are waiting for.
If it turns out you are the person running all of this, the founder as CMO post is about how long that should last, and the onboarding sequence for SaaS picks up where the welcome sequence hands a signup to the product.
Frequently asked questions
What is Codex Sites?
Codex Sites is the part of OpenAI’s Codex, launched in June 2026, that lets non-developers build and host a web page by describing it. Custom domains and public sharing followed in July 2026. It is a fast way for a founder to ship a landing page without a designer or a page builder.
What happens to leads from a vibe-coded landing page?
By default, nothing beyond the form storing the submission. The agent that built the page has no knowledge of what should happen after someone signs up, so there is no welcome email, no booking path and no follow-up unless you build them somewhere else. That gap is where most AI-built pages lose their first leads.
Do I need to rebuild my landing page in a marketing tool to add nurture?
No. Leave the page where it is. The nurture is a separate system: an automation triggered when a new signup lands on the list, with a welcome email, a booking path and timed follow-ups. Marqeable runs that automation and your page keeps its current host, whether that is Codex Sites, Vercel or anything else.
Can Codex draft the follow-up sequence itself?
Yes, through an MCP connector. With Marqeable connected, Codex or ChatGPT can read your business context and calendar and create an automation draft anchored to new signups from the page, with each email as a content draft. Every draft waits for your approval; the connector has no send tool.
The bottom line
Codex Sites solved the page. It did not solve what happens after the form, because that is not a page problem: it is timing, people and state, which live in a marketing system, not in code. Draft the four-step welcome from the same assistant, land it as an automation with quiet hours, exits and an approval gate, and leave the page where it is. The forty signups get a welcome tomorrow morning, and the next forty get one without you being awake.
See the nurture side: Marqeable’s agents build and run your campaigns, run behavior-triggered automations across text and email, answer and qualify every visitor with AI website chat, and tie revenue to the exact message with attribution.
Marqeable runs your campaigns, answers every visitor, text, and email in seconds, and turns them into booked jobs and meetings - even at 9pm on a Saturday. We’re in private beta with a small early cohort. Get early access
