Step 1 · The product
What exactly will be supplied, and to whom.
What we do, in detail
Four services. The first one happens before anybody writes code.
Program 01 · Before the first line
Settling who the manufacturer is
This is twenty minutes of work that occasionally saves years of it. A client who commissions software and then sells it under their own brand becomes its manufacturer, and the duties attach to them: conformity, CE marking, a bill of materials, a disclosure policy, updates across a support period, and a vulnerability report within twenty-four hours. Whether a particular deliverable is a product on the market or a bespoke item for one client is not answered the same way in every case, so we do not pretend to a general ruling. We settle it for your project, in writing, and price the consequences.
Step 2 · The market
Whose name goes on it when it ships.
Step 3 · The duties
Allocated in writing, party by party.
Step 4 · The cost
Support period scoped and priced.
Step 1 · Scope
What it does, and what it will not.
Step 2 · Build
In increments you can see running.
Step 3 · Inventory
Every component and its licence.
Step 4 · Hand over
Code, documentation and instructions.
Program 02 · Code 62.100
Custom development
Two things are produced alongside the code rather than after it, because both become obligations the moment a product reaches a market. The first is documentation good enough for a developer who has never met us. The second is an accurate inventory of every third-party and open source component and its licence, which is what a software bill of materials actually is. Assembling that list at the end, from memory, is how projects discover a licence nobody can live with.
Program 03 · Code 70.200
Technology consultancy
The most useful answer a technology adviser gives is often that nothing should be built. Existing software frequently covers a need better and far more cheaply than something written from scratch, and the new obligations change that calculation again: buying a compliant product moves the manufacturer's duties to its vendor, while building your own keeps them. That trade-off deserves to be on the table before a budget is approved, not after.
Step 1 · The decision
What actually turns on this.
Step 2 · Options
Build, buy, or leave it alone.
Step 3 · Duties
Which option puts duties where.
Step 4 · Recommend
In writing, including the risks.
Step 1 · Period
How long, agreed and written down.
Step 2 · Scope
Which updates, on what timescale.
Step 3 · Channel
Where a researcher reports, and to whom.
Step 4 · Act
Within the periods the rules require.
Program 04 · Priced, not implied
Maintenance and support period
A support period is a commercial commitment with a cost, and the Regulation expects it to run for years rather than months. The honest consequence is that it has to be budgeted at the quotation stage, by whoever carries it. Where we carry it, the period, what it covers and what it costs are written down. Where we do not, we say so plainly, because a client who assumes maintenance that nobody agreed to is the most common way a secure system quietly stops being one.
Something to build, or a product about to carry your name?
A free first conversation, with no obligation. We will tell you where the duties land before you commit a budget.