You run the business. We handle the tech.
Dgntec is your technology partner. You bring the problem — a process that runs on paper, software that has stopped keeping up, a report nobody trusts. We work out what should be built, build it, and keep it working. You never have to learn how any of it works.
Reaches a person, not a queue: +880 1614 023305
- Where we are
- Dhaka, Bangladesh
- Who we work for
- Business owners, and the people who run them
- What you get
- A problem solved, and someone who keeps it solved
- What you never have to do
- Learn it, run it, or fix it yourself
Who we help
The work is not the same at every size of company. Pick the one that sounds like you.
Small and growing companies
Something in your business takes longer than it should. Orders, stock, invoices or customer records get written down twice, in two places, and the two copies slowly stop agreeing. You don’t need to know what to build. You need it fixed.
How we work on it
We are the technical side, so you don’t have to be. If something can be fixed, we fix it. If a spreadsheet is still the right answer, we say that instead of selling you a system. You never have to learn any of it, and you never have to manage us.
What you end up with
- You know what it costs and how long it takes before we start
- Software your team can try while it is still being built
- One person to call afterwards, and someone who is still there
Larger organisations
The problem is usually not the software. It has to work with the systems you already run, pass whatever checks your board or your regulator ask for, and still make sense to whoever takes it over.
How we work on it
You get the reasoning in writing before we build, not after. What it has to connect to, what happens when it fails, how your data moves across — written down in plain language, in a document you can hand to your own team or your board. Nothing gets decided in a meeting you were not in.
What you end up with
- You know what it costs and how long it takes before we start
- A safe path for the data and systems you already have
- Your own team able to run it without us
- You are in the room for the decisions
What we fix
The problems we are asked about most often. Open any one to see what the work involves, and what you are left holding at the end.
Replacing spreadsheets and paper with one system
Your business has outgrown the way it runs. Orders, stock, jobs or customers live in files only one or two people really understand, and everything takes longer than it should. We build the system that replaces them — one place that holds the truth, that your staff can use without training for a month.
What we do about it
- We watch how the work actually runs today, including the shortcuts
- We agree what changes and what stays exactly as it is
- We build it in small pieces, so you are never left without a way to work
- You see and use each piece before we start the next
What you are left with
- One system that holds the real numbers, not a copy of them in every department
- Something your staff can be shown in an afternoon
- A written record of how it works, so it does not depend on us
An app your customers or staff use on a phone
Some of what you do belongs in your customer’s pocket: ordering, booking, paying, checking a delivery, filing a complaint. We build that app for iPhone and Android, get it accepted into the app stores, and keep it working after release.
What we do about it
- Deciding what belongs in the app and what does not
- Designing it for a cheap phone on a slow connection, not a new one on wifi
- Getting it through Apple and Google review, which is rarely quick
- Working out how new versions reach people who never update anything
What you are left with
- The app live in the stores your customers use
- A way to release updates without asking us each time
- A report you can read yourself when something breaks
A software product you sell to other businesses
If you are selling software rather than using it, this is the work of getting from an idea to something people pay for. Sign-up, subscription billing, accounts, and the ability to hold many separate customers without their data ever mixing.
What we do about it
- Cutting the idea down to the smallest version worth paying for
- Building sign-up, subscriptions and billing properly the first time
- Making sure one customer can never see another customer’s data
- Launching to real users before the whole plan is built
What you are left with
- A product people can pay for, not a demo
- Billing and refunds that do not need you in the loop
- A foundation that can take more customers without being rebuilt
Systems that stay up, and bills that do not surprise you
If nobody knows what happens when the server fails, what the monthly bill is paying for, or whether last night’s backup actually works, that is the problem. We put your system somewhere reliable, set up the backups and the alerts, and bring the cost down to something predictable.
What we do about it
- Finding out what you are actually paying for each month
- Moving it somewhere it can be restarted, restored and moved again
- Setting up backups, and testing that they restore
- Making sure someone is told when it breaks, before your customers tell you
What you are left with
- A system that recovers from a failure, tested rather than assumed
- One bill you can read without a translator
- Alerts that reach a person who can act on them
Reports that match reality
When two people bring the same report and the numbers disagree, the problem is upstream of the report. We collect the numbers your business already produces, put them in one place, and make sure the figure you see is the figure that is true.
What we do about it
- Finding every place a number is currently entered or kept
- Working out which version is correct when they disagree
- Collecting it automatically, so nobody has to type it again
- Building the few reports you will actually look at
What you are left with
- One set of numbers, agreed once, instead of a monthly argument
- Reports that produce themselves on a schedule
- A clear record of where each number comes from
Replacing old software without stopping the business
The system you have run for years still works, but only one person understands it, it cannot be updated, and it is starting to be a risk. We replace it in stages — both systems running side by side — so the business never has to stop while it happens.
What we do about it
- Reading what you have, including the parts nobody documented
- Moving one piece at a time, with the old system still running until you say stop
- Checking every moved record against the original
- Keeping a way back to the old system until you are sure
What you are left with
- Your data moved across and checked, not copied and hoped for
- Both systems running side by side for as long as you want
- The old one switched off on a date you choose
How it works
What happens between your first message and the first line of code. No timeframes are quoted here, because none have been agreed with you yet.
-
01 You send a message
Tell us what isn’t working. A paragraph is enough: what the process is, who it affects, and what you would like to stop doing by hand. A diagram helps, but it isn’t required.
-
02 We talk it through
A conversation about the process, the people, the systems it touches, and what “done” means. Expect more questions than answers at this stage.
-
03 You get it in writing
What changes, what stays as it is, what it costs and how long it takes — written down before any build starts, so the disagreements happen early and cheaply instead of in month four.
-
04 We build in increments
You see working software regularly rather than one reveal at the end. When something needs to change, it gets discussed as it comes up instead of being absorbed silently and appearing on an invoice later.
-
05 We hand it over
You get the logins, the accounts, a written record of how the system works, and a walkthrough for whoever will run it. Nothing you depend on is left inside our heads or our accounts.
-
06 What happens next is agreed
We stay involved. Post-launch work is agreed case by case rather than sold up front, because a system that has real users tells you what it needs — and we would rather keep it running than hand it over and find out later that it wasn’t.
Why Dgntec
Our software runs in production, used by thousands of users every day. That changes what we pay attention to. Here is what it means for you.
-
You get the answer you need, not the one you wanted
If your idea is going to cost more than it is worth, or a spreadsheet would still do the job, we say so before you have spent anything. Turning down work we should not be doing is cheaper for both of us than discovering it halfway through.
-
We fit your business, not the other way round
We start with what you already have — your staff, your suppliers, the systems you cannot switch off — and build around them. Nothing gets replaced simply because it is old.
-
We stay after launch
The person who built your system is the person you call about it. Most of what makes software fail happens months after go-live, when the original builder has disappeared — so we do not disappear.
-
No jargon
You should be able to explain what we built to your own team, or your bank, without us in the room — and without needing a translator. If you have to ask what a word means, we have used the wrong one.
What customers ask before they start
The questions that come up every time, answered without the sales language.
How does a project start, and do I pay to find out?
With a conversation about the problem, not a proposal. If nothing comes of it, you have spent nothing. From there we write down what we think the work is — what changes, what stays as it is, what it costs and how long it takes — and you decide whether that is what you meant before anything is built.
You’re in Bangladesh. How does the distance actually work?
We are six hours ahead of London and eleven ahead of New York, so your morning is our afternoon — the overlap is real. Written updates carry the detail; calls get booked for when both sides are awake. Nobody has to stay up late.
If we stop working together, what do I lose?
Nothing you have paid for. What you own, what you can take with you and what we keep is set out in the agreement before any work starts, and you read it before you sign it rather than taking our word for it here. If you want to move the system to someone else later, nothing in it should stop you.
Where does my data live, and who can see it?
Your data stays yours. Where it is held, who can reach it, how it is backed up and what happens to it when the work ends are agreed before anything is built, and you can pass that to your own advisers. If you work under rules about where data may be stored, tell us at the start and we will tell you straight away if we cannot meet them.
What happens after launch?
You get the logins, a written record of how it works, and a walkthrough for whoever will run it. Nothing you depend on is left inside our heads or our accounts — if you ever handed the whole thing to somebody else, there is enough there for them to pick it up.
Will you sign an NDA?
Yes. Send yours with your first message, or ask us for one. We sign before you share anything sensitive — you should not have to decide whether to trust us with the whole problem before we have even spoken. If you are not sure whether you need one, say so, and we will tell you plainly.
Do you look after it once it is live?
Yes. We do not hand it over and disappear. Most systems need adjusting once real users and real data reach them, and leaving that to somebody who has never seen the system is how software goes rusty. You get one person to call who knows your setup, rather than a queue — and whatever you need is agreed as it comes up, so you are not buying support you will never use.
Do I deal with one person or a different one every time?
One. There is no account manager between you and the people doing the work, and no handover to a different team halfway through. If something is going wrong, you tell one person and it is dealt with.
Start with a message
WhatsApp or email, whichever you actually use. Both reach a person, and the first reply is written by one — not by a bot, and not by a queue.
What to put in your first message
- What isn’t working, in your own words
- Who it affects, and what they do about it today
- The tools and the people it has to work with
- When you need it, if there is a date
- A rough budget, if you have one — it makes the first reply more useful
Dgntec works from Dhaka —