Here is what happens at each step. Every project is its own case, and the process adapts to it.
A no-obligation conversation
In the first contact, we try to understand the real business problem — not a feature list, but what is costing the team time, money or risk today. This first conversation carries no obligation: it is there to find out whether there is a genuine fit between the client’s problem and the way we work.
A proposal, case by case
Building on the conversation, we design a proposal specific to the problem described: the scope, phasing, timeline and cost of each phase, and what is needed to get started. When the case calls for it, the proposal comes with a small demo built around the client’s actual case, to show how we would solve the problem before any commitment. Not every project needs this step: some are clear enough from the conversation and the written proposal. The decision to go ahead always rests with the client, based on the proposal.
Phased delivery
We work in phases: each phase goes into production as soon as it is ready for real use, and the client follows and validates what is being delivered against their own criteria, throughout the whole journey. Nothing moves forward without validation: observations from the people who will use the system day to day shape what comes next.
Hand-over and ongoing support
At the end of the last phase, the system is in use and documented. The documentation, delivered phase by phase, allows another team to carry it forward, if and when the client so decides. After hand-over, we support the system in use: fixes, adjustments and new phases, on the terms set in the proposal. The commercial model is also set in the proposal, based on the project: it can be a one-off delivery, ongoing support, or a mix of both.
The data always belongs to the client and can be exported at any time, with no forced dependency on Fluxidy.
Frequently asked questions
Do I need to know exactly what I want before talking to you?
No. The first conversation is for understanding the problem and its context; the scope is defined later, in the proposal.
Can we start with consulting only?
Yes. Consulting can be a standalone service or the first phase of a project.
Where is the data hosted?
Hosting is agreed with the client on each project, in the cloud or on the client’s own infrastructure. The data always belongs to the client.
What happens if we stop working together?
The data is yours, and the documentation delivered at each phase allows another team to carry the system forward.
How much does a project cost?
It depends on the scope. The proposal sets out the cost and timeline of each phase before any commitment.