SPEOS · environnement de production · Bruxelles
2024 — 2025
Brussels · Hybrid
Service Design case study · case 02

Installing the UX function in a postal subsidiary of the bpost group.

Freelance mission of twelve months. Large-scale document production, key accounts in banking, insurance, telecoms, energy. Mandate · lay down the Service Design method, align Business and IT, deliver a sponsor-ready Concept Report and a prioritised MVP.

Scroll · l'histoire
In 90 seconds
The problem

Belgian mail loses 8% per year. SPEOS, postal subsidiary of bpost, had to shift to digital without breaking its print revenue, and defend its leadership against cloud-native pure-players.

The tension

Business was defending revenue. IT was building Agile in parallel. The UX function did not yet exist as a dedicated department. Three worlds to bring into the same conversation.

What I did

12 internal expert interviews (CEO, CTO, R&D, Operations). 6 pilot customers interviewed, including Luminus on energy billing. Physical Customer Journey workshop, persona Johnny on the wall.

What came out of it

76-page Concept Report signed by sponsor. 6 out of 6 customers validate. Three market segments (Large Accounts, Easy2Mail SMEs, API Integrators) prioritised in SAFe sprints. Design team integrated into the org chart.

The brief

Industrial postal. A UX function to install.

At the exit · 76-page Concept Report signed by sponsor · 6 pilot clients validate the direction · 5 MVP Value Props prioritised · Shared Value Proposition Business + IT.

Freelance mission · 12 months · December 2024 → December 2025 · CX / UX / Service Design Consultant

Mandate · lay down the Service Design method, align Business and IT around the user, deliver a sponsor-ready Concept Report and an MVP prioritised in user stories. Technical context · IT in Agile transition, not yet SAFe.

SPEOS, a postal subsidiary of the bpost group. Large-scale document production for key accounts in banking, insurance, telecoms and energy. The UX function did not exist as a dedicated department.

The dedicated UX department pattern, deployed in large Belgian accounts, SPEOS chose to adopt. Catalyst · B2G PEPPOL mandate of 1 January 2026 and competitive pressure of digital-first players.

Two initiatives were under way · Archetype (E2M refactor, Angular) and Communication Platform (out of the Ethias tender, React). Same stream platform back-end. The direction sought a unified product vision · UX consultant onboarding registered in the 21 November 2024 exec review.

The proposed roadmap

How I framed the twelve months.

From Business ↔ IT friction to an MVP everyone signs. Four methodological acts, co-creation workshops as the spine, customer focus as the shared compass.

Double Diamond Design Thinking + Sprints agiles · de l'intake au product release INTAKE VALUE PROPOSITION SPRINTS · AGILE RESEARCH ANALYSE PROTOTYPE CONCEPT REPORT DISCOVER DEFINE DEVELOP DELIVER
Research
  • Internal interviews · CEO, CTO, experts 20+ years
  • External interviews · key accounts + small accounts
  • Market segmentation · 3 client segments
  • Personas at the controls · per typology
Analyse
  • Friction map Project Owners ↔ Project Managers
  • AS-IS journey · separate, messy processes
  • Could-Be journey · unified platform
  • Co-creation workshops · alignment Business + IT
Value Proposition · bridge
  • Host platform · one-stop shop
  • Onboarding driven by goal + needs
Prototype
  • Common host · unified layer
  • Specifics per market typology
  • Customisations per persona
  • User tests · 3 segments validated
Concept Report · deliverable
  • Concept report · features + wireframes
  • Prioritised user stories · MVP scope
  • UX/UI directions per persona
  • Decision pack · sponsor + steering committee

At the exit: a one-stop platform MVP prioritised in user stories, signed by Project Owners (Business) · Project Managers (IT) · Operations · Sales. Six clients across typologies validated the concept, sponsor go for production. What follows shows what played out at each step.

Discover · Observe & Understand Phase 01 · Research You are here · Diamond 1 · left half · 4 milestones
Phase 01 · Discover · internal interviews

Listen before drawing.

Management, IT, Operations, Customer Service, Production, Sales, Marketing · 20+ years seniority.

Understand how SPEOS runs its business, and what each role expects of a unified platform.

  1. 01

    The CEO

    "We stay leader, but the market is moving. Digital puts us in frontal competition."

    Market vision and competitive vigilance. Wants a product that defends the leadership position before the B2B PEPPOL mandate on 1 January 2026.

  2. 02

    The CTO

    "We have platforms per segment. They do not talk to each other."

    Fragmented historical architecture. IT freshly moved to Agile, still far from SAFe. Looks for a maintainable stack, not a patchwork.

  3. 03

    Project Owners (Business)

    "I know what my client wants. IT does not listen to me."

    On Business side, owners of the commercial offer. Frustrated by opaque technical cycles.

  4. 04

    Project Managers (IT)

    "Business changes its mind every sprint. We deliver fuzziness."

    On IT side, in charge of delivery. Frustrated by fuzzy specs, late feedback and political trade-offs.

  5. 05

    Domain experts 20+ years

    "Everything is in our heads. Nothing is documented for a client."

    Tacit knowledge of the postal/print/mailing business. Living memory of the organisation.

  6. 06

    Operations & Production

    "We absorb the misses at the end of the chain. Every day."

    The arm of delivery. Direct visibility on what breaks on the end-client side.

Phase 01 · Discover · 6 pilot clients

Six clients. Three segments.

Build-to-Mail · Easy2Mail · Channel · two accounts per segment · 22 questions, 6 themes

Internal experts read the organisation. Clients read the service as they live it.

The same six return for the final user test.

See the customer interview guide used Customer Interview Guide · 22 questions · 6 themes (Background · Customer Journey · Pain Points · Automation · Billing · Recommendations)
Phase 01 · Discover · competitive benchmark

Three market segments. Three buying logics.

3 segments identified · Large Accounts (Build-to-Mail) · SMEs (Easy2Mail) · Integrators / Resellers · competitors observed in parallel (Easypost, Doccle, European digital mail platforms).

Three distinct buying logics. Large Accounts buy complex solutions with high compliance. SMEs buy standard, low-touch, autonomy. Integrators buy an API and documentation. One platform must serve the three without drifting.

Segment 01 · Build-to-Mail

Large Accounts

Signature · complex solutions, high compliance

  • Banks, insurance, telcos
  • Massive volumes, end-to-end customised journeys
  • High compliance standards (GDPR, traceability)
Segment 02 · Easy2Mail

SMEs & professions

Signature · standardisation, automation, self-service

  • Lawyers, unions, medical practices, SMEs
  • Low volumes, need for immediate autonomy
  • High digital adoption potential
Segment 03 · Channel

Integrators & resellers

Signature · partners, embedded SPEOS services

  • Domain integrators who distribute the SPEOS services
  • API and white-label as entry conditions
  • Growth lever beyond the historical key account
Phase 01 · Discover · personas

Eight archetypes. Two illustrative personas.

Synthesised from the internal and field interviews. The map that prioritises the MVP, who we speak to and at which point in the cycle.

01

IT & Operations Manager

The multichannel pivot. Wants automation, clean APIs, a shorter time-to-market.

02

Finance Team

Billing, e-invoicing, B2B/B2G compliance. Tolerates zero errors on invoice routing.

03

Production Coordinator

Print and enveloping logistics. Holds the day-0 SLA, balances auto and human.

04

Large Account Decision-Maker

The KEY · bank, insurance, telecom. Renews, escalates, signs. Aligns the vendor on his business goals.

05

SME · Small Business Owner

The volume KEY · Easy2Mail. Wants standard, low-touch, IT-less onboarding.

06

Niche Professional

Lawyers, doctors, property managers. Highly specific workflows, non-negotiable confidentiality.

07

Marketing & BI Manager

Optimises per channel and per preference. Wants actionable data, not a dump.

08

Integrator & IT Partner

Embeds SPEOS in his offer. Stable APIs, clear doc, no integration friction.

Deep-dive · 2 illustrative personas

Out of the 10 field-tested, two that speak out loud.

01
Nicolas · 45

Document Operations Manager · large Energy account

"A good tool is invisible when everything works, and clear when something breaks."
  • Post-send black box · no visibility after sending
  • Drops on >10k volumes · system fails at high volume
  • Slow morning support · no one before 8am, while his batches leave at 5:30am
  • Generic errors · blind debug, no actionable message
02
Moustafa · 62

Print & Archiving Expert · large Energy account

"Not a cool product. An ultra-reliable cockpit to pilot his documents."
  • Black box · dependency on an intermediary for every debug
  • 5:30am anxiety · support unreachable when it crashes
  • Blocking batches · no partial reprocessing of a failed file
  • Slow changes · even for a logo or template, it takes weeks
Discover · Define Phase 02 · Analyse You are here · Diamond 1 · right half · 4 milestones
Phase 02 · Define · AS-IS Customer Journey

An end-to-end journey. Ten frictions mapped.

End-to-end journey. Ten pain points pinned where they block. Shared language across departments.

Customer Journey Map d'atelier · persona Johnny · stickers de pain points et d'opportunités placés sur les 5 phases du parcours par les parties prenantes Business + IT + Operations
The original artefact. Persona Johnny in the centre, pain point and opportunity stickers placed in workshop by all stakeholders. This wall replaced the PowerPoint slides as the shared language.
See the full SPEOS Concept Report Speos Concept Report 2024 · 76 pages · AS-IS Customer Journey + 10 mapped pain points
Pain Point 01

"Onboarding takes us months."

Became a design rule: automate onboarding. Self-service guided by goal and needs.
01Time-to-Market
Pain Point 02

"Everything goes through manual workflows."

Became a rule: standardise the base, customise the last mile per persona.
02Automation
Pain Point 03

"The client has to call us for the smallest change."

Became a rule: one-stop client portal with real-time tracking + self-service actions per persona.
03Autonomy
Pain Point 04

"Our tools do not talk to each other."

Became a rule: common host platform, customisations per typology on top.
04Fragmentation
Pain Point 05

"We learn about problems from the client."

Became a rule: proactive monitoring, alerts on client and SPEOS side, push communication before the client asks.
05Proactivity
Pain Point 06

"Our digital offer does not match the competition."

Became a rule: close the gaps through the one-stop portal + API opening for the Integrators.
06Digital gaps
Pain Point 07

"Once in production, no one touches it any more."

Became a rule: modularise the offer. Every feature configurable independently, without rebuilds.
07Rigidity
Pain Point 08

"The market moves faster than our offer."

Became a central argument: the VP must defend leadership AND open a new market segment.
08Competition
Pain Point 09

"Billing is opaque for our clients."

Became a rule: readable billing in the portal, breakdown by line item + consumption dashboard.
09Billing
Pain Point 10

"We stay glued to our historical accounts."

Became an MVP argument: capture SMEs through Easy2Mail and the Integrators channel through APIs. No more relying on mail as a crutch.
10Expansion
Phase 02 · Define · 11 opportunities

From pains to chances.

10 pain points reframed as 11 opportunities. Five become MVP Value Props, six placed in MVP++ phase 2.

  1. 01

    Enhanced Customer Experience

    Self-service, real-time tracking, personalized dashboards per segment.

  2. 02

    Automation & Scalability

    Automate repetitive tasks, API integrations, self-onboarding for SMEs.

  3. 03

    Multi-Channel Integration

    Email, SMS, print unified. Automatic fallback if a channel fails.

  4. 04

    Data-Driven Insights

    BI reporting, client behaviors analysed, sector-specific insights.

  5. 05

    Flexible Pricing Models

    Tiered Basic / Gold / Custom. Pay-as-you-go or subscription for SMEs.

  6. 06

    Market Expansion

    Multi-language, multi-jurisdiction, country-by-country B2G compliance. MVP++.

  7. 07

    Proactive Customer Engagement

    Predictive analytics, proactive alerts before the client calls.

  8. 08

    Standardization with Flexibility

    Reusable templates + modular add-ons for Large Accounts.

  9. 09

    Innovation in Product Offerings

    Consent management, drag-and-drop builders, payment integrations.

  10. 10

    Unified Client Portal

    Tracking + billing + reporting + ticketing in one portal. Open API marketplace.

  11. 11

    Competitive Differentiation

    Advanced analytics, fallback mechanisms, "One Stop Shop" positioning. MVP++.

Phase 02 · Define · co-creation workshops

The shared language. In workshop, not in canvas.

Two regimes · small targeted workshops with IT Project Managers for technical trade-offs, large Customer Journey workshops with Business, IT, Operations and Customer Service. Four formats, four deliverables.

  1. 01

    Cross-department empathy mapping

    Project Owners and Project Managers at the same table. Each team builds the empathy map of a client persona, then confronts its reading. Immediate effect: people discover they talk about the same user, not the same contract.

    Output: 6 consolidated empathy maps · shared user language.

  2. 02

    Customer Journey workshops

    Rebuild the end-to-end journey with the real internal actors (sales, ops, support, IT). Each touchpoint is validated by whoever owns it. Pain points come out in conversation and get pinned on the wall.

    Output: 5-phase journey · 10 pain points mapped · clear ownership per step.

  3. 03

    "How might we" sessions

    Each pain point is reframed as an opportunity. The teams vote on the "how might we" worth an MVP. No debate on the canvas, focus on the prioritised action.

    Output: top 12 HMW · impact / effort scoring · VP backlog.

  4. 04

    VP synthesis workshop

    The final workshop that condenses previous outputs into a single VP statement. Everyone defends, adjusts, signs. Out of the room = VP shared by IT + Business + Innovation.

    Output: VP in one sentence · alignment signed · go for Diamond 2.

Phase 02 · Define · methodological choice

Why these tools, here.

At SPEOS I didn't start with a Lean Canvas. I started with a Stakeholder Map and a Customer Journey AS-IS. Context dictates the tool, not the other way round. An early-stage organisation in digital transformation needs to see before it imagines. A Value Proposition crystallises after observation, not at the start of a session.

The initial pitch · why a UX department

Classic vs Best Practice.

Dimension Classic approach Best Practice (large Belgian accounts · banking, energy, telecoms)
Business (ROI) Define needs. Work with UX to define expectations.
IT (Technology) Implements solutions. Focus on architecture & delivery.
UX (Users) Rare or integrated into IT. Dedicated, cross-functional, strategic department.
At the end of diamond 1

Everything converges on a single VP.

Four Discovery + Analysis inputs converge into one sentence, not into a canvas.

Diamond 1 · crystallisation Value Proposition · pont

Not a platform per segment that multiplies entry doors. One one-stop host, with persona-driven onboarding, API-ised capabilities, print and digital without seams, ready for tomorrow's compliance demands.

The value contract

A platform is not five entry doors.
It is an orchestration that tunes itself to the persona in front of it.

Before · POs wanted features, PMs a stack, clients five logins. After · an orchestrated host · 10 pains → 5 MVP deliverables + 6 MVP++.

01

The posture

Not a platform per segment. An orchestrated platform.

  • Not 5 products with 5 logins, 5 back-offices, 5 supports.
  • One one-stop host with onboarding driven by persona and typology.
  • API-ised capabilities shared by the 3 segments below.
  • Print and digital without seams, automatic multi-channel fallback.
  • Compliance ready for tomorrow's B2G requirements.

Source · SPEOS Concept Report 2024 · slide "VP statement" verbatim

02

The 2 personas who decide

10 field-tested personas · 8 synthesised archetypes. Here are 2 of them, as illustration.

  1. 01

    Nicolas · 45 · Document Operations Manager · large Energy account
    "A good tool is invisible when everything works, and clear when something breaks."

  2. 02

    Moustafa · 62 · Print & Archiving Expert · large Energy account
    "Not a cool product. An ultra-reliable cockpit to pilot his documents."

Three shared jobs-to-be-done: take back control, reduce blind spots, have tools tuned to their hours (support from 5:30am) and their compliance stakes.

03

10 pains → 11 chances → 5 MVP VPs

The verbatim mechanics of the Concept Report. The 10 pain points produce 11 opportunities; 5 are scoped MVP, 6 placed MVP++.

10 Pain Points 5 MVP VPs delivered
1. Time-to-Market DelaysVP 01 Onboarding · IT-less
2. Lack of AutomationVP 01 Onboarding
3. Customer AutonomyVP 02 Monitoring · real-time
4. Tool ComplexityVP 03 Reports & Archives
5. Lack of ProactivityVP 02 Monitoring
6. Gaps in DigitalVP 03 Reports
7. Service RigidityVP 05 Support · self-service
8. Competitive PressureVP 02 + VP 05
9. Billing ComplexityVP 04 Billing · tiered
10. Expansion Challengesplaced in MVP++

MVP / MVP++ scope. 5 MVP deliverables cover the 6 phases of the Customer Lifecycle. The Market Expansion and Marketplace API Integrators opportunities are scoped MVP++ phase 2, post one-stop host validation.

Project Owners, Project Managers, Operations and Sales share the same sentence. Shared foundation signed. Arbitration moves from "what" to "when".

Logical next Ideation · Develop · 2 directions explored, one retained Ideation · 2 directions, une retenue
Develop · co-creative workshops · exploring directions Phase 03 · Ideation You are here · Diamond 2 · left half · Develop
Phase 03 · Develop · 2 directions explored

Two directions explored. One retained.

Two paths out of the workshops. Silo · each product with its own login, shipped in 6 months but reproduces fragmentation. One-stop · orchestrated host, persona-driven onboarding, API-ised capabilities, dev time doubled. Sponsor picks the second · tiered pricing opens the SME segment left to competitors.

One door per product

Silo as-is

Five siloed apps, five logins, five supports. The client juggles, IT maintains five stacks, Business sells five products instead of a platform. Fastest to ship, but reproduces the fragmentation pointed at by the 12 expert interviews.

One-stop platform

One-stop platform

One entry door. Onboarding recognises the persona, their role, their channel. Five Value Props cover the ingest · compose · distribute · archive cycle. IT maintains one stack, Business sells one platform.

Not a suite of products each with its own door. One orchestrated host, driven by persona and need typology.

Phase 03 · Develop · 5 Value Props prioritised MVP

From the document pipeline to the 5 Value Props.

Canonical pipeline · ingest → compose → distribute → archive. Five priority Value Props on that skeleton · Onboarding · Monitoring · Reports & Archives · Billing · Support.

Five Value Props forming a single experience loop. The client enters through onboarding, monitors continuously, archives proofs, pays for what they consume, and resolves incidents in self-service. The cycle loops back on the next product, the next volume, the next channel.

MVP++
6 OPPORTUNITÉS

Market Expansion · Marketplace API

Multi-langue · multi-juridiction · B2G pays par pays

Phase 2 · roadmap 2026-2027
Phase 03 · Develop · 4 Value Props MVP

Cinq promesses, une seule plateforme.

De dix points de friction à cinq leviers défendables.

01

Démarrer sans passer par l'IT.

Self-onboarding piloté par persona & typologie de besoin.

Voir VP 01 →
Onboarding
02

Voir les flux en direct.

End-to-end visibility · proactive alerts · fallback multi-canal.

Voir VP 02 →
Monitoring
03 · 04

Tracer, archiver, facturer juste.

Audit-ready by default · pricing tiered transparent.

Voir VP 03 + 04 →
Reports & Billing
05

Résoudre sans appeler.

Portail self-service · knowledge base intégrée · ticket asynchrone.

Voir VP 05 →
Support
Phase 03 · Develop · VP 01 · Onboarding

Start without going through IT.

Value Proposition · verbatim Concept Report

Our IT-less onboarding helps Customer Account Managers who want to onboard new clients quickly, by removing IT dependencies and accelerating time-to-market.

  • 01

    Self-service capabilities

    The client configures and monitors campaigns on their own, without an IT ticket. Source: Concept Report · Opportunity 1 · Enhanced Customer Experience.

  • 02

    Persona-driven dashboards

    Tailored views for Large Accounts, SMEs and specific sectors (Finance, Operations, BI). The wizard knows who is in front of it.

  • 03

    Self-onboarding for SMEs

    Simplified process for small structures. Source: Concept Report · Opportunity 2 · Automation & Scalability.

See the original slide Speos Concept Report 2024 · VP 01 Onboarding · Value Proposition verbatim
Phase 03 · Develop · VP 02 · Monitoring

See the flows live.

Value Proposition · verbatim Concept Report

Our real-time monitoring helps Operations and Business teams who want to trace document flows with confidence, by providing end-to-end visibility, proactive alerts, and by reducing risks and support dependence.

  • 01

    End-to-end visibility

    The ingest → compose → distribute pipeline is made observable step by step. No more calling Customer Service to know where a sending stands.

  • 02

    Proactive alerts

    The system flags the incident before the client notices. Source: Concept Report · Opportunity 7 · Proactive Customer Engagement.

  • 03

    Automatic multi-channel fallback

    If the digital channel fails, print fallback in one click. Source: Concept Report · Opportunity 3 · Multi-Channel Integration.

See the original slide Speos Concept Report 2024 · VP 02 Monitoring
Phase 03 · Develop · VP 03 + VP 04 · Reports & Billing

Trace, archive, bill right.

Value Proposition · verbatim Concept Report

Our Reports & Archives help Finance, Compliance and Operations teams who need to master costs, guarantee traceability and stay compliant, by delivering structured reports, centralised archives and audit-ready proofs, accessible in a single place.

  • 01

    Audit-ready by default

    Every flow generates its proof at source. eIDAS trusted service. B2G PEPPOL compliance for the Belgian mandate of 1 January 2026.

  • 02

    Transparent tiered pricing

    Basic / Gold / Custom tiers. Pay-as-you-go or subscription for SMEs. Source: Concept Report · Opportunity 5 · Flexible Pricing Models.

  • 03

    Flow ↔ invoice reconciliation

    Every invoice line points to its source batch. Finance Teams stop reconciling CSVs. Source: Pain Point 9 Billing Complexity.

See the original slides Speos Concept Report 2024 · VP 03 Reports & Archives + VP 04 Billing
Phase 03 · Develop · VP 05 · Support

Resolve without calling.

Value Proposition · verbatim Concept Report

Our integrated support platform helps operational users handling critical flows (documents, invoices, mailings), who want more autonomy, visibility, and faster resolution of their technical incidents, by offering a self-service portal with ticket creation, real-time tracking, SLA priorities and direct access to the tech teams when needed, unlike traditional models that rely on slow, manual processes and human bottlenecks.

  • 01

    Self-service portal

    Ticket creation, live tracking, knowledge base per persona. The user resolves first, escalates if needed.

  • 02

    Structured 3-tier escalation

    Tier 1 self-service · Tier 2 SPEOS support on SLA · Tier 3 Engineering access. The human bottleneck becomes an escalator.

  • 03

    Unified ticketing cross-VP

    A single portal for onboarding, monitoring, billing, archives. Source: Concept Report · Opportunity 10 · Unified Client Portal.

See the original slide Speos Concept Report 2024 · VP 05 Support
Phase 03 · Develop · MVP++ horizon 2026-2027

After the one-stop host, the ecosystem.

Two capabilities identified in Discovery, placed outside the MVP. They only wait on host consolidation to activate. Source: Concept Report · Opportunity 6 (Market Expansion) + Opportunity 11 (Competitive Differentiation).

01

International expansion

Multi-language, multi-jurisdiction, B2G compliance country by country. The API stack and tiered pricing make expansion economically viable, where dependence on Belgian paper volume capped it.

02

Marketplace API · Integrators

The 3rd Concept Report segment, Integrators and Resellers, embeds the Value Props in their own offer. The marketplace exposes the APIs, docs and partner pricing. Growth through leverage.

Roadmap horizon 2026-2027 · post-MVP rollout
Phase 04 · Deliver · user test 6 pilot clients

Six clients. Three segments. A pre-validated go.

6 / 6 validate the one-stop direction · Combined score 4.03 / 5 · NPS 9 / 10

Concept Report presented to the six pilots. In parallel, two Energy personas · Moustafa and Bogdan · test three prototype scenarios.

  • 6/6 Clients tested across 3 segments
  • 4,03/5 Validate the one-stop direction
  • 9/10 Luminus reference · sponsor go production
01

Real-time Dashboard

Combined score 4.4 / 5 — 88%

  • Moustafa · 4.0 / 5 · Simplicity, usefulness, relevance, quality validated
  • Bogdan · 4.8 / 5 · NPS 9/10 on the scenario
  • Scenario · submit a large batch via SFTP, follow processing live
02

Error Handling

Combined score 4.1 / 5 — 82%

  • Moustafa · 3.7 / 5 · Low reassurance (3.0) on the quick decision
  • Bogdan · 4.5 / 5 · Maximum simplicity and quality
  • Scenario · an isolated rejected file, reprocess, replace without blocking the batch
03

Audit Trail / Traceability

Combined score 3.6 / 5 — 72%

  • Moustafa · 3.2 / 5 · Reassurance at 1 / 5 on legal proof value
  • Bogdan · 4.0 / 5 · NPS still 9/10, but area to refine
  • Scenario · produce a proof of submission to a legal department two weeks after sending

The six pilot clients in directional validation

Build-to-Mail

Luminus

Energy · large multichannel volume · strong validation on orchestration and audit-ready. The reference that reassures the sponsor.

Build-to-Mail

Large Account · regulated sector

B2G compliance + multi-language. Validation on conformity, expansion request in phase 2.

Easy2Mail

SME · property manager / specialised profession

Moderate volume, confidentiality demand. Strong validation on IT-less onboarding.

Easy2Mail

SME · liberal profession

Validation on tiered pricing and readable billing. Pay-as-you-grow requested.

Integrators

IT integrator · Belgian reseller

Embeds SPEOS in its client offer. Top request: marketplace API and partner documentation.

Integrators

IT integrator · ERP partner

API validation. Reproducible with their own ERP clients, leverage effect identified.

Six clients out of six validate the direction before development. The sponsor decides go-production based on the Concept Report and the SUPERQ test — combined score 4.03/5, NPS 9/10.
The sponsor tipping moment Concept Report · livrable

Nothing left to imagine. The sponsor sees where he invests, and six clients tell him yes.

The post-DD deliverable
76
structured pages

CEO, CTO and teams have everything they need to decide together.

  1. 01 Introduction
  2. 02 Stakeholder Map
  3. 03 Segmentation & Personas
  4. 04 Journey AS IS vs TO BE
  5. 05 GAP Features · Goals · Questions
  6. 06 Value Proposition
  7. 07 User Stories
  8. 08 Concept
  9. 09 ULab Insights
  10. 10 Prototype
  11. 11 Next Step
Open the full document Speos Concept Report 2024 · full PDF 76 pages
Stakeholder Map · Alignment

How Business and IT ended up speaking the same language.

Business Project Owner wanted sellable features, IT Project Manager a maintainable stack, Project Lead arbitrated the schedule. Two workshop formats bridged it · small IT workshops, large Customer Journey workshops.

Project Owner · Business

"Which growth driver?"

AvantThe print rent erodes while pure players capture SMEs.
AprèsMultichannel Value Proposition + tiered pricing. Expansion opened, SME segment recaptured.
Project Manager · IT

"We can build tomorrow."

AvantUrge to code before aligning. Five disconnected systems to orchestrate.
AprèsAS-IS Customer Journey built on the 12 expert interviews. 10 Pain Points mapped before any MVP line.
Project Lead · arbitration

"The 2026 deadline does not move."

AvantHolding the timeline against the wish to do everything.
AprèsMVP scope cut at 5 Value Props. The rest placed in phase 2. Written decision, not a fuzzy compromise.
UI & UX · validation

"And the experience?"

AvantExperience stays unthought when we slice by feature.
AprèsPersona-driven onboarding + tests at 6 pilot clients. Sponsor signal secured. Luminus among them.
When the four roles saw the same six pilot clients at the centre, the project became everyone's platform. No more debate on "if", arbitration on "when".
The artefact that tipped it

The same Value Proposition. Business side, IT side.

Business and IT described the same product with two vocabularies. The sentence below came out of both sides, word for word.

Business wanted

"A recurring revenue channel on the key accounts, with possible expansion to SMEs via a simpler onboarding."

IT wanted

"A platform with a single production layer and clean API-isation, to avoid building the same integration twice."

What they ended up saying together

"A one-stop platform with persona-driven onboarding, opening SMEs without destabilising key accounts, on a single production layer with public API."

That sentence ended up on the cover of the Concept Report. No arbitration questioned the direction afterwards.

The arbiter of every decision

Customer · Business · Tech. The triangle that rejected the false leads.

The platform only held if all three vertices won. An idea where two won and one lost was set aside. No compromise, no middle ground. Three criteria, not an average.

  • Customer · 3 segments

    One door, not five.

    Large Accounts (built2mail), SMEs (easy2mail), Integrators. Three segments, three entries into the same platform. Persona-driven onboarding, self-service autonomy, audit-ready by default. The client stops juggling between apps.

  • Business · SPEOS Group

    New segment captured, position defended.

    Tiered pricing opens the SME segment left to agile competitors. The seamless print and digital multichannel frees SPEOS from paper-volume dependence. The compliance leadership position consolidates as the 2026 B2B mandate approaches.

  • Tech · IT & Engineering

    One stack, not five.

    Orchestration replaces the inherited silos. API-isation per layer, observable pipeline, automatic fallback between channels. IT maintains one platform, no longer five inherited debts.

Any idea that didn't validate the three vertices was set aside. Three criteria, not an average.

At the end of the journey

Not an intention. A platform ready to scale.

Concept Report signed by sponsor. Six pilot clients validate. Prioritised Value Props roadmap, ready in SAFe sprints. Written production decision.

  1. 01

    No longer dependent on the rent alone.

    The seamless print and digital multichannel frees SPEOS from paper-volume dependence. Pricing per channel and per typology becomes manageable, where the structural 8 percent yearly drop in Belgian mail would have made it untenable.

  2. 02

    New market segment captured.

    The easy2mail tier (SMEs, pay-as-you-grow) and the marketplace API (Integrators) open two segments left to agile competitors. The PEPPOL mandate on 1 January 2026 catalyses demand on the Belgian mid-market.

  3. 03

    Market leadership defended.

    Against digital-first players targeting SMEs and international players targeting line-of-business SaaS, SPEOS remains a B2G compliance pioneer and scales through API leverage. Position consolidated, not eroded.

Integrity note. Concept Report delivered and validated. Rollout moved into Agile sprints on the SPEOS side. What I claim stops at the exit: 76-page deliverable, six aligned clients, Customer · Business · Tech triangle in the green.

What SPEOS taught me

Three levers I would replay.

Six months after delivery, three choices still hold. Nothing to replay differently. Design found its place in the workflow and in the org chart.

01

The toolkit, not the school.

Strategyzer, Customer Journey, Service Blueprint, Design Sprint are tools from the same Design System. Mastery is not picking one. It is knowing which, when, with whom in the room. On SPEOS, the AS-IS Customer Journey and Pain Points had the right ratio of narrative and precision to align Business and IT.

02

Enter via Business, install with IT.

The sponsor hired me on the Business side to defend a new revenue line. But the Value Proposition only held if IT saw a maintainable stack in it. Come in through the Business story, validate every trade-off with the tech lead before the workshops: that is the pattern that avoided the 'very nice, not implementable'.

03

Show don't tell. The artefact beats the slide.

At every tension, moving from argument to artefact unblocked the conversation: the journey map on the wall, the wireframe in hand, the pain point quoted in a customer's own words. The sponsor does not buy a method. He buys a validation signal. The toolkit exists to produce the artefact that makes the invisible visible.

Postscript · references

Anyone I worked with on SPEOS, from CEO to tech lead, can vouch for it. That is the matter of Service Design: people who call you back.

Christophe van Engelen · Service Designer · Brussels
Other case

BNP Paribas Fortis · Enterprise Intelligence

A different mission, a different toolkit. Lean Canvas and Value Proposition Canvas for a mature bank, all the way to a signed purchase commitment from a pilot customer.