Skip to content
i

DZ IT STRATEGY

Advisory · Design · Delivery · AI training

IT engineering, from strategy to production

Projects supported end to end: scoping the real need, designing it, shipping it to production, training the teams who will use it. AI is a production lever here, never a sales argument.

Twelve years of software engineering and six years of IT strategy advisory for SME executives. A vague business need becomes a costed scope, then a tool running in production, then a skill the team owns. For the past two years, AI has multiplied what fits inside a given deadline: that is what DZ IT STRATEGY demonstrates and teaches, with measurements to back it.

See the work Get in touch

Work

Client work

Projects delivered and running in production, at real companies.

Bar Su Cuile (Sardinia, Italy) · 2026

1 recorded demonstration

A menu reachable by QR code in the languages of his customers, and a back office designed so the owner publishes it himself, with no agency in the loop and nothing to break.

BE MOBILITY, bemobility.fr · 2024

Site designed, hosted, secured and maintained. And the director briefed on real threats: a secure site behind a weak password is not secure.

SMO Solar Process

SMO SOLAR PROCESS, · 2022-2026

An engagement that began with a detailed audit of what was already there, before a single line was written. The delivered site ran for several years without intervention.

Sales enablement

Equipping a team that sells: the data cleaned up, the call script given structure, the time handed back to the reps.

BDD CleanUP

Engagement, sales team · 2026

63,634 rows analysed in 18 seconds, without ever touching production data, and a false positive rate brought down from 76 % to almost zero over two documented passes.

The call script tree editor

Business development · 2026

A call script is not a text to read out: it is a tree of possible answers. Here the outline is drawn as linked bubbles, and unfolds during the call without taking your eyes off the conversation.

The Gantt generator

Business development · 2026

A prospecting campaign is run like a project: who does what, on which day. The schedule is generated from the task list, instead of being redrawn by hand on every change.

The prospect search filter

Business development · 2026

Sorting a prospect list by eye has to be redone for every new list. Here the criteria are written once: off target profiles are set aside, the rest come to the front.

In-house products

Tools built for internal needs, which show what is achievable for yours.

ClaudeManager

Proprietary product · 2026

Running several AI agents in parallel, unsupervised, with the guardrails that make such autonomy acceptable in the first place.

Suite LTSC+ / Windows OS MAX

DZ IT STRATEGY offering · Since 2022

A clean, fast, hardened and reproducible Windows that installs itself. Plus a recovery promise: back at work within the hour after a failure.

DZtools

Proprietary ecosystem · Since 2022

Shortcut managers, widgets, system control by mouse: around sixty portable utilities that run from a USB stick, with no installation and no administrator rights.

DZNav

Proprietary product · 2026

The menu on this site is a product: it knows where you are in the page, folds away at the visitor's choosing, and installs on any site without writing a line of code.

This domain no longer exists

smosolarprocess.com

smosolarprocess.com was not renewed. The site disappeared along with the domain name; the delivered work itself ran in production for several years.

A domain name is a yearly deadline and an invoice for a few euros. Two things that slip through the cracks as soon as whoever handled them changes job, takes leave at the wrong moment, or leaves the company. By the time anyone notices, the name is free, and sometimes already taken by somebody else.

This is administration that can be taken over, indefinitely.

  • Domain + hostingThe name and the site stay online.
  • Domain onlyKept, simply redirected (parking).

Renewed yearly, or a multi-year deposit with a reminder before it runs out. Held in the name of DZ IT STRATEGY on request, with a commitment to hand them back.

Talk about your domain names

Multilingual site and back office for a restaurant in Sardinia

Bar Su Cuile (Sardinia, Italy) · 2026 · In production

The Su Cuile bar menu as the customer sees it after scanning the QR code, in Italian, English and German

The QR code menu

  • 36updates published by the client, unaided, in 3 months
  • 3 languagespublic it/en/de, admin fr/it
  • 85contextual help entries built into the tool

The context

A restaurant owner, neither technical nor French speaking, who had to call his supplier for every menu change, and therefore never changed his menu.

What was done

  • Multi-menu QR system with a time slot engine: the right menu shows at the right hour, automatically.
  • Draft then publish workflow: the client tests, gets it wrong, starts again, and nothing breaks in production.
  • A simulator to view the menu at any given hour, to check before publishing.
  • 85 contextual help entries written into the tool: autonomy lives in the interface, not in a PDF nobody reopens.
  • 8 functional iterations delivered in a single day, on his feedback.

The outcome

Three months after delivery, the client had published 36 updates without ever asking for help. That is the only measure of success that counts.

Role of AI: Designed and developed 100 % with AI, from the first line to production. The delivered site itself contains no AI at all: no assistant, no generation. It is a conventional tool, simply built ten times faster.

PHPJavaScriptMySQLAI assisted design

End to end support for going digital

BE MOBILITY, bemobility.fr · 2024 · In production

BE MOBILITY mobile charging unit, yellow frame on castors, built-in charging socket

The mobile charging unit

  • 2024live and maintained without interruption since
  • 2FAtwo factor authentication and brute force protection

The context

A company with no structured online presence and no security culture.

What was done

  • Design, development, hosting and launch of the site.
  • Hardening: two factor authentication, brute force protection, hidden admin URL, monitoring.
  • Password policy and password manager rolled out with the team.
  • Automated backups, with a restore procedure that was actually tested.
  • Awareness session on common threats, run with the director.

The outcome

A maintained site in production, and a director who can recognise a phishing attempt.

PHPMySQLShared hostingHardeningMonitoring

SMO Solar Process

Audit of the existing system, then a full rebuild

SMO SOLAR PROCESS · 2022-2026 · Engagement closed, site stayed in production for several years

SMO mobile solar unit on a trailer: mirrors, concentrator and processing modules

The mobile solar unit

  • Audit firstthe picture first, technical decisions after
  • Several yearsin production, untouched
  • 99/100speed measured four years after delivery (83 on mobile)

The context

A solar industry firm already holding technical assets, with no clear view of what deserved to be kept.

What was done

  • Detailed audit of the existing system: what works, what it costs, what leaves it exposed.
  • Full rebuild: design, development, hosting, launch.
  • Hardening and monitoring, automated backups.
  • Good practice briefing for the team.

The outcome

A deliverable that stayed stable over time. The views above are the state of the site in January 2026, four years after launch and a few weeks before the domain lapsed; the speed measurement is dated 5 February 2026. That is the best proof an upfront audit saves paying twice.

PHPMySQLAuditHardening

BDD CleanUP

Making a prospecting database trustworthy

Engagement, sales team · 2026 · Delivered

Before and after on a database of 63,634 rows
  • 63,634rows processed in 18 seconds
  • 76 % → ~0false positives, over two tuning passes
  • 88.5 %confidence on reconstructed e-mail addresses

The context

A polluted prospecting database: duplicates, dead addresses, inconsistent formats. Nobody dared touch it for fear of deleting the good contacts.

What was done

  • Read only processing first, then a dry run: nothing is deleted until the result is validated.
  • Every deletion traced and reversible.
  • Two documented tuning passes to collapse the false positive rate.
  • E-mail pattern detection per domain, to rebuild missing addresses.
  • Quantified report with precision and recall analysis, and a reasoned recommendation.

The outcome

A usable database, and above all a method: data does not get deleted on a hunch, what is about to be lost gets measured first.

Role of AI: La logique de nettoyage (détection de doublons, reconstruction d'adresses, faux positifs) a été conçue et affinée avec l'IA, itération par itération sur les deux passes documentées ci-dessus.

PythonGoogle Sheets APIPrecision/recall analysis

The call script tree editor

An argument built as linked bubbles, and followed live during the call

Business development · 2026 · Used by the team

The call script tree editor: the outline is built as linked bubbles and followed during the call
  • 0 installationa standalone file, opened in the browser
  • Guide + demowritten guide and video walkthrough shipped with the tool

The context

A team of business developers with real tooling needs and no development resource in house.

What was done

  • The outline is built as linked bubbles: an objection, an answer, the rest of the path.
  • It is followed live during the call, with no window switching and no document scrolling.
  • Standalone format: a single file, opened in the browser, sendable by e-mail.
  • Another tool delivered to the same team is not shown here: the automated export to lemlist for prospecting sequences.
  • Business side: target segmentation and prioritisation for a Qualiopi certified body selling generative AI training, covering personas, pitch and prospecting sequences.

The outcome

A tool a colleague uses without its designer next to them is a delivered tool. The others are prototypes.

Role of AI: L'éditeur d'arbres et sa logique de navigation ont été conçus avec l'IA, en partant directement des besoins réels de l'équipe.

Standalone HTML/JSPythonlemlistGoogle Sheets API

The Gantt generator

A prospecting campaign schedule, per person and per day

Business development · 2026 · Used by the team

The Gantt generator: the tasks of a prospecting campaign, spread per person and per day
  • 0 installationa standalone file, opened in the browser
  • Guide + demowritten guide and video walkthrough shipped with the tool

The context

A team of business developers with real tooling needs and no development resource in house.

What was done

  • Campaign tasks are spread per person and per day, on a timeline readable at a glance.
  • The schedule regenerates when the tasks change: no diagram to redraw.
  • Standalone format: a single file, opened in the browser, sendable by e-mail.

The outcome

A schedule nobody updates is a false schedule. This one updates itself, so it stays true.

Role of AI: Le moteur de régénération du planning a été conçu avec l'IA, pour éviter d'avoir à redessiner le diagramme à la main à chaque changement.

Standalone HTML/JSPython

The prospect search filter

Rules written once, that sort every list after that

Business development · 2026 · Used by the team

The prospecting filter: rules written once set aside off target profiles and bring the others forward
  • 0 installationa standalone file, opened in the browser
  • 0 data collectedsorting happens on screen, nothing is copied or sent

The context

A team of business developers with real tooling needs and no development resource in house.

What was done

  • Targeting criteria are written once as rules, and replayed on every new list.
  • Off target profiles are greyed out, the others highlighted: the sort can be reread and corrected, instead of redone.
  • Everything happens on screen, in the browser, on results already displayed: no data is copied, stored or sent anywhere. This is highlighting, not collection.
  • Shipped with its written guide, like the others.
  • Standalone format: a single file, opened in the browser, sendable by e-mail.

The outcome

The time saved is not on the first sort: it is on all the following ones, where the rule replaces the rereading.

Role of AI: Le moteur de règles et le surlignage ont été conçus avec l'IA, comme le reste de cette suite d'outillage commercial.

Standalone HTML/JSPython

ClaudeManager

Orchestrator for autonomous AI agents

Proprietary product · 2026 · In daily use

The ClaudeManager interface: the list of tracked projects, what each one is doing and the session controls
  • 8,715 linesof Python written in 16 days
  • 1,188 linesof automated tests, written alongside
  • 16 daysfrom empty folder to daily driver

The context

A coding AI agent left to itself is productive and dangerous. The goal was to keep the first without the second.

What was done

  • Agent actions intercepted before execution: pure testable rules, refusal by default, every decision logged.
  • Blocking safety net: restore point, isolated branch, archive. If the net fails, the session does not start.
  • Human governance: the agent may propose a rule, never edit its own instructions.
  • Remote multi-machine execution through an authenticated HTTP agent.
  • 21 automated tests covering the guardrails themselves.

The outcome

This project is its own demonstration: 8,715 tested lines in 16 days. That is the figure to put against the question of what AI really changes about productivity.

PythonCustomTkinterClaude APIGitAutomated testing

Suite LTSC+ / Windows OS MAX

Industrialising the Windows workstation

DZ IT STRATEGY offering · Since 2022 · Active offering

Windows workstation deployed automatically from a PXE server
  • 3,663 linesof PowerShell, parallel orchestration
  • 1 hourtarget time back at work after a failure
  • PXEimage deployment over the network, no USB stick

The context

A freelancer or a small business that loses its workstation loses its activity. Reinstalling by hand takes a day and never gives back exactly the same machine.

What was done

  • Installation, tuning and hardening fully automated, driven by configuration files.
  • In-house software catalogue, mostly open source, updated automatically.
  • Privacy and security reinforcement of the Windows image.
  • PXE server: optimised images deployed straight over the network.
  • Backup and restore service, with a tested procedure.
  • Shipped as a standalone executable, no installation and no administrator rights.

The outcome

The same workstation, identical, in one operation, and a failure that becomes an hour long incident instead of a lost day.

Role of AI: This is not an AI project: it is the automation groundwork the rest stands on. It appears here for that reason, and no other.

PowerShellPXELinuxDockerConfiguration driven scripts

DZtools

Around sixty portable Windows micro-tools

Proprietary ecosystem · Since 2022 · Under continuous development

Icon grid of the DZtools utilities
  • ~60tools designed and maintained
  • Portableno installation, no administrator rights

The context

Every daily annoyance on the workstation eventually turned into a tool. After four years, that adds up to an ecosystem.

What was done

  • Ultimate Widget Manager: positionable widgets, custom actions, an SOS mode that cuts the network and sends a full system report.
  • Ultimate Mouse Control: driving the system through click combinations, with macros, text capture and speech synthesis.
  • A suite of utilities for administrators and developers.
  • Standards shared by all of them: single instance, tray icon, configuration kept separate from the executable, logging, versioned archiving.

The outcome

A permanent training ground, and the reason delivery is quick: the foundations are already written.

PowerShellWinFormsC#PythonP/Invoke

DZNav

Navigation, reading progress and back to top, for any site

Proprietary product · 2026 · In production on this site

The DZNav menu in both orientations, with the reading gauge and the back-to-top button
  • 24 kBminified, JavaScript and CSS included, zero dependency
  • 5 stylesof reading progress, switched from the admin screen
  • 0 cookieno data sent to any server, nothing to declare

The context

The same menu had been written twice, for two different sites: one could switch from horizontal to vertical, the other displayed a reading gauge. Two codebases diverging with every fix. They were merged into a single component, then generalised to graft onto whatever menu a site already has.

What was done

  • Orientation chosen by the visitor: horizontal bar or floating vertical panel, on one button, with the choice remembered.
  • Adaptive contrast: the button's colour recalculates in real time against whatever is actually painted behind it (translucent header, background image, dark section), through a real WCAG contrast ratio calculation, not a colour declared in advance.
  • Continuous reading progress: the line under the active entry is a gauge filling at the exact rate of the scroll through that section. Five styles to choose from.
  • Back to top with a gradual appearance, configurable, and unreachable by keyboard while invisible.
  • Menu built automatically from the page's headings, for a site with no hand-written table of contents.
  • Accessible and lean: full keyboard navigation, ARIA labels, animations turned off if the system asks for it, five interface languages.
  • WordPress extension installable as one file: full settings screen, no code, no cookies.
  • Dependency free, in JavaScript compatible with older browsers: nothing to compile, nothing to maintain.

The outcome

This site is its first client: the menu you have just used IS the product. That migration also surfaced five defects the isolated demo had never shown, which is exactly why a component ships in production before it goes on sale.

JavaScript (dependency free)CSSWordPress pluginPHP



The support

Support, end to end

What is sold here is neither a website nor an application: it is the answer to a need. And that need is nearly always the same one, namely growing an activity, finding clients, keeping them, and no longer losing time on what could run by itself. The tool comes afterwards, chosen for the need. Never the other way round. That is why DZ IT STRATEGY sets out to understand the need in full and to act as a genuine partner in the project.

Three stages, taken together or separately.

01

Understand and decide

Advisory and strategy

Listening to the business need, auditing what is already in place, reporting back in plain language: what works, what it costs, what leaves you exposed, and what deserves to be done first. A documented decision beats a project started in a hurry.

  • Audit of the existing system before a rebuild (SMO Solar Process)
  • ERP deadlock resolved and reported straight to the chairman (KERR France)
  • 15 years spent talking to company directors, not only to IT departments

Technical auditNeeds analysisRisk assessmentCostingReporting to non technical audiencesDomain name selection

02

Design and deliver

Design and build

Design and development: applications, websites, automation, workstation industrialisation. What is delivered runs in production, stays maintainable, and depends on no single person to keep working.

  • Applications running in production at client sites for several years
  • Large scale data processing automation
  • Full industrialisation of the Windows workstation

PythonC#PowerShellPHPJavaScriptSQLAndroidDockerLinuxPXESelf hosted AI modelsSecurity and hardeningGitAutomated testing

03

Hand over

Training and autonomy

An engagement that leaves the client dependent is a failed engagement. The teams who will use the tool are trained, and the help is placed inside the tool itself: nobody reopens a training handout three months later.

  • 85 contextual help entries built into the client tool (Su Cuile)
  • Business walkthroughs built into the application
  • Two years mentoring apprentices, plus school partnerships (Groupe Cerise)

Plain language explanationInstructional designEmbedded documentationFacilitation with company directors

AI training

AI training

Not a conference about artificial intelligence. A day spent on your own use cases, with a deliverable that leaves with you and is useful the next morning.

Real use cases

The work happens on your files, your records, your daily irritants, never on a demonstration example.

A deliverable, not slides

Every session ends with something that runs: an assistant, an automation, a library of prompts for the job at hand.

Measured at three months

The success of a training day is not read in the end of session feedback form, but in actual use a few months later.

1 day

Winning back 5 hours a week with generative AI

Directors and staff, no technical prerequisites

The useful overview: which tool for which use, what should never be handed to them, and the automations that give time back the following week.

What you leave with: A prompt library matched to the recurring tasks of each participant.

Half a day

Searching and deciding with AI

Any role producing notes, summaries or documented decisions

Sourced research, verification, spotting an invented answer. How to obtain usable information and be able to say why it can be trusted.

What you leave with: A written verification method, and a research workspace set up for the participant's field.

1 day

Creating your content with AI

Communications, marketing, training

Text, image, video, voice: which tool for which result, at what cost, and where the legal and quality limits sit.

What you leave with: One real piece of the participant's content, produced in the session, from brief to publishable version.

1 day

Automating without coding

Support functions, operations, freelancers

Assembling automations and an assistant plugged into your own documents, without writing a line of code.

What you leave with: A working automation and a document assistant plugged into one of the participant's own repositories.

1 day

AI without data leaks

Regulated professions, HR, healthcare, accountancy, public bodies: any organisation whose data protection officer refuses cloud tools

What actually reaches the supplier when a document is pasted into an online tool, what the GDPR says about it, and how to run a model on a company machine so that nothing leaves. Short theory, real demonstration.

What you leave with: An AI usage policy written for the organisation, and a local assistant running on its own documents.

Half a day

Bringing the AI bill down

Teams already using AI daily and watching the spend climb: management, IT, support functions

AI is billed by the volume of text exchanged, counted in tokens. The same question can cost ten times more depending on what it is given to read: a spreadsheet sent as a PDF, a conversation history reloaded with every message, a scanned document rather than a converted one. We measure the real spend, identify what drives it, and cut it without losing answer quality.

What you leave with: A costed statement of current spend, the three items behind it, and the settings applied during the session to the participant's own tools.

Subcontracting for training providers is part of the offer: trainer CV, programme, learning objectives, sequencing, materials and assessments are supplied in the format your quality process expects.
Formats: Remote · In-house · On site, northern France.

Separate offering

AI on your premises, nowhere else

An artificial intelligence model installed on a machine in your own offices. Your documents are analysed on site. Nothing leaves for a supplier, in France or anywhere else.

Who for

Organisations whose data cannot leave the building: accountancy firms, HR departments, healthcare, early years care, regulated professions, local authorities. Everywhere the online tool gets refused, whether by the data protection officer, by internal policy, or by plain common sense.

No data sent anywhere

The model runs on the machine installed at your site. Your files pass through no external server, and there are no supplier terms of use to keep watching, terms that could change tomorrow.

Compliant by design

Compliance here comes from the architecture rather than from a ticked box: if the data never leaves, there is no transfer to govern. Processing agreement provided, records of processing kept up to date, hardware location verifiable.

What it changes day to day

Querying your own documents in everyday language, producing summaries, finding information inside a bulky case file, preparing a written report. The gain is measured in hours per file, not in demo effect.

You buy no hardware

The machine is installed, configured and maintained by DZ IT STRATEGY, on a monthly subscription. It stays their property: if you stop, it goes back, and you are not left holding obsolete equipment.

What you should know

A model running locally is slower and a little less brilliant than the best online services. On document analysis and search across your own files, the gap does not show. On long creative writing, it does. This is said before the sale rather than after, and the trial runs on your own documents before any decision.

A trial on your own documents, before any decision. Talk it through

Quality

A good site is something you can measure

Everyone promises a site that is “fast” and “secure”. Nobody gives a number. Here are this page's, not taken once on our machine but counted by your own browser, at the moment you are reading, and reproducible by you in thirty seconds with the public tools below.

211 kB

7 % of the weight of the median page

The weight of the first screen

870 kB, whole page, images included

What has to be downloaded before the first sentence can be read.

13.6 times lighter than the median home page on the web (2 862 kB)

The weight of the first screen

Benchmark: 2 862 kB · median home page on the web, on desktop

What has to be downloaded before the first sentence can be read.

This is the only weight a visitor really feels, and the one performance tools measure. The median home page on the web weighed 2 862 kB on desktop and 2 559 kB on mobile in July 2025, most often because of images that were never resized and scripts that were never removed. On a mobile plan with poor coverage, every hundred kilobytes is a second of waiting, and a share of visitors who leave before the first sentence.

Source of the benchmark: Web Almanac 2025 (HTTP Archive), “Page Weight” chapter, July 2025.

29 files

38 % of the files of the median page

The number of files to load

Every file is one more round trip to the server.

2.7 times fewer than the median page on the web (77 files)

The number of files to load

Benchmark: 77 files · median page on the web, on desktop

Every file is one more round trip to the server.

The median page asks for 77 of them on desktop and 72 on mobile. The total weight can stay reasonable: the waiting, on the other hand, adds up with every round trip.

Source of the benchmark: Web Almanac 2025 (HTTP Archive), “Page Weight” chapter, July 2025.

8 out of 8

100 % of the headers in place

The security headers

Security instructions sent to the browser before the page itself.

most brochure sites send none at all

The security headers

Benchmark: most brochure sites send none at all

Security instructions sent to the browser before the page itself.

They say what may run, what must be refused, and where the site agrees to be displayed. They can be checked publicly, on any site, in ten seconds.

Source of the benchmark: Web Almanac 2025 (HTTP Archive), “Security” chapter, July 2025.

1 external domain

Third parties told about your visit

The number of outside companies that receive the visitor's IP address, purely because the page was opened.

Third parties told about your visit

The number of outside companies that receive the visitor's IP address, purely because the page was opened.

A font hosted by a third party, a map, a social network button: each one is a transfer of personal data, and as such an obligation to document. The only third party on this site measures audience without cookies or identifiers, keeps only aggregated figures, and meets the criteria French regulators (CNIL) set for skipping a consent banner.

0 cookie

No banner to click

Nothing is stored on your device, except your menu display preference, which never leaves it.

No banner to click

Nothing is stored on your device, except your menu display preference, which never leaves it.

The banner is not a compliance measure: it is what you have to show once you have chosen to track people. Not tracking solves the problem at the root, and gives the visitor back the first second of the visit.

5.0 : 1 minimum

The contrast of the text

The measured ratio between the colour of the text and that of its background.

above the threshold required for readable text, which is 4.5:1

The contrast of the text

Benchmark: 4.5 :1 · threshold required for readable text

The measured ratio between the colour of the text and that of its background.

Below 4.5, text becomes painful to read for someone who is long-sighted, on a screen in the sun, or simply tired. It is calculated, not judged by eye on one's own screen, and it is the most widespread accessibility defect there is.

Source of the benchmark: W3C, WCAG 2.2, criterion 1.4.3 “Contrast (minimum)”, standard in force.

Figures measured when this page was built, on the files actually put online.

PageSpeed Insights Measured on 14 August 2026 48 % of sites on mobile and 56 % on desktop pass the three Core Web Vitals. In other words: more than one site in two fails on mobile.

PageSpeed Insights

Measured on 14 August 2026

Full report PageSpeed Insights on mobile Full report PageSpeed Insights on desktop

A score carries a date because it ages. Run the test again now : the test is the proof, not the picture.

Security Headers Measured on 5 August 2026 The eight headers above are rarely found together: Content-Security-Policy is present on only 21.9 % of sites, Permissions-Policy on 3.7 %, and Cross-Origin-Opener-Policy on roughly 2 %.

Security Headers

Measured on 5 August 2026

Full report Security Headers

A score carries a date because it ages. Run the test again now : the test is the proof, not the picture.

MDN Observatory Measured on 9 August 2026 Out of the 2.8 million sites in its ranking, 2.5 % get an A+ and 36 % get an F, the lowest grade.

MDN Observatory

Measured on 9 August 2026

Full report MDN Observatory

A score carries a date because it ages. Run the test again now : the test is the proof, not the picture.

SSL Labs Measured on 4 August 2026 TLS 1.3, the most recent version of the encryption, covers about 76 % of pages served over HTTPS. The browser padlock does not tell you which one you have.

SSL Labs

Measured on 4 August 2026

Full report SSL Labs

A score carries a date because it ages. Run the test again now : the test is the proof, not the picture.

And for everything else?

What is measured here is this site, because it is the object in front of you, and one you can check yourself. The same standard applies to everything delivered, with the units of each trade: a data pipeline is judged in rows per second, an application by the number of breakdowns it does not cause, a training course by what is actually used three months later.

The 8 security headers, one by one
  • Content-Security-Policy what the page is allowed to run and to load
  • X-Frame-Options forbids showing the site inside someone else's frame
  • X-Content-Type-Options forbids the browser from guessing a file's type
  • Referrer-Policy what is passed on to another site when you leave
  • Permissions-Policy capabilities refused by default (camera, microphone, location)
  • Cross-Origin-Opener-Policy cuts the link with the page that opened the site
  • X-Permitted-Cross-Domain-Policies refuses the old cross-domain policies
  • Strict-Transport-Security forces encryption for every later visit
Check for yourself

The results below carry their date. The same tools apply to any site in a minute, including a competitor's, or your own.

  • PageSpeed Insights Performance, accessibility, best practices and search engine readiness, scored out of 100 by Google, on mobile and on desktop.
  • Security Headers Which security headers the server actually sends, graded from F to A+.
  • MDN Observatory Mozilla's examination, in ten tests. It does not simply note that headers exist: it judges their contents (a Content-Security-Policy that allows “unsafe-inline” protects nothing and loses its points), and it looks at six things the previous tool ignores: cookies, CORS, redirect chain, script integrity, resource isolation, HSTS duration.
  • SSL Labs The quality of the connection's encryption, beyond the padlock the browser shows.
Where the comparison figures come from

These figures are not a sales pitch: they are the default values of a site built properly. They are here because they are rarely met, and because a site is judged on what it does, not on what it says about itself.

Ownership

The site is yours

A delivered site should not force you to call back whoever built it just to change a colour, nor hold it hostage inside a tool nobody else knows how to open. Here is how this one is built, and what its owner drives without help.

The architecture, in three sentences

The content knows nothing about the appearance

Texts, prices and projects live in readable files, kept apart. The appearance is a theme, next to them. Changing the design entirely does not touch a word of the content; correcting one figure corrects it everywhere, on every page, at once.

No database, no weekly updates

The published site is HTML: nothing to update, no plugin that breaks at the next patch, no attack surface to watch. That is also what explains the figures in the previous section.

Your content stays readable without a middleman

The content files open in a text editor and make sense on reading. No proprietary format, no export to negotiate: if you change supplier one day, you leave with content you can use, not with a backup nobody knows how to reopen.

The test bench: the owner's dashboard

A settings panel that applies changes live, on the real site, without touching any code. It was built to drive this very site, and it comes with every site DZ IT STRATEGY delivers.

The settings panel on the right, the site on the left: every change applies live.
The same panel, floating above the page.
Usable with a thumb, so usable on the move.

The same test bench on all three formats. Settings can be changed on the move, from a phone.

What you set on your own

  • Spacing, columns and widths are set with the mouse, format by format: the phone is adjusted without moving the desktop layout.
  • Order and prominence of projects, offers and sections.
  • Speed and range of the animations, down to removing them.
  • Immediate preview: what is on screen is what will be published.

What stops you from breaking something

  • Every setting is undone step by step, and everything resets with one click.
  • Nothing is published until it is asked for: trials stay local, then go through a staging site.
  • Every publication is recorded and reversible: going back to the previous version is a one minute operation.
  • An unknown or inconsistent setting stops the publication instead of being ignored in silence. That is the most common defect of admin interfaces: you think you have set something, nothing happens, and nobody tells you.

What “yours” means, precisely

A promise of ownership that does not say what it covers binds nobody. Here is the split, as it appears in the quote.

What is transferred to you, with no rent

  • The content: texts, images, page structure.
  • The design of the site and its complete configuration.
  • The source files, in a readable and usable format.
  • The domain name and the hosting credentials, in your name from day one.
  • The published site runs and stays online, whatever happens between us.

What is a service, not a good

  • The test bench is a hosted tool, reused from one client to the next: it is rented, it is not sold.
  • It is included for the whole support period, then continues monthly if you want to keep it.
  • Stopping it stops nothing else: your site carries on exactly as it is, online, untouched.
  • You lose the comfort of adjusting, never your site: that is the whole difference with a rented site.

What that changes in practice

  • You can hand the site to another supplier, without asking for anything or buying anything back.
  • You leave with all of the content, in a format anyone knows how to reopen.
  • Nothing switches off if the relationship ends: the site is yours, and it stays there.

The same budget, two opposite outcomes

The rented site

The usual arrangement: a site for a few hundred euros, then €150 to €200 a month for forty-eight months. That is €7,000 to €9,600 by the end, for a site that still does not belong to you, and that switches off with the subscription, content included.

Market figures, collected in August 2026.

The site you own

The same order of budget, paid once, and the site is yours on day one. No rent to keep it, no minimum term, no possible switch-off.

The price is given after seeing the real need, never before.

After delivery: support, not a leash

Six to twelve months depending on the project, test bench included: we stay reachable for content and settings changes, and we make them with you rather than for you. After that, keeping the test bench is a modest subscription, with no commitment, and with no consequence if you stop it: your site depends on nothing. Anything that belongs to design work, a new page or a new feature, is quoted separately and said in advance.

What is better not done yourself

The test bench handles the staging, not the structure. Adding a page, reworking a journey, plugging in an outside service remains design work, and that is exactly as it should be: an interface that claims to allow everything ends up allowing everything, breakage included. The line is stated at delivery, it is not discovered along the way.

Contact

Let's talk about your project

The first conversation is there to understand your situation: what you want to achieve, what is blocking it, what deserves doing first. It ends with a clear opinion and usable leads, with no commitment to anything after that.

E-mail write a message
Phone call
Where Lille (59), France
How Fully remote · on site across the Lille metropolitan area