Websites
A website with the system
built into it
Enquiries land in a private dashboard instead of somebody's personal inbox. Replies go out from your own address. A booking writes itself into a real calendar.
A brochure site ends the moment somebody fills in the form. The sites I build carry on from there: the enquiry is recorded, the reply goes out from your own address, and the booking writes itself into your calendar.
I build the front of the site and the system behind it as one thing, because they are the same job. The pages are written and built with AI, which is why a site like this can carry scroll films, a walkthrough and a working dashboard without a studio of people behind it. The domain, the hosting account and the code are yours.
Enquiries land where you can see them
Every enquiry goes into a private dashboard, with a record of what the visitor read and what has been said back. Nothing sits buried in one person's inbox.
Replies from your own address
The reply goes out from your own domain, signed by your company. The visitor never sees a third party, and the thread stays in your own mailbox.
Booking into a real calendar
A visitor picks a slot and it writes into your Google Calendar with the details attached. My own booking page works this way and replaced a subscription I used to pay for.
Scroll films and walkthroughs
Where a page has to show a building or a product moving, the keyframes are generated and the camera is driven by the visitor's scroll. There is no video file to sit and wait for.
Your accounts, your code
The site is handed over on hosting and a domain in your name, with the code. There is no monthly software subscription for the parts I build.
It is built to be edited
The content sits in plain data files, so changing a room, a list, a photograph or a paragraph of text does not need me.
What the system behind the site does
The visible part is a website. Underneath it, an enquiry becomes a record: who asked, what they were looking at, what they said, and what has been sent back. That record sits in a private dashboard you log into, and it is the same record the reply is written from. Nobody has to forward an email to find out whether a lead was answered.
The same pattern covers a booking that has to show up in a real calendar, a form that has to reach the right person, a file somebody uploads that has to land in the right folder, and a short reply that can go out before anyone is at a desk. Each of those is a small system. The site is where it becomes visible.
- A private dashboard for enquiries, not a shared inbox
- Replies sent from your own domain
- Booking written into Google Calendar
- Uploads filed into your own Drive
- A record of what the visitor read before they wrote
Sites I have built
I built the website for Forsyth's Homes and the enquiry system behind it, and ran the photography pipeline for it. For Qi Studio I built and host their pages, including their creative-direction site and their links page. For YBF I designed and built a redesign of their site in their own brand. Sunstar Graphics is in production now, a rebuild of their existing site.
There is also a concept site on my projects page built as one continuous scroll with no cuts. It is the clearest way to see what a scroll film does to a page, and it runs in a phone browser. The same page carries the booking system and the enquiry dashboard, and both of them can be used from there.
What I do not do
I do not run photography shoots, paid advertising or monthly search retainers. For one client I built the photography pipeline, which is the organising and processing of images after a shoot. If what you need is a marketing agency, this is the wrong page.
I also do not keep control of the site. The hosting account, the domain and the code are in your name from the start, and the handover is written so your own developer can take it over. If you want AR or a 360 walkthrough on the site as well, that is a separate piece of work on the same page.
What a site like this costs
The quote follows a short conversation about what has to happen after the visitor arrives, because that is what the work actually is. It names the pages, the systems behind them, where the records go, and the handover. There are no figures here: a small site with a working dashboard behind it and a large site with a plain form are not comparable.
Four things move the number: how many pages there are, whether the site has to do something after the form is submitted, whether it needs scroll films or a walkthrough, and whether the photographs and the text already exist. Hosting sits on an account in your name. Changes afterwards are quoted separately and can be stopped.
How it runs
- 01
What happens after the form
We start at the end. I ask what should happen the moment somebody enquires, and work backwards into the pages.
- 02
Design
You see the look and the page structure before anything is built, usually as a page you can scroll on your own phone.
- 03
Build
The site and the system behind it are built together, and you get a private link to use while it is still being changed.
- 04
Handover
The domain, the hosting account and the code go into your name, with a written note on how to edit the content.
Built, not described
Questions people ask
How much does a website like this cost in India?
There is no fixed price. The quote names the pages, the system behind them and the handover. What moves it: how many pages there are, whether anything has to happen after a form is submitted, whether you want a scroll film or a walkthrough, and whether the photographs and text already exist.
What does the AI actually do here?
Two things. The site itself is written and built with AI, which is how one person covers work that used to need a small team. And the keyframes for scroll films are generated rather than filmed. The system behind the site is ordinary code, because it has to be right every time.
Can enquiries stay out of my personal inbox?
Yes, and that is the usual reason people ask. Enquiries land in a private dashboard you log into, with a record of what the visitor was reading. Replies go out from your own domain, so the thread stays with your company.
Will a booking show up in my calendar?
Yes. The visitor picks a time and it writes into your Google Calendar with their details attached. My own booking page works exactly this way, and you can try it on the projects page before you ask me for one.
Who owns the site afterwards?
You do. The domain, the hosting account and the code are in your name, and the handover is written so your own developer can take it over. There is no monthly software subscription for the parts I build.
Can I edit the text myself?
Yes. The content sits in plain data files, so a list, a room, a photograph or a paragraph can be changed without me. I write down how, and I walk one person in your office through it at handover.
Do you do SEO or run ads for the site?
No. I build the site so search engines can read it and I set up the basics once. After that I do not take a monthly retainer for search and I do not run paid advertising. Those are somebody else's job.
Next step