Attachment 3
iDevTeam
Unofficial redesign concept
An unofficial redesign concept for a Warsaw B2B software house. It was not commissioned or approved by iDevTeam.
- Sector
- B2B software house, Warsaw
- What it proves
- Complex technology, told in a business buyer's terms.
- My role
- Concept, content strategy, offer model, UX/UI and development.
01 · Problem
A service list is not yet a way to buy
Systems, apps, APIs, websites and maintenance describe what a supplier can do. A business buyer also needs to know where to start and what working together looks like.
02 · Decision
I turned services into engagement models
The offer was organised around responsibility and outcome, rather than the technology list alone. That lets the conversation begin with what the business needs to launch, connect or hand over for ongoing support.
PRZEKRÓJ
PRZEKRÓJ shows where the decision happens
Selecting a condition changes the whole system cross-section. You can see what happens in the device and protocol, where integration begins, and what the operator needs to see.
- 01Device
- 02Protocol
- 03Integration
- 04Operator
What I created
Complexity should be visible, not chaotic
I created the offer architecture, the layer language, the screen system and a working PRZEKRÓJ that explains dependencies without reducing them to a row of technology logos.
Why it is specific to this business
This is specific to an integration business: it shows responsibility boundaries and the flow of information between a real device and a business system.
What this means for your project
If your offer is technical, the site does not have to flatten it. It can show the dependencies while still naming the outcome and the way an engagement begins.
Tell me about your project