Independent technical assessment of software and hardware projects
A second, independent engineering opinion on any software or hardware project: before you sign, while it is being built, or when a delivered system does not work as promised.
Who it is for
- Companies about to buy a software system, a device, a production line or an upgrade, and who want to know what they are really getting.
- Investors and buyers who need technical due diligence on a technology company, a product or a production asset.
- Project owners who want an outside check of a supplier's design, code, schedule or acceptance tests.
- Teams whose system is slow, unstable or late, and nobody can say why.
What we assess
- Software: architecture, code quality, security, scalability, documentation, maintainability and how dependent you are on one supplier.
- Hardware and devices: electronics, firmware, sensors and the algorithms behind the measurements, test methods and readiness for production.
- Production lines and industrial systems: integrations, control software, data flows, bottlenecks and single points of failure.
- Proposals and specifications: are the requirements complete, is the solution realistic, what is missing from the price.
- Acceptance testing: test plans, measurement rigs and witnessed FAT/SAT on your side of the table.
What you receive
- A short written review: risks, gaps, questions to ask the supplier and a realistic estimate of cost and schedule.
- For a deeper assessment: a report with findings ranked by impact and a 30/60/90-day plan.
- If you wish, a walkthrough of the findings with your team or with the supplier.
How we work
- Second opinion. Send us the proposal, specification, design or code. Within days you get a short written review.
- Assessment. We study the system in depth: we read the code and the documentation, measure, test and talk to the people who build and run it.
- Follow-up. We can support the negotiation, the acceptance tests or the fix itself.
Strict confidentiality
Every assessment is done under a strict NDA. Nothing you show us leaves our team: no names, no documents, no details in our publications or conversations with others. All materials you give us are destroyed on our side at your first request.
Frequently asked questions
Why should we trust your assessment?
Because we have no stake in the outcome. Our independence rule: we do not assess projects in which we have a stake, so our recommendations serve your project, not a sales target. And we build software, electronics and devices ourselves, so we know where such projects usually fail.
What kinds of projects can you assess?
Software and hardware projects of any kind: business and industrial software, data platforms, embedded systems and devices, electronics, production lines and their control systems.
What happens to our documents and code after the assessment?
They stay confidential under the NDA, and we destroy all materials on our side as soon as you ask.
When is the best moment to ask for a second opinion?
Before you sign. Changing a specification costs almost nothing compared with changing a system that has already been built. The second best moment is before the acceptance tests.
How long does an assessment take?
A second opinion on a proposal usually takes a few working days. A deeper assessment takes from one to a few weeks, depending on the size of the system and on how much documentation exists.
Can you assess systems that have no documentation?
Yes. Older and undocumented systems are a normal part of our work: we read the code, trace the protocols and document what we find.
Do you work outside Finland?
Yes. We work in English, remotely and on site.
Have a proposal or a project you are unsure about? Write to info@kuorelab.fi and we will tell you what we would check first.