Modules that don't break your upgrades.
Functionality built on the system's extension mechanisms, documented and transferable. No patches to the core.
Today's cheap development is tomorrow's impossible migration.
What we find when we review legacy developments.
Core modifications
Direct changes to the base system that make it impossible to upgrade without breaking everything.
No documentation
Nobody knows what that module does or why, and whoever wrote it is gone.
No tests
Every upgrade is a game of roulette: you find out what broke when the user complains.
How we develop.
It's implemented in stages, in the order that least disrupts your operation.
On top of the standard
We use the mechanisms the system provides, so upgrades keep working.
Written and accepted
Acceptance criteria agreed on before writing the first line.
A deliverable
What it does, how it's configured and how it's maintained.
Before production
Validation in a test environment with real cases from your operation.
Change control
Every version recorded, with the ability to roll back.
Yours
The code belongs to your company, transferable to any team.
From where you are to where you want to be.
Assessment
We look at how you operate today and where time or money is being lost. A fifteen-minute call to define the next step.
Data load and setup
We define the functional scope, the acceptance criteria and the delivery plan.
Assisted go-live
We train the team that will use it and support you through the first month-end close.
Ongoing operation
Support with an assigned account owner and contractual response times.
What people ask before signing up.
Does the module survive a version upgrade?
That's the criterion it's built on: without touching the core and on supported mechanisms.
Can I take the code to another provider?
Yes, it's documented and it's your company's property.
Is it tested before it goes to production?
Yes, always in a test environment with real cases before release.
How we quote.
We don't publish a price list because it would be made up: two companies in the same industry can need very different things. What we do guarantee is how you get to the number.
Quote after the assessment
After the call, if the case calls for it, a one-hour consultation sets the scope and a fixed price. If the scope changes, it's quoted separately and you approve it first.
Processes, data and users
Functional scope, number of integrations and complexity of the business rules. How many people will use it, how much data needs to be migrated, and how custom it needs to be.
Support by plan
Ongoing operation runs on a monthly plan, with an assigned account owner and contractual response times. It's contracted separately from the implementation.
Let's build what you're missing.
A fifteen-minute call and you walk away with a clear next step — even if the answer is that you don't need us yet.
Book your assessment
Leave us your details and we'll set it up for the next business day.
You're talking to Génesis, Valtriom's AI