Buyer Tools
Before you sign a software development agreement.
Before you commit, confirm that your proposal, statement of work and contract clearly define each of the following. Ambiguity here is where disputes, overruns and change requests begin.
The Checklist
Does the paperwork clearly define each of these?
Anywhere the answer is “not really” is where disputes, overruns and change requests tend to begin.
- Scope
- Deliverables
- Exclusions
- Milestones
- Acceptance criteria
- Response / performance requirements
- Security requirements
- Scalability assumptions
- Hosting
- Third-party integrations
- Source-code ownership
- IP rights
- Documentation
- Credentials / access
- Warranties
- Support
- Handover
- Change requests
- Delay / escalation procedure
Pannu Advisory may identify commercial and technical areas for consideration. Legal advice and contract drafting or review should be performed by qualified legal professionals where required.
Not sure your proposal covers all of this?
Send it over. We’ll review it against exactly this checklist and tell you what’s missing before you commit.
Independent Technology Advisory
A signature is expensive to undo. A review isn’t.
An independent read of your proposal and contract terms is the cheapest insurance a software buyer can buy.