Estimating software · ERP
We choose a family of works. Olivia gets the assumptions, risks and limits of the ratios used spelled out, then links them to the reference files.
Sector · Construction and engineering
Your estimating software, ERP, plans, standards and site reports hold the documents. Estimating ratios, technical pitfalls and the lessons of a job often stay in the teams' heads. Skillsay links these explanations to the sources so you can prepare the next file without redoing the same searches.

Installation tips, points to watch and fixes are often passed on by word of mouth. When people move to another job or leave, the context can be lost.
Plans, reports, method statements and exchanges can sit in several places. Finding the right document and its version means knowing where they are.
A method that works on one job doesn't always apply to another. A useful answer must point to the job, the source and its context.
The spreadsheet keeps a price or a duration, not always the assumptions. To estimate a new job, the project manager has to find whoever knows the original constraints.
Today
Reuse a spreadsheet ratio, then call the expert to check its assumptions.
With Skillsay
Find the documented ratio, the reference job and the explanations that set its limits.
Today
Pass on instructions as exchanges happen and people are available.
With Skillsay
Capture practices orally or in writing and make them available to authorised roles.
Today
Search separately in the known folders and storage spaces.
With Skillsay
Ask a question about the connected documents and access the items cited.
Today
Manually check whether the document found is the one that applies.
With Skillsay
Keep documents with their source and version to make checking easier.
Today
Have someone who knows the file decide.
With Skillsay
Surface diverging information with its context and direct it to the right named expert.
Your tools, your knowledge, your agents
Your teams' knowledge, linked to your documents, dated and sourced.
Custom agent
Answers questions from the accessible instructions and lessons learned, citing their sources.
Custom agent
Gathers documented ratios and their assumptions to prepare an estimate to check.
Custom agent
Finds the documents linked to a topic and highlights their versions and original units.
Custom agent
Matches similar situations without mixing up their contexts, and suggests the sources to review.
Fictional example. Agents and their scope are defined with your teams.
Estimating software · ERP
We choose a family of works. Olivia gets the assumptions, risks and limits of the ratios used spelled out, then links them to the reference files.
Site reports · Plans
We gather the documents and have people describe the technical choices, difficulties and solutions. The next job finds the lessons with their context.
Standards · Technical documents
We connect the corpus your teams use. Answers point to the sources and their versions; gaps are submitted to a named expert.
ERP · Site reports
We capture the landmarks the site manager or design lead passes on orally. Authorised people find the explanations and the useful documents.
Estimating software · Plans
We bring together comparable files and field feedback. The team checks the differences in context before reusing a solution.
We start from a concrete situation: an expert leaving, a search that keeps repeating or knowledge to share. We choose the first useful scope with you.
We agree the people to interview, the sources to link and the expected result. You know what will be delivered and at what price before launch.
Olivia captures the teams' knowledge. We link it to the documents and tools, then open the platform on the chosen scope to make that knowledge usable.
We estimate time lost per process, then measure the gains with the teams. The quarterly roadmap is used to choose what to improve next.
You choose what goes into the memory, who can query it and where it runs.
Access is defined by role. Each person and each agent queries the memory within their authorised scope. The data stays under your control.
Claude, ChatGPT, Copilot or your own agents can query the memory via MCP, with each person's access rights. Skillsay works with the AI model you choose.
Skillsay is hosted in France and can be installed on your premises. A fully sovereign chain is possible, including Olivia's voice and intelligence. Data is AES-256 encrypted and never used to train a model.
The data belongs to you and remains exportable. You stay in control of your company memory and its scope.
The questions to ask before linking your line of business's knowledge to your tools.
Book a demoNo. Connectors link the useful tools. Custom connectors can be considered depending on your systems.
Units and documents are associated with their source and version so the context can be checked. Choosing the applicable document remains for your teams to approve.
Yes. Knowledge can be captured orally and in writing, in the languages the teams use.
Hosting can be in France or on the customer's premises. Data is AES-256 encrypted, with role management and the option to export.
Contradictory information should be presented with its context and source, then submitted to the right named expert.
Choose a concrete situation, link its sources and check the answers with your teams.