Public tenders: Offer software successfully in the public sector

Public procurement: Providing software successfully in the public sector

The public sector in Germany is a huge market with great potential for software companies. But the path to the successful conclusion of the contract is often stone and characterized by bureaucratic hurdles. Many IT service providers do not fail to the quality of their software, but to the inadequate presentation of their offer in the procurement procedure. In this article you will learn how to create a convincing software concept for public tenders and thus maximize your chances of success.

Das A und O: A convincing solution concept

For public tenders for Software in the public sector it is not enough to present a long list of features. Rather, it is important to provide a conclusive and convincing solution concept that is precisely tailored to the needs and requirements of the writing-out location. The support for tendering and evaluation of IT services (UfAB) makes it clear that often not the best technical software receives the award, but the best described concept.

The structure of the concept: mirror of the performance directory

A key success factor is the structure of your concept. Instead of using general marketing texts, you should align your solution concept exactly with the layout of the performance directory. If the invitation to tender under point 3.1.2 calls for the “candidate capability”, your concept should also describe in detail how your software meets this requirement. This facilitates the work of the examiners and signals that you have understood the requirements and take them seriously.

The central building blocks of a successful concept

A convincing concept for Software in the public sector consists of several central modules which will be explained in more detail below.

The functional description: The heart of your offer

The functional description is the core of your solution concept. Here you will describe how your software meets the required functionalities. Go beyond a pure list of features and explain the concrete benefits for the client. Visualizations such as diagrams or screenshots can help to illustrate complex facts in a comprehensible manner.

Configuring security and planning

Clients fear failed IT projects. A detailed implementation concept that includes a clear project plan with milestones, a risk management strategy and a description of the project team creates trust. The choice of methodological methods – classic according to the waterfall model or agile – is also important.

| Procedure | Benefits | Cons | | :--- | :-- | :-- | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Waterfall | Clear phases, fixed dates and budgets