Answers to the questions everyone asks.

Discovery usually begins within five working days of your first call. Small builds can start within two weeks; larger programmes depend on how quickly we can access your stakeholders and existing systems. We will give you a real start date in the proposal, not an optimistic one.

Yes. We are based in Owerri, Imo State, and deliver remotely across Africa, Europe and North America. Where on-site presence is needed we schedule it into the plan and price it transparently.

Vida ICT staff and vetted specialists we have worked with before. You are introduced to the people delivering your project at kick-off, and the same lead stays accountable through handover — we do not rotate teams mid-build.

We work alongside them. Many clients keep their internal team for day-to-day operations and use us for projects, specialist skills and overflow capacity. We document everything so your team can take over whenever they choose.

Fixed price for well-defined scope, time-and-materials for discovery and evolving work, and monthly retainers for managed IT and support. Every quote is itemised by milestone so you can see what each payment buys.

It depends entirely on scope. Rather than publish a misleading range, we will give you a budget band after the discovery call, and a firm price after the diagnostic. There is no charge for either.

Yes — that is the Vida Impact Tier. Qualifying registered NGOs, faith-based organisations and public institutions can access subsidised rates and pro-bono technology grants. We reserve fixed annual capacity for this work. Apply and we will tell you honestly whether you qualify.

You do, on final payment. We hand over source code, credentials, documentation and deployment access. We retain the right to describe the work in our portfolio unless you ask us not to.

Weekly demos of working software, a shared project board you can see at any time, and a single named point of contact. If something is slipping you hear it from us first, with the recovery plan attached.

A defined support period is included in every build, then you can move to a managed support SLA with agreed response times, monitoring, patching and backups — or hand everything to your internal team with our documentation.

Frequently. We start with a technical audit to establish what is actually there, what is safe to keep and what needs rebuilding. You get a written assessment before we quote for any remediation work.

Access is role-based and logged, data is encrypted in transit and at rest, and we work to recognised security practice. We can sign an NDA before discovery and support your own compliance obligations where they apply.

Yes — on-site, virtual, or a blend. On-site works best for teams that need to train on your own systems; virtual suits distributed staff. We bring the curriculum either way.

That is the default, not an upgrade. We run a training needs analysis first and write the syllabus around the software and workflows your team actually uses.

Learners receive a Vida Academy certificate of completion and an assessment report. For vendor certifications we run dedicated exam-prep tracks and register candidates with the awarding body.

Corporate programmes typically run from five learners upward. Individual enrolment is available on our public bootcamp cohorts — contact us for the next intake date.

No — that is exactly the right time. Our discovery sprint is designed to test whether the idea holds up before you commit build budget. Sometimes the honest answer is "not yet", and we will tell you.

A tightly scoped MVP typically ships in eight to twelve weeks. Anything promised much faster usually means scope has been cut somewhere you will pay for later.

We can prepare the technical due-diligence pack, architecture documentation and the technical section of your deck, and make introductions within our investor and grant network. We do not guarantee funding and we do not take equity as a condition of working together.

We plan for it. Handover is a supported, documented stage — code walkthroughs, runbooks, a transition period of paired working, then we step back. Several of our clients run their own teams today on systems we built.