A custom software project moves through six stages: discovery, scope, design, incremental development, testing with security, and launch with ongoing evolution. Each one has defined roles and a deliverable the organization can review.
The six stages
- 1. Discovery: understanding the goals, users, processes and existing systems. Deliverable: needs map.
- 2. Scope: setting priorities and defining a first version. Deliverable: scope and release plan.
- 3. Design: architecture, user experience and prototype. Deliverable: clickable prototype.
- 4. Development: incremental releases with periodic reviews. Deliverable: working versions.
- 5. Testing and security: quality, performance and security testing. Deliverable: test report.
- 6. Launch: deployment, training and support. Deliverable: system in production and evolution plan.
What gets defined in the first few days
The first few days of a project shape what follows. One practice we use at Xcapit is to separate each core capability into its own module, with defined contracts for what goes in and what comes out, and to start connections with existing systems in read-only mode. That foundation makes it possible to move forward in releases and add integrations one at a time.
Who is involved
- Product: translates goals into priorities.
- Design: looks after the user experience.
- Development: builds the system.
- Quality and security: review each release.
- Project management: coordinates timelines, communication and decisions.
What the organization contributes
- A point person with decision-making authority.
- Access to users and to current processes.
- Review of each release and timely feedback.
- Clarity on the metrics that will define success.
How progress is measured
Each release includes usable features and is reviewed against metrics agreed on at the start: usage, quality, security and business value. Each project's timelines are agreed on according to its scope.
Frequently asked questions
How long does a custom software project take?
It depends on the scope. It is estimated at the end of discovery.
Can you start with a first version?
Yes. It is a common practice, and features are added later.
Who owns the code?
It is defined by contract at the start.
If you have an idea in motion, let's talk about your project and map out your project's path together, from day one.
Fernando Boiero
CTO & Co-Founder
Over 20 years in the tech industry. Founder and director of Blockchain Lab, university professor, and certified PMP. Expert and thought leader in cybersecurity, blockchain, and artificial intelligence.
Need custom software that scales?
From MVPs to enterprise platforms — built right.
You Might Also Like
The Custom Software Development Process: A Step-by-Step Guide
A comprehensive guide to the custom software development lifecycle — from discovery and requirements gathering through architecture, development, testing, deployment, and ongoing support.
Software Factory: Five Questions for Choosing a Development Partner
What a software factory is and five questions for choosing the right development partner: comparable cases, team, security, communication and certifications.
Custom Software Development: From Idea to Production in Four Steps
How a custom system gets built: design, decide with data, build and earn trust, with examples in energy, credit and cash assistance.