All work

VenueFlow AI

Venue inquiries can be fragmented across ads, forms, inboxes, follow-up, tours, and reporting. The product thesis is to make that journey clearer and harder to drop.

Role
Web, Product, and SEO Developer
Type and status
Public product · In progress
Period
2026

See the system.

Actual interface evidence is embedded here. External links are secondary.

Current VenueFlow AI public homepage on desktop.
Public

The live site frames the venue problem and the intended inquiry-to-tour system.

Public site captured September 3, 2026
VenueFlow AICurrent product surface
Current VenueFlow AI public homepage on desktop.

The live site frames the venue problem and the intended inquiry-to-tour system.

The operational problem

Venue inquiries can be fragmented across ads, forms, inboxes, follow-up, tours, and reporting. The product thesis is to make that journey clearer and harder to drop.

An in-progress venue growth product with a live public site, lead-journey explanation, calculator, guide, contact flow, booking embed, and SEO system.

Why this system exists

A venue does not benefit from more clicks if inquiries are slow to qualify or disappear before a tour. The useful unit is the whole inquiry journey, not one advertising channel.

The repository proves the public product surface, calculator, guide, content system, and LeadConnector form and booking embeds. It does not prove a proprietary CRM or autonomous AI follow-up engine.

Who uses itWedding and event venue owners and operators.

How the work moves

  1. Explain venue problem
  2. Capture inquiry
  3. Route to human review
  4. Offer booking
  5. Support follow-up
  6. Measure journey
  7. Improve acquisition system

What shaped the solution

The repository does not prove a proprietary CRM or autonomous AI follow-up engine.

One free-guide image and the local Windows Sharp binary were missing during audit.

What I owned

Designed

Public product narrative, venue journey, calculator, guide, and conversion paths

Developed

Next.js pages, responsive components, content system, and visuals

Integrated

LeadConnector form and booking embeds, Vercel, and public analytics

Tested

Desktop/mobile reflow, routes, content, metadata, and recurring SEO changes

Operated

Public deployment, maintenance, audit, validation, and content updates

Context matters. The work happened with teams and stakeholders. These statements describe my contribution without turning shared delivery into a solo claim.

Decisions that carried the work

Close the delivery loop

Recurring work must finish audit, fix, validation, evidence ledger, commit, and push before optional diagnostics.

Verified outcome

Live public product, service, calculator, guide, blog, contact, and calendar routes.

Working LeadConnector form and booking embeds.

Repeatable source-led SEO and content workflow.

What I will not overclaim

Public product marketing metrics are not repeated as Ayub's personal outcomes. Ongoing automation health is not overstated.

Verified from the VenueFlow AI project brief and public site.

Tools used where they fit

Next.jsTypeScriptLeadConnectorVercelPlaywrightGSAP
Open public project