Full-stack developer & brand designer · Gujarat, India
I am a full-stack developer by trade and a brand designer by training, which in practice means one person handles the identity, the interface and the code. Businesses get a site or an application built around how they actually work. Teams get an engineer who has shipped production software and can argue about both halves of it.
Invoiced through PayPal in USD or GBP. A deposit up front, the balance on delivery — both agreed in writing before anything starts.
Selected work
All six of these are concepts — self-initiated, with no client behind them and no results to report — and every card says so before you open it. What makes them worth your time is that they are not screenshots: each one opens into a working interface or a complete brand system you can actually use.
Showing 6 of 6 projects.
The dashboard layout I build for B2B products: KPIs legible in three seconds, a revenue trend, channel split, and a sortable account table.
Interactive · charts hand-built, no library
A complete landing flow — proposition, proof, an interactive plan picker and objection handling — with a working pricing calculator.
Interactive · live pricing calculator
Runs inside a phone frame — log a set, switch tabs, watch the progress rings respond. The touch patterns I hand off for React Native builds.
Interactive · 3 screens, live state
Restraint as the whole strategy: a serif wordmark, a near-black palette, one metallic accent, and enough whitespace that the product carries the page.
4 logo variants · full type and colour system
A mark built on a strict 8-unit grid, a cool industrial palette, and a type scale tight enough to survive inside dense product UI.
Grid-constructed mark · colour with a rule behind it
One restaurant, two shifts. The identity flips Cream-on-Fig by day to Fig-on-Cream at night — same mark, same grid, no sub-brand.
Day/night system · 9 touchpoints from one mark
Services
Four things, with a starting figure against each. Every project is quoted as one fixed price in USD or GBP before any work begins.
A logo and the system around it — type, colour, and the written rules for using them — so the business looks the same on a sign, an invoice and a social post.
Suits New businesses, and established ones whose branding has drifted.
The structure and look of the site before anything is built — what goes on each page, in what order, and what it looks like on a phone. You approve it before code starts.
Suits Anyone who wants to see it before they buy it.
The build: fast, responsive, search-ready, and set up so you can change the content yourself. Hosting and domain handled if you would rather they were.
Suits Businesses replacing a site that is slow, dated or hard to edit.
Software for a job a spreadsheet has outgrown — bookings, quotes, inventory, client portals, internal dashboards. Built around how the business already works.
Suits Teams doing a repetitive process by hand.
A starting figure, not a quote. Final pricing depends on scope, functionality, integrations, content and timeline — and every project is quoted as one fixed price, in USD or GBP, before any work begins.
No account manager relaying your feedback to someone you have never met. Whoever answers your email is doing the work.
Nothing is lost in the handoff between a designer and a developer, because there is no handoff. What you approve is what gets built.
Deliverables, timeline and cost agreed in writing before anything starts. If the scope changes we agree that too — in writing, before it costs you anything.
Not a template with your logo dropped on top. The structure comes from what your customers need to do.
Source files, code, domain and hosting accounts all in your name on final payment. No licence to renew, nothing holding you here.
Thirty days included for anything that breaks, and a straightforward rate after that. I am not gone the day the invoice clears.
Engineering
Everything listed here is backed by something else on this page — a case study you can open, or a service you can commission. A stack list that outruns the evidence is the cheapest thing on a portfolio to inflate, and the easiest to catch in an interview.
Process
Written from your side of the table: when you pay, when you see something, and when you can stop worrying about it.
A short form — what you do, what you need, roughly what you want to spend. No call required to get started.
You get A reply within one business day.
A call in your working hours to go through the business, the goal, and what actually needs building. Most of the useful thinking happens here.
You get A shared understanding of what "done" means.
Written deliverables, a timeline with dates, and one fixed price in USD or GBP. Nothing starts until you have agreed to it, and the number does not move unless the scope does.
You get A written proposal you can compare and keep.
Structure first, then the visual design, desktop and mobile. You review before anything is built — changing a layout is cheap and changing a build is not.
You get Designs to approve, with two rounds of revisions included.
Development, integrations, responsive behaviour and testing on real devices. A live preview link from the first week, so you watch it come together rather than waiting for a reveal.
You get A preview link, updated as work lands.
Deployment, final checks, and a walkthrough of how to run it. You receive the source files and the accounts — everything in your name, not mine.
You get The live site, every source file, and 30 days of support.
There are no testimonials on this page. I have not done enough commissioned work to have collected real ones, and inventing them is not something I am willing to do — so this is the list instead. Every line is a commitment you can hold me to.
Estimate
Tick what you need. It shows a range, not a quote — the real number comes with a written proposal once we have talked about the scope.
About
I am Gautam Goklani, a full-stack developer in Gujarat, India. I came to this from both directions — a computer engineering degree and production software on one side, and design work on the other — and I never found a good reason to pick one.
In practice that means the same person decides what the thing should look like and then makes it work, which removes the handoff where most of the quality usually goes. It also means I will tell you when the design is the problem and when the architecture is, rather than defending whichever one is mine.
I like problems where the interface has to hold something genuinely complicated without making the user hold it too: dashboards over real data, booking and scheduling, internal tools that grew out of a spreadsheet. Outside client work I tend to go a layer lower than the job strictly requires, which is where most of what I know about performance and memory came from.
I work with small businesses and independent teams more than with agencies, because the conversation is direct and the decisions get made by the person who has to live with them.
Questions
Roughly in the order they get asked. If yours is not here, the form below is the right place for it.
Anywhere PayPal is available, which is most of the world. That is the real constraint and the only one — I invoice through PayPal in USD or GBP, with a deposit up front and the balance on delivery, both agreed in writing beforehand. If PayPal does not operate where you are, tell me and we will see whether there is a workable alternative before you spend time on a brief.
USD or GBP. Not both on one invoice — you pick one at the proposal stage and the whole project is quoted and billed in it, so the number you agreed is the number you pay regardless of what the exchange rate does in between.
Calls are booked in your working hours rather than mine. I am on IST, which overlaps the full European and UK working day comfortably; US mornings and Australian afternoons work with a little scheduling. Between calls you get written updates and a live preview link, so you can check progress whenever you want without booking anything.
Enough to understand the business: what you do, who buys from you, and what this needs to achieve. If you have existing branding, content or a current site, send those too. If you have none of it, that is a completely normal starting point and part of what I help with.
A single well-built marketing page starts around $350, a multi-page business website around $750, and custom applications from $1,500. What moves the number is the volume of content, how many integrations are involved, and whether branding needs doing first. You get one fixed price in writing before anything starts.
Branding runs about one to two weeks, a marketing site two to four, and a custom application four to twelve. The single biggest cause of delay is content — if the text and images are ready when the design is approved, projects land at the early end of those ranges.
Yes, and it is a large share of the work. It usually starts with what is currently wrong: hard to use on a phone, slow, difficult to update, or simply no longer matching the business. A redesign can keep your existing content and URLs so you do not lose search rankings.
Yes. If you have a logo, colours and fonts you are happy with, I design within them. If you have a logo but no rules around it, building out the system can be part of the project so everything stays consistent afterwards.
The foundations, yes: clean semantic markup, fast load times, correct titles and metadata, structured data, sitemaps, and a URL structure that makes sense. That is what gets a site indexed properly and competing fairly. Ongoing content marketing and link building are a separate, longer-term discipline — I will say so plainly if that is what you actually need.
Yes, if you want to. Sites are set up with a content management system so you can edit text, images and pages without touching code, and handover includes a walkthrough. If you would rather not touch it at all, I can handle updates instead.
You do, completely, on final payment. The code, the design source files, and the domain and hosting accounts registered in your name. There is no licence to renew and nothing that stops you working with someone else later.
Thirty days of support are included for anything that breaks. After that you can take it from there yourself, come back for one-off changes at an hourly rate, or put a small monthly retainer in place for ongoing work.
I am employed full-time and open to hearing about roles that are a genuine step up — particularly anything involving systems work, real-time data, or performance that has to be measured rather than assumed. The stack is further up this page and the case studies say what was actually built; email is the fastest way to start that conversation.
For a project we work on together, yes — the repository is yours on final payment, and you get it either way. For the concepts on this site the case studies go into the technical decisions rather than linking a repository. Client work is never published without permission, which is the answer you would want if you were the client.
Contact
What you are trying to build, improve or launch — or, if you are hiring rather than commissioning, what the role is. I read every message myself and reply within one business day.