Compare Excel, existing applications and custom software by workflow, controls and total effort before committing to a build.
Compare the workflow before choosing Excel, an existing product or a custom build.
A wholesaler in Bharatpur receives an order on the phone. Sales enters it in one workbook, stores checks another, and accounts prepares the bill elsewhere. At closing time, the owner asks a simple question: which orders are still waiting for stock?
If answering means joining several files and calling three people, the problem deserves a closer look. It does not automatically mean the business needs custom software.
For Nepal SMEs, the better choice depends on the workflow, controls and cost of maintaining reliable information. Excel, an existing business application and custom software can each have a sensible role.
Choose tools around the work your business needs to complete.
Keep Excel when the work is still straightforward
A spreadsheet can be a practical tool for a small, stable process: a purchasing estimate, a cash forecast or a list maintained by one responsible person. It is flexible, familiar and useful for exploring a calculation before turning it into a formal process.
Review the current workflow before choosing a replacement for the workbook.
Excel is also capable of collaboration. Microsoft’s co-authoring guide describes supported versions and shared storage requirements. “Several people need access” is therefore not, by itself, a reason to commission software.
Before replacing a workbook, try clear ownership, stable item and customer references, controlled input fields, protected formulas, a shared location and a documented backup routine. Check whether the real problem is inconsistent entry or an unclear process.
Be precise about protection. Microsoft distinguishes worksheet protection from security. Preventing accidental formula edits is different from restricting who can access sensitive information.
Trace one order through sales, stores and accounts before deciding what the software must change.
Look for workflow problems rather than a row limit
The useful warning signs are usually operational:
| What happens repeatedly |
What the business may need |
| Staff re-enter the same order in several files |
Shared transaction references and fewer handovers |
| A completed sale still needs approval from a manager |
A recorded approval rule and exception route |
| Stock and accounts disagree about the same delivery |
Linked movements, values and reconciliation |
| Former staff retain copies of customer data |
Managed access and a defined offboarding process |
A workbook with many rows can still work well. A short sheet can be unsuitable if it must enforce several roles, approvals and linked transactions. Count the recurring decisions and failure points before counting features.
A clear process and an existing-product trial come before a custom-build decision.
Compare an existing product before commissioning a build
Custom software is one option, alongside improving Excel or configuring an existing application. An existing product may already handle the ordinary workflow and provide maintained updates. Its tradeoffs can include subscription costs, configuration limits and dependence on the supplier’s roadmap.
Custom development becomes more compelling when a documented, important process cannot be handled adequately by available products. It also gives the business responsibility for requirements, testing, support arrangements and future changes. A bespoke system can reproduce a confusing process just as faithfully as a good one.
Ask vendors to demonstrate one real workflow with anonymised examples: create an order, approve an exception, reserve stock, reverse an error and export the records. A presentation showing dashboards alone does not answer those questions.
Time used by a process is not the same as cash a system will save.
Calculate the work involved without inventing a return
Consider a hypothetical distributor that spends 45 minutes per working day copying order information between files. Assume 26 working days per month and an illustrative staff-cost equivalent of NPR 400 per hour.
| Calculation |
Result |
| 45 minutes × 26 days |
1,170 minutes per month |
| 1,170 ÷ 60 |
19.5 hours per month |
| 19.5 × NPR 400 |
NPR 7,800 of staff-time equivalent |
This is an estimate of time used by the present process, not a promise of cash savings. It is not a W3 quotation, salary benchmark or projected profit. Staff may use recovered time for other work; payroll may remain unchanged. Some checking and exception handling will still be necessary.
Compare that baseline with a pilot. Measure entry time, corrections, unresolved orders and the time needed to reconcile records. Do not add a second “productivity saving” for the same 19.5 hours under another label.
The commercial comparison should include setup or development, migration, subscriptions, hosting where relevant, training, support, backups, exports and future changes. Ask which costs recur and which are one-off. Agree what happens to the data if the arrangement ends.
A bounded pilot gives the team something specific to test and price.
Move one complete workflow before moving everything
Choose a bounded pilot, such as orders for one branch or one product group. Define the start and finish, responsible people and acceptance checks. Clean duplicate customer and item references before importing them.
Use a bounded workflow and representative records for the pilot.
The pilot should handle ordinary work and realistic exceptions. Can a mistaken order be corrected without losing history? Can an authorised person export the records? Can the team restore a backup and explain the totals at the cut-off date?
During transition, name the authoritative system for each record and define how temporary parallel entry ends. Running two independent “final” stock balances indefinitely creates a fresh reconciliation problem.
W3’s software and business-system services are a relevant starting point for discussing an assessment. For planned WorkSphere workflows, CRM, Inventory, Accounting, HRM and Task Management could share references where the process requires them. The specific scope and availability need to be agreed; the software name alone is not an implementation plan.
Release follows demonstrated acceptance checks, not the number of features delivered.