---
title: 'From prototype to reliable application'
url: 'https://grassroot.it/en/artikel/vom-prototypen-zur-anwendung'
markdown: 'https://grassroot.it/en/artikel/vom-prototypen-zur-anwendung.md'
lang: en
date: '2026-11-11'
description: 'A prototype makes an idea tangible and shows whether it can support a business process. Sustained use also requires clear expectations, limits and operational arrangements. Gras…'
taxonomy:
  category:
    - Development
  tag:
    - 'Getting started'
    - Development
    - Lifecycle
---

Development 11.11.2026

# From prototype to reliable application

A prototype makes an idea tangible and shows whether it can support a business process. Sustained use also requires clear expectations, limits and operational arrangements. Grassroot IT c…

 ![From prototype to reliable application — symbolic illustration](https://grassroot.it/user/pages/03.artikel/02.vom-prototypen-zur-anwendung/cover.png) 

A prototype makes an idea tangible and shows whether it can support a business process. Sustained use also requires clear expectations, limits and operational arrangements. Grassroot IT connects these tasks across the lifecycle.

## Clarify the need and alternatives

Start with a specific task: who does what today and what should improve? An example with inputs and an expected output makes the question precise. Check whether a suitable application already exists or an existing solution can be adapted.

Expected value should be observable, such as shorter processing or more reliable reconciliation for a monthly report. Maintenance, data collection and dependencies count too. Record the criteria for later deciding whether the application fulfils its purpose.

## Develop a manageable part

The first prototype addresses a limited use case. Structure business rules, interaction and data access so changes can be understood. This applies to a workbook in Microsoft Excel, an application in Microsoft Access or a low-code workflow.

Use suitable sample data. Confidential information and credentials belong in approved handling procedures. Record prerequisites and error cases not yet covered.

## Test against business expectations

Begin with independently established expected results. Include normal processing, empty or unsuitable inputs, duplicate records and interrupted processing. A repeated run must not, for example, silently create duplicate postings. Select tests according to the task and consequences of errors.

A short test record identifies the version, examples, expected and actual results and remaining limitations. Business acceptance and the need for independent review follow the organisation’s applicable rules.

## Connect introduction and operation

Before introduction, name an owner and deputy and define the approved storage location. Brief instructions explain use, errors and recovery. A change must identify the version being replaced and how the previous state can be restored if necessary.

After introduction, check actual value. Changes follow the appropriate testing and approval process again. If the need disappears, address data, access and dependencies in an orderly way. The [framework overview](https://grassroot.it/en/konzept) shows these connections; [Reliable application operations](https://grassroot.it/en/artikel/anwendungen-verlaesslich-betreiben) develops the operational foundations.

## Further reading

Microsoft describes requirements, development, testing, deployment and maintenance in its [application lifecycle management overview](https://learn.microsoft.com/en-us/power-platform/alm/overview-alm). The Grassroot approach here is our own tool-independent interpretation.

---

## Navigation

- Parent: [Articles](https://grassroot.it/en/artikel.md)
- Previous: [When does a spreadsheet become an application?](https://grassroot.it/en/artikel/tabelle-zur-anwendung.md)
- Next: [Operate applications reliably](https://grassroot.it/en/artikel/anwendungen-verlaesslich-betreiben.md)