As a digital agency, we have certainly received hundreds of requests for proposals, and questions about how much commitment is required from the client are relatively common.

This is often because many companies want to spend minimal time on their intended web solution, which is completely understandable – since time also means money. As a result, many companies choose suppliers who require less commitment from their clients. However, it is problematic that a client’s commitment is perceived as something negative.

In our opinion, a web project requires a lot of commitment from the client in order for it to be successful. We are aware that a requirements specification can be interpreted in different ways, which is why continuous communication is required.

In addition, there are a lot of details that never fit within a requirements specification and therefore must be discussed during the project. This is an important building block in modern project methodology for web and system development, so-called agile methodology. This is a collective name for most project methodologies that are based on the fact that not all details in a web solution can be determined before the project begins.

We have previously written a white paper about what you as a client need to know about requirements specifications before ordering a web project. Read that post here.

Despite a correctly written requirements specification, it is almost impossible to describe every single detail of the intended web solution. Therefore, you always need to expect that questions about the web solution will arise during the course of the project. To create the most successful project possible, several coordination meetings and possible workshops are usually required.

Unfortunately, it is a common misunderstanding that you as a client only need to follow the development of the project through status updates in a project management system. Therefore, many people also believe that there is no need for weekly coordination meetings.

However, we believe that many coordination meetings are important for a successful web project. During these meetings, everything from the project status should be discussed, but also any questions should be clarified. In addition, as a client, you also need to reserve time to think about issues that may have arisen during reconciliation meetings.

Shouldn’t the supplier do this themselves?

Of course, a supplier can to some extent assume how the intended web solution should be developed to give your business maximum business value. However, an outsider never has the same insight into the company, your wishes or business model. Precisely because it is important that there is close communication during the course of the project.

Usually, it can even be difficult for you as the client to know what type of web solution can give your business more business value. Our recommendation is to create a reference group of employees who discuss the web solution during the course of the project. This way, you get perspectives from people who represent different parts of your business.

Why doesn’t the supplier come up with proposals?

Within a digital or web agency, there should of course be the competence to develop proposals for details. However, this does not apply to everything, but the supplier can only provide suggestions for small details that do not require much rework. When it comes to larger details and work that could lead to an exceeded budget if rework is done, a discussion must always take place in consultation with the client.

With this, you as the client must not only reserve time for coordination meetings but also time to think about proposals and possible changes. In addition, you must also reserve time to test the web solution in several rounds.

How much commitment is required from the client during a web project?

As you probably understand, this depends entirely on the type of web solution to be developed and how large the project is. It is difficult to state exactly how much commitment and time is required, but usually there is more than one coordination meeting a week.

We recommend reserving plenty of time to test the work you have done and then provide feedback. In addition, you will probably need to answer additional questions, collect requested data and review similar web solutions for inspiration. From time to time, you will need to evaluate the project work and discuss potential improvements with the project manager.

“We recommend reserving plenty of time to test the work you have done and then provide feedback.”

It is desirable to have a consistent intensity throughout the project, but it usually becomes more time-consuming at the beginning and end of a project. Absence from a project can lead to rework, delays and thus an increased budget. Which is of course never desirable!

As you may understand, commissioning a web project is usually more work than many people think. Although men The level of commitment depends on the type of web solution to be developed. For example, a business-critical web system requires more commitment and time than developing a website.

But regardless of what is being developed, web projects usually require a great deal of commitment to enable the web solution to be successful. Therefore, it is important to reserve time for planned coordination meetings and possible workshops, but also for unexpected problems and questions before the project starts.

In addition to this, we recommend that there are several people within the organization who are familiar with the order. This way, they can assist as contact persons if something unpredictable should happen or if your time for the project is not enough.

Summary

  • It requires a great deal of commitment from you as the client to develop the intended web solution according to your needs and wishes.
  • As a client, it can sometimes be perceived as time-consuming and unnecessary to be involved during the course of the web project. It is certainly time-consuming, but by being involved, the chances of a successful web project will also increase.
  • A requirements specification cannot possibly include every single detail of a web solution, which is why coordination meetings and possible workshops are required during the project. You as the client should also reserve time for unexpected problems and decisions, as well as set aside time to test the web solution.
  • By being involved in the web project, you also get better insight into the work and can thus influence the development of the intended web solution.
  • Sometimes it happens that you as the client are not able to set aside the time required for the web project, in which case it is good if there are additional people in the organization who are familiar with the order.