Build
A fee per solution.
Goal, scope, deliverables, milestones, and acceptance criteria defined before we build.
Our method
First, a version.
We test it with you and decide how to move forward.
Four questions to move forward.
A specific challenge
What do you want to improve?
How we check it
We choose a process and measure its starting point: time, quality, errors or cost.
To move forwardOne goal, one owner and one way to measure.
Information with boundaries
What can AI use?
How we check it
We define data, permissions and actions that need human approval.
To move forwardLimited access and explicit human decisions.
A useful test
How will we know it works?
How we check it
We test everyday cases and exceptions before expanding the solution.
To move forwardReviewable tests, known limits, and a clear decision to proceed.
Continuity
Who looks after what we build?
How we check it
We agree on ownership, recurring costs and what to do if something fails.
To move forwardAn operations and handover plan your team can follow.
Reproducible experiment
Try the next step.
Explore a process, review its output and decide what should happen.
Interactive lab
From repetitive work to a decision.
Choose an example and try where your team steps in.
- Input
- Preparation
- Your decision
What comes in
What are your hours and how can I book?
Available information
Example hours: Monday to Friday, 9 AM to 5 PM. A person confirms appointments.
Routine information is prepared; your team keeps control of confirmation.
Simulation with fictional data and fixed rules. It does not use AI, send or save information.
Try an example: Your request
Suggestion
AI agents and automation
Choose another service
See how it works
What the system processes
We get many WhatsApp messages with the same questions about opening hours and prices, and we are slow to reply.
Personal data hidden: 0
Rules that matched
- “whatsapp, messages, questions” points to AI agents and automation
- “app” points to AI products and platforms
Validation
- Emails and phone numbers are hidden before classifying.
- The suggestion cites the rules that produced it.
- Nothing leaves the browser or is stored.
- A person approves or corrects it before anything happens.
Demo with synthetic examples and fixed rules, without AI. Your data is never sent or stored.
Your idea takes shape.
Understand
Together, we choose the problem, the people and the outcome we want to improve.
We test a first version with you. What we learn defines the next step.
Start your projectA project to begin. A partnership to go further.
We get involved in the outcome you want to reach.
Continuity
A monthly fee.
Support, maintenance, and evolution, with priorities and capacity agreed on for your operation.
The proposal separates initial investment, ongoing support, and third-party costs. No generic packages, unlimited development, or unstated conditions.
The full journey.
From the first conversation to operations. You can hire one stage or the full journey.
First conversation
You tell us about the process, the people, and the result you want to change, by WhatsApp, by email, or with a written request.
Qualification
We confirm there is a concrete problem, a responsible person, and a case where AI can help. If it is not a fit, we tell you.
Scope exploration
We agree on the question the first version must answer and the authorized information we use to prepare it.
First version
We prepare an exploration you can walk through. It is not a production system yet.
Validation
We review it with you: what works, what is missing, and what deserves to be built.
Proposal
You receive scope, deliverables, investment, third-party costs, and acceptance criteria in writing.
Implementation
We build in stages and test security, permissions, and critical journeys with representative data.
Optional operations
If you choose it, we operate and improve the system with an agreed monthly capacity. If not, it stays documented for your team.
The first version
What it is, what you get, and what you decide next.
The first version is an exploration with an agreed scope that we prepare before the proposal. It lets you decide with something you can walk through.
- Who it is for
- Companies with a concrete problem, a person who knows the process, and someone who can decide. If you are still exploring what to do, start with the assessment or with strategy.
- What we need
- The problem you want to solve, the person to talk to, the information you authorize us to use, and the question the first version must answer. We start with anonymized examples when possible.
- What you receive
- A representation of the experience or a test of one concrete dependency, which we review with you. We state which part works, which part is conceptual, and what still needs validation.
- What it lets you evaluate
- Whether the approach answers your problem, which data and integrations it would need, where a person must approve, and what deserves to be built first.
- What is not included
- It is not a production system, it does not use real data without permission, it does not include unlimited work, and it does not guarantee technical feasibility or a financial result.
- What you decide next
- Three paths: move to a proposal with scope, deliverables, investment, and acceptance criteria, adjust the approach and review it again, or stop there.
The scope of each first version is agreed before we prepare it. Its conditions are defined case by case with the team.
Five answers for a useful first conversation.
You do not need a technical document. With these answers we can better understand your starting point.
Do not include passwords, customers' personal data, or confidential information in your first message.
Start your project- 1Which process or experience do you want to improve?
- 2Who uses it and who makes the decision?
- 3Which tools and data exist today?
- 4What result would tell you it worked?
- 5Which time, investment or security constraints should we consider?