# Implementer pilot: one IFS Cloud project in 90 days

An Implementer pilot is a fixed-price engagement that installs Implementer in your infrastructure and runs one real IFS Cloud project from registers for 30 or 90 days, ending with a licence decision or an export.

## How does a pilot work?

Four steps from the first call to your decision.

1. **Scoping call (30 minutes)**

   We check the project mode, the next gate, the templates you use today and the people who will work in the tool. You get a written proposal with success criteria drafted.

2. **Kickoff and installation (weeks 1 to 2)**

   Installation on your host, Entra ID sign-in, the project created with its gates and checklists. Success criteria are agreed in writing.

3. **Loading and daily use (weeks 2 to 12)**

   Your registers are loaded, the team works in them and the steering pack is generated from them. Review at day 45.

4. **Closing review (day 90)**

   We go through the success criteria one by one. You decide: annual licence, or a data export and removal of the installation.

## What is the Implementer pilot?

The pilot puts Implementer into your own infrastructure and runs one real IFS Cloud project on it. Your risks, CRIM objects, interfaces, test cycles and gate checklists move from Word and Excel into registers with an owner, a state and a history. At the end you decide on a licence with your own project data in front of you, and the pilot fee counts toward it. The [product page](https://implementer.ifs-erp.com/en/product.md) describes the tool.

## Who is it for?

Customer-side project managers, solution architects and PMOs on an IFS Cloud project that is running or about to start: a [new implementation](https://implementer.ifs-erp.com/en/new-implementation.md), a [rollout](https://implementer.ifs-erp.com/en/rollout.md) or [BAU with updates](https://implementer.ifs-erp.com/en/bau-evergreen.md). It makes sense when a gate is coming and the evidence sits in a dozen files, when the CRIM log and the interface list disagree, or when an update cycle starts and the regression set is in someone's mailbox. It does not make sense if the project has no plan for the next 90 days, or if nobody on your side can own the tool day to day.

## What does it cost?

| Variant | Duration | Price |
| --- | --- | --- |
| Mirror, about 10% of the project | 30 days | EUR 3,450 |
| Standard, one project | 90 days | EUR 6,900 (EUR 4,800 for the first three) |
| Extended, two environments, IFS connection, one gate decided in the tool | 90 days | EUR 13,800 |

The fee, in any variant, is credited against the first-year licence if you continue. Prices are net, plus VAT. See [pricing](https://implementer.ifs-erp.com/en/pricing.md) for the licence and payment terms.

## What is included?

- Installation on your Docker host behind your reverse proxy, with sign-in through your Microsoft Entra ID tenant.
- First-time setup: the first administrator, one project in its mode, its five gates with 61 checklist items, and your approval rules.
- Members and roles for the team. Access follows project membership and role.
- Loading of the registers you already keep, from your Word and Excel files: up to five registers and up to 500 rows in total. The team enters the rest after the working session.
- An optional read-only OData connection to your IFS Cloud environments, with one OAuth2 client per environment.
- One working session with the project team, a review at day 45 and a closing review at day 90.
- Email support, Monday to Friday, 9:00 to 17:00 CET, with a P1 response within 4 business hours.

## What are the success criteria?

They are written down at kickoff and fit your project. Typical examples: the registers named in the proposal are loaded and each open row has an owner, the team changes states in Implementer instead of in spreadsheets, one steering group meeting runs on the generated status report, the next gate has evidence recorded per item, and the audit log answers who changed what and when. No numbers are promised in advance. Your project sets the baseline and the closing review measures against it.

## What is out of scope?

A second project or installation, IFS Cloud consulting on the project itself, carrying out data migration into IFS Cloud, changes to the Implementer code, integrations with Jira, Azure DevOps or MS Project, and hosting. Implementer runs on your infrastructure.

## What do you provide?

A Linux x86_64 Docker host (4 vCPU, 16 GB RAM, 100 GB SSD) with DNS and a TLS certificate, an Entra ID tenant with an administrator, an IFS Cloud project in flight, a project manager who owns the tool on your side, and your existing templates and registers.

## What if you stop after the pilot?

Leaving is a data export, not a migration project. You get a database backup, the PDF files and JSON from the API, and on request a one-hour session to remove the installation. The IFS connection only reads, so the pilot cannot change anything in your IFS Cloud environments. Read more on [security and trust](https://implementer.ifs-erp.com/en/security-and-trust.md).

## How do you start?

[Book a scoping call](https://www.ifs-erp.com/en/book-time-with-me), or try the [live demo](https://implementer.ifs-erp.com/login) first. Questions are answered in the [FAQ](https://implementer.ifs-erp.com/en/faq.md).

Last updated: 13 November 2026

## Ready for a pilot?

A 30-minute scoping call and a 15-minute demo on demo data.

[Book a scoping call](https://www.ifs-erp.com/en/book-time-with-me)
