Preparation session for software
No inventory or development plan yet
An employee is missing a function, customers ask for an online facility, or information has to be manually transferred between systems every time. Such an internal signal can be a reason to start thinking about new software. A preparation session is intended to get acquainted with a developer about this. The session takes place before any inventory and does not yet include an elaboration of requirements, scope or software components.
- 01Preparation session
- 02Software requirement
- 03Introductory meeting
- 04Custom software
Starting with what your organisation itself notices
From internal signal to software requirement
Your employees and users experience daily how the existing software is used. They notice when a desired feature is missing, information is not available, or a digital application is needed.
The client determines for themselves which signals are relevant and which requirement is associated with them. For an initial introductory meeting, a complete software concept is not yet needed. A concrete reason and a few practical examples already provide context for the conversation.

Collaboration
Your course, our craft
You know your organisation, your processes and your users best. That is why you make the functional choices, and we make sure the technology fits them seamlessly. We are happy to think along, while you stay in charge.
Where you set the direction
- Your business strategy and how IT supports it
- Standard software or custom build: what fits best
- Package choices and how your processes map onto them
- The functional requirements for the custom build
- Which data needs to move to the new system
- Rollout and training of your users
Where we deliver the technology
- Technical specification of the custom build
- Software development
- Testing and quality assurance (QA)
- Software security
- Technical execution of the data conversion
- Hosting and monitoring
Clear roles, one shared result
Discuss the reason for your software requirement
Get to know APPelit
Has your organisation noticed a missing function, app idea or other software wish? Then invite a developer from APPelit for an initial introductory meeting. You share what is already known and get an idea of our technical development work. After the conversation, you decide for yourself whether you want to have the software wish inventoried separately. The preparatory session does not oblige you to start a software project or development process immediately.
Examples, experiences and existing software
First gather information yourself
Before inviting a developer, you can first check internally exactly what has been noticed. This is not a formal inventory, but an initial collection of information that helps to explain the reason in an understandable way.
Think of, for example:
You can also carry out your own online research into existing software products or similar applications. This creates an initial picture of what is already available and for which parts custom work may be desired.
The internal preparation may grow iteratively. You can start with what is already known and add to the gathered information when colleagues or users provide new examples.
- A short description of the missing functionality
- Comments from employees, customers or other users
- Examples of actions that are currently carried out manually
- Screenshots of existing software
- Forms, documents or data that are used
- Names of applications with which a connection is desired
- An initial idea for a mobile app, portal or dashboard
- People who could be involved in a possible inventory
Getting acquainted with the information already available
Inviting a developer
During the introductory meeting, the client explains what has been noticed internally, which software requirement has arisen from this and which preliminary research, if any, has already been carried out. APPelit explains which types of custom software, mobile apps, dashboards, portals and integrations we develop technically.
The developer listens to the background and can explain general technical concepts or development work. No functional requirements are drawn up at this stage, and APPelit does not determine which solution, functionalities or approach the client needs.
The introductory meeting gives both parties the opportunity to ask questions about collaboration, technical development and the available information. As such, the conversation serves solely as preparation for a possible separate inventory.
During this preparation, no business activities are examined and no final scope is compiled. A WBS, SRS, budget or development schedule are also not yet part of this phase. The client uses the introductory meeting to determine whether the software requirement will be further elaborated.
You decide whether and when to proceed
A separate inventory as a follow-up step
After the introductory meeting, the client decides whether an inventory is started. The information collected internally can be used as initial input. Only in that subsequent phase are confirmed functionalities and technical requirements further elaborated.

Information security
Secure by design. Demonstrably.
Do you work with personal or healthcare data? Then you want to be sure that your software partner handles information carefully. APPelit is ISO 27001- and NEN 7510-certified.
ISO 27001
The international standard for information security. Risks, access and incidents are recorded in a management system that is periodically assessed.
NEN 7510
The Dutch standard for information security in healthcare. Important when your software works with medical or health data.
- Security requirements included from the very first specification
- Test cases that align with recorded security requirements
- AI functions also fall within the same data agreements
Contact
Discuss your question
Leave your details. Within 24 hours, a specialist will contact you for an introductory meeting.
