A registered studio in Kaduna, building and teaching in the same week
Caxton Software Dev Hub exists because two problems in Nigerian software share one cause: businesses cannot find teams they can trust, and engineers cannot find training that ends in a job. Both are solved by people who actually ship.
- Registered name
- CAXTON SOFTWARE DEV HUB
- Nature of business
- Software Development / Web Designing
- Principal place of business
- No. 56, Issac A.A Street, Ungwan Zango, Maraban Rido, Kaduna, Kaduna State, Nigeria
Two businesses that make each other better
On one side, we are a software studio. Businesses come to us with something they need built — a dispatch system, a members’ portal, a marketing site that loads on a two-bar connection — and we scope it, price it, build it, and hand it over with the keys.
On the other, we are a training hub. Engineers come to us with half-finished tutorials and no idea what a code review feels like, and leave with deployed projects, a reviewed portfolio, and a mentor who will vouch for them by name.
These are not separate ventures that happen to share an office. The client work keeps the curriculum honest, and the training gives our client work a bench of engineers we have watched grow up. When we hire, we hire from our own cohorts first.
We are registered with the Corporate Affairs Commission as a business name under the Companies and Allied Matters Act 2020, operating from Kaduna, Kaduna State. That registration is on the certificate, the number is public, and we would rather you checked it than took our word.
What we are trying to do
Make “we hired a Nigerian software team” a sentence people say with confidence — by being one of the teams that earns it, and by training the next hundred.
How you can check us
Our registration number, our address, and our public code are all verifiable in a few minutes. We have written the steps out.
Verify usFour positions we will not trade away
- 01
A deposit is a matter of trust, not a transaction
Too many Nigerian businesses have paid a developer and received silence. We structure every engagement so you can see progress weekly and walk away with everything you paid for at any point.
- 02
Teaching and building belong together
Our instructors take client work in the same weeks they teach. That is deliberate: a curriculum written by someone who has not shipped recently goes stale within a year.
- 03
Tools should not become dependencies
We use AI heavily and teach it directly. We also refuse to let a model write a learner's assignment, because the shortcut costs them the interview later.
- 04
Local context is not a limitation
We build for the network conditions, the payment rails, and the devices our users actually have. A site that only performs well on fibre has not been finished.
The same four stages, every single project
- 01Week 0
Discovery
We sit with the people who will use the thing. You get a written scope, a fixed price, and an honest note on anything we think is a bad idea.
- 02Weeks 1 – 2
Design
Interface design and technical architecture, in parallel. You approve screens and data model before anyone writes production code.
- 03Weeks 3 – n
Build
Two-week sprints with a working demo every Friday. Repository access from day one, so you can watch it being built.
- 04Final week
Handover
Deployment, documentation, and a training session for your team. Then 30 days of free bug fixes while you settle in.