From property brochure to a working business tool. Clearer project information for buyers, and a dependable way for staff to manage content and enquiries.
- Scope
- Product design, website development, CMS, enquiry delivery and analytics
- Built with
- Next.js, Payload CMS, PostgreSQL and Resend
- Website
- vilniauskvadratai.lt ↗
Two sides of the same website
Visitors needed to understand a property and decide whether to arrange a viewing. Staff needed control over its information, a reliable record of interest, and a way to see which projects attracted attention.
The previous site depended on a legacy CMS. Property facts were inconsistent, and enquiry delivery depended on email. The redesign brought those separate concerns into one connected workflow.
Facts before sales language
Current projects lead the browsing journey. Price, area, status, and location are visible without hovering, so the same hierarchy works on a phone. Plans, units, and other details appear only when the source supports them.
A sold property offers a path to ask about similar projects. Missing information stays missing, instead of becoming a plausible-looking claim.
An enquiry that survives an email failure
A successful form means a saved enquiry, not just a green message. The submission is validated and stored in the CMS before staff notifications are attempted. Retrying an interrupted submission does not create duplicate leads.
- ValidateCheck the request and identify retries.
- SaveKeep a durable record for staff.
- NotifyDeliver email, retry failures, flag what needs review.
The visitor's confirmation promises only what is known: the enquiry was received. Email can recover independently.
Content and insight in one place
Payload replaced the legacy CMS, bringing projects, articles, media, enquiries, subscriptions, and email templates together. Recovered project content entered as drafts for staff review, with public routes preserved.
A first-party dashboard puts project views and enquiry interest beside the content staff manage. Analytics excludes contact details, IP addresses, and form content, and never blocks navigation or a submission.
Release confidence
Release checks covered 18 live pages and their internal links, preservation of five published project pages, recovery of six legacy project bundles, and 16 passing backend tests.
Database migrations were rehearsed against a restored production schema. Automated live checks created no enquiries and sent no emails. These checks demonstrate delivery and data integrity, not a measured increase in conversions.
What changed
The website became part of the business operation. Visitors get a clearer path to a viewing; staff get editable content, recoverable enquiries, and understandable demand signals.