Project enquiries and support · Brussels

Tell us what needs building

The fastest way to start is a short message describing the problem, not the solution. What is being done manually today, what system it has to work with, and roughly when you need it. We reply with questions, and if it looks like a fit, we propose a scoping conversation.

Replies land in a small number of working days. Belgian working hours: Monday to Friday, 9:00 AM – 6:00 PM.

Blueprint-style drawing of the studio intake desk with a correspondence tray, loose sheets and copper boards under north daylight

The intake window

A short description of the problem is enough to begin.

Reach us directly

Phone or email, whichever suits the thread

If the project is urgent, calling is faster. If it needs a written trail, email is better — particularly when several people on your side need to see the same thread.

Studio location

Uitbreidingsstraat 32, 1050 Elsene — the studio sits a short walk from the Elsene tram lines.

What to include

A few lines carry further than a long brief

Whether you are replacing a manual process or starting a new build, these are the details that let us answer honestly. Send what you already have; if a specification or a design does not exist yet, that is normal and not a problem.

The process today
What is being done manually, by whom, and how often — the manual path the new app would replace or take over from.
Systems it touches
Any software the app has to connect to — accounting, CRM, an internal tool — and who on your side owns it.
Devices
Whether it needs to run on phones, desktops, or both. We build all three, and that choice drives the stack conversation.
Any date you hold
A launch, a season, a contract deadline — even a soft one helps us tell you early whether the timing is workable.
What already exists
A specification, a design file, a prototype, a rough sketch on paper — send any of them; we will read what you have.
Budget signal
Not a number you must commit to — an order of magnitude is enough for us to steer the stack and the first release towards it.

Project intake

Send it straight to the studio inbox

The form collects your name, email, company and a description of the project. It goes to the studio inbox and is read by a developer, not filtered by a sales team. We do not sell or share form submissions.

The privacy policy explains how the information is handled in more detail — Privacy Policy.

Support and existing applications

If you have a live application that needs maintenance or repair, include the platform it runs on, roughly when it was built, and where the code currently lives. Taking over an existing project starts with a review of the codebase and the release setup. Sometimes the answer is to continue with it; sometimes it is a rebuild, and we will say which.

Intake · read by a developer

A short paragraph is enough. We will ask questions if something is missing.

Or call the studio during Belgian working hours to talk it through.

After you send it

A reply, then a real conversation

You get a reply within a small number of working days. It will contain questions, because the first message rarely has enough detail to estimate anything honestly. If the project looks like a fit, the next step is a scoping conversation, which can happen remotely or at our office in Brussels.

Request a scoping call

1

Day it lands

It reaches the studio inbox and is read by a developer — no queue, no sales filter.

2–3

Working days

A reply with questions. The first message rarely carries enough detail to estimate honestly, so we ask before we guess.

3

Scoping, then a plan

If it looks like a fit, a scoping call — remote or in Brussels — then time-and-materials working with a first release you can see moving.

Questions before you write

Things people ask first

If your question is not here, send it with your message and we will answer it in the reply.

Do you charge for the first conversation?

No. The initial exchange is a conversation about whether the project fits, and neither side is committed by it.

Do you sign NDAs?

Yes, if you need one before describing the project. Send yours, or ask and we will use ours.

Can you work with a specification we already have?

Yes. We will review it and tell you where it is thin, which is usually in the error states and the exceptions.

What if the app already exists and is failing?

Include the platform, roughly when it was built and where the code lives. We start with a review of the codebase and the release setup, then say plainly whether to continue with it or rebuild — and why.

The fastest way to know whether Eclipse Holdings Group fits is to describe what is not working yet.

Eclipse Holdings Group · Uitbreidingsstraat 32, 1050 Elsene, Brussels · +32478978211 · [email protected]