Free first conversation
What you need, and whether building something is the right answer.
Most one-person consultancies write as though they were a team. This one will not. You get the documentation as we go, every account in your own name, code in escrow if you want it, and a named substitute for longer work.
Documentation delivered as we go, accounts in your name, and a substitute named for longer engagements.
Building the application or tool a business needs, with documentation delivered alongside it.
See the programConnecting systems that do not talk to each other, and automating the work in between.
See the programReviewing a codebase, a quotation or a supplier's proposal before money is committed.
See the programDocumentation, escrow, access and a named substitute, so you are never dependent on one person.
See the programA written scope with deliverables rather than instructions, documentation delivered as the work proceeds, accounts held in your name, and a named substitute for anything long enough to matter.
What you need, and whether building something is the right answer.
Deliverables, dates, fees, exclusions and who owns what.
In increments you can see, documented as we go.
Access, documentation, and escrow if you want it.
Quoted per project or per review. Source code escrow is arranged with a third party and charged at cost.
A scope, a deliverable and a date.
Continuing development and support, on a written basis.
Said plainly, because it protects you too.
Every engagement is quoted after a free consultation. No subscription.
KRISDEVS is a company incorporated under Belgian law, registered with the Crossroads Bank for Enterprises under enterprise number 0778.905.149, based in Genk in Limburg and trading since December 2021. The work is software development, systems integration and IT consultancy, and it is carried out by one person.
That last fact is a risk and it belongs on the front page rather than in a footnote. So four things are agreed in writing at the start: documentation is delivered as the work proceeds and not promised for the end, every hosting account, domain and repository is registered in your name with you holding administrative access, source code and build instructions can be deposited with a third party at your request, and for longer engagements a named substitute contractor is identified. Separately, engagements are structured around deliverables rather than instructed hours, because an arrangement with fixed hours, direct supervision and exclusivity can be reclassified as employment under Belgian law — and the arrears of social security contributions that follow can be claimed from the client, not only from the contractor.
A fair question and the reason that is on the home page. You hold administrative access to every account, domain and repository because they are registered in your name, not ours. Documentation is delivered as the work proceeds. Source code and build instructions can be placed in escrow with a third party. And for longer engagements we name a substitute contractor in advance. None of that eliminates the risk, but it means your system does not stop being yours.
Because of how Belgian law treats the nature of a working relationship. An engagement presented as self-employment can be reclassified as employment where the reality shows subordination: set hours, direct instruction, integration into a hierarchy, exclusivity. Reclassification brings arrears of social security contributions, and they can be claimed from the client as well as from the contractor. Working to a defined scope protects both of us.
It means depositing the source code and build instructions with an independent third party, who releases them to you if agreed conditions occur, such as the supplier ceasing to trade. For a system your business genuinely depends on, it is worth the modest annual cost. For a small internal tool, probably not. We will tell you which we think it is.
Because an account in a supplier's name is leverage, whether or not it was intended as such. Hosting, domains, repositories and third-party services should be registered to you with you holding admin access, so that ending the relationship is an administrative matter rather than a negotiation. We would rather you stayed because the work is good.
No, and treat any supplier who says yes with suspicion. We apply proportionate measures, keep things patched, and report any incident we become aware of without delay. A guarantee of invulnerability is not a thing that exists, and promising one discourages the precautions that are properly yours.
Yes, and it happens reasonably often. Existing software frequently covers a need better and more cheaply than something written from scratch, and a process is sometimes better removed than automated. Saying so costs us a project and saves you more than the project was worth.
A free first conversation, with no obligation, to work out whether we are the right fit.