Client proposal
Describe the need and the scope, then prepare a proposal and its presentation slides from the same elements.
Saphan · Document automation
One project file.
Your documents
take shape.
A client request becomes a proposal, a presentation and a cost estimate. The Saphan document solution gathers the information they share: you prepare it once, you review it, then you produce several files.
Local prototype, shown as a demonstration. No automatic connection to your Microsoft account.
Documents · local prototypeThe common sourceYour project file, reviewed.
The need, the text and the cost estimate.
A validated version before every export.
- DOCXProposal
to rework - PPTXPresentation
to adapt - PDFCost estimate
to read
A COMMON STRUCTURE
The right content.
In every format.
The project file keeps the context, the text and the cost lines. Word and PowerPoint remain editable output formats, not frozen images.
Prepare
Enter the useful elements or add text extracted from authorized documents.
Review
Correct the project file, then validate that exact version. Any change calls for a new review.
Produce
Generate DOCX, PPTX, a demo PDF, CSV, HTML, Markdown and JSON from this project file.
Resume
Re-import the JSON into a new version, without overwriting earlier exports. Changes made in Word do not flow back automatically.
OPEN IT, DON’T JUST IMAGINE IT
From the client file
to the deliverable files.
L’Atelier du Léman is fictional. Its project file describes a pilot, three sections and three cost lines. The PDF and the JSON alongside are the actual outputs of this example in our prototype.
You can read the cost estimate, then open the structured source file. In a guided demonstration, this same project file also produces the Word document and the presentation.
The amounts are used only to test the calculations. They are not our prices, a quote or an invoice to be paid.
See Saphan’s budgets in CHF →IN YOUR BUSINESS
Where to start?
Three starting points to adapt. The benefit is measured on your documents and your corrections, not on a promise of productivity.
Intervention report
Gather the reviewed findings and the planned actions to prepare a report and an internal summary.
Project meeting
Organize decisions, constraints and next steps in a project file that can be reused for the document and the slides.
PROTOTYPE FEATURES AND LIMITS
A first workflow.
Clearly stated limits.
The basic mode assembles the information without calling an AI model. The amounts are calculated separately, never invented by a model.
- Local, single-userThe prototype stores its data unencrypted on the workstation. Trials use fictional or authorized non-sensitive data, and the lab is not put online.
- Files, with no connection to Microsoft 365No active Microsoft 365 connector, no SharePoint synchronization, no co-editing and no email sending. Opening the DOCX and PPTX files in your versions of Office is part of the pilot.
- Optional rewordingAn Ollama connection is planned for text. Its protocol has been tested with a simulated server; no real-model quality is claimed here.
- Keep your originalsThe prototype extracts text; it does not archive the imported documents. No OCR and no scan reading in this version.
The first trial: one project file, your team’s formats.
We agree on the inputs, the reviews and the outputs. We check compatibility and the full time needed before considering additional connections. The budget depends on this scope.