Why does requirements analysis matter so much?
Fixing a mistake during the analysis stage is as easy as changing a sentence. If the same mistake is noticed after go-live, screens, the database and training all have to be revisited. That is why the analysis is the cheapest and most valuable stage of a custom software project.
The goal of the analysis is to put the work you have in mind and the system we will build on the same page. By the end, both sides should understand exactly the same thing.
Analysis steps
- Introductory call: In a short phone call, we listen to the problem and your expectations.
- Process mapping: In online meetings, we talk with the people who actually do the work and map, step by step, where information comes from and where it goes.
- Review of existing documents: The Excel files, forms and reports you use show us how the work really happens.
- System inventory: We list the systems that need to be connected, such as your ERP, e-commerce site or accounting software, and how they can be accessed.
- Prioritization: We separate what must be in the first version from what can wait until later.
- Document and proposal: We review the analysis document together with you and, once you approve it, prepare a written proposal.
What goes into the analysis document?
| Section | Contents |
|---|---|
| Process flow | Step-by-step workflow, who does what, where approval is needed |
| User roles | Who sees which screen and what they can change |
| Screen list | The purpose and key fields of each screen |
| Data and integrations | Which information comes from where and where it goes |
| Reports | Summaries management will see, and how often |
| Personal data | Which personal data is processed, who can access it, how long it is kept |
| Out of scope | Work that will not be done in this phase |
The personal data section makes sure the requirements of KVKK (Türkiye's Personal Data Protection Law) are built into the design from the start, and we do not charge extra for this work. You can read more on our KVKK approach page.
A concrete example
When a service company comes to us asking for an application to track technicians' jobs, the analysis may reveal that the real problem is not job tracking at all, but not knowing how much spare-parts stock is left in the vans. A finding like that completely changes the scope and priorities of the project. That is exactly where the value of an analysis lies.
Preparation checklist
- Time for two or three people who run the process to join the meetings
- The Excel files, forms and sample reports in use today
- The names of the systems to be connected and who is responsible for each
- A short answer to the question of what would change if this software existed
- The name of the person who will make the decision
Frequently asked questions
Is the requirements analysis paid?
The first call and the general assessment are free. For larger projects, a detailed analysis may be proposed as a separate piece of work; if so, we discuss it openly from the start.
How long does the analysis take?
For work that covers a single process, a few meetings are enough. For projects involving several departments, it takes longer depending on how many people we need to talk to.
Can we work with another company after the analysis?
Yes. The analysis document describes your business, and it belongs to you.
You can see how we move forward after the analysis on our custom software service page, and our general method on the how we work page. To get started, use our contact page.