Commissioning software, a website or a mobile app differs from buying a ready product: you describe and build together something that does not yet exist. So the quality of the result depends not only on the developer's skill but on how clearly you explain the need, how you manage the process and how quickly you decide. This guide covers the perspective and steps you need as the client.
1. Needs analysis: define the problem first
Many projects start with a "we want these features" list. Instead, write down first:
- The problem to solve: Which job is slow, error-prone or impossible?
- Users: Who will use it (staff, customers, managers)?
- Success measures: How will you know what changed when the project ends? For example, order processing time should halve or form conversion should rise.
- Current process and systems: What must it connect to?
- Constraints: Budget, timeline, regulation, security requirements.
If skipped, scope swells with "let's add this too" requests as the project proceeds, and time and cost grow. For the ready-made versus custom decision, custom software or off-the-shelf? and, for web projects, WordPress or custom development? help.
2. Clarify scope: must-have and nice-to-have
Split features into three groups:
- Must have: Without these the product is useless.
- Should have: Important but can wait past the first release.
- Nice to have: If time and budget remain.
Targeting only the first group in the first release (MVP, minimum viable product) allows quick go-live and real user feedback. Splitting a large project into stages reduces risk compared with trying to receive it all at once.
3. Budget and comparing quotes
When getting quotes from different firms, do not look only at the total price. Compare:
- Scope and assumptions: Which features are included and which not?
- Delivery method: Fixed price or time-based (time and materials)? Both have advantages and risks.
- Stages and payment plan: Are payments tied to concrete deliverables?
- Team and experience: Similar projects, references.
- Source code and intellectual property: Who owns it? Will it be handed over?
- Testing, training and documentation: Included in the quote?
- Maintenance and support: For how long and with what scope after go-live?
- Ownership of infrastructure such as servers and domain.
For budget planning see how to plan a software budget and, for website-focused projects, website cost.
4. Working method: the agile approach
In projects where requirements are not fully known at the start, an agile approach fits better: work is split into short cycles (sprints), a working piece is shown at the end of each and feedback is taken. What is expected from you as the client:
- Appoint a project owner: One reachable person with decision authority.
- Hold regular meetings: Short weekly progress and demo meetings.
- Give quick feedback: Waiting slips the schedule.
- Prioritise: When a new request comes, decide what it replaces.
- Involve users: Real users should take part in demos.
For small, well-defined, fixed-scope jobs (such as a simple brochure site) a more classic staged method may be enough.
5. Design and prototype
Agreeing on screen sketches and flows (wireframes, prototypes) before code is written prevents expensive changes later. Showing users a clickable prototype is far more effective than reading documents. Brand identity, accessibility and mobile fit are settled at this stage.
6. Think security and data protection from the start
Security is not a feature added afterwards. Discuss at the start:
- Authentication, MFA and authorisation roles,
- Data encryption and backup; see backup strategy,
- Processing of personal data and KVKK requirements,
- Penetration testing and security review; see penetration testing and cyber security basics,
- Security of third-party integrations; see API integration.
7. Testing and acceptance
Enough testing before delivery is a must:
- Developer tests: Unit and integration tests (by the team).
- User acceptance testing (UAT): You and real users trying scenarios. Write acceptance criteria down from the start.
- Performance and speed: Especially for web projects; see speeding up your website.
- Device and browser compatibility.
- Data migration verification: Accuracy of data from the old system; see moving from Excel to business software.
8. Go-live
Go-live is a planned event:
- Choose low-traffic hours for cut-over.
- Have a rollback plan ready.
- Take backups; keep monitoring and alerting on.
- Announce to users and give short training.
- Plan intensive support for the first days.
For large systems, a staged cut-over (one unit first, then all) reduces risk; the cut-over lessons in why ERP projects fail apply to software projects too. For sites with SEO, address changes and redirects are covered by critical steps in the new website checklist.
9. Maintenance and continuous improvement
Software does not end at go-live: security patches, dependency updates, bug fixes and new needs continue. Agree a maintenance and support contract (response times, scope, monthly hours); see website maintenance and managed IT support. For modernising old systems, modernising legacy systems helps.
10. Common mistakes
- Jumping to a solution without defining the problem,
- Vague scope and no change management,
- Choosing by lowest price,
- Not clarifying source code, accounts and domain ownership,
- The decision-maker staying out of the process and slow feedback,
- Skipping testing and training,
- Leaving security to the end,
- Going live without a maintenance and support plan.
Checklist
- Problem and success measures written,
- Scope (must/should/nice) defined,
- Quotes compared by scope,
- Project owner appointed,
- Prototype approved,
- Security and KVKK requirements identified,
- Acceptance criteria written,
- Go-live and rollback plan ready,
- Maintenance contract signed.
Conclusion
A well-managed software project is the product of a clear problem definition, realistic scope, regular communication and disciplined delivery. Your being active and decisive as the client directly affects the quality of the result. For a wider transformation plan, see the digital transformation roadmap.
ujans offers transparent, staged, security-focused project management from needs analysis and design through development, go-live and maintenance.