Problem
Admission visitors need clarity before they share details.
The page had to explain the service quickly, build confidence, and make contact actions obvious without making the experience feel cluttered.
Featured Case Study
Bangalore EduConnect admission guidance website.
A responsive education consultancy website built for engineering admission guidance, enquiry collection, quick call and WhatsApp actions, and search-friendly page structure.
Approach
Put the user's next step in front of them.
I focused the homepage around a strong headline, enquiry form, WhatsApp and call actions, college guidance context, and predictable navigation.
Build
Static frontend with practical backend support.
The site uses responsive HTML, CSS, JavaScript, PHP form handling, SMTP email delivery, optimized metadata, and clear local business content.
Result
A real-world project with client-facing polish.
It demonstrates end-to-end ownership: UI, responsive layout, content flow, lead capture, deployment thinking, and SEO basics for a live website.
Results
Live, and still running.
Delivered, handed over, and in production. Client analytics stay private — what is listed here is verifiable on the live site.
Decisions & Tradeoffs
Where the design earned its shape.
The interesting parts of this project were arguments — mostly ones the client won.
Layout
The enquiry form sits beside the hero, not below the fold.
My first design put a tidy form at the bottom: explain, then convert. The client pushed back — their visitors are parents on phones, mid-decision, who want to talk to a person now. They were right. Tradeoff: a busier hero, traded for reachability at the exact moment of intent.
Contact
A floating call and WhatsApp bar rides the whole page.
Three contact routes stay one thumb away regardless of scroll depth, because the phone call is the product. Tradeoff: permanent screen space given up on mobile — accepted, because it serves the only conversion that matters.
Backend
PHP + SMTP on shared hosting, not a form service.
The enquiry pipeline runs on the hosting the client already pays for — no third-party service, no subscription, nothing new to manage. Tradeoff: enquiries land in an inbox rather than a dashboard, which fits how a two-person consultancy actually works.
Content
Static pages, no CMS.
Fast, cheap to host, and nothing to break. Tradeoff: every content change goes through me — the handover lesson I wrote up honestly, and the first thing I would design differently today.
Lessons
The code was the easy part.
I expected the build to be the hard part. It was not — I had built pages, forms and PHP handlers before. The real lessons were about scope, handover, and whose objective wins. The full write-up is on the blog: What I learned shipping my first freelance client site.
The contact flow is the product
I optimised for a clean page; the client optimised for a phone call. Theirs was the correct objective.
Write the scope down
Small verbal additions compound. A short written scope note makes changes a normal conversation instead of an awkward one.
Build the handover before you need it
Handover is not paperwork at the end — it is a design constraint from the start.
What This Shows
More than a pretty page.
This project shows that I can turn a business requirement into a working web presence: clear layout, conversion paths, technical setup, and real user intent.
Discovery
Understand the audience, service, required actions, and trust signals.
Interface
Design a responsive homepage with visible enquiry, call, and WhatsApp paths.
Delivery
Connect form flow, prepare SEO metadata, test responsiveness, and publish the site.