Projects in Offertes.AI: one file for documents, quotes, and follow-up
Bring project documents, quotes, tasks, and communication together in one place, so your team works with the same context.

In Brief (BLUF)
A project only becomes manageable when documents, quotes, communication, and follow-up are kept together. The Projects module turns scattered files into a workable project file.
Key Takeaways
- A project file prevents specifications, drawings, and quotes from being scattered across inboxes and local folders.
- Version control keeps old and new documents apart without manual filenames like final_v3.
- Projects are the foundation for comparing quotes, chatting with documents, sending requests, and following up on email.
A construction project quickly contains dozens of documents: specifications, drawings, clarification notes, quotes, schedules, and separate agreements from email. As long as that information is spread across inboxes, download folders, and personal drives, everyone works with a slightly different version of the truth.
You usually do not notice that during a quiet moment. You notice it when a subcontractor calls about an old drawing, an estimator cannot find a quote, or a project manager has to find out which version was sent to the client.
The Projects module in Offertes.AI prevents project information from remaining a loose collection of files. Every project gets its own file where documents, quotes, versions, tasks, and communication come together.
Why a project file is more than a folder
A folder stores files. A project file stores context. The difference seems small, but in practice it is significant: for every document, you want to know what it belongs to, whether it is still current, and what needs to happen with it.
That is why Offertes.AI does not start from separate uploads, but from the project. First you decide which request, quote phase, or execution phase the information belongs to. Then you add documents, quotes, and follow-up to that same context.
The practical rule: if someone has to ask "where is that file?", the project file is not complete enough yet.
What belongs in a project?
A good project file separates different types of information. Not because you want more administration, but because each document type has a different role in the process.
| Part | Examples | Why it matters |
|---|---|---|
| Project documents | Specifications, drawings, clarification notes, schedules | This is the scope your team, suppliers, and subcontractors rely on. |
| Quotes | Price proposals, additional work lists, supplier offers | You use these documents to compare prices, conditions, and deviations. |
| Communication | Emails, questions, answers, and attachments | Decisions stay linked to the project instead of someone's personal inbox. |
| Follow-up | Tasks, checks, deadlines, and responsibilities | The file shows not only what exists, but also what still needs to happen. |
Version control prevents silent mistakes
In many teams, version control only appears when it is already too late. Files get names like
drawing_final_v2_new.pdf, while nobody is completely sure which version was sent out.
In Offertes.AI, you can add a new version to the same document. The current version remains clearly visible, while earlier versions stay available in the history. That means you do not have to overwrite old documents or hide them manually in archive folders.
That helps especially in three situations:
- Control: you see faster whether the team is using the latest drawing or specification.
- Handover: a colleague can see what was previously delivered or replaced.
- Later discussion: you can retrieve which version was available at a specific moment.
Projects connect the other modules
The value of a project file is not only in storing information. The file becomes the foundation for the work that comes next. Because documents and quotes are already linked to a project, you can use them directly in other Offertes.AI modules.
- Compare: select quotes from the project and compare prices, conditions, and deviations.
- Document chat: ask questions about specifications, drawings, or clarification notes using project documents as the source.
- Requests: send relevant project documents to suppliers or subcontractors from one file.
- Inbox: link project email and attachments to the right project, so correspondence stays visible to the team.
This prevents every workflow from starting with another search. The project is where the context is already ready.
Who is project management in Offertes.AI for?
Projects are especially valuable for teams managing multiple requests, quotes, or execution files at the same time, where document versions directly affect margin, planning, or scope.
- Estimators keep specifications, clarification notes, and received quotes together.
- Work planners find the right drawing, attachment, or latest version faster.
- Project managers see which documents and actions still need attention.
- Management keeps overview of active projects, even when knowledge sits with different colleagues.
Conclusion: start with the project, not the file
Separate files seem efficient as long as everyone knows where everything is. But once projects grow, people switch roles, or deadlines increase, that informal structure becomes fragile.
With Projects in Offertes.AI, you build the project file first and the workflow around it afterwards. Documents, quotes, communication, and follow-up live in one place. As a result, your team searches less, works with the same context, and every next step becomes easier to control.
Want to see how project email becomes part of the same file? Continue with the Central Inbox.
Stop manual work
Try our AI tools today.
Key Features
- •Project File
- •Document Folders
- •Version Control
- •Task Follow-Up
Common Use Cases
- •Centralizing documents
- •Comparing quotes
- •Improving project follow-up