Based on our experience and projects implemented over the last 9 years, we would like to share some thoughts regarding the implementation of IT projects.

We start our series with arguably the most important topic, which is the issue of cost.

If you are planning an IT project, I think that below you will find some interesting tips that will help you implement the project on a lower budget without compromising on quality.

We will focus on four aspects:

  • specifications,
  • contract type,
  • selection of the contractor,
  • selection of the technology.

Fine-tuned specification.

Very often we receive projects with overly extensive specifications for valuation. In addition to the main functions, they contain a whole lot of additions that do not add much or duplicate popular and cheap SaaS solutions, significantly increasing the total value of the project.

For example, startups like to price functionality that will be used, when they pass several hundred of active users. These can be for instance: add-ons that allow users to create a community inside the application, automate payments, when it is not yet known whether it will be possible to acquire one user who will actively use and appreciate the generated value of the product.

Corporations often prepare the specification as a team, with each person contributing something from his or her share, often duplicating existing, relatively cheap products. This is where the unnecessary invoicing module often appears.

Software House converts functionality into time.

When preparing an offer, Software House relies on converting functionality into time estimations. Often the little things are more time-consuming than the essential functionalities.

Start by reworking the specification.

If you want to implement the project cheaper, start by reworking the specification. Find the essence of functionality. Completely basic functionalities that are the key to the success of your application.

Completely basic functionalities — MVP.

Such basic functionality is often called MVP (minimum viable product). Usually this is enough to see if our idea will catch on: among our clients or among employees. It happens that the implementation of the MVP of the project allows you to save up to 70% of the planned budget.

Sometimes we go a step further in cutting functionality to PoC (proof of concept). This often applies to projects that use machine learning and artificial intelligence, where we do not know if the functionality will be effective. For the test on first users, a demo of the application is enough, and often we do not need a refined interface and consideration of all use cases.

Here we can go down to 15–20% of the original cost estimate.

In the next article, we will deal with the type of contract.

If you are plannig an interesting project and are considering choosing a contractor, we will be happy to take a look at the specification. Maybe SmartShack will turn out to be a good choice. I encourage you to contact us.