> For the complete documentation index, see [llms.txt](https://docs.didge.io/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didge.io/home/pricing/fsms-starter-packages/packages-overview.md).

# Packages Overview

A Practical Pathway to Digital Food Safety

#### Introduction

The MFC Starter Packages are designed to provide businesses with an accessible, practical, and low-risk entry point into the world of digital food safety management. These packages support organisations in their transition from traditional paper-based or fragmented HACCP systems to a modern, data-driven food safety culture, built on real-time monitoring, accountability, and continuous improvement.

Each starter package offers a tailored introduction to the MFC Safe Didge platform allowing businesses to experience its capabilities before committing to a full-scale rollout.

The starter packages have a duration of 4 to 8 weeks, depending on the size and scope of your kitchens. Larger establishments may require longer periods.  After the starter period is complete, you can decide to continue to a production project, suspend or kill the trial. 

<table><thead><tr><th width="286.234375">Package</th><th>**Lead Time</th><th>AUS $ Price</th><th>USD $ Price</th></tr></thead><tbody><tr><td><ol><li>Essentials</li></ol></td><td>Same Day</td><td>Free</td><td>Free</td></tr><tr><td><ol start="2"><li>Mobile &#x26; Probe Set</li></ol></td><td>1 Week</td><td>$300</td><td>$200</td></tr><tr><td><ol start="3"><li>Tablet &#x26; Probe Set</li></ol></td><td>1 Week</td><td>$480</td><td>$320</td></tr><tr><td><ol start="4"><li>Thermal &#x26; Probe Set</li></ol></td><td>1 Week</td><td>$950</td><td>$620</td></tr><tr><td><ol start="5"><li>Food Product Sensor Set</li></ol></td><td>2 Weeks</td><td>$1600</td><td>$1100</td></tr><tr><td><ol start="6"><li>Cook Chill Set</li></ol></td><td>1 Week</td><td>$920</td><td>$600</td></tr><tr><td><ol start="7"><li>Combo Set</li></ol></td><td>2 Weeks</td><td>$2700</td><td>$1800</td></tr></tbody></table>

\*\*Lead Time to get you access and hardware for your package shipped to you.

\#Postage and GST, VAT or Import tax is additional to the prices quoted

***The first step is to book a meeting.***

<a href="https://calendar.app.google/5DhKWiVaGyCrRqh79" class="button primary" data-icon="arrows-to-circle">Book a meeting</a>

***

#### Purpose

The Starter Packages help businesses:

* Experience digital food safety in action — through live temperature monitoring, sensor data integration, and digital record keeping.
* Assess suitability — trial the MFC system in a limited scope (such as one kitchen or production area) to determine operational fit and user acceptance.
* Support change management — facilitate the cultural shift from manual to digital processes in a structured, low-risk way.
* Build internal champions — empower key staff to test, learn, and advocate for digital transformation in food safety.
* Establish a pathway to partnership — provide the first step in an ongoing collaboration between the business and MFC Safe.

***

#### Why Start with a Starter Package

Many organisations already have established Food Safety Management Systems (FSMS) or HACCP programs, often built on legacy paper forms or outdated digital tools. Transitioning to a new system can seem daunting — involving both technical and cultural challenges.<br>

The Starter Packages are engineered to bridge that gap. They offer:

* A cost-effective trial environment to validate performance and reliability.
* A scalable implementation model that can expand as the organisation grows in confidence.
* A hands-on demonstration of how digital food safety enhances compliance, efficiency, and visibility.
* A guided change process, supported by MFC’s implementation team.

***

#### How It Works

1. Select a Starter Package that best fits your business type, size, and operational priorities.
2. Deploy in a limited scope (e.g., a single kitchen, production area, or site).
3. Monitor and review system performance and staff engagement.
4. Evaluate outcomes — including data insights, workflow efficiency, and ease of compliance.
5. Plan the next phase — expanding into full system adoption with confidence.

***

#### Designed for Different Business Needs

Each Starter Package is tailored to a different operational context — from small food service operators to large-scale manufacturing or hospitality environments. While all packages share the same goal of introducing digital food safety, they differ in:

* Scale and number of sensors/probes included
* Reporting and dashboard capabilities
* Training and onboarding support
* Integration depth with existing FSMS or quality systems

***

#### Outcome

By the end of a Starter Package trial, your team will have:

* Hands-on experience with real-time digital monitoring.
* Practical insights into how digital tools can improve your existing HACCP processes.
* A foundation for decision-making on scaling the system across multiple sites.
* A clearer understanding of the role digital food safety plays in long-term compliance and operational excellence.

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didge.io/home/pricing/fsms-starter-packages/packages-overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.