DLVX Academy · Guide preview

Direct an AI website project.

A founder’s guide to directing Codex website work, reviewing Vercel previews, checking forms and attribution, and accepting a release with real evidence.

A starting point

You can lead the project without pretending to be the developer. Here is how I define the job, review the evidence and judge whether the result is ready.

The short answer

You can lead an AI website project without writing the code, as long as you define the job in buyer terms and accept work on evidence. "Make the website better" is a feeling, not an acceptance test. A coding agent can change colours and copy for hours without fixing what bothered you.

  • Name one buyer journey. For example: a business owner lands on a service page, understands the scope, sees proof, and sends an enquiry that reaches the right inbox.
  • Set a release boundary. Say whether the work is preview only or may go live, and what must stay untouched.
  • Ask for evidence, not reassurance. Changed files with reasons, a preview link tied to one version, desktop and phone screenshots, and a form test.
  • Review one version, release that version. A preview is not a production switch until the live address has been checked after the switch.

Worked example

Say a Bangkok accounting firm wants its services page fixed because "it feels small". This is an illustration, not a client result.

  1. Write the journey: a small business owner searches for monthly bookkeeping, reads the page, and sends an enquiry with their company size.
  2. Brief the agent with the route, the form handler, the approved design to preserve, and the evidence you need before release.
  3. Review the preview on a phone first, as the buyer. Write feedback as specific lines, such as "the price range sits below the fold on mobile", not "improve the layout".
  4. Submit a real test enquiry and confirm it arrives with the page it came from. A thank you message on screen does not prove the enquiry reached anyone.
  5. Release the exact version you reviewed. After the switch, open the live address and check the same journey again.

The skill is knowing which layer answers which question: the browser for what a buyer sees, the form log for whether the enquiry arrived, the host for what is actually live. A green build alone proves none of those. If you also need the page to be found, read Get Found before the launch. For the redesign side of the brief, see Bangkok website redesign, and practise the loop first on one small workflow.

The full guide adds the prompt we use, a one page release worksheet, practice exercises and downloadable templates.

Start with a buyer journey and a release boundary.

Lesson 02

“Make the website better” is a real expression of dissatisfaction, but a poor acceptance test. A coding agent can change colours, spacing, components and copy for hours without resolving the thing that bothered me. I need to describe the journey that should improve.

For DLVX, a useful journey is an established business arriving on a service page, understanding the scope, seeing attributable proof and sending an enquiry that reaches the right place. The homepage supports that journey. It is not the whole product.

Act as the implementation agent for this website change.

Outcome: A qualified visitor understands the service and can send
an enquiry that reaches the agreed destination with its context.

First inspect the current source, project instructions and live state.
Identify the route, shared components, form handler and deployment.
Do not infer that the newest local branch is the live website.

Preserve approved design and unrelated work. Propose the smallest
change that solves the stated buyer problem, then implement it.

Before release, provide:
- The changed files and why they changed.
- A preview link tied to the reviewed version.
- Desktop and mobile evidence.
- Relevant route, form and attribution checks.
- Remaining failures and the concrete release decision.

Keep the previous release recoverable. Do not claim a production
switch until the destination has been checked after the switch.

I would add the actual project’s permitted actions and limits below that prompt. If deployment is authorised, say so. If the work is preview-only, say that. Do not leave a business decision hidden inside “do whatever is best”.

Before edits begin, the agent should establish who else is working in the repository. A separate worktree can isolate a change, but it does not remove the need to integrate other people’s work before release. The practical question is whether the proposed release contains the accepted work already on production and the changes we intend to add.

Use the conversation for decisions and the workspace for implementation.

Lesson 03

A ChatGPT or Claude project is useful for collecting the brief, references and decisions. It is not automatically the local application folder, and attaching a screenshot does not give the assistant the source behind it. Be explicit about the working environment.

For implementation in Codex, name the repository, the route or component, the expected behaviour and the evidence required. Ask it to inspect the actual files before making a plan. If you hand the task from a planning conversation to a coding workspace, carry over the accepted brief rather than relying on the tools to share your entire conversation.

OpenAI’s guidance on Codex describes working with implementation tasks, worktrees and reviewable changes. Use the actual diff as part of review, alongside the rendered result. A long explanation from the agent is not a replacement for either. OpenAI: Codex for engineering work.

I would not start by giving the agent a ten-page identity as the world’s greatest designer, engineer, SEO expert and conversion psychologist. I would give it the relevant project rules, one clear task and the evidence it must return. Extra instructions can conflict with each other, especially when old design preferences remain mixed with current ones.

Inside this guide: what comes next

  • I can direct the website without pretending I wrote the code.
  • Ask the question at the layer where the answer exists.
  • Review the website as a buyer, then make the feedback specific.
  • The enquiry is not finished at the thank-you message.
  • Review one version, release that version.
  • Make the final review small enough to make a decision.
  • Practise before the launch pressure arrives.
  • A release worksheet for the person directing the work.
  • Take the templates into your next session.

Read the full guide

A free Academy account opens the full guide and practice lessons.

Create a free account Already a member? Sign in

No newsletter subscription. We use your email for sign-in and account messages.