Self-initiated project
iDevTeam: website concept for a B2B software house
How the website of a Warsaw software house that connects devices, protocols and business systems could sell. I made this concept on my own initiative; iDevTeam didn’t commission or approve it.
- Sector
- B2B software house, Warsaw
- My role
- Concept, content strategy, offer model, design and code
- What it shows
- Complex technology explained in a business client’s language
A list of services isn’t a way to buy
Systems, apps, APIs, websites and maintenance describe what a supplier can do. A business client also needs to know where to start and what working together looks like.
So I organised the offer by responsibility and outcome, with the technology list further back. The conversation can start with what the company wants to launch, connect or hand over for maintenance.
The cross-section shows where decisions happen
The chosen condition changes the whole cross-section of the system. You can see what happens in the device and the protocol, where integration begins and what the operator needs to see.
- 01Device
- 02Protocol
- 03Integration
- 04Operator
Complexity, shown in order
I created the offer architecture, the language of layers, the screen system and a working cross-section that explains dependencies without flattening them into a wall of technology logos.
The concept suits an integration company: it shows the boundaries of responsibility and how information flows between a real device and a business system.
What this means for your project
If your offer is technical, the website doesn’t have to dumb it down. It can show the dependencies and still name the outcome and how to start working together.