Hi, I'm Bijay — beecodeguy

I build small, useful tools for problems I keep running into.

I'm a full-time product engineer by day. On evenings and weekends I build software for everyday problems I see around me in Nepal: gyms still on paper registers, print shops juggling WhatsApp files, developers fighting Bikram Sambat dates. Each tool here starts with a real need, and each one comes with its story.

day: product engineer weekends: builder always: writing it down
~/side-projects/notebook.mdneed → built
gyms tracking members in a notebookGymSewain build
print files arriving over WhatsApp and USBMoharoshop pilot
studios collecting photos from customers' phonesStudioDropin build
apps that need Bikram Sambat datesNepali Calendar APIavailable
knowing what's actually safe to spendMeroCFObeta
SIP, EMI and IPO maths, gold and forex ratesFree toolslive
Things I've built

Every tool started with a need.

These are my own projects, built in my own time. Each card says what the problem was, what I made, and who it helps.

GymSewa

for gym owners and front desks
in build
The needGyms with 50–200 members run on a notebook, Excel or WhatsApp. Is this member still active? Who expires this week? How much did we make this month? Answering each one takes too long.
What I builtA mobile-first gym app that records a payment in under 20 seconds, flags who expires this week and shows a monthly P&L. It uses NRs, Bikram Sambat dates, and eSewa, Khalti or cash.
Who it helpsOwners who want the register off paper, and staff at a busy front desk.

I train at a small gym in Kathmandu — the kind with a few dozen regulars, not a chain with a turnstile. One evening I asked the front desk a simple thing: is my membership still active? The person there flipped a notebook, then scrolled a WhatsApp chat, then opened a spreadsheet on a phone. It was not careless. It was just how the register lived.

Next.js · NestJS · PostgreSQLRead the story →Try it

Moharo

for print and photocopy shops · फोनदेखि प्रेससम्म
shop pilot
The needCustomers send print files over WhatsApp, Viber or USB. Shop staff dig through chats, print, and then the files sit on the shop PC forever.
What I builtCustomers scan a QR and upload from their phone. The shop computer shows a Print / Cancel popup. Printed files are kept 24 hours for reprints, and cancelled jobs are deleted straight away.
Who it helpsSmall print shops, and customers who don't want their documents left behind.

I needed a form printed the same afternoon. In the morning I had already sent the PDF to the neighbourhood photocopy shop on WhatsApp, the way everybody does. When I got there, the person at the counter was scrolling. Up, down, yesterday's chat, a photo of somebody's citizenship, a USB still sticking out of the front of the PC. They found my file eventually. While I waited, I also noticed how many other files just… stay there. Assignment PDFs, scanned certificates, things you would not want sitting on a shop computer until Dashain.

Node · Electron tray appRead the story →See it [Moharo link]

StudioDrop

for photo studios
in build
The needCustomers bring photos and videos on their phones, and studios collect them by cable, chat apps or cloud links that shrink the quality.
What I builtA desktop app that turns the studio computer into a receiving station. Customers scan a QR and send full-quality files over the studio Wi-Fi with no app, no account and no cloud. Files are sorted by date, submission ID and name automatically.
Who it helpsStudio staff, and customers sending wedding or event shoots.

A cousin was getting married, and we spent an afternoon at a photo studio going through pictures people already had on their phones — guests, the couple, a few clips from the evening. The studio's options were a cable that never quite fitted the next phone, a "just WhatsApp it, hai" that quietly crushed the quality, or a cloud link that did the same thing and also sent the wedding off the premises. Nobody was being difficult. There was just no good way to move a lot of full-size files from a pocket to the studio computer.

Electron · local HTTP · resumable uploadsRead the story →See it [StudioDrop link]

MeroCFO

for households
beta
The needMoney sits in cash, wallets and bank accounts, plus what people owe you and what you owe. Notes and Excel never give one clear answer to "what can I spend?"
What I builtA phone app that puts all of it in one place and shows a single "Spendable Now" number. Your ledger stays on your phone.
Who it helpsFamilies and individuals who want a calm, honest view of their money.

After Dashain, the house was still in that soft, slightly tired mood — visitors gone, leftover sweets, and a quieter question at the table. Money was in too many places: cash in a drawer, an eSewa balance, a bank account, a bit we had already set aside, and money a cousin still needed to return. Someone asked, not dramatically, whether we could actually spend on a small trip or whether that would be foolish. We opened notes. We opened a spreadsheet. We added things up. We still did not have an honest answer. The totals were not the same as what was safe to touch.

Expo · on-device SQLite · NestJSRead the story →Join the beta →

Smaller things & open source

beecode-otp-uinpm 1.0.4

Need: Rewriting the same OTP input in every project. Built: A React OTP field that handles backspace and delete and works with Tailwind.

View on GitHub →

Receipt Lensexperiment

Need: Subscriptions hiding in receipt emails. Built: A privacy-first Chrome extension that reads Gmail receipts read-only and keeps the data on your device.

[link if you publish it]
A story, in full

How a calendar became an API.

Each tool gets a page like this: the need, the build and what's next.

Nepali Calendar API

Nepal runs on Bikram Sambat. Most software doesn't.

Salaries, rent, school terms and the fiscal year in Nepal all follow the Bikram Sambat calendar. The software we use is built around the Gregorian one.

01How it started

The first time it really annoyed me was on GymSewa. A membership does not expire on "31 June." It expires at the end of a Bikram Sambat month, and people will say "renew until Asar" as if that were a normal unit of time — which, here, it is. I reached for a quick formula and then remembered, again, that BS months are not a fixed length. You cannot just calculate them. You need the actual table.

Then the same need showed up in the next side project, and the next: an invoice date, a report "for Shrawan to Asar," a fiscal year that starts in Shrawan and ends in Asar. I was copying date tables between folders like a person who has not learned the lesson. Holidays and tithi were worse, because they change every year. A friend who was also fighting a calendar in their own app asked if I had "the one file." I did not. I had four slightly different ones.

02Two layers

So I split it on purpose. nepal-date-kit is the free, open-source toolkit: convert BS and AD, format dates in Nepali or English, build a month grid, and work out the fiscal year. It ships month lengths, not events. The Nepali Calendar API is for apps that need more — conversion, month calendars, the fiscal year, and public holidays, festivals and tithi. GymSewa uses BS dates for exactly this reason. Other people building payroll, school, booking or accounting apps for Nepal should not have to maintain that table alone.

03What it does now

The kit is on GitHub. The API is the fuller layer on top. I would rather a developer take the kit for basic conversion and only reach for the API when they need the year-by-year cultural calendar. That boundary is the product.

04What's still true

Software likes Gregorian dates because they are tidy. Nepal does not run on tidy. The work is not to pretend the months are even. It is to look the days up, carefully, and share the lookup.

Get a free key →[developers.bohoralabs.com]
Ideas & requests

Need something similar for your gym, studio or shop? Tell me about it.

Most of these tools started because someone described a problem to me. Tell me yours. If one of my tools already fits, I'll show you how to use it. If it doesn't, your problem might become the next one.

  • Feedback or a bug in one of my tools
  • A feature you wish GymSewa, Moharo or StudioDrop had
  • A problem in your business that software should solve

This opens your email app with the message ready. Nothing is stored here. I read everything, usually within a few days, since I build in my spare time.

Bijay Bohora
About

Mechanic's habits, engineer's job.

01Mechanical engineering
02Automotive service engineer
03Learned to code at a startup
nowFull-time product engineer

Before software, I fixed vehicles in front of customers who wanted to know what went wrong. I still work that way: find the real problem, make the smallest fix that works, and leave something people can use.

Today I work full time as a product engineer. The tools on this site are side projects I build on evenings and weekends, because I notice problems and can't stop thinking about them.

Side-project rules I keep: built in my own time, on my own machines, never using an employer's code, clients or data.