Skip to content
OUR APPROACH

We always demonstrate in your own branding

First a design book and a technical analysis, then a working demo. You decide afterwards.

Image for the MagicEverse way of working: from exploring to a working environment.
STARTING THE OTHER WAY ROUND

See it first, decide after

Most software projects start with a presentation and end in disappointment, because nobody along the way actually saw what they were getting. We do it the other way round. Before there is an order, we build a working demo in your colours, with your products, on its own address. You click through it, you show it to your team, and only then do you decide.

We always go for the best result, even when that means advising you against building something. A project we advise against costs us an order and saves you a year. So below you will find exactly what happens in each step, how long it takes and what you keep from it — even if you buy nothing afterwards.

THE FOUR STEPS

From exploring to keeping it running

1

Explore

We read your site, your product data and your processes. Two documents come out of that. The design book records your brand: colours with their codes, typefaces, imagery, the tone of your copy and the elements your pages are built from. Not a moodboard but a working document somebody can build from.

The technical analysis is about your current environment: what the site runs on, how fast it is, how findable it is, how security is arranged and what the five biggest weaknesses are. We also name what is good, because you rarely hear that. Both documents are yours, even if you buy nothing. Duration: a few days.

2

Demonstrate

On that basis we put a working demo on yourname-design.magiceverse.online: your branding, your products, your menu, with search, a quote list and Magic Logo where it fits. Not a picture and not a screenshot, but an environment you click through and can forward to a colleague.

Duration: usually five working days. On 20 September 2026 there are 24 such demo environments on our servers, built before any order existed. That is why we dare to make this promise: it has become routine, and we therefore know exactly where those five days go.

3

Build

The demo becomes a real environment: a sales environment, PIM, ERP, portal or agent. We bring your existing data along — products, customers, price agreements, history — and connect to what you already have. That last part is deliberate: you do not have to replace everything to start, and your bookkeeping can stay where it is.

We deliver in stages, so you keep seeing what happens along the way, and we never move a whole company over in a single weekend. With most customers the product data goes first, then the sales environment, then the price rules and then the chain into administration. A migration starts with a count: how many items, variants, images, customers and open quotes. That count sets the lead time, not the technology.

4

Keep it running

Hosting, monitoring, updates and support, plus further development: every month we look together at what could be better. Our customers call one number, even when the cause is a supplier feed — and that is usually the cause, because your environment is only as current as the feed from five in the morning.

There is a status page where you can see the state of the environments yourself, without having to call us. And because a supplier sometimes changes a feed without warning, we watch not only your environment but also what comes in. A web shop or an agent is never finished; it is maintained.

THE AGREEMENT

What you may expect from us

One point of contact

Someone who knows your business, not a ticket system in which you have to explain your own history. You get the same person on the line as last month, and they still know which price agreement was made then and why. That saves you the quarter of an hour in which you would otherwise explain again who you are and what you sell.

Short lines

What is discussed today is often ready tomorrow. We are small and here that is an advantage: there is no department between your question and the person who builds it. Large changes we plan in, small ones we do straight away — and if something does take longer, you hear it from us before you have to ask.

We say so when something is a bad idea

Even when you were willing to pay for it. A project we advise against costs us an order and saves you a year.

No promises of the earth

We would rather name a number than a promise. If there is no number, we have not measured it, and we say so.

Your data stays your data

We do not use your business data to train third-party models.

THE PROOF

What we built before there was an order

There are 24 demo environments on our servers: working sales environments in the branding of companies that had not asked us for anything yet. Each one has its own address, its own menu, its own products and, where it fits, Magic Logo built in. They exist to show what we mean, not to fill a presentation.

What you see in such an environment is what you get: the same building blocks, the same speed, the same way of working. That is why we do not ask for trust up front. You look first, you show it to your team, and after that we talk about money. The only environments we show by name are those of customers who gave their permission.

“We made this before there was an order. That way you know what you get.”
The line under every demo environment
24
demo environments on our server, built before any order existed
15
web shop environments running
74,136
products in the catalogue, with 61,693 variants
8
supplier feeds, in eight languages

Shall we build yours?

Tell us what you sell and to whom. It costs you a three-quarter-hour conversation, and you keep the design book and the technical analysis — even if you buy nothing afterwards.

Rather look around what is already up first? That works too.