How we work
We are a founder-led, remote-first studio in Nigeria. Our process is built around asynchronous-first communication, written documentation and staged delivery — designed to work reliably for Nigerian and international clients alike, without pretending to be a large agency.
The sequence
Stage by stage
A short call or questionnaire covering your problem, tools, expectations, timing and budget range. We confirm the project is a genuine match for our capabilities and our Halal-aligned standard. If it is not, we say so clearly — and where possible point you in a better direction.
Output: an honest go / no-go, on both sides.
We map how enquiries, bookings or orders actually move through your business today: the channels, the tools, the people, the hand-offs, and the points where information is lost, duplicated or delayed.
Output: a current-state workflow map.
A written scope covering the business problem, agreed outcome, deliverables, exclusions, your responsibilities, dependencies, timeline, review stages, revision limits, acceptance process, payment milestones, third-party costs and handover conditions.
Output: proposal + scope of work you can hold us to.
Terms are agreed and signed; the deposit or first milestone payment is made per the proposal. Work starts only when both are in place — this protects both sides.
Output: signed agreement, confirmed start date.
Implementation proceeds in agreed stages with written progress updates. You review work as it develops, not only at the end — surprises are expensive for everyone.
Output: working increments + weekly written updates.
We test against realistic scenarios: valid and invalid inputs, failure states, mobile behaviour, and the specific workflows in scope. Defects found are recorded and resolved before handover.
Output: testing checklist with recorded results.
You review the system against the agreed scope and confirm acceptance, or request changes within the agreed revision limits. Acceptance criteria were defined in the scope — not invented at the end.
Output: documented acceptance.
Documentation, access transfer and a working session for your team. You own your business data and the agreed custom deliverables, subject to the signed agreement and third-party licences; our pre-existing reusable components remain ours, as stated honestly in the agreement.
Output: handover checklist completed, documentation delivered.
Suitable clients can continue with a Monthly Operations Partnership: maintenance, monitoring, optimisation and agreed improvements, with defined response expectations, inclusions, exclusions and a change-request process.
Output: a support arrangement you can plan around.
Communication standards
Your responsibilities
Why this matters
Tools
We prefer free or affordable tools that match our capacity — and we record the selected toolset in each project's documentation. Typical categories: video calls and screen sharing, a shared project board, document storage and written updates, code collaboration with full history, design review, invoicing, and secure credential sharing. Specific tools are confirmed with you during onboarding so nothing depends on an account you cannot access.
Documentation & ownership
Scope, decisions, deliverables and handover are documented in writing. See Global Delivery for what you own.
Changes after handover
New work goes through a change-request process with scope, cost and timing agreed before implementation.
Project closure
At closure, access is reviewed and removed where agreed, and a closure checklist confirms what was delivered and what remains yours.
Questions
The first stage costs nothing and commits you to nothing: a short, honest conversation about your problem and whether we are the right studio to solve it.
