DimArn — ideas that work.
← Intrasoft portfolio
Intrasoft / Retrospective case study

Corporate web · Making capabilities visible.

Web & Responsive

How can a large technology-service offer become understandable to prospective customers and partners without reducing it to a list of technical terms?

Based on archived designs: context, design intent, observable work and available evidence.

Sector perspective & sources
Current sector perspective · 15 November 2026

Why this matters today.

Scale & operating context

Historical Intrasoft-branded material. Intrasoft joined Netcompany in 2021; present group strategy is context, not a description of the project’s original scale.

Historical identity; group context sourced

Today's priorities

Netcompany’s current strategy addresses complex public-sector and enterprise systems through reusable products, platforms and industry expertise.

Design perspective

A technology provider’s website needs to translate a broad technical offer into recognisable business needs, credible capabilities and a clear route to contact.

Sources & editorial note

Sector facts come from the sources below. Design implications are editorial analysis. This current perspective is not the original project brief and does not establish historical objectives, methods or results.

01 / Context & contribution

The starting point.

Intrasoft’s corporate pages bring together a wide technology-service offer, geographic reach, company information and news for prospective clients and partners.

Design contribution shown
Web structure & visual design
Design consideration
Technical breadth without information overload
02 / Design intent

What to make clearer.

Turn a broad catalogue of capabilities into understandable routes: explain the offer, show its relevance and make a useful next contact easier to identify.

03 / Method & feedback

Iterate. Listen. Refine.

Agile / ScrumIterative designFeedback loops

Refine service groupings and page modules through Agile content-design cycles. Align terminology with business owners and use design/development reviews to keep the system maintainable.

A methodological reading, informed by the visible work and professional practice; not a reconstructed log of workshops, tests or sprints.

04 / Observable design

Read the design.

  • Several routes into a broad service offer.
  • Visual modules for capabilities and corporate information.
  • A consistent relationship between brand, content and navigation.

Explore the archived screens and applications. Select an image for a closer look.

WEB 46 · Original portfolio material
WEB 47 · Original portfolio material
UX 04 · Original portfolio material
05 / Results & evidence

Define what success means.

Success criteria

Intended improvements to assess, rather than historical performance claims.

  • Clearer understanding of relevant capabilities
  • More relevant contact enquiries
  • Less effort to maintain consistent service pages
Documented evidence

The archived page designs show capability modules, corporate information and a recurring relationship between content, brand and navigation.

Archived survey results, approval rates and support statistics are not available for this case.

Your next assignment

Let's work
together.

Discuss your project