Software in production
Deployed and running for your users, not a demo or a staging link.
Process
From a requirement to software in production, in 30 working days.
Every accepted, scoped project follows the same structured process. You know what happens in each stage, what you receive at the end and what the relationship looks like afterwards.
The journey
Seven steps, from first conversation to ongoing care.
Consultation
You tell us what you want built. We ask the questions that turn an idea into something that can be scoped.
Scope and quote
You receive a written scope, a quote and the terms, including the annual maintenance contract, before you commit to anything.
Advance and kickoff
The project is accepted, the advance is received and requirements gathering begins. This is when the working-day count starts.
30 working days of engineering
Discover, plan, engineer, verify and deploy, in the four stages set out below.
Handover
The software is in production. Your team has admin access, documentation and training.
15 working days of refinement
Changes, new features and customisation within the agreed reasonable scope are included.
Annual maintenance contract
The system continues under a mandatory AMC, with coverage written for it.
The build
The 30 working days.
The count begins when the advance has been received and requirements gathering has started. Working days exclude weekends and public holidays; your contract sets out how approvals and outside dependencies affect the schedule.
30of 30 working days
Working days 28–30
Verify & Deploy
Testing, deployment to production and handover to your team.
Discover
Working days 1–3
Requirements gathered and the scope agreed in writing.
Plan
Working days 4–13
The solution's direction and the milestones you will see it reach.
Engineer
Working days 14–27
The software built, with its integrations, against the agreed scope.
Verify & Deploy
Working days 28–30
Testing, deployment to production and handover to your team.
Refine
The following 15 working days
Included changes, new features and customisation, within the agreed reasonable scope.
AMC
After refinement
A mandatory annual maintenance contract, with coverage tailored to your system.
Handover
What you receive.
Admin access
Your team can manage users, settings and data from day one.
Documentation
How the system works and how to run it, written for the people who will.
Training
Sessions with your team so the software is in use, not just delivered.
After refinement
The annual maintenance contract.
The AMC is mandatory for every SPEXA system. We state that here, in the quote and in the contract, so it is never a surprise.
Why it is required
Software in production needs someone accountable for it: security updates, upgrades, monitoring and fixes. The AMC is how that responsibility is kept after launch.
What it covers
Coverage is written for your system, not copied from a template. Your AMC schedule lists what is included, what is excluded and how support requests are handled.
How it is billed
Monthly or annually, as your contract states. It begins when the refinement period ends.
Renewal and termination
Set out in your contract, alongside licence and data-export terms. You see all of it before the project starts.
Questions
Common questions.
When does the 30-working-day count start?
When the advance has been received and requirements gathering has begun. Time spent waiting on approvals, content or access from your side, or on third parties outside our control, is handled as your contract sets out.
What counts as a working day?
Monday to Friday, excluding public holidays. The exact calendar is written into your contract.
What is included in the 15 working days of refinement?
Changes, new features and customisation that fall within the reasonable scope agreed at the start. It is not an unlimited allowance: anything beyond that scope is discussed, scoped and quoted before work begins.
Who owns the software?
You receive a licence to use the deployed software, along with admin access, documentation and training. TRUFFAIRE retains ownership of the source code. Your data is yours. Licence, data-export and termination terms are explained during consultation and set out in the contract.
Why is the AMC mandatory?
Software in production needs someone responsible for it: security updates, dependency upgrades, monitoring and fixes. Because TRUFFAIRE hosts the engineering knowledge and the source, the AMC is how that responsibility is kept, and it is why the system keeps working after launch.
What does the AMC cover, and what does it not?
Coverage is written for your system: typically maintenance, updates, support requests and agreed response times. New features and third-party fees are usually outside it. Your AMC schedule lists both, with billing, renewal and termination terms.