FAQ · Working with Silurus

Questions about working with Silurus.

Silurus Software collects here the questions that apply to every engagement, from pricing and contracts to quality system, team size and languages. Questions about a specific service or sector are answered on that page.

Company
Silurus Software Kft., founded 2017
Offices
Budapest and Singapore
Team
40+ engineers
Languages
English, German, Hungarian
Process

How a project starts.

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.

Before the call

What to send before the first call.

Each of these shortens the way from the first call to a proposal. A draft is enough.

Requirements or specification

A short description of the device and the software in it. Requirements and specifications follow once the NDA is signed.

Classification and route

The device class, the software safety class under IEC 62304 if known, and the intended route: EU MDR, IVDR, FDA 510(k) or De Novo.

Timeline and constraints

The submission or audit date you are working towards, the team you have, and the part of the work you want to keep in house.

Cost and contracts

Cost, pricing and contracts.

General questions only. Each service and sector page answers its own questions.

01

How much does it cost to work with Silurus?

Silurus Software does not publish a rate card, because every engagement is priced individually. Work packages, such as a gap analysis or a documentation package, are estimated in hours once the scope is clear, and the estimate is agreed in writing. Code and documents we create for you belong to you once they are paid, and on exit we hand over all of it. Dedicated engineers who join your team are billed on time and materials. The written proposal states the price model and the amount before anything is committed.

02

Is there a small first step before a larger contract?

Yes. A gap analysis against IEC 62304 ends in a written report, with scope and duration agreed in writing. It shows what the next phase needs before you commit to it. The price is quoted after a first look at the code and the documents. The first step is described on the How we work page.

03

Do you sign an NDA before we share documents?

Yes. We sign your NDA, or send our own, before any source code, specification or risk file is exchanged.

04

Can you contract on our supplier agreement and statement of work?

Yes. A manufacturer that qualifies its suppliers under ISO 13485 has its own supplier agreement and statement of work template, and we contract on those. Where none exists, our written proposal states scope, deliverables, team, duration and responsibilities, and the signed proposal becomes the order.

First steps

Fit and first steps.

From the first call to the written proposal.

01

Which devices and software do you work on?

Software in and around medical devices: imaging and radiotherapy platforms, embedded firmware, and the desktop, backend and cloud software around them, including Class IIa and IIb devices under EU MDR. The sectors overview lists every sector.

02

How does a project with Silurus start?

With a call, then your requirements, then an assessment or a proposal. On the call we check device type, software safety class, submission route and timeline. You send the requirements and, under NDA, the existing code and documentation. For finished software the next step is a gap analysis. For new development or added capacity it is a written proposal.

03

Who do we talk to on the first call?

A member of the management team with an engineering background: Péter Török, Founder and CTO, or Tamás Fodor, Head of Software Engineering. The technical questions are answered on that call.

Team and quality system

Quality system, team and location.

Whose QMS applies, how many engineers, where they sit and which languages they work in.

01

Do you work in our QMS or in your own?

In yours. The device and its quality management system are the manufacturer's responsibility, so the work runs inside your quality management system: your design controls, your software development and risk management procedures, your document control and your release gates. The split of tasks between you and Silurus Software is written down in the supplier agreement. Our engineers write the lifecycle records to your templates, for your technical documentation and your design and development file.

02

Which certificates does Silurus hold?

Silurus Software holds ISO 9001:2015 (NQA, certificate 171041, valid until 28 March 2027) and ISO/IEC 27001:2022 (NQA, certificate 728872, valid until 25 August 2029), see the Quality and standards page. The manufacturer's quality management system is the one assessed at audit, and our work is done inside it.

03

How large is the team, and how far can an engagement scale?

Silurus Software has more than 40 engineers. Each engagement is staffed to its work. Our longest running engagement has ten specialists working across several functional teams of one manufacturer, over several years.

04

Where are you located, and which time zone do you work in?

Our headquarters are in Budapest, Hungary, at Science Park B, and we have an office in Singapore. Budapest is in the same time zone as Germany, Austria and Switzerland, summer time included.

05

Which languages do you work in?

English and German with clients. Hungarian is the language of our Budapest office and is available to clients in Hungary.

Talk to us

A question that is not on this page?

Send it with your requirements, or book a 30 minute technical call.