Akshay P.
5+ years in UI/UX. Now I build the whole thing. Design, development, SEO and the speed it loads at — one person from the first call to the handover, so nothing gets lost in the gap between the mockup and the code.
How I ended up doing all of it.
I spent 5+ years designing interfaces — product flows, dashboards, mobile apps — at an agency. I got good at understanding what makes people click, convert, and come back.
Then I noticed a pattern: the sites I was handing off to developers were coming back slower, heavier, and harder to rank. Good design was getting buried under bad code. So I learned to build the whole thing myself — design, development, SEO, and performance — and went solo.
akay.design is the result. A one-person operation that works like a focused team: sharp design decisions, clean code, and a site that actually shows up on Google when your customers go looking.
I work with small businesses, restaurants, and early-stage founders who are tired of invisible, slow websites that don't convert. Most projects go live in about 2 weeks. Every one is built from scratch — no templates, no page builders, no bloat.
Adjectives are free. These three aren't.
Years in UI/UX & web design
Average PageSpeed score on launch
Standard time from kickoff to live
Where I work from
Udupi, Karnataka
I work from the Karnataka coast, on IST — UTC+5:30, which puts me roughly half a working day ahead of Europe and most of one ahead of the US east coast. In practice that means you send something at the end of your day and it's answered before you start the next one. Several projects on the work page are for businesses in Greece, which is where I learned that timezones are far less of an obstacle than people expect them to be.
If you've already found the snake game, that's the other thing that happens while a build is compiling.
No hand-holding required.
What it's actually like to have one person on the whole thing, rather than a team you have to keep in sync.
One point of contact
You talk to me — not a project manager, not an account exec, not a junior. I design it, build it, and optimise it. That's why decisions happen fast and nothing gets lost in translation.
Design that actually ships
I use Figma to show you exactly what you're getting before a line of code is written. No surprises on delivery. What you approved in the mockup is what goes live.
Performance as a baseline
Sub-second load times aren't an upgrade — they're the default. Every site is built on a modern stack and deployed somewhere that was designed to serve it quickly.
SEO baked in, not bolted on
Schema markup, canonical tags, sitemap, robots.txt, Core Web Vitals — all done at build time, not as an afterthought. Your site is ready for Google before it goes live.
Whatever fits the job.
A list of logos tells you nothing. Here's what I actually reach for, when, and — more usefully — what I don't.
What I reach for
- Astro
- The default for anything that is mostly content. It ships almost no JavaScript, which is most of the reason these sites open in under a second.
- Shopify
- When the job is selling things. I would rather hand you a boring, well-tested checkout than build a payment flow from scratch and hope.
- Next.js
- When there is a real application behind the website — accounts, dashboards, anything with a logged-in state.
- Figma
- Every project starts here. You approve a design before I write a line of code, so nothing is a surprise at handover.
What I stay away from
- Page builders
- Elementor, Divi and the rest generate exactly the bloat I would then be paid to strip out.
- WordPress by default
- It is the right answer far less often than it is the given answer. The longer answer.