A project with Silurus Software starts with a call and ends its first phase with a written proposal, before any team is committed.
The call settles whether the work fits: device type, software safety class, submission route and timeline. If it fits, the NDA is signed and you send the requirements and access to the code and the current documentation where they exist.
For finished software or firmware the assessment is a gap analysis against IEC 62304, with scope and duration agreed in writing. The embedded firmware gap analysis in our case studies took three weeks with two people. For new development or added capacity the proposal follows from the requirements.
The proposal names scope, deliverables, team, duration and price model. Work then starts inside your QMS, under your procedures and document control.