Company capability statement
Two pages: what eLON does, the five capability lines, how engagements are structured and how to verify our registration and licences.
Resources & Datasheets
The documents procurement actually asks for.
Technical datasheets, a capability statement, a vendor-neutral requirements template and a data-protection position paper. Written for the internal reader who has to defend the decision, with assumptions and exclusions stated.
How these are written
- Assumptions statedEvery document says what it assumes about your environment, so you can see where it would change.
- No unsupported claimsNo availability figure, project value or client name appears without a verifiable source.
- Version controlledEach document carries a reference and a review date, so nobody circulates a superseded datasheet.
Download centre
Documents you can circulate internally
Written for the internal reader who has to justify the decision: assumptions stated, exclusions stated, and no figure that we are not prepared to stand behind in a contract.
eKYC platform datasheet
The onboarding flow, integration options, biometric modalities supported, hosting choices and the auditability model explained for a technical evaluator.
VISP service catalogue
Every service available over the VISP licence, with the design considerations, typical use cases and the information we need from you to quote.
Biometric architecture note
Modality comparison, template versus image storage, liveness and spoof detection, deployment shapes and the privacy design rules we apply.
Infrastructure delivery method
The five-stage method for fibre, microwave and site works, the documents produced at each stage, and how risk and permitting are tracked.
AI & data capability note
Ethiopic script handling, naming conventions, language coverage, on-premises deployment and how accuracy is measured and re-measured.
Data protection position paper
Where data resides, who can access it, sub-processor disclosure, retention and deletion evidence, and incident notification obligations.
Vendor-neutral requirements template
A ToR annex covering identity, biometrics, connectivity and data protection. Use it to write a requirement, or to benchmark the bids you receive. Free to use regardless of supplier.
How to get a document. Use “Request a copy” and we will send the current version, so that nobody circulates a superseded datasheet.
For procurement and legal
The paperwork questions that decide a bid
What we can provide on request
- Company registration and licence documentation — trade licence, TIN and the service licences relevant to the scope.
- Tax and compliance certificates in the form your tender requires.
- Signed capability statement on company letterhead for inclusion in a submission.
- Data protection position paper describing where data resides, who can access it, and how deletion is evidenced.
- Sub-processor list naming any third party involved in delivery, with the scope each covers.
- Insurance and bonding documentation where a tender requires it.
What we will not claim
We do not describe ourselves as endorsed or designated by any government body, we do not publish service levels that are not also in a contract, and we do not cite client names or project values without written permission. If a bid document requires a claim of that kind, we would rather discuss the underlying requirement than sign something we cannot support.
Next step
Bring us the problem, not a specification.
The most useful first conversation is a technical one: what has to work, by when, and what has already been tried. We will tell you plainly whether it is something we should be doing.
Technical first responseA qualified engineer reviews your requirement before anyone calls you.
Written scopeYou receive a documented approach, assumptions and exclusions you can circulate internally.
Local channelsReach us on phone, WhatsApp, Telegram or email — whichever your team already uses.
One point of accountabilityOne contract and one escalation path across connectivity, identity and AI.