> For the complete documentation index, see [llms.txt](https://pmse.gitbook.io/pmse-dhdk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pmse.gitbook.io/pmse-dhdk/1.-project-charter/1.8-financial-budget.md).

# 1.8 Financial budget

The financial budget for the project is divided into four primary categories: **Development Costs**, **Testing Costs**, **Operational Costs**, and **Documentation and Support Costs**. Each category includes specific elements that contribute to the overall project expenses.

## Development Costs

* **Software Development**:\
  This includes the costs associated with designing and developing the user interface (frontend) and the server-side functionality (backend). The team will require a software developer and an AI engineer specialised in NLP tasks. They will work on the chatbot's implementation and user interaction flow and integration with backend systems.
  * Software developers and engineers in Italy typically charge between €20-€70 per hour, depending on their experience. Assuming 2 developers working 300 hours each:
  * Estimated cost: **€12,000 - €42,000** (based on €20-€70/hour)
* **AI Pipeline Development**:\
  This encompasses the development and integration of the AI engine, specifically the Mistral language model and other AI components, including fine-tuning the model, embedding generation, and integrating it into the chatbot system.
  * AI engineers in Italy typically charge between €40-€90 per hour.  Assuming 1 AI engineer and NLP Specialist working 250 hours:
  * Estimated cost: **€10,000 - €22,500**
* **Integration with the Customer’s Web Platform**:\
  The integration of the chatbot with the customer's existing web platform, ensuring seamless functionality and a consistent user experience, will require specialized development and coordination.
  * *Estimated cost cfr. "Hosting and Infrastructure Costs" in Operational Costs below.*

## **Testing Costs**

* **QA Resources for Unit and System Testing**:\
  This covers the cost of Quality Assurance (QA) resources for performing unit testing (testing individual components) and system testing (ensuring all components work together as expected).
* **Performance and Security Testing**:\
  This includes the costs of testing the chatbot's performance (e.g., speed, scalability) and security (e.g., vulnerability testing, data protection). Ensuring the chatbot can handle high traffic and operates securely is critical.
  * QA engineers in Italy typically charge between €25-€60 per hour. Assuming 1 QA engineer working 200 hours for testing:
  * Estimated cost: **€5,000 - €12,000**

## **Operational Costs**

* **Hosting and Infrastructure Costs**:\
  The hosting costs for both the prototype and final application include server and cloud storage expenses. This also includes the cost of managing the infrastructure that supports the AI chatbot during development and after deployment.
  * The cost of integration will depend on the complexity of the platform. Cloud hosting services (e.g., AWS, Google Cloud, or Microsoft Azure) typically cost between €200-€1,000 per month, depending on the scale of the infrastructure and traffic. In addition to this, we need to account for the cost of managing and scaling the infrastructure that supports both the AI chatbot and the RESTful API.\
    For a medium-scale project, the cost for 6 months of hosting might range:
  * Estimated cost: **€1,200 - €6,000** (this includes API infrastructure, cloud storage, and scaling)
* **Licensing Costs for Third-Party Services**:\
  This covers the costs of licensing third-party services, such as the Mistral language model tokens, cloud storage, and other external tools or APIs required for the AI chatbot to function.
  * <mark style="background-color:yellow;">Licensing fees for LLM tokens or similar services typically range from €500 to €3,000 annually, depending on usage and pricing tiers. However, for this project, the decision was made to use</mark> [<mark style="background-color:yellow;">Mistral AI</mark>](https://mistral.ai/)<mark style="background-color:yellow;">, which offers open-access API tokens at no cost.</mark>

## **Documentation and Support Costs**

* **Documentation Creation (User Guides, Technical Manuals)**:\
  This includes the costs for creating user documentation (guides on how to interact with the chatbot) and technical manuals (detailing the architecture, deployment, and maintenance processes). Clear documentation ensures the application can be easily used and maintained by both users and developers.
  * Creating user guides and technical documentation in Italy typically costs between €25-€50 per hour. Assuming 1 technical writer working 150 hours:
  * Estimated cost: **€3,750 - €7,500**
* **Customer Support for Post-Deployment**:\
  Post-deployment support is crucial for addressing any issues that arise after the chatbot is live. This includes technical support, bug fixes, and addressing user feedback.
  * <mark style="background-color:yellow;">Customer support services in Italy typically range from €20 to €40 per hour. This can be further discussed with the customer to establish a contract for ongoing updates and interventions, but this won't be included in the current estimate.</mark>

## Contingency Funds

To account for unforeseen expenses, we can allocate a contingency fund, typically 10-15% of the total estimated cost. This fund is set aside to manage unexpected costs that may emerge during the project, offering flexibility to address risks while maintaining the project's scope and quality.

For the sake of this estimation, we will allocate 5% of the total estimated cost as contingency funds.

## Budget Summary

The cost estimations were calculated with both lower and upper ranges to provide flexibility and account for uncertainties in the project. The **lower range** reflects the **best-case scenario** with **minimized costs**, while the **upper range** accommodates **unforeseen challenges** that may increase expenses. This approach offers stakeholders <mark style="color:blue;">**a more realistic view**</mark> of the financial requirements, supporting better planning and risk management throughout the project's lifecycle.

| Category                        | Estimated Cost (€)     | Percentage of Total Budget |
| ------------------------------- | ---------------------- | -------------------------- |
| Personnel                       | €37,750 - €122,500     | 45% - 55%                  |
| Development Costs               | €22,000 - €64,500      | 27% - 32%                  |
| Testing Costs                   | €10,000 - €24,000      | 12% - 16%                  |
| Operational Costs               | €1,200 - €6,000        | 2% - 5%                    |
| Documentation and Support Costs | €3,750 - €7,500        | 4% - 6%                    |
| Contingency Funds               | €2,000 - €7,000        | 5%                         |
| **Total**                       | **€42,700 - €109,122** | **100%**                   |

***

*See bibliography for source references:*

{% content-ref url="/pages/AREq45CUwxFVZbKIgeeZ" %}
[Bibliography](/pmse-dhdk/sources/bibliography.md)
{% endcontent-ref %}

{% embed url="<https://www.statista.com/statistics/416213/average-annual-wages-italy-y-on-y-in-euros/>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pmse.gitbook.io/pmse-dhdk/1.-project-charter/1.8-financial-budget.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
