Youalreadypayfortheassistant.Nowgiveityourcompany.
An AI Skin is the layer that turns a generic AI assistant into your company's operating system.
CH.01·What changed
It is generic by construction. The AI Skin is what gives it shape.
Claude, Codex and Copilot became the place where work happens. The earlier applications turn into data providers, and people stop opening them.
An assistant without a skin knows how to talk and does not know your company: how a proposal is written here, who may see which data, what must be reviewed before a deploy.
The person is the integration
Each application lives alone. The person carries the data between them.
12
steps for one question
4
logins along the way
0
systems that talk to each other
The assistant crosses them
The applications stay where they are. They become data services, and nobody opens them.
AI SKINreads the rules, crosses the systems
Quarter review
Set the quarter, see the impact live, and export both files with working formulas.
Quarter sales
1.84 M€
plan +9%
New customers
127
HubSpot
Open pipeline
3.2 M€
Salesforce
Win rate
31%
plan 28%
CH.02·The assembly
Five layers turn generic into yours.
Plugged in: the skin the console just built, on any of them.
One skin, any runtime
what every runtime has to do
- Take an instruction
- Read your files
- Call your systems
- Record what it did
You are buying the capability. The runtime is the socket it plugs into.
CH.03·The two variants
One stack, two kinds of work.
The stack is the same. What changes is the method, the connectors and the dashboards.
AI Dev Skin
The whole software lifecycle in the place where code is written. House practice stops living in a wiki nobody opens.
AI Business Skin
Office work in the same place. Integrations wired, permissions defined, dashboards per role.
| AI Dev Skin | AI Business Skin | |
|---|---|---|
| What it covers | The whole software lifecycle | The office work around it |
| Where it runs | Where the code is written | Where the work is discussed |
| The method | Standards, reviews, quality gates | Proposals, brand voice, follow-up |
| The connectors | Repositories, pipelines, trackers | CRM, mail, ads, ERP |
| The dashboards | Release health, review load | Pipeline, budget, campaigns |
| Who asks | Engineers | Sales, marketing, finance, HR |
Same five layers underneath. What differs is the method, the connectors and the dashboards.
A skin can be narrower than either of these. A sales-only skin is a legitimate product, and usually the better first sale: small scope, visible value in weeks.
CH.04·A day with it
No application was opened.
The CRM is still the system of record and email is still email. What changed is where the person works.
A sales role, at a company with its CRM, mail and ad accounts connected.
- 09:10
Prepare my 11am with Nortec.
The skin reads the CRM history, the recent email thread, who accepted in the calendar, the open tickets, and the spend on the live campaign.
- 09:11
It returns a dashboard. Who is in the room and their role, contract value and stage, what was promised last time, the two unresolved issues, and budget spent against plan.
- 09:14
Draft the renewal proposal.
It comes out on the approved template, with current list pricing, a discount inside the policy limit, and the house visual identity.
- 11:55
Log this.
Notes go into the CRM, the stage moves, and the follow-up is written in the brand's tone of voice and left as a draft for review.
CH.05·Said honestly
What it is, what it is not, and where it stops.
What an AI Skin is
Five plain claims, in the order they matter.
- 01
Your company, written down
How work is done here, as rules a machine can follow. Written once, read by every assistant you use.
- 02
Installed in the tool you already pay for
It goes inside Claude, Codex or Copilot. There is no extra application to open and no migration to run.
- 03
Wired to the systems you already have
The CRM, the mail, the drive and the ticket queue stay where they are. The skin reaches them with your permissions and leaves a trail.
- 04
Answers ready to act on
A dashboard, a document or a report, in your visual identity, with the action at the end already prepared.
- 05
Versioned like software
A rule changes in one version and reaches everyone on Monday. What changed is readable, and it can be rolled back.
What an AI Skin is not
- 01
Not a chatbot
A chatbot answers. A skin acts in the systems, with permissions and with a trail.
- 02
Not a coding copilot
A copilot completes lines. The Dev Skin covers the whole cycle, from spec to operations.
- 03
Not RPA
RPA repeats a fixed path and breaks when the screen moves. A skin works on intent and data.
- 04
Not another SaaS
There is no extra application to open. It is the opposite.
- 05
Not a model trained on your data
We do not train models. We give governed access to data that already exists.
- 06
Not a folder of prompts
Prompts have no versions, no permissions and no audit.
Limits, said before you ask
A sales page with nothing but upside loses the technical buyer in the first meeting. These are for saying out loud.
- 01
Source applications do not disappear
The CRM is still the system of record. What changes is who goes there.
- 02
Portability is not equal in every layer
Connectors travel best. Method and widgets follow each runtime's formats and take work to cross.
- 03
A skin is only as good as the rules you give it
If the company does not know its own discount policy, neither will the skin. Much of the value sits in the discovery.
- 04
It is not instant
A useful skin comes out of a process. What is fast is the first narrow scope, rather than full coverage.
- 05
It needs an owner on your side
A skin with nobody maintaining it decays like any other software.
See one of your own tasks built as a capability
Book an hour. We pick one real task, design it with the people who do it today, and tell you what it takes.
We connect nothing to your systems for a first conversation.
Glossary
- AI Skin
- The full layer, access through distribution, installed above your runtime.
- Runtime
- The AI assistant the skin runs on: Claude, Claude Code, Cowork, Codex, Copilot.
- MCP
- The standard protocol connecting an assistant to an external system. In practice, the connector.
- Gateway
- The MCP of MCPs. Single point of access, permissions, limits and audit.
- Skill
- A unit of method: a house procedure the assistant knows how to execute.
- Hook
- A rule that fires automatically at a point in the flow, without anyone invoking it.
- Widget
- An actionable visual interface returned inside the conversation, in your identity.
- Marketplace
- Your private channel, through which the skin is installed, versioned and updated.