Implementation and support
A tool on its own changes nobody's work
The platform can be up and running quickly. Whether anything really changes is decided by what happens around it: how you set the process up, what people see, and who takes you through the first cycle. Below we set out what we do at each of these steps, and what stays on your side.
What the platform does, and what we do
Platforma
The core, which stays with you for good.
- ready process modules we assemble your flow from
- reminders and a pace that keep teams in a rhythm
- one place with data on activity, progress and results
- permissions, an event log and data held in the European Union
Us, around the platform
The work that makes the core start working at your company.
- translating your goals and priorities into the structure of the process
- preparing the content and presentation your employees will see
- prowadzenie przez pierwszy cykl, do pomiaru ustalonej liczby
- moving what worked across to the next teams
We do not advise you on strategy and we do not write bespoke software. We reproduce your process in a working system.
What a rollout looks like
At every stage you can see what is on your side and what is on ours, because the most common question before the start is “how much work will this take my team”.
01
We agree what has to change
We start from the outcome, not from features. We name the process that has to work, and how you will know it worked.
- Po Waszej stronie
- you point to the process and the person who runs it
- Po naszej
- we translate it into a structure in the platform
02
We build the process from ready modules
We do not write bespoke software. We assemble your process from steps the platform already has, and show it working before it enters your company.
- Po Waszej stronie
- you look at it and say what to improve
- Po naszej
- we assemble it and make the corrections
03
We prepare the layer people actually see
The content and the visual side of the process are part of the rollout, not an add-on. Without them the process works technically and nobody uses it.
- Po Waszej stronie
- you give us the materials and the tone you speak to your teams in
- Po naszej
- we prepare the content and the presentation inside the platform
04
We start on one slice
A start with one team, one site or one group of roles. With a date, and with a number we check once it is over.
- Po Waszej stronie
- you choose the slice and the deadline
- Po naszej
- we launch it and run it through the first cycle
05
We roll it out to the rest
Only what worked on the slice goes to the whole organisation. Every next team joins on a process that already exists, so each start is shorter than the first.
- Po Waszej stronie
- you decide the order
- Po naszej
- we move the process across and keep it repeatable
You do not have to start with the whole company
Most often we start with one slice: one team, one site or one group of roles. The pilot has a set end date and one number that we check when it finishes. If that number does not move, you know within a few weeks rather than after a year.
- Jeden procesthe one that gets in your way the most today
- Jeden wycinek organizacjia team, a site or a group of roles
- End dateset at the start, not moving
- Jedna liczbaagreed before we start, checked once it is over
What actually makes a rollout longer
Rarely the software. Four things that pushed deadlines most often in our projects, and what we do about them.
A process that does not exist yet
If the process is being designed alongside the rollout, the rollout takes as long as designing the process. At one customer that stretched the whole thing to well over a year.
That is why the pilot starts from a process you already run, even if it lives in a spreadsheet.
The security review
In large companies the security documentation has to be closed before the integration starts. That is a separate calendar, and the rollout waits for it.
That is why we share the documents without a non-disclosure agreement and up front, not on request. See what is ready →
Data from your HR system
We do not claim ready-made connectors to HR systems. Employees join the platform through a file import or through automatic account creation over SCIM, and our API is designed to exchange data with your systems.
That is why the pilot does not wait for an integration project. We start on the import and set the integration up in parallel.
No owner on the customer side
A rollout without one person who decides drifts into agreeing things between departments. It is the most common cause of delay we see.
That is why at the start we agree who makes the decisions, and work with that person.
Opinia klienta
“I honestly wish every IT solution could be rolled out as smoothly as Gamfi. Internal candidate satisfaction is a perfect 5/5, which reflects how well this went.”
What happens after the start
You are left with a working process
The process is in the platform and it belongs to you. You connect the next teams on the same pattern, without starting from scratch.
Zmiany robicie u siebie
Changing the content, a deadline or the order of steps does not mean commissioning work from us. That is the difference the phrase “software, not a project” is about.
Every next team joins faster
The first start costs the most work, because that is when the process is created. Every team after that joins on a pattern that is ready.