SparshaTech is a senior product engineering studio in Kathmandu — custom software, applied AI, and cloud platforms for teams in twelve countries.
Nine years. Forty-some products. Twenty-two people, twelve time zones, one office dog.
01 · स्पर्श — SPARSHA, "TOUCH". OUR NAME, DRAWN IN INK. MOVE — THE INK LISTENS TAP — THE INK RIPPLES
Three of the forty-odd products we've taken from first sketch to production. Names and numbers are demonstration content for this preview build.
TELEMEDICINE · 2023—
A consultation platform built for clinics at the end of the road — offline-first records, SMS fallbacks, and video tuned to survive a 2G monsoon. Doctors in Kathmandu now reach patients a two-day walk from the nearest highway.
FLUTTER · NODE · POSTGRES · WEBRTC
AI DOCUMENT PIPELINE · CHICAGO · 2024—
Customs brokerage runs on paper that pretends to be PDF. We built an extraction and validation pipeline — layout-aware models with a human-in-the-loop review bench — that turned an eleven-minute manual entry into forty seconds.
PYTHON · PYTORCH · REACT · TEMPORAL
RETAIL OPERATING SYSTEM · 2021—
Inventory, billing, and credit ledgers for South Asian neighbourhood retailers — built to work one-handed, in three scripts, on a cracked phone behind the counter. It held 99.98% uptime through the last three festival seasons.
TYPESCRIPT · REACT NATIVE · GO · COCKROACHDB
Four practices, one studio. Every engagement is staffed by senior engineers only — nobody learns on your budget.
Web and mobile products taken from first sketch to first hundred thousand users — architecture, APIs, and the unglamorous plumbing that keeps them standing.
TYPESCRIPT · REACT · NODE · FLUTTER · POSTGRES
LLM pipelines, retrieval systems, and models that survive contact with production — evaluated, observable, and priced per answer, not per demo.
PYTHON · PYTORCH · RAG · EVALS · VLLM
Infrastructure as code, one-command deploys, observability that pages the right person — and cloud bills that stay embarrassingly small.
AWS · GCP · KUBERNETES · TERRAFORM · GRAFANA
Interfaces with real fit and finish — design systems, motion, and accessibility treated as engineering, not garnish. This page is the demo.
DESIGN SYSTEMS · MOTION · WEBGL · WCAG 2.2
Sparsha (स्पर्श) is the Sanskrit word for touch. We took the name seriously: everything we ship is handled, checked, and finished by a person who signs it.
The studio was founded in 2017 by three engineers who came home from jobs in San Francisco and Singapore to prove a point: the software they were paid to build over there can be built just as well from here. Today we are eighteen engineers and four designers in a converted house in Jhamsikhel — plus one very good office dog.
We keep a four-hour overlap with every client timezone, write things down, and say no to work we can't do beautifully. The studio runs Monday to Friday; the mountains are for the weekend.
02 · KATHMANDU TO THE WORLD — TWELVE COUNTRIES SERVED.
They rebuilt in five months what our previous vendor circled for two years — and the Friday notes alone were worth the invoice. It is the first agency work I've seen that our own engineers didn't want to rewrite.
SparshaTech treats a bug the way a careful craftsman treats a flaw — it simply does not ship. Eleven thousand shops run on what they built, and I sleep fine.
We work from a studio in Jhamsikhel, Kathmandu, and most of our clients are in North America, Europe, and Australia. Every project gets a four-hour daily overlap window with your timezone, a weekly release, and a written progress note — the distance shows up in your invoice, never in the communication.
Two shapes. Fixed-scope product builds start with a two-week paid discovery, then run in weekly releases until launch. Embedded teams place two to five of our engineers inside your existing team on a monthly basis. Both start with a free scoping call.
TypeScript, React, and Node for product work; Python and PyTorch for AI and LLM systems; Flutter for mobile; Postgres, Kubernetes, and Terraform on AWS or GCP for infrastructure. We pick boring, durable tools and spend the excitement budget on your product.
Yes — about half of our work is version one of something. We keep early builds deliberately small: one thin slice of the product, shipped to real users, then widened. We do not take equity; it keeps the advice honest.
You do, from the first commit. Work happens in your repositories and your cloud accounts wherever possible, and everything ships with documentation and a recorded handover — no lock-in by design.
Tell us what you're making — a paragraph is plenty. We reply within two working days, with questions rather than a sales deck.
03 · A WAVE FROM KATHMANDU — SAY HELLO BACK.