Global delivery
Based in Nigeria, working remotely — the practical details, answered up front
Amarisen Systems is a halal-aligned digital systems studio operating from Nigeria with a remote-first delivery model. We build customer, booking and operations systems for suitable businesses locally and internationally. This page answers the practical questions an international prospect should ask before booking a meeting.
Remote-first process
Every stage works at a distance — by design, not by compromise
Discovery, collaboration, demonstrations, feedback, implementation and handover are all conducted remotely. This is our normal operating model, not a fallback.
Discovery
Video calls, screen sharing and structured questionnaires map your current workflow. Where calls are impractical, discovery runs fully in writing.
Collaboration
A shared project board, written updates and documented decisions keep everyone aligned without requiring simultaneous availability.
Demonstrations
Live walkthroughs on video calls, plus recorded walkthroughs you can review asynchronously with your team.
Implementation
Staged builds with access to review environments, so progress is visible rather than promised.
Handover
Documentation, access transfer and a working session — the same handover standard whether you are in Lagos or London.
Honest limits
Some activities — physical site assessments for hardware-heavy projects, for example — may need a local partner or cannot be done remotely. We say so during scoping.
Time zones
Our reference time zone is West Africa Time (WAT, UTC+1)
- Meeting times are always agreed in advance and stated in both WAT and your local time
- The UK's offset from WAT changes seasonally (GMT/BST), and US offsets vary by region and daylight saving — so we never publish fixed offsets; every meeting invitation carries both times explicitly
- There is meaningful working-hours overlap with the UK, Europe, the Gulf and West Africa; North American overlap is smaller but workable with asynchronous-first habits
- We do not promise round-the-clock live support; actual collaboration windows are defined only once agreed operationally for your project
Why asynchronous-first
Written updates and documented decisions mean your project does not depend on both parties being awake at the same time. Meetings are used where they materially improve discovery, decisions or review — not to substitute for a paper trail.
Communication expectations
What you get, and what you should expect to give
From us:
- Written project updates — at minimum weekly while work is active
- An agreed project board showing tasks, statuses and owners
- Documented decisions, so agreements survive memory and time zones
- Scheduled meetings where they add real value
- A defined escalation route for urgent project issues, agreed in the scope
From you:
- A single project owner with authority to approve and give feedback
- Responses within agreed windows at review points
- Content, access and business inputs the scope depends on
- Early notice of changing constraints — timing, budget or personnel
Documentation & ownership
What is written down, and who owns what
Documented throughout
The project scope, decisions, deliverables, testing results and handover materials are documented in writing. What was agreed is verifiable afterwards by both sides.
Ownership, stated accurately
- You own: your business data, and the agreed custom deliverables — subject to the signed agreement.
- We retain: our pre-existing reusable tools and components, as stated honestly in the agreement — not hidden in fine print.
- Third parties: software and services remain under their own licences; accounts should be in your name wherever practical, and this is set up during onboarding.
Data handling & security
Principles we actually apply — without certification theatre
- Access control: least-privilege access to project systems and data, reviewed and removed at closure
- Data minimisation: systems collect only what the workflow genuinely needs — scheduling needs a name and a slot, not a medical history
- Secure configuration: secrets kept server-side, credentials exchanged only through secure channels, HTTPS enforced
- Responsible handling: your customer data is treated as a trust (amanah), used only for the agreed project purpose
- Subprocessor transparency: third-party services involved in a project are listed in the scope
An honest statement
Payments & contracts
Confirmed in writing, before work starts
- Commercial terms, payment options, currency and schedule are confirmed in the proposal and agreement
- International quotes default to USD unless another currency suits both sides better
- Payment methods are offered only once verified to work for our account and your intended transaction — we do not advertise options we cannot actually accept
- Third-party service costs, transaction charges, refund and late-payment conditions are stated up front
See the pricing page for how quotations are scoped.
Contracts & jurisdiction
Agreements specify scope, deliverables, ownership, payment, confidentiality, liability limits and dispute handling. For jurisdiction-specific contract requirements, tax treatment or data-protection duties, we recommend — and where necessary require — review by qualified professionals on the relevant side. We do not provide legal or tax advice.
Onboarding
From first message to first delivery
- Fit assessment
- Discovery
- Written scope & proposal
- Agreement & initial payment
- Access & information collection
- Implementation
- Review & testing
- Handover & agreed support
Questions
Questions international prospects ask us
Do you already have international clients?
Will the time difference be a problem?
How do we pay you from abroad?
What language do you work in?
The practical questions are answered — what about yours?
Bring your specific situation to a free fit assessment: your time zone, your tools, your constraints. We will tell you honestly whether remote delivery from Nigeria works for your project.