Can we start a project even though not all requirements are settled yet?

Yes. For an initial conversation, a real example case is usually enough: who starts it, what information is needed, which systems are involved and how does the company recognise a good result? At this stage, a complete list of requirements can even be a hindrance if it already prescribes a technical solution before the actual problem is understood.

Before a larger implementation, a binding scope is still needed. It can develop step by step: first through assessment and definition, for complex projects through a paid process or technical check, and then through a first verifiable scope of delivery. Roles, data sources, exceptions, interfaces and acceptance criteria are documented along the way. “Starting with open requirements” therefore does not mean “developing without an agreement”. It means deriving the agreement from real workflows instead of from a hastily invented feature list.

As of 3 September 2026

Further reading

Related topic: Custom software development