Questions
The things people ask before they email.
Answered here so you do not have to book a call to find out whether we will hand over the code, or how long this takes. If your question is not on this list, ask it directly.
How much does a website or app cost in Nigeria?
It depends on scope, and anyone quoting a price before understanding the scope is guessing. What moves the number is how many systems have to talk to each other, whether money or stock has to stay correct across them, and who operates it afterwards. A marketing site and a platform that reconciles orders, inventory and payout are different problems by an order of magnitude. Send us what you are trying to achieve and we will tell you honestly whether it is a small build or a large one.
How long does a project take?
Most projects start with a two-week architecture map at a fixed fee, which produces a written picture of the systems involved before anyone commits to a build estimate. From there the work runs in short cycles with working software in your hands every sprint, so you are never funding months of work you cannot see. The map is deliberately fixed-fee and yours to keep whether or not you go on to build with us.
Who owns the code?
You do, from the first commit. The repository, the pipeline, the credentials and the documentation are all yours throughout, not at the end. No client is ever trapped with us because leaving is expensive, and if the relationship ends tomorrow you can hand the codebase to another team without a fight.
What does API integration actually involve?
Usually the least visible and most expensive part of a project. Getting a happy path to work is the easy half. The half that decides whether the system is still standing in a year is everything around it: the marketplace that changes its API without warning, the webhook that fires twice, the network that drops mid-request, the retry that must not double-charge a customer. We build for those cases, not for the demo.
Do you work with clients outside Nigeria?
Yes. We are based in Lagos, Nigeria and work remotely with clients in other time zones. The practical constraint worth naming early is that we deliberately build for the conditions our own market has, which is mostly metered mobile data on mid-range Android hardware. A site that scores well on a fibre connection in Europe can be unusable on a 3G connection in Lagos, and we treat that gap as a commercial problem rather than a technical one.
What happens after launch?
We operate what we ship until your team is ready to take it, then we hand it over properly: monitoring, runbooks, and an integration layer written to survive a provider changing its API without warning. There is no cliff edge at go-live, and no dependency on us that we have not designed out.
Why is performance treated as a requirement rather than an extra?
Because most of the market we serve is browsing on a mid-range Android over metered data, where a slow site is not an inconvenience but a lost sale. Page weight, Core Web Vitals and first-load behaviour get designed in from the start rather than retrofitted once someone complains. It is also simply better engineering, and it is measurable, so there is no argument to have about it.
Can you work on just one piece, like the API layer?
Yes, and it is often the right way to start. Most clients end up using three of the five capabilities, but the seams between them are where projects usually fail, so it is worth knowing early which seams you actually have. If one piece is genuinely the constraint, start there and let the rest follow from evidence rather than assumption.
How do I start?
Send us what you are building or what you suspect is costing you more than it should. The more specific the detail, the more useful the first response will be. We are at 62A Bayo Osinowo Street, Ogudu, Lagos, you can reach us on hello@resocore.africa or +234 902 710 1991, and we reply within one working day.
Still deciding?
Tell us what is breaking. We would rather answer a hard question now than quote optimistically and renegotiate later.