Lamp

Lamp Solution Pvt Ltd · Kathmandu

One light, many hands.

Lamp builds tools that take charge of the work behind a customer conversation. Not a copilot that waits to be asked — software that does the job, shows what it did, and gives the decision back whenever it matters.

See what we makeTalk to us

What we make

Each product takes charge of the light.

Jimmaa
Jimmaaजिम्माby Lamp

A shared inbox for businesses that sell through DMs and comments. Jimmaa reads the conversation, prepares a grounded reply from the business's own catalog and policies, and waits for a person to approve it.

जिम्मा — Nepali, “to take charge of.”

  • Instagram, Messenger, WhatsApp and TikTok in one inbox
  • Answers from the shop's real catalog, prices and stock
  • Turns a conversation into a confirmed order
  • Commits inventory, then hands off to the courier
  • Replies in Nepali, English, or the mix people actually type
  • Every send attributed, every decision on the record
Visit JimmaaFirst product · Live in Nepal

What comes next

More products, one recipe.

Every Lamp product inherits the same three things: a mark that holds the light its own way, a refusal to answer without grounds, and authority the owner grants rather than the software assumes. Jimmaa takes charge of the conversation. What takes charge of the next problem gets built the same way.

How we work

Software should hand the work over, not the judgement.

01

Authority is granted, not assumed

A tool starts by asking. It earns more room one step at a time, only where the owner has said so, and it hands the decision straight back the moment anything is uncertain.

02

Grounded, or silent

A tool that does not know an answer says so. We would rather return nothing than return something invented — a wrong price is worse than a slow reply.

03

Always say who acted

Whether a person sent it or the software did, the record shows which. Autonomy without attribution is not automation, it is guesswork nobody can audit.

04

Built where it is used

Made in Kathmandu, for the way business is actually done here — rupees, cash on delivery, Nepali and English in the same sentence, and customers who arrive in a DM.

Why here first

Depth in one market beats breadth in ten.

Global tools treat a Nepali shop as an edge case. Cash on delivery is an afterthought, the courier is somebody else's problem, and nobody handles a customer who writes half in Nepali and half in English.

Those are not edge cases here — they are the job. Building for them properly takes local work that a generic product will not do, and that work is exactly what makes the tool hard to replace.

Nepal is where we prove it. The parts that differ between markets — currency, language, payment, courier — are built to be swapped, so the same core can travel when it has earned the right to.

Working on something that should take charge of itself?

We are a small team in Kathmandu. If you are building in this space, hiring, or want to use what we make — we would like to hear from you.