Skip to content

(1)Work

Things I've built, with the decisions written down: what, why, and what it cost.

A browser frame labelled fiwoodart.co.in/collections holding a wireframe of the catalogue: a round logo, five navigation lines and an orange Enquiry button with a count of three, a column of filter checkboxes with one ticked, and four cards marked F1 to F4, each holding the same winged silhouette. Beneath, the caption The catalogue as a wireframe, no cart, one enquiry list, sent on WhatsApp, the line Browse, then ask, and the note 203 pieces.
[01]2026

A family wood-art business, from a PDF catalogue to a website with WhatsApp in place of a cart

The first website for FI Woodart, my family's business, which handcrafts layered 3D Zoroastrian wood art in Pune. Until October 2026 the whole range lived in a 51-page PDF catalogue. I designed and built a site that turns it into 203 pieces a visitor can browse by collection, wood shade, format and price, then sends whatever they pick to the makers as one ready-written WhatsApp message instead of through a checkout. It went live at fiwoodart.co.in on 15 October, a day after I started, and I have kept it up to date since.

203 pieces online, and every enquiry arrives as one WhatsApp message

WebsiteCatalogueStatic site
Three rows of blocks. Eight outlined boxes named for the prompt modules, from identity to examples. Twelve solid grey blocks for the knowledge-base files, all of them. Then a dashed box for the conversation history and one solid accent block for the new message. The first two rows are labelled as the cached prefix, byte-identical on every call
[02]2026

A WhatsApp sales bot with no RAG: the whole knowledge base rides in a cached prompt

A WhatsApp sales and support bot for Divo, an Indian car dashcam brand, built as a freelance project and live on the brand's main WhatsApp number since 30 September 2026. It answers product, installation, warranty and policy questions only from a 12-file Markdown knowledge base, recommends one camera for the customer's car, and sends anyone who wants a person to the support line. There is no vector store: the whole knowledge base sits in a cached prompt prefix, so prompt size is the bill, and on the live service a cached reply costs about $0.0004.

Live since 30 September, about $0.0004 per reply, measured

AI agentConversational AILLM cost engineering
A browser frame labelled Nextoar, preview, holding a wireframe of the home page: a header with a logo, six navigation lines and an orange pill button reading Request a Demo, then a hero made of five slanted grey photograph panels with two heading bars across them, and beneath it a line of copy, an email field and the same orange button. Below the frame, the caption The home page as a wireframe, plain HTML with a little script on top, the line Static, on purpose, and the note 25 KB of script.
[03]2026

A startup's website, built twice: first in Next.js, then as plain static pages

The new website for Nextoar, the industrial AI startup in Bangalore where I work as an AI engineer intern. I designed and built it to replace a WordPress site that the company had outgrown: five products where there had been none on the menu, a demo request within reach on every page, and nothing to patch. I built it in Next.js, then moved the whole thing to Eleventy, because every page is the same for every visitor and a framework was weight it did not need. It is finished and on a preview address, waiting for the switch to nextoar.com.

Every interaction on the site runs on 25 KB of JavaScript

WebsiteStatic siteFront end
[02] Contact

Want to talk? Say hello.

A project, a question, or just to compare notes. I read everything and write back within a couple of days.