Technical specification template for Kazakhstan tenders

1. Regulations

• Reference local laws: the Law on Public Procurement, MIIR orders.
• For quasi-state companies (Samruk-Kazyna, Baiterek) include internal regulations.

2. Mandatory sections

1. Business goals & KPIs (conversion growth, automation share).
2. Functional scope — user stories, tables, acceptance criteria.
3. Integrations — Kaspi, 1C, EDS, local payment providers.
4. Security — backups, access matrix, audit trail.
5. DevOps — environments, CI/CD, code standards.
6. Support — warranty 6–12 months, reaction SLA.

3. Budget example (KZT)

| Phase | Timeline | Cost | | --- | --- | --- | | Discovery & spec | 2 weeks | 3,080,000 ₸ | | Development | 6 weeks | 9,100,000 ₸ | | Integrations (Kaspi/1C) | 2 weeks | 1,960,000 ₸ | | QA & launch | 1 week | 1,190,000 ₸ | | Total | 11 weeks | 15,330,000 ₸ |

4. Submission checklist

• BIN certificate, licenses, case studies.
• Project schedule + resource plan.
• Letters of recommendation / references.
• Warranty letter for timeline compliance.

5. Attachments

• Prototype or wireframes.
• ER diagrams, API contracts.
• RACI matrix.

Read next

• Tender checklist for Kazakhstan — 16 vendor selection criteria.
• Kaspi, 1C and CRM integration case — real automation results.

Takeaway

TL;DR: a winning spec links business KPIs, integrations and proof documents.

• lead with metrics (conversion, automation, SLA);
• detail integrations (Kaspi, 1C, payments, EDS) and DevOps expectations;
• attach prototypes, RACI and warranty letters to build trust.

Use this template, customize it and the tender committee will have fewer questions.

---

➡️ Want help with the tender package? Fill out the brief and I’ll send a tailored scope + budget within 24 hours.