This is an AI translated post.
[SI Developer Story] 11. Let's Secure an SI Project - Proposal Story
- Writing language: Korean
- •
-
Base country: All countries
- •
- Information Technology
0000-00-00 00:00:00
Select Language
Summarized by durumis AI
- To win an SI project, a proposal must be submitted to the client, which should cover various aspects such as development methods, security, training, and more.
- While typically written by sales personnel, proposals for already established projects are usually prepared by the development team, providing valuable experience for new developers.
- Proposals are a form of documentation written towards the end of the project, often following a similar format with only the requirements section being newly drafted.
The Story of SI Developers
#6. How to Secure an SI Project - Proposal Story
To win an SI project, you need to submit a proposal to the client who has issued the project. You will then be awarded the project through a competitive bidding process. In this process, the client will write a request for proposal (RFP), stating their requirements and asking for a proposal.
Based on this RFP, SI companies will write a proposal that matches the table of contents and the content. The proposal will include information about development methods, security, user training, risk management, and other aspects related to the requirements. Usually, the sales department will be responsible for writing the proposal, but it is common practice for the SI company to handle both the RFP and the proposal. This is because the SI company is typically involved in the next operational project after the development is completed.
Since the SI company has already built the system, they are familiar with it and have already built trust with the client. Although the project is awarded through a competitive bidding process, it often becomes a formality as the SI company can secure the project.
In this case, the project manager will work with the client beforehand to determine the requirements and write the RFP, which will be reviewed by the client before being released. The next year's project will be aligned with this RFP. The proposal is typically written by a team of junior developers.
The format of the proposal is generally similar, and except for the requirements section, the rest of the content is essentially a copy-paste from a resume. There is no need to worry too much about it.
Think of the proposal as a type of documentation that is written at the end of the project. It helps to put your mind at ease. Once you've written one, you'll get a feel for it, and by the second or third time, you'll be able to write it much faster. In the future, when you take on the role of a project manager, you'll need to be mindful of these aspects. If you have the opportunity, it's good to experience this process at least once.
