Fixed time - fixed price
"Fixed price - fixed time" business model is very popular. It is chosen by those Clients who don't want to waste their time inquiring into details of the development process.
What does it mean?
You have an idea of a new project and want to receive a high-quality ready-made product. You don't want to stuff your head with issues of technologies and management. Your main concern is to provide a most exact description of your ideas to somebody who can realize them in the best way.
How does it work?
Fixed price model consists of several interrelated phases.
The general scheme is as follows:
Discussion=>Analysis=>Development
1. Discussion
We familiarize ourselves with the project description you provide us with. Then we discuss with you all important points of the design and architecture. The preliminary talks help us understand the project objective and the Client's demands.
2. Analysis
The Client is provided with the project estimation after all the key moments are clear.
First we list features and functionalities needed for the successful functioning of the system.
This list is drafted according to the Client's vision of the project discovered during the discussion phase. Then we make time (in man-hours) and appropriate cost estimation. In other words, we fix the time for the project delivery and therefore the price is also fixed.
As a result, the Client receives an accurate and detailed quotation of the whole project, so that s/he can see what s/he pays for.
The agreed estimation allows to sign the contract. After the contract is signed we start writing the specification. The specification includes an exact, even scrupulous documenting of the requirements. It is often accompanied by a clarification of nuances. The main purpose of the specification (and discussion) is the exclusion of any misunderstandings and ambiguous points.
Writing a clear and precise project documentation is important, because it influences greatly the speed and efficiency of the development.
Thus, such a precise specification is a benefit for both sides:
The Client is satisfied, because AlarSoft develops exactly what s/he wants.
AlarSoft developers are satisfied, because their work is exactly what the Client wants.
In other words, the specification serves as the guarantee of mutual understanding and meeting of expectations the basic document for verifications of correct project implementation.
However if the Client has a ready-made specification the step of specification writing is skipped. We just make sure that we understand it completely.
3. Development
This phase starts with the division of the project into milestones. The development phase includes the full cycle of services from system architecture up to the final quality assurance.
We also provide Clients with regular report during the development.
4. Technical support
This phase comes after the project is launched.
We provide Client with:
clear instructions about how to use the system we created.
free bug-fixing period, which varies from two month to one year. The time length depends on the project complexity.
assistance in the resolution of different problems, for example: problems with hosting, domain registration, integration of 3rd party systems and so on.
What does it mean?
You have an idea of a new project and want to receive a high-quality ready-made product. You don't want to stuff your head with issues of technologies and management. Your main concern is to provide a most exact description of your ideas to somebody who can realize them in the best way.
How does it work?
Fixed price model consists of several interrelated phases.
The general scheme is as follows:
Discussion=>Analysis=>Development
1. Discussion
We familiarize ourselves with the project description you provide us with. Then we discuss with you all important points of the design and architecture. The preliminary talks help us understand the project objective and the Client's demands.
2. Analysis
The Client is provided with the project estimation after all the key moments are clear.
First we list features and functionalities needed for the successful functioning of the system.
This list is drafted according to the Client's vision of the project discovered during the discussion phase. Then we make time (in man-hours) and appropriate cost estimation. In other words, we fix the time for the project delivery and therefore the price is also fixed.
As a result, the Client receives an accurate and detailed quotation of the whole project, so that s/he can see what s/he pays for.
The agreed estimation allows to sign the contract. After the contract is signed we start writing the specification. The specification includes an exact, even scrupulous documenting of the requirements. It is often accompanied by a clarification of nuances. The main purpose of the specification (and discussion) is the exclusion of any misunderstandings and ambiguous points.
Writing a clear and precise project documentation is important, because it influences greatly the speed and efficiency of the development.
Thus, such a precise specification is a benefit for both sides:
The Client is satisfied, because AlarSoft develops exactly what s/he wants.
AlarSoft developers are satisfied, because their work is exactly what the Client wants.
In other words, the specification serves as the guarantee of mutual understanding and meeting of expectations the basic document for verifications of correct project implementation.
However if the Client has a ready-made specification the step of specification writing is skipped. We just make sure that we understand it completely.
3. Development
This phase starts with the division of the project into milestones. The development phase includes the full cycle of services from system architecture up to the final quality assurance.
- We develop the system design, if the project complexity requires this step. So for simple projects this step can be skipped.
- We provide the Client with several design mock-ups. The design is being changed until the Client is 100% satisfied with the result.
- After the design is approved we start programming. Programming follows the approved sequence of milestones. We provide the Client with the intermediate versions of the project, so that the Client can see the progress of the project.
- Quality assurance. The quality of the system functioning is tested at every project stage and after the project is completed.
We also provide Clients with regular report during the development.
4. Technical support
This phase comes after the project is launched.
We provide Client with:
clear instructions about how to use the system we created.
free bug-fixing period, which varies from two month to one year. The time length depends on the project complexity.
assistance in the resolution of different problems, for example: problems with hosting, domain registration, integration of 3rd party systems and so on.