Skip to content
Loading CodeVani

Digital Studio

000

CodeVani

Available for new work

Ahmedabad IST

Design and engineering for brands that intend to last.

We are a small studio of designers and engineers building websites, products and automation for companies who would rather be considered than loud.

Projects
142
Countries
11

Scroll to begin

Website Design· Full Stack Development· SaaS Platforms· AI Automation· Branding· UI/UX Design· Custom Software·

Studio

A studio built for the long form, not the quick win.

CodeVani was founded on a narrow belief: that most digital work fails not from a lack of ideas but from a lack of finish. We keep the team small so the people who shape the thinking are the same people who ship the code.

That means fewer projects each year, longer engagements, and an unreasonable amount of attention paid to the parts most studios treat as details — the weight of a heading, the timing of a transition, the shape of an empty state.

How we work
Type specimens and layout studies pinned across a studio wall

Type studies — Meridian

Interface wireframes laid out in sequence on a large desk

Flow mapping — Atlas

Why CodeVani

Anyone can ship a website. Fewer can ship one that still feels deliberate three years later, under a team that has changed, at ten times the traffic. That is the only standard we find interesting.

01 — Small by design

No account layer

You talk to the people doing the work. There is nobody in the middle translating.

02 — Craft as strategy

Finish is the feature

Trust is built in the details a spreadsheet never captures. We budget for them.

03 — Built to hand over

Documented, not locked

Every engagement ends with your team able to continue without us. Most choose not to.

04 — Measured

Performance as a promise

Budgets for weight, motion and Core Web Vitals are agreed before design begins.

Process

Five stages, in the open.

  1. 01 — Discovery

    We argue about the problem first

    A week of interviews, analytics and honest disagreement. We would rather lose the brief than solve the wrong thing.

  2. 02 — Direction

    Two directions, honestly costed

    Territory, type and motion language — presented with the build cost attached, so the choice is real.

  3. 03 — Design

    Design in the browser, early

    Layout, rhythm and interaction reviewed on real devices from week two. Static mockups hide too much.

  4. 04 — Build

    Typed, tested, reviewed

    Weekly deploys to a staging URL you can share. Performance budgets checked on every pull request.

  5. 05 — Launch & care

    Launch is the midpoint

    Handover documentation, a training session, then a retainer only if you actually want one.

Technology

Boring tools, chosen on purpose.

We pick what your team can still hire for in three years. Novelty is a cost, and we only pay it where it earns something back.

Infrastructure diagrams and deployment logs on a studio display

Front end

  • TypeScript
  • React
  • Next.js
  • Astro
  • Tailwind CSS
  • GSAP
  • Three.js

Back end

  • Node.js
  • Python
  • Go
  • PostgreSQL
  • Redis
  • tRPC
  • GraphQL

Data & AI

  • Claude API
  • OpenAI
  • pgvector
  • LangGraph
  • Temporal
  • dbt
  • DuckDB

Platform

  • Vercel
  • Cloudflare
  • AWS
  • Docker
  • Terraform
  • GitHub Actions
  • Grafana

Design

  • Figma
  • Rive
  • After Effects
  • Storybook
  • Chromatic
  • Playwright
  • Lighthouse CI

Principles

  • Progressive enhancement
  • Typed end to end
  • Accessible by default
  • Budgeted performance

Case studies

Three, in detail.

Numbers matter, but only alongside what they cost to reach. Each of these took between four and fourteen months.

Swipe to continue →

Meridian treasury platform interface and brand collateral

Case 01 — Fintech

Meridian

A cross-border treasury product with a brand that had outgrown its own interface. We rebuilt both together over fourteen months — identity, design system and the entire front end.

Activation
+38%
Time to task
−54%
Lighthouse
99
Atlas fleet planning software shown across several views

Case 02 — Logistics

Atlas

Fleet planners were running a nine-figure operation out of spreadsheets. We replaced them with software that respects how planners actually think, then automated the reconciliation nobody wanted to own.

Planning time
−61%
Manual entry
−88%
Adoption
94%
Sable editorial commerce pages and lookbook spreads

Case 03 — Retail

Sable

A slow-fashion label whose storytelling was being flattened by a stock theme. We built an editorial commerce front end where each collection can be composed like a magazine, without a developer.

Revenue
+72%
Return rate
−19%
LCP
0.9s

Yours could be the fourth.

Start a project

By the numbers

0
Projects delivered
0
Countries served
0
Years in practice
0
Median Lighthouse

In their words

The part we cannot write ourselves.

Drag, swipe or use ← →

“They argued us out of our own brief in week one. It was uncomfortable, and it was the single most valuable thing anyone did for the product that year.”

Priya Raghunathan

VP Product · Meridian

“Our planners had used spreadsheets for eleven years. Six weeks after launch, ninety-four per cent had moved over without a mandate. That never happens.”

Daniel Okonkwo

COO · Atlas Freight

“The handover was the surprise. Full documentation, a recorded walkthrough, and my team editing collections on day two without asking anyone's permission.”

Elise Marchetti

Founder · Sable

“We came for a website and left with a design system three other teams now build on. They costed that honestly before we committed to it.”

Ingrid Halvorsen

Brand Director · Norda

“Automation projects usually end with a dashboard nobody opens. This one ended with four hours a week back for every researcher on the team.”

Marcus Feld

Research Lead · Verity

Questions

Asked before you ask.

Anything not covered here — just write to us. We answer every enquiry ourselves.

  • Most website engagements land between ₹6L and ₹28L. Product and SaaS work is scoped monthly, typically ₹4L–₹9L per month for a two- to three-person team. We give a fixed range after the first call and a firm number after discovery — never a number before we understand the problem.

  • A focused marketing site is six to ten weeks. A product or platform is four to fourteen months. We deploy to a shared staging URL from week two, so you are never waiting on a reveal.

  • Often, and it is usually the better arrangement. We work inside your repository, your review process and your standards. Where you have none yet, we will help set them — and document them so they outlast the engagement.

  • Handover documentation, a recorded walkthrough and a live training session are included in every project. A retainer is available but never assumed — the whole point of the handover is that you can choose.

  • Sometimes — a landing page, an audit, a design system rescue. We take on a handful of short engagements a year, usually where the work is unusually well defined. Ask, and we will be straight with you about capacity.

  • We are based in Ahmedabad and work across eleven countries. We hold a four-hour overlap with every client's working day, whichever timezone that means for us.

Start something

Let's make something worth keeping.

Tell us what you are building and what is in the way. We reply within two working days, always with a real answer rather than a calendar link.

New business

studio@codevani.com

Telephone

+91 90000 00000
Availability
Two slots, Q4 2026
Typical start
Three to five weeks
Studio time
IST
Write to the studio
The CodeVani studio wall during a review