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.
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.
Work
Client work
Projects delivered and running in production, at real companies.
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
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
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
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
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
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
Running several AI agents in parallel, unsupervised, with the guardrails that make such autonomy acceptable in the first place.
Suite LTSC+ / Windows OS MAX
A clean, fast, hardened and reproducible Windows that installs itself. Plus a recovery promise: back at work within the hour after a failure.
DZtools
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
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.
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 pageThe 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)
29 files
38 % of the files of the median pageThe 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)
8 out of 8
100 % of the headers in placeThe security headers
Security instructions sent to the browser before the page itself.
most brochure sites send none at all
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.
0 cookie
No banner to click
Nothing is stored on your device, except your menu display preference, which never leaves it.
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
Figures measured when this page was built, on the files actually put online.
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-Policywhat the page is allowed to run and to load -
X-Frame-Optionsforbids showing the site inside someone else's frame -
X-Content-Type-Optionsforbids the browser from guessing a file's type -
Referrer-Policywhat is passed on to another site when you leave -
Permissions-Policycapabilities refused by default (camera, microphone, location) -
Cross-Origin-Opener-Policycuts the link with the page that opened the site -
X-Permitted-Cross-Domain-Policiesrefuses the old cross-domain policies -
Strict-Transport-Securityforces 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
- Web Almanac 2025 (HTTP Archive), “Page Weight” chapter July 2025 Weight and number of requests of the median page on the web. The annual reference study, run on several million real sites, with a public and reproducible method and data set.
- HTTP Archive, “Page Weight” report updated continuously The same measurement, updated continuously. So you can check that the figures quoted above have not aged.
- W3C, WCAG 2.2, criterion 1.4.3 “Contrast (minimum)” standard in force The minimum contrast ratio of a text. This is not an average of the web but a normative threshold: the benchmark shown is a requirement, not observed practice.
- Mozilla, MDN HTTP Observatory, “Benchmark comparison” tab of any report 9 August 2026 Distribution of the grades of the sites scanned by the Observatory. Figures from the tool itself, on the sites it has actually graded: 2 819 254 scans, of which 70 883 A+ and 1 014 548 F. They can be read again in the report's “Benchmark comparison” tab, and recalculated from the same public data that feeds its chart.
- Web Almanac 2025 (HTTP Archive), “Performance” chapter July 2025 Share of sites that pass the Core Web Vitals. Real usage measurements (Chrome CrUX data), not a laboratory test: this is what visitors actually experience.
- Web Almanac 2025 (HTTP Archive), “Security” chapter July 2025 Adoption rate of security headers and of TLS 1.3. Measures the same headers as Security Headers, on millions of sites, with a public and reproducible method.
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 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.