DIGITAL SOLUTIONS & AI IN LIÈGE

Digital solutions & AI

Your needs.
The right tools.

I develop bespoke software to organise your information, track your activities and simplify tasks. Business interfaces, applications, AI assistants or automation: every solution starts with the way you work and the approvals you need to retain.

A practical use.
A suitable tool.

Your information

A defined workflow

Your approval

THE INTENTION

Start with a use case,
build the right solution.

We begin with a practical task: what data should be used, what action should be prepared and who approves the result? This helps us choose between a form, a dashboard, an assistant or a connection between applications. I clarify the technical possibilities and operating requirements before implementation, so the tool has a clear place in your day-to-day organisation.

Here, AI is used to process information, automate tasks and assist with programming. My graphic design process remains entirely human: I do not generate logos or visual identities using AI.

Illustrative example · Fictional data

Track a project from brief to production.

I work on tools that connect sales tracking, design and production. The aim is to recover a project’s context, identify what is missing and prepare the next step. The demonstration below uses fictional data only and illustrates a possible workflow.

A project moves forward on several fronts.

A quote may be awaiting a response while files still need preparation. A print proof must be approved before production begins. How can one tracking system make these stages clear without mixing them up?

One shared view. Distinct stages.

A project record can distinguish sales tracking, design and proof approval, production, delivery and invoicing. A next action and any blocker complete the picture. The workflow is defined around the needs and available tools.

01
Gather
Describe the need and bring the useful information together in one project record.
02
Assess
Distinguish the progress of the quote, design and production, then identify what is missing.
03
Approve the next step
Define the next action and retain the necessary approvals, including proof approval before production.

How it could work

Three entirely fictional projects, with no client data. This illustration does not provide access to the application.

An identity to develop

Sales: Accepted
Design / proof: Design in progress
Production: Not scheduled

Next action: Prepare an initial proposal and the materials to present.

The design choices still need approval.

Printed materials to finalise

Sales: Accepted
Design / proof: Awaiting approval
Production: Not scheduled

Next action: Obtain print proof approval before production.

No manufacturing is shown as having started.

Signage to prepare

Sales: To be estimated
Design / proof: Incomplete brief
Production: Not scheduled

Next action: Clarify the dimensions, materials and site constraints.

The scope and estimate still need confirmation.

A role for AI: prepare a useful overview.

Possible uses include finding information, summarising a project’s status and preparing points to check. Suggestions must be reviewed before any action.

A principle to adapt. This demonstration illustrates a possible use. Feasibility, prototyping and testing must be defined around the need; the example makes no claim to be a working production system.

Possible integrations, access, subscriptions, any API costs and support are assessed for each project. Human approvals are defined before the relevant actions.

THE POSSIBILITIES

What we can create.

Bespoke software

Configurators, dashboards, management applications and forms: interfaces organised around the information and workflows specific to your business.

AI assistants

Assistants that search, summarise or prepare content using agreed sources and instructions, with the necessary human approval steps.

Connections & automation

Links between compatible applications to carry out agreed sequences of tasks. Triggers, access, limits and any follow-up are defined for each solution.

A SHARED METHOD

From need to delivery.

Describe the actual work

We look at a task, the data it uses and the software involved. We identify the actions to simplify and the decisions that should remain under human control.

Check & prototype

I check the integration options and propose a workflow. A prototype or an initial user journey lets us test the solution against real use cases.

Test & hand over

We test the planned steps and relevant failure cases. Onboarding, operating requirements, subscriptions and support are defined according to the chosen solution.

YOUR QUESTIONS

Before we start.

Can any applications be connected?

The options depend on the interfaces available, access permissions and the plans offered by the software providers. I check compatibility before defining an integration or automation.

Can AI act without approval?

The level of autonomy is defined for each use case. We distinguish between research, preparing a result and taking an action, then place the necessary human approvals before the relevant steps.

Will subscriptions and ongoing support be needed?

This depends on the chosen tools and how they operate. Any accounts, subscriptions, hosting and support requirements are identified in the proposal; no subscription is started automatically.

OTHER NEEDS?

LET’S DISCUSS YOUR NEEDS

Let’s prepare
your quote.

A few details to help shape a proposal for your project.

USEFUL INFORMATION

The task or problem to address
The software and accounts you already use
The data and its sources
The actions needed and human approval steps
How often the tool will be used and any operating constraints