Working with us
How does an engagement start?
It starts with a conversation. You describe the workflow you need supported and who uses it; we ask the questions that are missing. From there we write up an approach, a scope and a timeline for you to review before any development begins.
Do you work with organisations outside Nigeria?
Yes. The work is delivered remotely, and the systems we build are web applications reachable from anywhere. Where a project needs on-site time, we agree that up front.
Can you take over a system someone else built?
Often, yes. We start by reviewing the codebase, the data model and how it is deployed, then tell you honestly whether it is better to continue with it or replace it.
Projects & pricing
How much does a project cost?
It depends entirely on scope — the number of workflows, the integrations involved and whether the system replaces something already in use. Send a quote request with as much detail as you have and you will get a written scope and price rather than a guess.
How long does a build take?
That also follows from scope. We break work into stages so you see something usable early rather than waiting for one large delivery at the end, and each stage has its own agreed dates.
Who owns the software you build for us?
Ownership is set out in the written agreement for each engagement. Tell us what you need and we will cover it there explicitly rather than leaving it implied.
Technology & hosting
What do you build with?
Python and Django on the backend, PostgreSQL for data, and server-rendered interfaces with HTML, CSS, JavaScript and Bootstrap. Systems run on Linux servers behind Nginx and Gunicorn. The full list is on our technology page.
Can the system run on our own servers?
Yes. The applications are standard Linux deployments, so they can run on infrastructure we manage or on your own, depending on what your organisation requires.
How is our data protected?
Access is role-based, traffic is served over HTTPS, and configuration secrets are kept out of the codebase. Backups and their restore procedure are part of every deployment we operate.
Support
What happens after the system goes live?
Launch is not the end of the work. We monitor the deployment, apply security updates, restore from backup if anything goes wrong, and build the changes your operations need next. The arrangement is agreed with you rather than assumed.
Do you train our staff?
Yes. A system nobody can use is not delivered. Handover includes walking your team through the workflows they will run day to day.