You are on page 1of 1

Remove item 3 and 4 since our goal is to simplify the deployment for the

Indonesia in a most practical way for them and suit to the time they require
for it. Any complex and complicated add-ons will entail time of development
and testing. We would like to partner with them, therefore we should focus on
the actual needs based on your experience with esfi. rather than the
additional nice to have.
Item 1-timeline this is the biggest player so we have to really determine as
to when we are able to deliver the project in accordance to their expected
schedule of project.
Item 2- already answered by Emma. We can decide if we will reuse the
existing, and our decision is to reuse.
The rest is we need to itemize and summarize their requirements. We need to
identify what will require extra development, and they have to decide which
are required, given the timeline they wanted. Of course the more
requirements, the better on our side. But because part of the constraint is the
time of when this is actually needed, then we need to focus on what is
necessary.
I think these are the key messages our team need to send them. Then the
rest of the proposal will be identified by their answers on what is required
amongst the list they gave us.

Note:

We must imply to the client that they must only say yes to the items that has
upmost important. Also saying yes to items that has additional development
comment entails additional time and we don't have that much time within the
given period.
We also must to say to them that we need to make the system run first in their
network/server and make sure that the basic functionalities are working before
we do additional development/enhancement for them. Prior to this, we need to
ask them the details of their server configurations for uploading and accessing
the database

You might also like