From the idea to the call for proposals

We set the course for successful projects

Whatever project methods your agency or IT service provider users, clear standards in the form of objectives, result expectations and precise specifications are essential in order for your web relaunch or new application to do exactly what benefits your business.

A rule of thumb says that 80% of all later weaknesses, shortcomings, delays and extra costs are caused by insufficient diligence BEFORE the project. Good old requirement specifications/functional specifications are still a good precaution against later "surprises".

Besides its own production Dimando has always supported customers that are preparing a new portal, shop, website, CRM system, CMS system or app, or planning a relaunch, or need other IT applications for marketing or HR, in developing their functional specifications and through product-neutral assessments.

We accompany them through the preparation and planning phase when compiling the requirements catalogue and provide support in preparing the necessary documents. When necessary we will completely implement a WTO-compliant call for proposals for you. We have familiarity with and mastery of the set of tools for compiling checklists, prioritisation and analysis documents. If you would like, we will organise the entire process with our own Project Office and lead you and your team in a safe and structured way through the call for proposals process.

Although the IT standard nowadays regularly provides for compiling functional specifications or at least a requirements profile, companies again and again wonder – understandably – whether the benefit is worth the cost and effort: will it amortise?

The proportion of a proper pre-project phase ranges from 5 to 12% of the total project expense depending on the complexity and customer's own share of the expense. If the introduction costs for your new e-shop or your CRM system are 250,000, would it not be possible to save about 30,000 and just perform a simple briefing? Three concrete benefit arguments speak in favour of careful project support and preparation:

Benefit of functional specifications

a) Benefit from completely capturing the business objectives

The mere functionality of a piece of software in now way entails that it effectively reproduces business processes and contributes to the earnings/cost objectives as efficiently as possible; on the contrary, all functions must be integrated in such a way that the users achieve the greatest benefit from the smallest operating expense.

b) Benefit through minimised risks

Every project generates typical risks; any important project can lead to undesired effects on the course of your business or on the business processes. The less specifically the expectations are captured and quantified, the greater the danger is that risks due to errors or omissions will be overlooked.

c) Benefit through timely = market-oriented implementation

Typical example: An e-shop should generate revenue of 350,000 per month; because of incomplete specifications and costly follow-up programming the shop goes into operation four months late; that means 1.4 million in lost revenue and usually also high costs for fire drills.