Case study

VAEngineering

VAEngineering is a young engineering company focused on electronics design, firmware, production support and end-product development. The team works on technical products across sectors such as consumer electronics, aerospace, healthcare, mobility and industrial applications.

Strategy
Positioning
Messaging
Webdesign
UX
Customer journey
Video concept
Sector
Engineering · B2B
Scope
Website · Cases · Sector pages · Outreach · Offline

The project in overview

Client type
Engineering company
Challenge
Electronics, firmware and technical product development
Work
Visitors needed too much explanation before seeing where VAEngineering could help
Focus
NDA restrictions and sensitive client information
Output
Website structure, messaging, case pages, sector pages, outreach and offline material
Impact
The website, cases, outreach and sales material started supporting the same explanation

Beyond services and sectors. Closer to the client's situation.

The technical expertise was already there. The website had to make it easier for new visitors to see where VAEngineering could help.

A visitor could see that VAEngineering worked with electronics and firmware, but still needed extra context. When should they involve the team? What kind of technical problems could VAEngineering support? How was their way of working different from other engineering companies?

The website had to move beyond services and sectors, and start closer to the client's situation. One company might have an idea but no technical direction yet. Another might have a working prototype that needs to become more reliable. Another might be preparing for production and needs better decisions around hardware, firmware or testing.

That became the line used across the website, cases, outreach and offline material.

Several channels that did not yet support each other.

VAEngineering already had several communication channels in place. There was a website, social media, outreach and material for events and meetings.

The problem was that these channels did not yet support each other enough.

A prospect could see that VAEngineering worked on electronics and firmware, but the next step was less obvious. The website did not show clearly enough when a company should contact them, what type of technical challenge fitted their expertise or how they helped during product development.

As a result, too much of the explanation still happened in personal conversations.

That created a positioning issue. Many engineering companies present themselves in a similar way: services, sectors and technical capabilities. That gives information, but it still leaves the visitor to figure out the relevance alone.

VAEngineering needed to show more of how they think with clients, how they reduce technical uncertainty and how they support companies when an idea, prototype or product challenge needs a technical path forward.

The NDA barrier

A second challenge was confidentiality.

A lot of VAEngineering's work cannot be shown in full. Some projects involve client IP, prototypes, product details, technical decisions or internal development work protected by NDAs.

That meant the strongest proof could not always be used openly. It was often impossible to show the product, name the client, explain the technical setup or publish the full process.

The cases had to build trust in another way. They focused on what could be shared safely: the client situation, the technical challenge, VAEngineering's role and the progress created.

This made it possible to show how the team works while keeping sensitive information protected.

What needed to change

The main shift was from service-first communication to situation-first communication.

Before, VAEngineering was mostly presented through what the company could do: electronics design, firmware, technical development, sectors and project experience.

After, the communication started from the moments where clients usually need help. Some clients need to turn an idea into a technical direction. Others need to improve a prototype that already exists. Others are moving toward production and need better decisions around reliability, testing, hardware or firmware.

That shift made the company easier to place. Visitors could recognise when VAEngineering was relevant for their situation, instead of only reading a list of capabilities.

From first visit to first conversation.

The work started by looking at the path from first visit to first conversation.

The website had to explain more before a visitor spoke with the team. The structure was rebuilt around the questions a prospect would have first: what VAEngineering does, when to involve them and what kind of projects they can support.

The messaging moved away from an internal service list. The content was shaped around the situations where clients usually need technical help.

Because of the NDA restrictions, the case pages needed more care than a normal portfolio page. They had to show credibility without depending on client names, product visuals or technical specifications. The cases focused on the situation, VAEngineering’s role, the decisions made and the progress created.

Outreach, sector pages and offline material followed the same message, so VAEngineering felt consistent online, by email and during events.

One message across every channel.

VAEngineering already had a website, but it did not yet explain enough before a first conversation.

The structure and navigation were refined so visitors could find their way faster. Services became easier to reach, sectors received more context and the website became more useful as a first introduction.

Case pages were added to make the work more concrete. Since many projects could not be shown openly, each case had to balance detail with confidentiality. The focus was placed on the situation, the technical challenge, VAEngineering’s role, the decisions involved and the progress created.

The website was also translated from Dutch into English, so the same explanation could support international prospects.

For outreach, the general website was sometimes too broad. A healthcare company, aerospace contact or industrial prospect needed a faster link to their own world.

Focused sector pages were created to give those prospects a more direct entry point. Instead of sending them to a broad website and expecting them to find the relevance themselves, the sector pages made the connection earlier.

Email outreach followed the same line. The messages were rewritten so they sounded more natural and more specific to the person receiving them.

The same message also had to work offline. Business cards and a brochure were developed with a visual direction inspired by electronics and PCB design, so the material felt connected to what VAEngineering actually does.

A stronger first impression. One consistent story.

The website became stronger as a first impression. Visitors could see faster what VAEngineering does, who it helps and when it makes sense to start a conversation.

The English version made the same explanation usable for international prospects. Sector pages gave outreach a more relevant landing point, because prospects no longer arrived on a broad website without context.

The case pages gave VAEngineering a way to show project experience while respecting NDA limits. Even when full details had to stay private, the work became easier to explain through context, role and outcome.

The website, cases, outreach and offline material started working together instead of explaining the company in separate ways.

Technical companies often have strong expertise that is difficult to explain online. The work can be complex. The strongest proof can be confidential. The details that make a project impressive are often the same details that cannot be shared.

That makes it easy to fall back on broad service descriptions that sound like every other engineering company. For VAEngineering, the work was about making the company easier to recognise for the right clients.

The communication started from situations clients already recognised, while keeping sensitive project details protected.

The company already had the technical expertise. The work was about making that expertise easier to trust before someone had spoken with the team.

Clearer positioning, built around the real reason people choose you.

If you have a strong offer but people don’t see the value behind it, it’s time to change how it is presented. Let’s make it clear what your offer does, who it is for and why people should choose you.