News

Custom Software or Ready-Made Tools? 7 Questions for Bhutanese Organisations

When an office in Bhutan needs a better way to track requests, manage records or serve customers online, the first choice is often “buy a ready-made tool” or “build custom software.” Both paths can work. The wrong path usually shows up later as unused licences, awkward workarounds, or a system nobody can change when a process changes.

eDruk Private Limited has been building software, websites and mobile apps in Bhutan since 2004, alongside networking and fibre work for organisations across the country. Before you commit budget or a tender, these seven questions help you decide what fits your people and processes.

1. What exact work must the system support?

Write down the daily tasks: who enters data, who approves it, who needs a report, and what happens when something is rejected or delayed. Ready-made tools are strong when your process is close to a common pattern such as invoicing, basic CRM or simple ticketing. Custom software is stronger when your rules are specific to your organisation or a workflow that must match forms and approvals you already use.

2. How much can you adapt your process?

Off-the-shelf products usually expect you to follow their way of working. If your team can adjust a few steps and still meet policy, a standard tool can be faster to launch. If the process is fixed by regulation, audit or long-standing practice, forcing staff into a mismatched product creates shadow spreadsheets and chat workarounds. Be honest about what you can change before you buy.

3. Who will use it, and on which devices?

Desk staff, field teams on phones, and occasional public users need different interfaces. Check whether a ready-made product supports the languages, forms and mobile use you need. If people must work offline, upload photos, or follow a multi-step approval that no standard product covers well, a tailored web or mobile application may be clearer.

4. What must connect to systems you already have?

List email, accounting, SMS, identity logins, payment channels or other portals the new system should talk to. Some ready-made tools offer connectors; others stop at export spreadsheets. Custom development can build the integrations you need, but only if those other systems have clear interfaces and owners. Map the connections early so the choice is not based on a demo alone.

5. Who owns the data, logins and configuration?

Keep domain names, hosting accounts, admin users and export rights in your organisation’s name. For a ready-made SaaS product, confirm how you export data and what happens if you stop the subscription. For custom software, agree where the source code and documentation live, and how another developer could maintain it later. Ownership problems are harder to fix after go-live than during procurement.

6. How will it be supported after the first month?

Ask who resets passwords, fixes bugs, applies updates and trains new staff. Vendor support hours, local partners and in-house skills all matter in Bhutan, especially when a problem appears outside Thimphu. A cheaper licence with no practical support can cost more than a clearer support plan. For custom systems, plan maintenance the same way you would for a network: updates, backups and a named contact.

7. Can you start small and grow?

Many successful projects begin with one process — applications, inventory or service requests — then expand. A ready-made tool that covers that first process well can be enough. A small custom module that matches your real workflow can also be enough. Avoid a large all-in-one build or purchase until the first version is used daily and you know what to improve.

Making the decision

There is no single right answer for every organisation. Ready-made tools suit common needs when you can adapt a little and the vendor can support you. Custom software suits distinctive processes, local integrations and long-term control — when you also plan ownership and maintenance. A short requirements note and a few demos usually make the choice clear.

If you are weighing a ready-made product against a custom web or mobile system, tell us what staff need to do each week. We can help you compare options and plan a practical first version.

Contact eDruk:
Email: edruk@edruk.com.bt
Phone: +975 2 332277
Web: https://www.edruk.com.bt

News

Planning an IoT Project in Bhutan: 7 Questions Before You Connect Devices

More offices, shops and compounds in Bhutan are connecting sensors, controllers and automated equipment — from door and gate motors to parcel lockers, environment monitors and building controls. Internet of Things (IoT) systems can save time and reduce manual checks, but they only work well when the problem, the site and the support plan are clear before any hardware is ordered.

eDruk Private Limited has been building software, networks and automation in Bhutan since 2004, including systems such as automatic sliding gates and doors and the DrukBees Cube automated parcel pickup point. Before you start an IoT project, these seven questions help you plan a system that people will actually use and that someone can keep running.

1. What job should the system do every day?

Write down one or two concrete tasks: open a gate for authorised vehicles, notify staff when a sensor reading is out of range, let customers collect a parcel without waiting at a counter, or log when a room is occupied. Avoid a long wish list at the start. A focused first version that solves a daily problem is better than a complex network of devices that nobody maintains.

2. Where will the devices live, and what is the site like?

Note power availability, weather exposure, dust, distance between buildings, and whether staff or the public will be near moving parts. Outdoor gates, rooftop sensors and roadside cabinets need different housings and protection from indoor office controllers. A short site walk with photos of mounting points and cable routes prevents surprises during installation.

3. How will devices talk to each other and to your network?

Decide whether devices will use wired Ethernet, Wi-Fi, a dedicated radio link, or a mobile data connection. Poor coverage in a basement, a remote compound or a metal-clad store can break an otherwise good design. Plan how the system joins your existing LAN or internet link, and keep management traffic separate from guest Wi-Fi where that matters for security.

4. Who may control it, and how do you revoke access?

Remotes, keypads, cards, phone apps and admin dashboards all create accounts and credentials. Agree who can open, stop or reconfigure the system, and how you remove access when a staff member or contractor leaves. Default passwords left unchanged are one of the most common ways connected equipment is misused.

5. What happens when the power or internet goes down?

Power cuts and short outages are normal in many places. Decide whether a gate should unlock manually, a locker should keep last-known access rules, or sensors should buffer readings until the link returns. Battery backup, a clean shutdown path and a simple manual override often matter more than a flashy feature list.

6. How will you see faults and keep firmware updated?

Connected devices need someone to notice when a sensor stops reporting, a battery is low, or a controller needs a security update. Plan a basic alert path (email, SMS or a dashboard) and agree who owns updates. Unpatched IoT gear on an office network can become an easy entry point for attackers.

7. Who installs, documents and supports it after go-live?

Ask for labelled cables, a simple diagram of devices and logins, and a clear support path when something fails. Keep admin accounts and documentation in the organisation’s name, not only with one installer. Agree how spare parts, warranty and call-outs work before you depend on the system for daily operations.

Talk through your IoT idea with eDruk

Whether you are considering an automatic entrance, a parcel pickup point such as the DrukBees Cube, building sensors, or another connected control system, eDruk can help you turn these answers into a practical design that fits your site and your team.

Email edruk@edruk.com.bt, call +975 2 332277, or visit https://www.edruk.com.bt.

News

Building a Mobile App for Your Bhutanese Business: 7 Questions to Answer First

Many Bhutanese businesses and offices are asking whether a mobile app would help staff in the field, customers on their phones, or both. A good app can make bookings, approvals, stock checks and service requests faster. A poorly planned one becomes expensive to maintain and hard for people to use. Before you choose a platform or start development, these seven questions help you decide what to build.

1. What problem should the app solve first?

Write down one or two concrete jobs the app must make easier: taking field readings, approving leave, checking parcel status, or letting customers book a service. Avoid starting with a long wish list. A focused first version that people actually use is better than a large app that stays half finished.

2. Who will use it, and on which devices?

Staff on Android phones in remote gewogs have different needs from office users on computers, or customers who only open the app occasionally. Note the devices, network quality and language preferences of each group. That drives whether you need offline support, a simple interface, or both a mobile app and a web portal.

3. What data does it need, and where does that data live today?

List the information the app will show or collect, and whether it already sits in spreadsheets, paper forms or another system. Decide early how records will sync, who owns the master copy, and what happens when two people edit the same item. Clear data rules prevent confusion after launch.

4. How will people sign in, and who may see what?

Plan logins, roles and permissions from the start. Staff, managers and customers should not all see the same screens. Agree how accounts are created and removed when someone leaves, and whether one-time codes, passwords or organisation accounts fit your risk level.

5. Web app, native app, or both?

A responsive web app can be enough when users mostly need forms and reports in a browser. A native or cross-platform mobile app is stronger when you need camera access, push notifications, offline use or a place on the home screen. Choose based on the jobs you listed, not on what sounds modern.

6. Who will host, update and support it after go-live?

An app needs hosting, security updates, backups and someone to fix bugs. Agree who owns the domain, store listings, admin accounts and source code in your organisation’s name. Plan a small support path so the system does not depend on one developer’s personal laptop.

7. How will you measure success in the first months?

Define a few simple signs that the app is working: fewer phone calls for status checks, faster approvals, or more completed field reports. Collect early feedback from a small group of users, then improve in short steps instead of waiting for a big redesign.

Talk it through with eDruk

eDruk Private Limited has been building software, web and mobile systems in Bhutan since 2004, alongside networking, fibre and IoT work such as automatic gates and the DrukBees Cube. If you are planning a mobile app or deciding between a website and an app, we can help you turn those seven answers into a clear brief and a practical first version.

Email edruk@edruk.com.bt, call +975 2 332277, or visit https://www.edruk.com.bt.