How to Select a Government Software Development Vendor in Sri Lanka

Price-only selection creates expensive systems

The lowest bid often wins the contract and loses the citizens. Government software fails when vendors underprice complexity, skip change management, or disappear after go-live. Score total cost of ownership across build, training, hosting, and 3–5 years of maintenance.

Capability evidence to demand

Ask for live references in the public sector or regulated industries, sample architecture diagrams, accessibility approach, and a named delivery team — not a generic capability statement.

• Similar system in production (portal, case management, payments, trade)
• Security practices: SDLC, vulnerability management, audit logging
• Localization: Sinhala/Tamil/English UX and content workflows
• Interoperability experience with agency or national systems
• Training and knowledge-transfer plan for officers

Mandatory post-go-live terms

Require warranty conditions, an AMC option with SLAs, source code escrow or full IP assignment, admin documentation, and a hypercare period after launch. Systems without funded support degrade within a year.

Phased delivery reduces risk

Prefer proposals that pilot a high-value citizen or officer journey first, then expand. Big-bang national launches without pilots create political and operational risk.

Evaluation scorecard (example weights)

Technical approach 25%, relevant experience 20%, team 15%, security & compliance 15%, maintainability & AMC 15%, price 10%. Adjust weights to your agency’s risk profile — but never let price dominate.