Launch engineer for AI-built site: audit, harden, deploy, verify. Est. 12 to 15 hours over 2 weeks.

B2B travel microsite launching 4 September 2026. Built in Lovable (React, GitHub-synced), content-complete and functional. We need an experienced technical specialist to take it to production: audit the existing build, set up Cloudflare deployment, harden the security-critical parts, and verify the cutover. You lead the AI tooling yourself. You orchestrate coding agents (Claude Code, Codex, Cursor, or your preferred setup) for implementation: prompting, reviewing diffs, iterating, merging. We do not run agents for you. You make the calls that need experience, decide where hand-writing beats agent output, and own the final verification. If you have not worked this way in production, this is not the right engagement. The hours below are our estimates, not yours. If any line looks unrealistic, push back in your proposal. We would rather adjust the plan now than mid-engagement. The launch date is fixed; the hours are not. THE PROJECT - 7 regions, 18 itineraries, enquiry form as the primary conversion point - Lovable build, GitHub repository under our control, target hosting Cloudflare Pages - No database, no user accounts, no CMS. Static content plus one form - All accounts (GitHub, Cloudflare, domain, Lovable) remain in our name; you work inside them TIMELINE HEADROOM Two full weeks for an estimated 12 to 15 hours. The site already functions and content is complete, so this is hardening and deployment, not building. The buffer exists so that anything found in the audit can be fixed calmly before launch. ENGAGEMENT STRUCTURE 1. Paid audit, 1 to 1.5 hours. Inspect the repo, hosting, DNS, form implementation, dependencies, and external services. Deliver a short written assessment: what is clean, what is risky, whether the estimate holds for this codebase. 2. Decision point. If the audit is clean, we confirm the plan and proceed. If it uncovers real complexity (missing form backend, email deliverability work, undocumented DNS, CSP-hostile third parties), we agree an adjusted estimate in writing before further hours. Either side can walk away after the audit; the audit is paid regardless. 3. Execution, staging first. Staging is established early. Every change is tested there before promotion to production. SCOPE AND ESTIMATES (open to your revision) - Audit and plan, 1 to 1.5h: repo, hosting, DNS, form, dependencies, external services. Written risk assessment. - Staging and pipeline, 1.5 to 2h: Cloudflare Pages, staging and production environments, GitHub deploys, rollback path, secrets. - Enquiry form, 2.5 to 3h: server-side validation, spam protection (honeypot, rate limiting), reliable delivery, failure handling and tests. A failed email must never silently lose a lead. - Security, 2.5 to 3.5h: headers, CSP tested against real third parties, HSTS, WAF, dependency audit and patching. - Monitoring, 1h: uptime checks, application errors, enquiry form failure alerts. - Documentation, 2 to 2.5h: architecture overview, deployment guide, environment variables, recovery and rollback steps. Written to be readable by a future maintainer picking the site up cold, not a generated dump. - Cutover and QA, 1.5 to 2h: production deploy, mobile and desktop smoke tests, real form submission, CSP verification, monitoring confirmation, rollback check. Total: 12 to 15.5 hours. SIGN-OFFS THAT REMAIN WITH US DNS changes, the CSP allow-list, risky dependency updates, enquiry delivery destination, secrets, and the final cutover. You recommend, we approve. MAINTENANCE AFTER LAUNCH We intend to place this site on a monthly maintenance retainer, currently being confirmed with the end client. Likely shape: approximately 4 hours per month covering monitoring, dependency updates, and small fixes, unused hours rolling over one month. The person who launches the site is the natural first choice. If ongoing work interests you, say so; it factors into our decision. TIMELINE - Start: on hiring, ideally by 22 to 24 August - Audit delivered within the first two days - Staging live with working form: 28 August - Security and monitoring verified on staging: 1 September - Cutover: 2 to 3 September - Launch: 4 September (fixed, client commitment) - Async communication during Singapore business hours (SGT), response within one business day BUDGET AND TERMS - Hourly against the agreed estimate; state your rate in your proposal - Hours beyond the agreed estimate require our written approval before they are worked - Invoice on completion, or split at the staging milestone - 14-day defect-fix window on delivered work after launch TO APPLY Keep it short. Include: 1. One Cloudflare Pages (or Netlify/Vercel) deployment you have hardened, and what you personally handled 2. Your CSP approach on a site with third-party embeds, in 3 to 4 sentences 3. Which line in our estimate you would change, and to what. This is the answer we read most carefully 4. The AI coding tools in your own workflow, with one example of their use on production work 5. Whether monthly maintenance interests you 6. Your rate and availability, 22 August to 4 September Applications opening with generic boilerplate will not be read.