I have worked across different ERP platforms such as Oracle ERP, PeopleSoft, SAP. My role in these respective companies started at a developer level and moved up to the level of an architect. I, therefore, have a strong understanding of what it takes to develop and build an ERP application.
In recent times I have also worked in organisations like Apigee and Google which specialize in API and platform architecture.
If selected I would spend a lot of time in understanding the requirements. My experience with the other ERPs has shown that a strong focus on the correct stack design which includes key factors like multi-tenancy, API, extensibility and integration capability. While not all of these will be required on day 1 any architecture and design should factor in these factors.
Open questions
1. What would the definition and scope of a prototype?
2. What modules would be part of the prototype?
3. What access will be provided to functional people who understand the specific modules?
4. What are the non-functional requirements for the application?
For clarity and transparency, I would like to state that the delivery timeline of 60 days is only indicative at this point and will need to be refactored depending on answers to the questions above. The milestones are also indicative at this point since the requirements are very broad at this stage.
I look forward to hearing back from you.