Services
Professional services we provide
Calventory — Inventory & Accounts Software
Calventory is our own inventory and accounts software, built in Dhaka for wholesale businesses in Bangladesh — hardware, building materials, agro-vet, and distributors who sell on credit and get paid later. It runs on a computer and on an Android phone, in Bengali, and it is the product most of the businesses we work with came to us for.
Who it is for
A shop that buys and resells in volume, keeps party accounts, and lives or dies on how much of last month's sales has actually been collected. If your stock moves faster than your paperwork, and the real position of the business is spread across a register, a spreadsheet and someone's memory, this is the problem Calventory was written to solve.
It is not built for a single retail counter, and it is not a general-purpose accounting package with a stock module bolted on. It is a wholesale system: challan and invoice, party ledger and receivables, purchase and stock, and the profit-and-loss that falls out of all three.
What it costs to keep doing it by hand
The expensive part is never the bookkeeping. It is the decisions made without it.
Money you have already earned and cannot name. Nearly every wholesale business we have worked with was owed more than the owner thought, and could not say by whom without an afternoon of adding up. A ledger that is always current turns collection from a memory exercise into a list.
Stock that stopped selling months ago. Dead stock does not announce itself. It sits, quietly holding capital, and it looks exactly like stock until someone compares what is on the shelf against what actually moved.
A month-end that arrives as a surprise. If the profit figure only appears weeks after the month closes, it is history, not information. By then whatever caused it has been repeated four more times.
None of that requires software to notice — it requires software to notice it on time.
The depth is the point
Anyone can show you a stock list. What separates a system you keep from one you abandon after three months is whether it answers the questions you actually ask.
Calventory ships 31 built-in reports, and they exist because customers asked for them one at a time over several years: party balances and group balances, customer follow-up and paid-versus-due, top collection and top customers, stock against sales, negative stock, reorder levels, margin on sales, item statements, daily cash, bank and cash summaries, monthly balances, the balance sheet and the income statement.
It also carries the parts of a real business that most inventory software ignores:
- NBR Mushak 6.3 tax challan generated to the gazette form — including the eleven-column table that is routinely printed with ten. We worked the legal basis out from the VAT Act and rules rather than copying someone else's template.
- Multiple branches under one business, with stock, accounts and reporting kept straight per branch and consolidated when you want the whole picture.
- HR — attendance pulled from an attendance device, salary profiles, salary sheets and payables, employee ID cards.
- SMS to customers, so a due reminder does not depend on someone remembering to call.
- An Android app — the real application, not a mobile website: fingerprint login, camera capture, notifications, and it updates itself.
How we work
Software only pays off once the staff use it. So the first thing we do is not install anything; it is sit with your existing numbers.
We load your item list, your opening stock and your outstanding party balances, so that on day one the system shows your business rather than an empty template. Then we train the people who will actually run it — not the owner alone, which is the single most common reason a rollout stalls. Then we stay reachable, and you run the old method alongside the new one for as long as it takes to trust the numbers.
That changeover is a service in its own right, and most of our customers arrive needing it — see moving from Tally, Excel or paper.
Support comes from the people who wrote it
When you call about Calventory, you reach the engineers who build it. Not a ticket queue, not a reseller, not a support tier that escalates to someone who will call you back.
That is a deliberate constraint on how large we let the customer base grow relative to the team, and it is the reason improvements arrive steadily: the person who hears the complaint is the person who can fix it, and the fix reaches everyone.
Seeing it for yourself
The honest answer to "can I try it" is that a demo is worth more than a screenshot tour, because the first question anyone asks is how would this handle my stock, my parties, my way of doing challan — and that is a conversation, not a feature list.
Get in touch and we will walk you through it on your own numbers. If you would rather look before you speak, the Calventory page on Facebook carries screens and updates.
Existing customers sign in at calventory.com.
If your question is about the company rather than the product — whether we can build something you cannot buy, or take over a system someone else left behind — see what else we do.
Setup, Training & Direct Support
Software only pays off once the staff use it. Buying it is the easy part; the projects that fail almost never fail because the software was wrong.
This is the part of the job we take most seriously, and it is the reason people stay with us.
Why rollouts fail
We have watched enough of them to know the pattern, and it is nearly always one of these four.
The system starts empty. Staff are asked to work in something that knows none of their items, none of their customers and none of their balances, while the register beside it knows everything. They use the register. Within a month the software is a data-entry chore with no payoff and it is quietly abandoned.
Only the owner was trained. The owner understands it, is convinced by it — and is not the person entering sales at four in the afternoon. The people who actually operate it learned by watching, so they learned the parts that were visible and none of the parts that matter at month-end.
The changeover was a cliff. Everything switched on a Monday, something did not match, and nobody could tell whether it was a bug or a mistake. Trust once lost is expensive to rebuild.
Nobody could be reached. The first real problem arrived, the phone number in the contract led to somebody who took a message, and the business went back to what it knew.
Everything below exists because of those four.
We start with your numbers, not a blank system
Before anyone is trained, we load what you already have.
Your item list, with the names your staff actually use rather than the ones a catalogue thinks are correct. Your opening stock, counted and entered so day one shows a real position. Your outstanding party balances — who owes you, who you owe, and how much — because a ledger that starts at zero is worse than no ledger. Where the source is a Tally export, a spreadsheet, or a register that has to be typed, we do that work.
The point is that on the first morning your staff open the system and recognise the business in it. That single fact decides most rollouts.
Coming from Tally, Excel or paper is common enough that it is its own service.
We train the people who will use it
Not a demonstration. Training the counter staff on selling and challan, the storekeeper on stock and purchase, whoever handles collection on the ledger and follow-up, and the owner on the reports that answer the questions you actually ask at the end of the month.
In Bengali. On your data, with your products, doing the tasks they will do tomorrow.
Then we run old and new side by side until the numbers agree and everyone believes them. That period is not wasted effort — it is what converts a system people were told to use into one they trust.
Then we stay reachable
Support comes from the engineers who wrote the software. Not a call centre, not a reseller, not a first tier who will raise a ticket and call you back. The person who takes your call is the person who can change the code.
That matters more than it sounds. A support agent can tell you which button to press. They cannot tell you why the balance is wrong, and they cannot fix it. When the answer is "the software is doing the wrong thing here", we can have that corrected — and the correction reaches everyone we support, not just whoever complained loudest.
In Dhaka we come to you. Outside Dhaka we work through our agents and online. Either way there is a person, not a queue.
What this is worth
The value is not the hours of support. It is that a problem gets fixed instead of worked around.
Every business that runs on workarounds accumulates them: the report nobody trusts, the entry that has to be corrected by hand every week, the number two people compute differently. Each one is small and each one is permanent, because nobody who can remove it is listening. Over a few years that is what separates a system the business relies on from one it merely tolerates.
Keeping the people who write the software reachable by the people who use it is not a service tier. It is a deliberate limit on how fast we take on new customers, and it is why more than 130 businesses across Bangladesh are still with us.
Already have software that nobody supports?
That is a normal call for us. A system built years ago by someone who has moved on, still running, still important, and increasingly frightening. We take those over — see custom software development — and the first useful thing is usually just writing down what it actually does.
Get in touch and tell us what happens today when something goes wrong.
Moving from Tally, Excel or Paper
Most of our customers were keeping accounts in Tally, in a spreadsheet, or in a register before they moved. Almost none of them changed because the old method stopped working. They changed because it stopped keeping up.
Whatever you are on now, the changeover is the part that frightens people, and it is the part we do for you.
The real reason people stay too long
It is rarely that the current system is bad. It is that switching feels like it risks the one thing a business cannot afford to lose: knowing what it is owed and what it owns.
That fear is reasonable. A migration done carelessly leaves you with a system full of items nobody recognises, balances that do not tie to anything, and staff quietly keeping the register going in parallel "just to be safe". Six months later you are paying for two systems and trusting neither.
So the whole job is one thing: get you across without ever losing sight of your real numbers.
What we actually move
Your item list, with the names your staff use. Not a tidied catalogue — the actual names, codes and units they will search for tomorrow. A migration that renames everything for consistency is a migration that makes every counter operator slower for a month.
Your opening stock. Counted, entered and reconciled, so that day one shows a real position rather than zero. Where the count and the old system disagree, that difference is worth seeing — it is often the first thing the new system tells you.
Your outstanding balances. Who owes you, how much, and how old it is; and the same for what you owe. This is the number the business runs on, and a ledger that starts empty is worse than no ledger at all.
Your parties and suppliers, with their groups, so the reports you want on day one actually group things the way you think about them.
Where the source is a Tally export we work from that. Where it is a spreadsheet, we clean and map it. Where it is a register, we type it. That last case is normal and it is not a reason to postpone.
Coming from Tally specifically
Tally is capable software, and we do not pretend otherwise. The reasons our customers left it were consistent and none of them were "it did not work":
- The people using it could not read it. The interface is English, and the staff entering sales at four in the afternoon are more confident in Bengali. That gap shows up as errors, not complaints.
- It lives on one computer. The owner who wants to see today's collection while away from the shop cannot, and a system you can only consult from one desk is a system you consult less often than you should.
- Local paperwork. NBR forms and the way Bangladeshi wholesale actually documents a sale are not what a general-purpose package assumes.
- Support meant a reseller. When something was genuinely wrong, the distance between the person who took the call and the person who could change anything was very large.
If none of those describe you, staying is a perfectly good answer, and we will say so.
Coming from Excel or a register
Different problem, same fix. Spreadsheets do not fail loudly — they fail by being right in one place and stale in another, and by depending entirely on one person who understands the formulas.
The register has the opposite trouble: it is trustworthy and completely un-queryable. Every question costs an afternoon, so most questions never get asked.
Migration here is mostly data entry and structure, and the payoff is immediate: the first time a report answers in three seconds a question that used to take half a day, the argument is over.
Nothing switches on a Monday
We run the old method and the new one side by side until the numbers agree and everyone believes them. Not as a formality — until your staff, not us, say it matches.
That period costs some duplicated effort and it is worth every hour. It is the difference between a system people were told to use and one they trust, and trust is what determines whether it is still in use next year.
Training runs alongside it — the counter staff, the storekeeper, whoever chases collection, and you. See setup, training and direct support for how that works.
Start with a conversation, not a quote
Tell us what you are on now and roughly how much of it there is: how many items, how many parties, whether balances are current. That is enough for us to tell you what the changeover looks like and what it does not.
Get in touch. If the honest answer is that you should stay where you are for another year, you will hear that instead.
Business Websites
We build company websites, product catalogues and online stores — and then we keep them running. They are built on a platform we wrote and maintain ourselves, not assembled from a theme somebody else will stop updating.
The page you are reading is running on it. So is every other page on this site. That is the demonstration; the rest of this page explains what it means for you.
What you get
A site your own staff can update. Every site comes with an admin dashboard. Products, prices, photos, notices, blog posts, team profiles, job openings, contact details — your people change them, from a phone if necessary, without emailing a developer and waiting. This is the single biggest difference between a website that stays current and one that quietly becomes wrong.
Pages that Google can actually read. The public site is rendered on the server, so a search engine sees finished HTML rather than an empty shell it has to run JavaScript to fill. Clean, readable addresses. An automatically maintained sitemap.xml that adds every new product and post as you publish it. Per-page titles and descriptions you control. Structured data so search engines — and increasingly AI assistants — can tell what your business is and where it is.
An online store, if you want one. Cart, checkout, order tracking by phone number or link, PDF invoices, stock status, wishlists, and returns handling. It is a switch, not a rebuild: catalogue sites and selling sites are the same platform.
Speed on a real connection. Your customers are on 4G, on mid-range Android phones, sometimes outside Dhaka. The platform is engineered to a hard memory ceiling and streams images rather than loading them into memory, which is unglamorous work that shows up as pages that open when the connection is poor.
Why a platform beats a template
Most agency websites are built once, handed over, and then age. The theme stops being updated, a plugin becomes a security hole, the developer who built it moves on, and three years later the honest advice is to start again.
Ours are all the same codebase. Nine live sites run on it today, each with its own content, colours, menus and features, all served by one system we maintain. When we improve something — a faster page, a search-engine fix, a new capability — it reaches every site we host. Nobody has to buy an upgrade or authorise a migration.
The proof of that is recent and specific. In one week this month the platform gained canonical link tags, an automatic social-sharing image, a per-page title system that had been silently broken, and a corrected robots.txt. Every site we host got all four the same day. A templated site would have needed nine separate pieces of work, and would most likely have received none.
What a website that has gone stale costs you
It is rarely dramatic. The phone number is two years old. The product list stops at what was in stock in 2023. A customer checks whether the company is still trading, sees a copyright date from three years ago, and quietly calls someone else.
For buyers who are choosing between suppliers they have not met, your website is the only evidence available. It does not need to be elaborate. It needs to be current, fast, and to look like it belongs to a business that is paying attention — which is exactly what a site your staff can edit gives you, and a site they cannot does not.
How we work
We start from what the site is for — enquiries, credibility, a catalogue buyers can browse before calling, or actual online orders — because those are four different sites.
We handle the domain, whether you already own one or need it registered, and the SSL certificate. We do the initial content load: products, photos, staff, services. Then we train whoever will maintain it, so the handover is real rather than a folder of instructions nobody opens.
Afterwards it is hosted and maintained by us, with someone accountable when something breaks. See hosting, domain and maintenance for what that covers.
Talk to us
Tell us what your customers currently do when they cannot find you online, and we will tell you what kind of site fixes it — sometimes a smaller one than you expected.
Start a conversation, or look at what else we build.
Custom Software Development
Some problems have no product. The process is specific to how your business works, the software that nearly fits would need to be fought every day, and the spreadsheet that currently holds it together is one person away from disaster. That is when it is worth building something.
When custom is the right answer — and when it is not
We will tell you when to buy instead of build. An off-the-shelf product that covers 80% of what you need, today, for a fraction of the cost, usually wins — and if that is the situation we would rather say so than take the work.
Custom is the right answer when one of these is true:
- The process is your advantage. Whatever makes you faster or cheaper than your competitors is, by definition, not in a package everyone can buy.
- The gap is between systems, not inside one. You have software; what you do not have is the thing that makes two of them agree without someone retyping.
- The manual work scales with the business. Every new branch, customer or product adds hours of someone's week. That cost compounds; the software does not.
- Nothing that fits exists in Bengali, or for Bangladeshi practice. Foreign products assume foreign paperwork, foreign tax forms and foreign banking.
What we build
Internal dashboards that put the numbers a manager actually decides on in one place, instead of four exports. Quotation, costing and order tools shaped around how your business quotes, not how a generic CRM thinks you should. Reporting on top of data you already have but cannot get at. Integrations with the accounting, inventory or messaging systems already running. Android applications where the work happens away from a desk.
Everything is built in .NET and SQL Server — the same stack as Calventory, which is the best evidence we can offer that it holds up: a multi-branch inventory and accounts system with 31 reports, HR and payroll, NBR Mushak 6.3 tax challan, an Android client, and years of production use by businesses that would notice immediately if it stopped being correct.
How we work
We start with the process, not the screens. The first conversation is about how the work is done now, including the parts that are done badly and the parts done outside the system entirely. Software that automates a process nobody has examined is an expensive way to go wrong faster.
We build the smallest thing that is genuinely useful, and put it in front of real users early. A large specification agreed in advance and delivered six months later is how projects fail — not because the specification was wrong, but because the business moved and nobody was allowed to notice. Short cycles let you change your mind while changing it is still cheap.
Your data stays reachable. Standard SQL Server, documented tables, exports that open in Excel. Nothing is stored in a private format whose only purpose is to make leaving difficult — the ability to walk away is what keeps a supplier honest, including us.
We are honest about scope. If a request is expensive, or is going to cause a problem in a year, you will hear so at the time rather than after the invoice.
What it costs to keep patching
The spreadsheet that runs a critical process has a shape everyone recognises: one person understands it, it breaks quietly, and the error is discovered downstream by a customer. The cost is not the licence you are saving. It is the day spent reconciling, the order shipped wrong, and the fact that the business cannot grow past the person holding it together.
The same is true of a system somebody built years ago and no longer supports. Software that nobody will change is not an asset — it is a constraint that gets tighter every year. We take those over too, and often the first useful thing we do is simply document what it actually does.
After it ships
This is the part most quotes leave out, and the part that decides whether the project was worth doing.
Software that is not maintained rots — the operating system moves, the browser changes, a certificate expires, the business changes shape. We keep what we build running, and support comes from the engineers who wrote it. The person who takes your call is the person who can fix it. That is a deliberate constraint on how fast we grow, and it is how we work on everything, not a premium tier.
Talk it through
The first conversation costs nothing and is usually the most useful part of the process — sometimes the outcome is a product recommendation rather than a project.
Tell us what the problem is. Not what software you think you need — what breaks, how often, and what it costs when it does. We will tell you honestly whether it is worth building.
Hosting, Domain & Maintenance
We register or point your domain, install the SSL certificate, host the site or system, and keep it working. It is the least glamorous thing we sell and the one that decides whether everything else was worth buying.
What "maintained" actually means
A website is not a finished object. It is a thing running on a computer, on a network, behind a certificate, in browsers that change every few weeks. Left alone, it does not stay the same — it degrades.
The failures are boringly predictable:
- The certificate expires and every visitor is shown a red security warning. This one is entirely preventable and still happens constantly.
- The domain lapses, because the renewal notice went to an address nobody reads any more. Recovering it ranges from awkward to impossible.
- The platform ages out. The framework it was built on stops receiving security fixes, and one day the site is a liability rather than an asset.
- Something breaks quietly. A form stops sending, an image stops loading on phones, a page starts returning an error to Google. Nobody notices, because nobody is looking — and by definition the people who hit it are the ones who never became customers.
Maintenance is not "we will fix it if you call". It is that someone is responsible before you have to.
What we cover
Domain. Registered by us or pointed from wherever you already own it. Renewals handled — this is the single cheapest disaster to prevent.
SSL. Installed, renewed, and enforced so the site is served over HTTPS, which browsers now require and search engines expect.
Hosting. On infrastructure we run, tuned for the platform rather than generic shared space.
Updates. Framework, security patches and the platform itself. Not optional and not billed as an event.
Accountability. When something breaks there is a person to call, and that person can change the code.
Improvements arrive without you buying them
Every site we host runs on the same platform we build and maintain. Nine live sites today — each with its own content, colours, menus and features, all served by one system.
That means improvement is not a project you commission. When we make the platform better, every site we host gets it, on the same day, at no additional cost and with nothing to authorise.
A recent and specific example. In one week this month the platform gained canonical link tags, an automatic social-sharing image, a per-page title mechanism that had been silently broken for a long time, and a corrected robots.txt. All nine sites received all four the same day. Sites built individually from templates would have needed nine separate pieces of work — and would almost certainly have received none of it, because nobody commissions work to fix a problem they cannot see.
This is the argument for a maintained platform over a site handed over and forgotten, and it is easier to demonstrate than to explain: the page you are reading got those improvements the same way your site would.
What it costs to have nobody responsible
The usual arrangement — a site built once, handed over, and left — has a predictable ending. Two or three years in, the developer is unreachable, nobody knows where the domain is registered, the login has been lost, and the honest advice is to rebuild from scratch.
The money spent on that first site is not partially recovered. It is gone, along with whatever search-engine standing the domain had accumulated.
Continuity is worth more than it looks. A site that has been running, maintained and current for years is treated differently by search engines and by the customer checking whether you are still trading, than one that appeared last month.
Already have a site somebody abandoned?
Common, and fixable more often than people expect. We take over existing sites: work out where the domain and hosting actually are, get control of them back into your name, assess whether what exists is worth keeping, and either maintain it or move it onto our platform.
The first step is usually just finding out what you own, which is a conversation rather than a project.
Talk to us
Tell us what you have — a domain, a site, a system somebody built, or nothing yet — and we will tell you what keeping it running involves.
Get in touch, or see how we build the sites in the first place.