Software development in Ibadan
Service Category
Need To Build Software?
Software for a named workflow
Custom software is for operators who have outgrown spreadsheets and generic tools. From 27 Adebajo Street, Kongi, Bodija, Ibadan we have shipped an escrow platform and a visitor-management portal. Those are the kinds of briefs we still take: a defined workflow, named users, and a person who will run the system after launch. A website explains the firm. Software runs a process.
Beckfort is the public escrow example. The travel operator’s visitor portal is the public operations example. Comments attached to those jobs sit on the testimonials page. We do not invent uptime graphs to decorate them.
Typical systems
Inventory, bookings, staff portals, client dashboards, vendor registration, and payment-held-in-trust flows. The contact form already lists inventory management software as a discussion topic. If you only need a brochure, use web design. If the job is a store, use ecommerce. If the job is a phone client on top of a clear API, use app development. If the idea is unproven and you need a first release for ten real users, use MVP development.
If the process already moves money or stock, you are asking for software even if the first conversation said “website.” Say so early. A store checkout and an escrow hold are different products. We will not hide one inside the other to make the quote look smaller.
What a software brief must name
The user, the record, and the action. A visitor arrives, a log is written, a gate opens. A buyer pays, funds sit, funds release. A clerk counts stock, a manager sees the gap. If you cannot name those three, you are not ready for a build. You are ready for a workshop, and we will price the workshop. Do not send a deck that lists every competitor’s feature and call it a specification.
Say who will run the system on week two. Software without an owner becomes a WhatsApp group. Say whether kickoff is a room in Bodija or a call. Phone +234 802 092 9620.
What a weekly build is for
You should click something every week: a permission that now works, a record that now saves, a report that now matches the spreadsheet you are replacing. If two weeks pass with only slides, the project is drifting. We will stop and ask why. A demo that only the developer can operate is not a demo.
Write down who can see a record and who can change it before we draw screens. A clerk who can delete the audit log is a bug, not a feature. Those rules belong in the scope, not in a chat thread after launch.
Working method
We write the entities and permissions first. Who can see a record, who can change it, and what happens when money or stock moves. Then screens. Then weekly builds you can click. You do not get a six-month silence. You do get questions when the brief still has two owners who disagree. We ask for one decision-maker.
Hosting and third-party APIs stay in your name where possible so you are not locked to a vendor account you cannot see. After final payment, project IP transfers as described in the services agreement. We can use non-confidential work in the portfolio unless you sign an NDA. If you want an NDA before the brief, say so on the contact form.
Taking over an existing codebase
Sometimes. We review it first. If the stack is unmaintainable we will say so before we quote a rebuild. If the previous vendor still holds the only login, that is a risk we will write into the scope. We will not promise a two-week rescue of a system we have not opened.
Old code we have not opened, logins held by a previous vendor, merchant accounts you cannot open, and data you cannot export all belong in the first email. We will not discover them in week six and pretend they were implied. After launch you should hold the hosting, the repository, and the admin users. That is the point of paying for custom work instead of renting a tool you cannot leave.
Software work we will decline
We will not build a trading platform, a casino, or a system whose only pitch is “disruption” with no named user. We will not take unpaid equity-only work. We will not hide merchant accounts inside a studio login. We will decline a six-month silence sold as a waterfall. We will take a named workflow, a named owner, and weekly builds you can click.
Escrow and visitor logs are the public proof that we mean production, not theatre. If your process is smaller than that, you may only need a website. Say so early. To brief a system, contact the studio and describe the user and the job they must finish.
Frequently asked questions
No. A website explains the firm. Software runs a process: payments in escrow, stock counts, visitor logs, staff access.
Sometimes. We review it first. If the stack is unmaintainable we will say so before we quote a rebuild.
After final payment, project IP transfers as described in the services agreement. We can use non-confidential work in the portfolio unless you sign an NDA.
Yes, when you can name the clerk, the record, and the action. The contact form already lists inventory software as a topic.
