We don't do hard sells and we don't disappear after the contract. This is how we actually work: we listen first, build carefully, train properly, and stay for the long run. Here's what that looks like in practice.
We spend time understanding how Dzombo actually works — the team, the clients, the data, the bottlenecks. Not a generic questionnaire. We talk to Japsie, talk to the guides, look at how you operate today. We figure out where AI would actually help versus where it would just add noise.
Based on what we learn, we design your AI setup — which services make sense to start with, which tier, what infrastructure is needed. For Dzombo, we expect to focus on: website updates, booking coordination, client records and hunt logs, permit tracking, and proposal drafting. We present a clear plan: what we'd build, what it would cost, what it would take from your team, and what you'd see change. No surprises. No hidden phases.
We procure the GPU cluster, set up the server in Windhoek, configure the AI models, and connect to your existing systems. Most of this happens remotely. We deploy to Windhoek for the critical setup phase. Staff training starts in Week 5 — while final configuration wraps up. You're not waiting months to see anything work.
We don't hand over a password and leave. We run hands-on training sessions with everyone who'll use the system — guides, admin, management. Everyone gets comfortable before go-live. We create reference materials your team will actually keep, not a PDF nobody reads.
Soft launch with a small team, then full rollout. Year 1 has two goals: make your clients happier (faster responses, smoother bookings, better communication) and make your team's work easier (less admin, fewer copy-paste errors, permits tracked automatically). From there, it's an ongoing partnership: monthly check-ins, quarterly reviews, responsive support. We track what's working, report honestly on what isn't, and keep improving the system over time.
Not marketing language. These are the operating principles we hold ourselves to in every engagement.
The GPU cluster is yours. When this partnership ends — for any reason — you keep the hardware and everything running on it. We won't hold your infrastructure hostage.
Every AI decision is explainable. You understand what the system is doing and why. We build trust through transparency, not mystery.
We recommend starting with one service — AI Chat Essential, usually — proving the value, then expanding. No forced bundling. No requirement to buy everything at once.
You have a direct line to the team that built your system. When something breaks, you call us. When something could work better, you tell us. We actually answer.
N$0.86/kWh electricity. 0% SACU import duty on GPUs. Windhoek fiber + LTE backup. ISP realities. Local tech vendors. We've built the infrastructure plan for exactly this context — not for a textbook scenario.
Most engagements follow this timeline — from first conversation to a system your team actually uses:
Enterprise Solutions follow a longer timeline (8–16 weeks for full implementation).
But you see early value within the first 4 weeks — a working system, not just a proposal.
Let's start with a real conversation. Tell us about your operation, what you'd want to see work differently, and whether this looks like the right kind of partnership. No commitment required.