By Rob Steadman, Digital Solutions
I do not need a client’s budget as the starting point for understanding their software. I want to know what they need, what the end result should be and how the project should work.
From there, I can develop a proposal for that requirement. My approach is to establish the work and its cost, then discuss what is affordable if the proposed scope goes beyond what the client can spend.
Quoting for the requirement
A client brings an idea or a business problem. We work through the app, any admin controls and the way people will use the system. The proposal also covers costs, build times and the supporting requirements involved in delivering it.
That gives us a defined project to discuss. The client can check the proposal and we can agree the brief, rather than treating an initial amount of money as the entire specification.
Making a smaller first version
If the proposal is outside the client’s budget, I ask what is most important. We look at the minimum needed to operate and the tasks taking the most time. That helps shape a smaller first version.
Features still require development effort, whether they sit in the admin panel, the Apple app or the Android app. Reducing the first scope should mean making clear choices about that work, with the client understanding what is included and what would come later.
This is my own way of approaching a project. It is not a criticism of other developers or a suggestion that financial planning is unimportant.
Our software development and mobile app development services can begin with a consultation about your needs. You can explain the outcome you want, then we can work through a practical proposal and its priorities.