Start with the actual work.
With your teams, we describe a process, its pain points and constraints. We select a useful, measurable use case.
Outcome: scope, required data, responsibilities and success criteria.
SMEs & mid-market
AI agents for your internal tasks.
I start with a process and your teams: find useful information, prepare a reply or a summary. A bounded pilot checks the results before any deployment.
Work with Frédéric Brédard. 9 years in software architecture · Vaujany, near Grenoble, France.
SME EXAMPLE · INTERNAL REQUEST
A prepared reply, with sources to review.
Someone asks how to access a project folder. The agent prepares a reply; the responsible person keeps the decision.
An entirely fictional case explaining the workflow. No software connected and no access granted.
-
The request
“How do I request access to my project folder?”
The specific folder and the person responsible for the project have not yet been identified.
-
Authorised sources
- [1] Access procedure · section 2The request must be approved by the person responsible for the project.
- [2] Permissions matrix · read accessThe intended permission level for this type of request is read-only.
Two fictional extracts. In a pilot, sources and reading permissions are agreed with your team.
-
The sourced draft
Prepared · not yet sent“Your request must be approved by the person responsible for the project [1]. The intended permissions are read-only [2]. Please specify the folder and your project lead.”
Missing information is requested; no access is described as already granted.
-
Human approval
The responsible person reviews the sources and scope, corrects the reply if needed, then approves it.
Granting permissions remains within the company’s process. This illustration performs no action.
What a pilot needs to check: the correct source retrieved, a faithful reply, missing information flagged and the approval respected.
Discover. Test. Deploy.
Test a bounded use case.
The agent works in a controlled environment. Replies, limits and approvals are evaluated using representative cases.
Outcome: observed results, gaps and a decision to continue or stop.
Adapt to your environment.
Access, hosting, connections and operations are defined with your responsible teams. Launch follows an agreed acceptance process.
Outcome: an operational scope, identified owners and a defined follow-up process.
Each stage has a fixed price and defined deliverables. Connections to your software are assessed during discovery; no integration is assumed to be available.
Governance is part of the work.
Appropriate access
Permissions limited to the useful scope, agreed with your IT team.
Clear decisions
Explicit roles for reviewing, approving and taking over.
Useful evidence
Tests, records and a stop procedure reviewed before activation.
A first conversation, focused on one task.
A short conversation to understand your task and its constraints, then choose a useful next step: a tailored demonstration or an initial scoping discussion.
Describe my need