Proces and timescale. Who's in charge?
The timeline is not defined at this point. An estimate is included.
We need to get to the bottom of who you are, what you stand for, and who you stand beside.
Only then can we begin to create a design that portrays the value you offer in a way that resonates with the people who matter: the people you want to use your platform.
We will evaluate the design together, to avoid planning unrealistic deadlines and target the main areas of risks. This will help us avoid delays and problems in the future. We can focus on functionalities and user experience while listing the priorities and set the pipeline correctly.
This step will define what we develop when. Of course, the platform will have tons of functionalities, but we can identify the high-impact ones to start with. We usually suggest having 2 to maximum 5 main features and list the rest after launch. It will allow us to better control the development process while the public can test the main functions and give us important feedback to correct errors or bottlenecks.
Well, that's it. We can start to build. We have the timeline, the priorities and the goal is now clear. We can start the development.
Reiteration in this part is key. We will go back and forth between developing and testing so that you can follow the progress on a weekly basis.
Once the beta is cleared from mistakes, we can put it online. We usually like to go live on a Friday, so we can use the weekends to gather any issue and be able to fix it before the beginning of the week after for the hard launch. And don't forget the popcorn.
In total, it will take us between 8-10 weeks to get your website live.
You managed until here, great job. Let's see if we can undermine your beliefs.