European projects

Preparation: a brief that can be delivered and checked

Before you apply, we help pin down what you actually need and turn it into a technical specification that meets the call's requirements. We describe the software functions, the hardware, the training and the support so that every item can later be demonstrated and verified.

If the call requires quotes, we prepare ours in the required format with a clear breakdown: what is licensing, what is development, what is rollout and training. That way the budget in your application rests on real figures rather than guesses.

We also help you choose between a packaged product and custom development. Sometimes the call only allows certain types of cost; sometimes a ready-made licence is cheaper within the project but dearer once it ends. Those questions are better settled before you apply than after approval.

• A description of the current process and what digitisation will change.
• A technical specification for software and hardware, written to the call's rules.
• A quote broken down by activity, in the required format.
• A schedule that is realistic against the project deadline.

Delivery: the digitisation the project is for

Once the project is approved, we deliver what was planned: a warehouse or production system, an ERP or CRM, an online store, a mobile app, integrations, AI features, cloud infrastructure. We work the same way as on any other project — site visit, prototype, staged development, rollout and training.

The difference is that the timeline is fixed. The project end date does not move because development ran late. So we plan with slack, sign off stages early and keep an eye on the points where we depend on you: access, data, decisions. If something in the plan turns out to be unnecessary or better done another way, we say so in good time, so your consultant can judge whether the grant agreement needs amending.

When the project includes hardware — servers, terminals, scanners, tablets — we supply, install and record every device, and agree its labelling under the funding's publicity rules with your consultant. Software and hardware are signed off together, so the equipment does not sit in boxes while the system is being finished.

Reporting: the evidence you will be asked for

At inspection it is not enough for the system to work. You have to show that exactly what was described was delivered, that it was installed where stated and that people were trained. We prepare the documents usually expected from the technical supplier as the work goes along, not in the final week:

• Handover protocols for each stage and a final acceptance protocol.
• A mapping between each item in the specification and what was delivered, with screenshots.
• User and administrator documentation.
• Attendance lists and materials from the training sessions.
• An inventory of installed hardware with serial numbers and locations.

The sustainability period

EU-funded projects usually carry an obligation to keep the system in use for a set period after the project closes. That means the software has to be maintained, updated and running, and you must be able to prove it at a later check. Our support covers exactly that: monitoring, backups, updates and fixes, with 24/7 cover for critical systems.

Because we built the system, we know what is in it and why. Nobody new has to start deciphering someone else's code just when you need to show that everything works.

Where to start

If you already have a call in mind, or a consultant working on one, put us in touch with them early. If your project is approved and you are looking for a supplier, send us the technical specification and we will tell you honestly whether, and how, it can be delivered on time. And if you are midway through with another supplier and things have gone wrong, we can take a look at that too.