What happens today?
Describe one real situation and who is involved.
CONTACT
What needs to work differently?
Tell us what happens today and where it gets stuck. You don’t need a complete plan to start.
DIRECT CONTACT
Start with one situation.
Email us your situationinfo@fiusion.nl
Please don’t send confidential documents or details about clients, residents or colleagues. Our privacy statement explains what we do with your message and how long we keep it.
Where does work get stuck?
Tell us about the workaround, manual step or uncertainty that takes up time.
What needs to change?
Describe the outcome you’re looking for. You don’t need a technical solution yet.
How your message could begin
A few concrete sentences can say more than a long feature list.
‘Our scheduling and administration teams use different systems. Every change means someone retypes the data. We want both teams to know which information is current.’
The situation
Make clear where the work happens and which people or teams depend on each other.
The difficulty
Describe the recurring action or uncertainty you want to change.
The intended outcome
Say what needs to work better. The technical solution can remain an open question.
This is a fictional example message. Describe your own situation in general terms without confidential information.
If you already know
This context helps explain the question.
Tell us how often the problem occurs, which tools are used today and who works with the process every day.
A target date, dependency on another project or an existing internal agreement can be relevant too. Explain that context so the reasons behind the constraint are clear.
You do not need every answer in advance. If you are unsure where the problem begins, describe one recent situation. Distinguish what you know from the questions you want to explore.
QUESTIONS & ANSWERS
Useful to know before you start.
Do I need technical knowledge?
No. An account of everyday work is a useful starting point. Describe what someone is trying to do, what happens now and the outcome they need. You do not need technical terminology to do that.
Do I need to know the project budget already?
No. There is no price list for custom software. Price, timing and the form of the engagement follow from what the software needs to do, and we make that concrete together first. If you already have a budget or a target date, mention it as context.
What information should I leave out?
An initial description does not need real customer files, passwords or other people’s personal details. Use general roles and fictional data to explain the problem. Appropriate arrangements need to be in place before sharing confidential material.