You know your business.I know how to bring your ideas to life.
A modest idea or an ambitious project: tell me what wastes your time, what your tools cannot do, what you would like to create. I take care of the rest, from design to launch.
One point of contact.From first conversation to handover.
The person who listens to you is the one who designs, builds and delivers. Your need is understood once, first-hand, and followed through to the end — with no go-between to explain everything to again.
You decide
Whatever concerns your business and your goals: the need, the priorities, what is acceptable and what is not. Important decisions are put to you as the project goes along, with their consequences.
I take care of
The technical choices, the recommendations and putting them into practice, within the agreed scope. Every trade-off is explained to you in plain terms; nothing important is decided without you.
The whole picture
The need, the data, the interface and day-to-day operation are held by the same person: nothing gets lost between two teams.
The right questions, early
Broad professional experience — management responsibilities and other roles, in varied settings — to understand an organisation quickly, and what it expects.
Straightforward decisions
No meeting to pass a decision on, no chain of intermediaries: a technical choice is settled when it comes up, and explained to you.
Regular conversations
You see the work move forward step by step, and you stay in charge of the decisions that matter.
Few projects at a time: yours gets real attention, from the first conversation to day-to-day operation.
A step-by-step approach.Checkable at every stage.
Understand
The work as it is really done, its constraints, what genuinely matters to you.
Clarify the assumptions
What is known, what is assumed, what still needs proving — written down and shared.
Choose the proofs
A proof of concept, a proof of value or a minimum viable product, only when the uncertainty warrants it.
Build in stages
Usable versions early on, rather than everything delivered at the end.
Check with you
Every stage is tried out and approved with the people who will use it.
Deliver and hand over
Documentation, access, the keys: what is needed to run the tool and have it taken over.
Timescales and budget are set at the outset and tracked at every stage. If the need changes, they are explicitly reassessed with you before going further: any gap is flagged when it appears, not at delivery.
POC, POV, MVP: the three proofs explained
Four published products, in four unrelated fields, designed, built and launched by the studio — several of them developed side by side. See the work
What you can bring
An original digital product
From idea to launch: interface, architecture, data, operations. That is what the studio’s first published projects were.
A bespoke business tool
To replace side spreadsheets, re-keying and approval chains that only live in mailboxes.
Data made readable
Dashboards, visualisations, source traceability: turning complex material into an understandable interface.
A prototype taken through to production
The demo already exists. What remains: permissions, exceptions, data migration, monitoring, security.
A decision before any development
Build, buy, fix what exists, or do nothing? A written recommendation, with its risks and its cost.
A need that is hard to classify
It fits none of these boxes? Tell it as it is: the classification can come later.
Off-the-shelf software or a tailored solution?It depends on the problem.
An ERP, a CRM or standard software meets many needs very well: others have tested it, it evolves, it is maintained. When that is the case, it is the right choice. A tailored solution becomes worthwhile when an organisation keeps piling up workarounds — side spreadsheets, re-keying, manual steps — or gives up a practice that makes its value because the tool cannot follow it.
Use what exists
The need is common and the tool covers it: the right choice is often to configure it properly, and stop there.
Extend it
The tool covers the essentials; a module, a bridge or a specialised interface handles what it cannot do.
Create
The need is singular, or the product itself is the idea: an original design, from the first screen to day-to-day operation.
The right question
Which software do you want?
What problem are you trying to solve?
The first question assumes the answer has already been found; it produces specifications that describe an imagined solution. The second lets people talk about the work as it actually happens. Translating it into data, interfaces and architecture is my problem, not yours.
What a solution is worth, beyond its price
- Time given back
- Errors avoided
- Simpler operations
- Better-coordinated teams
- Information that flows
- Better-informed decisions
- New possibilities
- A tool that lasts, and is yours
These gains are estimated before building, then checked afterwards: you decide on concrete grounds.
Fifteen situations.You will recognise at least two.
Everyday problems that recur from one organisation to the next. For each: what happens, what it costs, what a solution can change. Is your idea more about an original product or data to make readable? Start straight from your project.
Manufacturing
Whatever the design office decides, the shop floor must receive accurately, on time and in the right version.
Two departments re-type each other’s information by hand
The situation
Design and production use different tools. Part of the information is typed again from one to the other, often at the end of the day, sometimes twice.
What it costs
Hours of data entry every week, and discrepancies found too late: at inspection, in production or at the customer’s.
What a solution can change
- A single entry, passed on automatically to the other department
- A careful migration of existing data before the switch
- Consistency checks visible to both teams
The first questions
- Which information is actually re-keyed?
- Which tool is authoritative when the two disagree?
- When is a discrepancy discovered today?
What you gain
Reliability · data-entry time saved · discrepancies caught before the shop floor
An important change does not reach everyone
The situation
A change is decided, then shared by email, through a shared folder or by word of mouth. Nothing guarantees that everyone has seen it, or that they are working on the right version.
What it costs
A batch made on an outdated version means scrap, rework and arguments about who was responsible.
What a solution can change
- A single, dated reference version, with its history
- Targeted circulation, with read receipts and reminders
- Outdated documents locked, not merely archived
The first questions
- Who decides that one version replaces the previous one?
- Who needs to be told, and how quickly?
- What does production on an outdated version cost?
What you gain
Traceability · scrap avoided · clear responsibilities
Quality tracking relies on files, emails and memory
The situation
Inspections, non-conformities and corrective actions live in spreadsheets, folders and email threads. The team knows the job, but rebuilding a file takes half a day.
What it costs
Every audit or complaint takes time to track down evidence that already exists, somewhere.
What a solution can change
- Inspections recorded with their photos and documents attached
- A clear approval workflow with a tamper-proof history
- An evidence file produced in one click instead of being rebuilt
The first questions
- What must be proven, to whom, and how quickly?
- Who is allowed to approve what?
- Which inspection data already exists without being used?
What you gain
Evidence on hand · half-days saved · calmer audits
Management & systems
Several tools, several versions of the same figures, and a question never settled: which one is authoritative?
The main software covers the essentials; the rest lives in spreadsheets
The situation
Several side spreadsheets handle the cases the main tool cannot. They have become indispensable, and often only one person knows how to keep them up to date.
What it costs
Essential know-how rests on a few fragile files: one absence or departure, and the business slows down.
What a solution can change
- First check the configuration or an existing module: often the cheapest option
- Otherwise, a targeted application connected to the main software
- A checked migration of historical data, not a raw copy
The first questions
- Are these cases a genuine business specificity, or a setting nobody ever configured?
- What happens if the person who maintains these files is away?
- Does a module already exist, bought but never deployed?
What you gain
Continuity · less dependence · risk under control
Two systems disagree, and nobody knows which to believe
The situation
The same customer, quantity or price exists in several tools, with different values. Everyone checks the one they know.
What it costs
Decisions made on wrong figures, and meeting time lost working out who is right.
What a solution can change
- A designated reference source for each sensitive piece of data
- One-way synchronisation, with a log of discrepancies
- An alert as soon as a discrepancy exceeds a threshold
The first questions
- For each sensitive piece of data, which tool should be authoritative?
- Who can correct it, and does the correction carry through?
- Which decisions have already been made on wrong data?
What you gain
Reliable figures · better-grounded decisions · no more arguing over numbers
The same dashboard is rebuilt every week
The situation
One or two days a week go into gathering data from several sources to rebuild the same report. It is already out of date when it arrives.
What it costs
Whole days spent compiling, and decisions made on last week’s figures.
What a solution can change
- First drop the unused indicators: an immediate gain
- Automatic consolidation of the remaining sources
- A continuously updated view, according to everyone’s access rights
The first questions
- Which decisions really depend on these figures?
- Which indicators nobody looks at any more?
- Are the sources accessible, and who is responsible for them?
What you gain
Days freed up · fresh information · real steering
Sales & projects
A job moves from quote to design, then to delivery and invoicing — often changing tools at every stage.
The same job is re-keyed from quote to invoice
The situation
Quotes, tracking, delivery, invoicing: several tools, the same information entered several times, and as many chances of a gap between what was sold and what is produced.
What it costs
Time lost on every job, and a margin that erodes without anyone noticing before closing.
What a solution can change
- A single entry at the start, picked up by the other tools
- A shared job reference, right through to the documents
- The gap between sold and produced visible along the way
The first questions
- When does a job change status, and who needs to know?
- Which information must stay identical from start to finish?
- How long does re-keying take over a normal month?
What you gain
Time saved · margin protected · promises kept
Job tracking lives in mailboxes and in a few people’s heads
The situation
To know where things really stand, you have to ask people. Follow-ups, commitments and decisions are scattered across personal inboxes, or phone calls that leave no trace.
What it costs
A two-week absence is enough to stall a file, and commitments made in conversation get lost.
What a solution can change
- One thread per job, fed from the tools already in use
- Decisions recorded at the moment they are made
- Follow-ups suggested automatically, approved by a person
The first questions
- What happens when one of these people is away?
- Which commitments exist nowhere in writing?
- What level of detail is useful without turning into bureaucracy?
What you gain
Company memory · continuity · commitments kept
Every project is tracked its own way
The situation
Depending on who runs it, a project is tracked in a spreadsheet, a management tool or a notebook. Comparing two projects, or taking over a colleague’s, takes real effort.
What it costs
No reliable overview, and every handover loses time and information.
What a solution can change
- A deliberately light common base that everyone accepts
- A gradual migration, project by project
- An overview built on that base, with no re-keying
The first questions
- What absolutely has to be shared?
- Are current habits disorder, or a useful adaptation?
- Who needs an overview, and to decide what?
What you gain
Comparable projects · easier handovers · a view of the whole
Documentation
The information already exists, in documents the company owns. It is simply hard to reach.
Twenty years of documents, readable only one at a time
The situation
Thousands of files: drawings, reports, contracts, data sheets, letters. The information is there, but you have to open the documents by hand, and know where to look.
What it costs
Hours of searching, answers that depend on a few people’s memory, and knowledge that fades as people leave.
What a solution can change
- Text recognition and indexing of the whole collection
- Plain-language search that always cites the source document
- Extraction of only the useful information, checked by sampling
The first questions
- Which questions do you want to be able to ask of these documents?
- What share is scanned as images, with no usable text?
- What level of error is acceptable, and who checks?
What you gain
A dormant asset made useful · faster searches · knowledge preserved
Every morning, documents sorted, renamed and passed on by hand
The situation
Every day, someone opens what has come in, identifies the file, checks the version, renames it to the in-house convention, files it, then lets the right people know.
What it costs
Hours of handling every day, filing mistakes, and a growing backlog as soon as that person is away.
What a solution can change
- Automatic reading of the key information, with a person approving doubtful cases
- Automatic naming and filing, following your convention
- Automatic circulation to the right people, with a record
The first questions
- Is the naming convention written down anywhere?
- Do incoming documents follow a common format?
- What happens when the person in charge is away?
What you gain
Hours given back every day · fewer mistakes · traceability
Useful information stays stuck in attachments
The situation
Quantities, commitments, specifications or reservations arrive as PDFs, spreadsheets or photos. The software itself holds only a link to the file.
What it costs
Everything has to be re-read by hand to check, compare or find a piece of information — and discrepancies go unnoticed.
What a solution can change
- Targeted extraction of the few pieces of information that matter
- Automatic matching between document and software, with discrepancies flagged
- The document kept as evidence, the data made usable
The first questions
- Which information should become usable data?
- Who currently checks that the document and the software agree?
- What volume each month, and in which formats?
What you gain
Usable data · automatic checks · less re-reading
Construction & property
Between what is decided in the office and what happens on site, there are variants, approvals and a great many photos.
Drawings and approvals do not always reach the site
The situation
What is decided in the office takes time to reach the site, or arrives in an earlier version. On site, people work with what they have.
What it costs
Rework caused by an outdated version costs days of work, materials, and sometimes a dispute.
What a solution can change
- On site, only the current version, even offline
- Approvals and circulation tracked, with confirmation of receipt
- A history kept for disputes, without getting in the way of daily use
The first questions
- Who on site needs what, and with what network coverage?
- How do you know a document has actually been received?
- What does rework cost on average?
What you gain
Rework avoided · deadlines met · disputes documented
Snags, photos and site notes remain scattered
The situation
Observations are photographed, jotted in a notebook or sent by messaging app. Grouping them by trade, contractor or unit means a long job of piecing things together.
What it costs
Handovers that drag on, forgotten snags, and hours spent putting information back in order.
What a solution can change
- An item recorded on site, photo and location included, in one step
- Clearance tracked by owner, with automatic reminders
- Handover documents produced straight from the recorded items
The first questions
- Who must act on each item, and how do you know it has been cleared?
- How many outside contractors need to contribute?
- Which final document is expected: a list, a letter, a formal report?
What you gain
Faster handovers · clear responsibilities · complete files
Customer choices get lost between sales, design and the site
The situation
Options, changes and decisions are approved at some point, somewhere, by someone. At the end of the chain, nobody is quite sure what was promised or what was invoiced.
What it costs
Costly oversights to put right, an eroded margin, and a customer relationship put to the test.
What a solution can change
- A dated, approved register of choices, shared by all three teams
- The impact on cost and lead time calculated when the choice is made
- Automatic carry-over into site and invoicing documents
The first questions
- Where is the authoritative version of a customer choice recorded?
- Which choices affect costs or lead times?
- Up to what stage is a change accepted?
What you gain
Promises kept · margin preserved · a reassured customer
Your situation resembles one of these without matching it exactly? That is the usual case: the exceptions specific to your organisation are precisely the subject. Describe mine
Which projects
One person, five or five hundred: the size of an organisation does not decide the value of a need. What counts is a real problem and the will to solve it.
Your project fits if
- The problem exists today, for you or for your organisation
- It costs you time, money, reliability — or an opportunity
- You have an original idea, even a hazy one
- Off-the-shelf tools do not fit your rules, or you are not sure they are enough
- Your information is scattered across several files or systems
- The people who do the work every day can be involved
Frequently asked questions
What does Visionary Édition design?
Original digital products and solutions tailored to specific needs, in any field: an original product, a business tool, data made readable, a prototype taken into production, or a written recommendation before any development.
Why work with an independent studio?
The person who listens to you is the one who designs, builds and delivers: no intermediary to re-explain the need to, decisions made quickly and explained, one view of the whole, from the need to day-to-day operation.
What is the difference between a POC, a POV and an MVP?
Three ways of reducing uncertainty, not a compulsory path. A proof of concept (POC) answers “is it possible?”; a proof of value (POV), “is it worth it?”, against criteria set in advance; a minimum viable product (MVP), “what really needs to be built to learn and move forward?”, in real conditions of use.
Why start from the need rather than the technology?
Because the right solution follows from the problem, the volumes and the users. You do not need to know which software you want: describe the problem to solve, and the technical choice is my job.
When is an existing solution better than a custom build?
When off-the-shelf software covers the need well: then it is the one to choose, and I will recommend it. A tailored solution becomes worthwhile when the organisation piles up workarounds (parallel spreadsheets, re-keying, manual steps) or gives up a practice that creates its value. In between, extending what already exists is often enough.
How does a project request work?
You describe your situation in four guided steps: a few sentences are enough, with no technical jargon, no specification and no budget required up front. Every request is read personally, and the next steps are worked out together, starting with a first conversation.
What does the client receive on delivery?
Within the scope agreed in the contract: the documentation needed to install, use, operate and develop the tool; the agreed access rights and configurations, in your name; what day-to-day operation requires (backups, monitoring, procedures); a handover of knowledge; written conditions for taking the tool over; and the freedom to entrust future changes to Visionary Édition, or not. The rights transferred are those set out in the contract.
Which products demonstrate the studio’s skills?
Four products designed, built and launched by the studio, in unrelated fields: France ÉcoScan (public economic data), FYRIS (wildfire risk prevention), Visionary Stats Pro (statistics for draw games), Astro Destiny One (astrocartography and personal readings). Each is presented with its features, its verifiable evidence and a link to its site.
“We’ve always done it this way.” What if we did it better?Your idea deserves a proper look.
An everyday problem, a tool that no longer keeps up, an opportunity to seize, a product that does not exist anywhere yet: let’s work out together what is worth doing, and how to build it.
Every idea, however modest, deserves a real conversation. No specification or set budget needed: just tell me what you would like to improve or create.