Tender checklist for Kazakhstan
I often support procurement teams and founders when they evaluate vendors. This checklist consistently saves budgets in local tenders.
1. KPIs and timelines
- Fix KPIs: LCP < 2s, conversion target, SLA for bug fixes.
- Confirm the vendor can work with KZT billing, local taxes and official paperwork.
2. Local integrations
- Explicitly mention Kaspi API, 1C, Halyk acquiring, fiscal registers, NCALayer/EDS.
- Ask for a live reference where these integrations already work.
3. Tender-ready scope
- Business goal and measurable metrics.
- Compliance requirements (Kazakh regulations).
- DevOps, environments, release pipeline.
- Payment milestones (30-40-30 or similar).
4. Financial & legal due diligence
- Check BIN/IP status via eGov.
- Demand a transparent change request process.
5. Why hire directly
- No agency overhead (30–50% cheaper).
- Direct communication and faster iterations.
- Single responsible engineer for code + support.
Recommended reading
- Kaspi, 1C and CRM integration case study — middleware architecture and measurable impact.
- Tender technical spec template — structure + budget example for public procurement.
Takeaway
TL;DR: define KPIs, check local integrations and make the vendor financially accountable before signing.
- capture KPIs + SLA in the contract;
- review Kaspi / 1C / payment experience;
- demand a clear change-request process and a single accountable engineer.
➡️ Ready to start? Fill out the brief and I’ll reply with scope and budget within 24 hours.