Guide · Procurement, legal and IT reviewers · 5 min read
Procurement checklist: what we provide for tenders and due diligence
Institutional buyers have requirements that product customers do not. This checklist states what we can provide, so a procurement officer can confirm fit before anyone writes a proposal. Items marked on request are supplied directly to the requesting organization rather than published.
Company documents
- Legal entity: GeezSoft Technologies, registered in Ethiopia, with a team in Europe and Ethiopia
- Business registration, trade licence and tax identification: on request
- Ownership and management information: on request
- Company profile in a printable format: see the company profile page
Proposal contents
Every written proposal from us contains the items a tender evaluation normally asks for.
- Understanding of the requirement, restated in our words
- Scope, with must / should / could clearly separated
- Solution architecture and how it connects to existing systems
- Milestones, deliverables and acceptance criteria for each
- Team and roles
- Price, payment schedule and what is excluded
- Assumptions and risks, stated plainly
Delivery and quality
- A documented six-step delivery method, from discovery to support
- Weekly written updates and staging demos during delivery
- Requirements documentation and a signed-off scope
- Technical documentation and user training as deliverables
Security, data protection and operations
- Role-based access control and per-action audit logs in every back office
- Encrypted connections and encrypted storage at rest
- A public security page stating what is live, what is designed and what we do not claim
- Data-protection practice aligned with Ethiopia’s Personal Data Protection Proclamation
- Backups and recovery planning, monitoring and alerting
- In-country hosting and data-residency options where required
Ownership, support and continuity
- Client ownership of code, data and infrastructure accounts
- Handover with runbooks, environment documentation and a recorded walkthrough
- Support agreements with response times by severity
- Source-code escrow available on enterprise terms
What we do not claim
We do not hold formal security certifications and we do not publish availability guarantees for environments we do not control. We state this up front so nothing in a proposal has to be withdrawn during due diligence. If your tender requires a certification we do not hold, tell us and we will say whether we can meet the requirement another way.
What we need from you
- Terms of reference or the brief, even if rough; see our guide on how to brief a software project
- Evaluation criteria and the required proposal format
- Submission deadline and expected project timeline
- Data-residency, hosting and security requirements
- Any mandatory documents beyond the ones listed here
Occasional notes from GeezSoft
More notes like this one, by email.
What to ask a vendor, how to brief a project, what we learn operating our own products. Sent when there is something worth sharing, unsubscribe any time.
Prefer chat? Get the notes on Telegram. Message the account and the first note is a welcome.
More guides
Keep reading.
Directors, programme managers and IT leads
How to brief a software project
What to write down before you talk to any vendor, so the first conversation is about your problem rather than their product.
7 min readAnyone evaluating proposals
Questions to ask any software vendor
The questions that separate a partner from a risk, and where to find our own answers.
6 min readPublic institutions, NGOs and large organizations
What a digital transformation programme actually involves
For institutions moving from paper and spreadsheets: where to start, what to sequence, and what to budget for beyond the software.
9 min readStart a conversation
Ready to talk it through?
Send a short brief and an engineer replies within one business day. We are happy to get into detail before anyone talks about price.