SAI in-house build
This website
The standard we build to, down to how an enquiry is kept from getting lost.
Lead capture
Enquiry form
- Name
- Sam Example
- sam@example.com
- Message
- A question about a workflow.
What happens next
- Notification email sent first
- Confirmation sent to the sender
- Record stored, no public access
3 passed
Illustrative sample data
The problem
One failed service could lose an enquiry without anyone knowing.
What we built
Server-side validation, then the notification email first, then the stored record.
Where it stands
Live. Every lead path verified end to end in production.
The full write-up
The problem
An agency that builds production systems should run its own site like one. The first version of the enquiry form relied on a single external backend, so one failure could stop enquiries reaching us. We rebuilt it so no single failure can lose a lead without someone knowing, and gave the site a design that shows the standard we build to.
What we built
Next.js with the App Router and strict TypeScript, and Tailwind CSS. The opening is a real-time scene built with Three.js: one sheet of paper on a lit cutting mat, the headline printed on the mat from the page's own heading, and a camera move that follows the scroll. Every form is validated on the server; the notification email goes out first through Resend, independently of the database write, and each enquiry is then stored in Supabase with row-level security and no public access. If everything fails, the visitor is shown our email address instead of a dead end.
Where it stands
Live at strategicaiinnovations.com. Lead capture was verified end to end in production on every path: the notification email, the confirmation to the sender and the stored record.
How it fits together
Parts: Visitor (Enquiry form); Server (Validates every field); Notification (Resend, sent first); Stored record (Supabase, row-level security); Confirmation (Email to the sender); Our email address (Shown if all else fails). Connections: Visitor to Server; Server to Notification (first); Server to Stored record; Server to Confirmation; Server to Our email address (if all fail).
Dates we can point to
- First commit.
- Lead capture merged: email first, then stored.
- Database schema merged, public-access flaw fixed.
- Security and privacy pages list every processor.
Want a build like this for your business?
Tell us the process you would hand over. We will say plainly whether it fits.
Book a call (opens in a new tab)or email contact@strategicaiinnovations.com