SPEOS — from paper to digital, six pilot clients out of six
Six pilot clients out of six validated the platform before development. CX / UX consultant: field research, service blueprint, prototype tested with clients.
The SPEOS case study (new tab)You run a business and what you need first is a website? see the business entrance — its price is written in plain sight.
You’re launching a product. I build it and I put it online.
Website, SaaS, shop, app: a validated idea to build, or a product that already exists and has to scale.
I’m a designer, not a developer.
I build with AI assisting, and I own that: what comes out runs in production, not in a demo. The code is readable, in documented technologies, with no in-house framework, and the repository is in your name from the first line. Your future developer will open it and judge it — that’s their job. Seven live products are there to be opened before we even speak, and if you already have someone technical around you, have them read it before you sign.
Six workstreams
Identity, design, development, launch, marketing, measurement.
Identity
The name set down properly, a logo, colours, a typeface, a way of writing. You receive the source files and the exports, in your space, not mine.
Design
The journeys, the screens, and a design system that holds when you add three features the following month. The part your users never see — the one you open every morning — is designed too.
Development
A product that works, and a back office that holds as volume grows. What already exists gets plugged in rather than rewritten: accounts and sign-in, payments and subscriptions through Stripe or Mollie, catalogue, basket and shipping, transactional emails, invoicing.
Launch
Domain, hosting, backups including a restore that has actually been tested, error logging, named access. It’s online from the first phase: on launch day there is nothing left to install.
Marketing
The page that explains the product, the sign-up emails, what goes out on LinkedIn and in your newsletter. Written, not just laid out. Two channels, not six.
Measurement
Three numbers chosen before launch, not thirty after it. A month later we look at those three and decide what changes. No cookies, no advertising trackers: no banner, and numbers that blockers don’t cut in half.
Four stages
We cut
What ships first, what waits, what will never be built — and it’s written down.
We design
On your real prices and your real words. Which means I ask you for them before I design, not after.
We build
In phases. Each one ends with an address you can open in front of an investor.
We measure
Then we decide what’s next. The next quote covers the next version; if you stop there, the product still runs.
No price on the page
A landing page and a platform with accounts, payments and a back office do not cost the same. A single figure would overcharge one and undercharge the other, and you should be wary of anyone who gives you one before understanding what you’re building. Twenty minutes on a call, then a written quote within 48 hours: what we do, the phases, the timings, the firm price, the start date, the deposit and the payment schedule.
For scale, while you wait for that quote: a first publishable version is counted in weeks, rarely fewer than four. A product with accounts and payments is counted in months. The exact dates are in the quote, phase by phase.
I work alone. What if I stop?
The repository has been yours since the first line, the hosting is in your name, and you can revoke my access whenever you want. Another developer opens it and carries on: they need my files, not my permission — and you already have them.
What can be checked
Designed, coded and published here. Open them before we even speak.
-
Live · App stores soon
unfold (new tab)
Birth chart, transits and guided reading. A calm object, made for daily use.
unfold-nine.vercel.app -
Live
AtHOMI (new tab)
The family pays the subscription, the senior never pays, the carer is paid directly.
athomi-app.vercel.app -
Live
Lucida (new tab)
Decode the psychological games in a conversation and answer well.
lucida.love -
Live
Launch Your Idea (new tab)
From idea to live product: landing page, payments, dashboard.
launch-your-idea.vercel.app -
Live
MissionPilot (new tab)
Scoping, progress and delivery of client work in one place.
missionpilot.vercel.app -
Demo
WeJustice (new tab)
Clear legal guidance, written without jargon.
wejustice-demo.vercel.app -
Live
Folio — Christophe Van Engelen (new tab)
The founder’s service design portfolio: case studies and fieldwork.
christophevanengelen.com
Horizontal scrolling list. Use the left and right arrows to move through it.
Seven products I designed, coded and published, open right now: unfold, AtHOMI, Lucida, Launch Your Idea, MissionPilot, the WeJustice demo, my folio. WeJustice, a legal tech launched in 2025, has more than 4,600 pre-registrations before launch — a measure of interest, not a commercial result.
Client work
HMS Networks — three platforms merged, €2M unlocked
Three legacy platforms merged into one experience, €2M unlocked for production. Service design and UX/UI in an engineering environment: cross-team group, unified product vision, validated roadmap.
The HMS Networks case study (new tab)BNP Paribas Fortis — payment data becomes a B2B service
Léonidas committed as first client before a line of code was written. UX lead digital banking, then service design: a data MVP for SMEs.
The BNP Paribas Fortis case study (new tab)WeJustice — European legal tech, 4,600 pre-registrations
More than 4,600 pre-registrations before public launch. Partner: brand strategy, experience and a complete MVP online.
The WeJustice case study (new tab)What they say
The recommendations signed in July 2026 are on my profile.
-
A decisive role on design thinking
“At SPEOS, Christophe played a decisive role in helping our business team recognise the strategic value of design thinking.”
-
Grasping complex problems quickly
“Christophe has a real ability to grasp complex problems quickly, to put the user back at the centre and to make things move.”
-
The right stakeholders, in one room
“He quickly assessed our needs, identified the right stakeholders across departments and brought them together.”
-
UX inside an engineering culture
“He introduced UX and service design practices into a highly technical, engineering-led environment.”
-
Data turned into a value proposition
“One of his greatest strengths is turning data opportunities into concrete value propositions.”
-
Complex banking problems made simple
“He offered compelling ways to answer user needs simply, and to turn complex banking problems into clear journeys.”
-
From brand vision to execution
“Christophe can structure a brand and product vision, then turn ideas into real experiences.”
Horizontal scrolling list. Use the left and right arrows to move through it.
Questions
I pay for three months and walk away with mock-ups?
No. Every phase ends with an address you can open in front of someone — an investor, a first user, your co-founder. Mock-ups are there to decide fast and to avoid building twice; they are never the deliverable. If we stop after the first phase, you keep a live address, not a PDF.
You have other clients. When do you start?
One build at a time. The next one starts when the previous is online, so your week never depends on another client. Maintenance for my subscription clients runs alongside: short, planned, capped. The start date is in the quote.
We’re raising funds. Who owns what you produce?
You do. The contract assigns to you, use by use and on the last paid invoice, every right I hold over what I produce: design, code, copy, logo. I warrant that no third party has a claim over any of it and that nothing sits under a restrictive licence. Registering your trade mark at BOIP is a separate step: I tell you when to do it, and it’s done in your name. That’s the question you’ll be asked in due diligence, and the answer is written before we begin.
The scope will move along the way. How does that work?
The quote is split into phases, each with what it contains and its price. Whatever appears along the way goes into the next phase, priced separately, or it doesn’t go in at all. You never discover an extra after the fact.
Once it’s live, who fixes it?
For thirty days after each release, fixing what I delivered is on me. After that, two ways to work: you call me as needed, billed by the day, or we set up a monthly support retainer, priced in the original quote so you know the cost of the whole year before we start. And if you’d rather hand that to someone else, the repository is already yours.
I sell online. Who handles compliance?
Me for what gets coded: strong customer authentication on payments, the fourteen-day withdrawal journey, the mandatory notices, VAT settings for the countries you sell into. Not me for what gets written and signed: your terms and conditions are drafted by a lawyer, and I tell you when to go and see one. A shop delivered without that is a problem delivered ready-made, and that isn’t what I sell.
What you leave with
You show me what you have: a link, a deck, some notes. You hang up with your project broken into pieces — it’s yours, you can have it built elsewhere — and with a straight answer. If it isn’t for me, I tell you during the call.
Book the call
Twenty minutes, by video or phone. It’s me on the line, and it’s me who will do the work.
You’d rather email directly: cve@hi-def.be
No sales sequence, no automated follow-up.