Custom Software Development for EU-Funded Projects

In an EU-funded project software is a budget line before a system: a cost to justify, a scope to procure, a delivery on time, evidence in the file. Under ЗУСЕФСУ a beneficiary that is not a contracting authority awards the work by public invitation (процедура за избор с публична покана) once the estimated cost, own co-financing in and VAT out, reaches the legal threshold and the grant exceeds half the approved project value, and at half or less where the conditions of your procedure provide for it. Below the threshold, how the price is evidenced is set by those same conditions, usually through comparable offers; ours is only one of them. If chosen, we build to the tendered specification and close with an acceptance protocol and invoice. Which rules and which system apply is set by your programme and procedure conditions; your consultant or the managing authority confirms it.

Consultants write the application; we describe the software. On a deadline we confirm with you, we produce an indicative offer with a stated validity period, a technical description of the proposed solution written as functional requirements, and a cost breakdown that maps to the budget line you are drawing up. We stay in the vendor role: we do not advise on eligibility, aid intensity or state aid, and we do not compete with you for the advisory work. We do not draft your client's публична покана or a specification shaped around our own stack, because the ЗУСЕФСУ selection rules require a neutral invitation, with no steer toward a specific product, brand or manufacturer. That offer gives us no right to the contract: the beneficiary picks the contractor under the procedure. Contact runs the way you prefer, directly with your client or only through you.

A budget line is approved before the work starts and the end date is fixed in the grant contract, so a beneficiary cannot absorb a price that grows or a date that slips. We quote a fixed price and a fixed date for a scope written down in the technical specification, planning in reverse from the end date, with room for acceptance, corrections and reporting. Scope is settled before the offer goes in: the technical specification and the draft contract are an integral part of the invitation, and at reporting what was delivered has to match what was tendered and offered. After signature we absorb the detail inside the agreed price, and any change to contracted scope or value goes to the beneficiary and the consultant first, because it lands in the procurement file, not just our schedule.

The obligations outlive the project. EU rules require the investment to stay in place for a set period after final payment, commonly five years and shorter for some SME investments, and it is your procedure's conditions that fix the term; breaking it makes the aid repayable in proportion to the time out of compliance. Hosting, maintenance, updates and user support after the end date sit outside the project budget unless your procedure's conditions provide otherwise, and are priced separately, at your cost. Source code, scripts and documentation are handed over at acceptance, so the system can keep running or pass to another team. For software booked as an intangible fixed asset (ДНА) we supply the screenshots and documentation your procedure calls for, and the product can show the funding acknowledgement its conditions require; publicity stays your obligation.