Working with Desishub
How we work
Written scope before any money, a working demo every Friday, and the code in your name at the end
Most people shopping for software in Kampala have been burnt once already — a developer who went quiet, a system that was 90% done for four months, a handover that never came. This page is what we do differently, stated plainly enough that you can hold us to it.
Facts on this page last verified 6 November 2026
- Written scope before you pay
- A working demo every Friday
- You own the code
The four stages
Discover. We sit with the founder or operations lead and walk the work as it happens today — the paper, the spreadsheet, the workaround everybody uses. You get a written scope document out of it, not a Gantt chart.
Design. We pick the stack, model the data, and put real screens in front of you as a clickable prototype before production code starts. The projects that go well are the ones where a client marks that prototype up heavily — every note at that stage is rework that never happens.
Build. Milestone by milestone, with a staging link every Friday. Every change is read by a second engineer before it ships.
Launch and grow. Load tested before it goes live, monitored after, and handed over with documentation. Then the support window, and a retainer or a clean exit.
What “you own everything” means in practice
It means the repository is in your organisation, the database is in your account, and the deployment account is billed to you. We have access because you granted it, and you can revoke it. If Desishub disappeared tomorrow, your system would keep running and any competent engineer could pick it up.
That is the honest answer to the question behind source-code escrow. Escrow exists to protect a client from a vendor who holds the code hostage; we do not hold it, so there is nothing to escrow. If your procurement process asks for an escrow clause anyway, say so and we will work out the wording.
What we are not
We are not the cheapest option in Kampala, and when a project only needs a five-page brochure site we will say so and point you at the smallest thing that solves it rather than the largest thing we could sell. We do not take work we cannot staff, and we do not promise a date we have not scoped. If your timeline needs a team twice our size, we would rather tell you on the first call than discover it in month three.
Ask us for the paperwork
If you are evaluating us against another vendor and need something concrete to compare, ask. We will send a sample scope document, the milestone and payment structure for a project of your size, and the security practices summary from our security page. Reference calls with founders already running our systems are available on request.
Related: pricing, security, performance and design.
Why teams pick us
The six commitments
- 01
A written scope before you pay
We walk your current workflow and write down what the system has to do, broken into milestones and priced in UGX. You approve it before a line of code exists.
- 02
Milestone payments, not hourly
50% on kick-off, milestones through the build, balance on delivery. Priced per milestone in UGX, so the number you approved is the number you pay.
- 03
A demo every Friday
A staging link with that week's work in it — not a status report. It is the simplest guarantee that a build cannot quietly stall for four months.
- 04
Senior review on every change
No code reaches your production system without a second engineer reading it. Dependencies are scanned, and an enterprise launch gets a penetration test first.
- 05
You own all of it
Source code, database, deployment account, documentation — in your accounts at handover. No licensing fee on top, no lock-in, nothing held back as leverage.
- 06
A support window, then a clean exit
3–12 months of bug-fix support depending on tier, then a small retainer or a documented handover to your own team.
FAQ
Frequently asked questions.
01What do I get before I pay anything?
A written scope document. We sit with you or your operations lead, walk the workflow you have today, and write down what the system has to do — screen by screen, with the build broken into milestones and each one priced in UGX. You approve that document before any code is written, and it is what you hold us to.
02How are payments structured?
50% deposit on kick-off, milestone payments through the build, and the balance on delivery. We price per milestone in UGX, never per hour, so the number you approve is the number you pay. MTN Mobile Money, Airtel Money, bank transfer, or cash at the office on Kampala Road.
03How do I know it is actually progressing?
You see working software every Friday. Not a status report or a percentage — a staging link you can click, with that week's work in it. Starter projects run 4–6 weeks, Professional 8–12, Enterprise 12–20. There are no six-month black-box builds here, because a demo you can open every week makes one impossible.
04Who owns the code?
You do, outright. At handover you get the full source code, the database, the deployment account and the documentation, in your own accounts. There is no licensing fee on top and no lock-in. This is also why source-code escrow is moot for our contracts: escrow protects you against a vendor who holds the code, and we do not hold it.
05What happens if something breaks after launch?
Bug-fix support is included and scales with the tier: 3 months on Starter, 6 on Professional, 12 on Enterprise. A defect in what we agreed to build is fixed inside that window at no charge. After it, we move to a small monthly retainer, typically UGX 300K–800K, or hand off cleanly to your internal team.
06What if I want to leave, or hire someone else?
You can, and it is mechanical rather than a negotiation, because you already hold the code, the database and the deploy account. We will write a handover document, walk your new team or your internal developer through the architecture, and transfer anything still in our name. We would rather be the vendor you could leave and did not.
07How quickly do you respond?
An engineer reads your enquiry and replies within 24 hours. A written, milestone-priced quote follows within 48 hours of the scoping call, because it is scoped first rather than guessed.
08Do you work with clients outside Uganda?
Yes. We have delivered work in Uganda, Zambia, the United Kingdom and the United States, invoice in USD where that is easier, and keep the same weekly demo cadence wherever you are. CertusQS, a UK contractor's commercial platform, runs on a system we built and maintain from Kampala.
Ready to grow your business in Uganda?
Desishub Technologies is the partner you need for world-class web design and custom software development.