Questions we get asked before someone signs on.

Most projects are quoted as a fixed price against a written scope, agreed before any work starts — so you know the cost up front rather than watching an hourly clock. Ongoing support and hosting run on a monthly agreement sized to what you actually need. We'll always tell you honestly if a smaller, cheaper option would serve you just as well.

A focused website usually runs four to eight weeks from kickoff to launch. Custom software or systems integration varies more with scope, but we deliver in short, visible cycles throughout — so you're seeing and testing real progress every few weeks, not waiting months for a single reveal at the end.

Yes, fully. Source code, domain registrations, and cloud or hosting accounts are set up in your name from day one — not held in ours. Leaving us should never mean losing access to your own systems.

A support agreement covers security patching, monitoring, a defined response time when something breaks, and a reasonable allowance of small changes and fixes each month. The exact scope and response time are written into the agreement itself, not left as an assumption — ask us for the specifics for your situation.

Access control, encryption in transit and at rest, and audit logging are standard on any system handling sensitive data, not a paid add-on. For NGOs and government clients with specific compliance or donor requirements, we build to those requirements explicitly — see our note on Uganda's Data Protection Act for the general landscape.

Often, yes. A lot of our systems-integration work connects existing tools rather than ripping them out — it's usually the cheaper, lower-risk option, and we'll recommend it over a rebuild whenever it genuinely solves the problem.

Yes — we're based in Kajjansi, Uganda, and build for clients across Africa. Most collaboration happens remotely with video calls and shared documents; in-person visits are arranged for larger engagements where they add real value.

Because scope is agreed in writing before we start and we deliver in short, visible cycles, disagreements about direction usually surface — and get corrected — early, while changes are still cheap. If something genuinely isn't right at delivery, we fix it against the agreed scope as part of the engagement.