Start small, build it out step by step.

How a systems project runs, from the first call to a system that works. You start with two features, not with everything at once.

The phases in order

Every phase is a finished piece you can use straight away. Quoted separately, paid separately, and you decide per phase whether to continue.

build it calmly

00
A call
free
Tell me in five minutes what is going wrong now. That is often enough for me to know whether I can help. Sometimes the answer is that a good standard package suits you better, and then I say so.
01
A visit
free, no obligation
I come over, show you a working system and walk through your process from request to invoice. Who does what, where things get stuck, what gets entered twice. After that you know what a system can do for you, and you get a proposal with a fixed price per phase.
02
First phase
1 to 2 weeks
The two features causing you the most trouble right now. Nothing more. Those go live while the rest of your business carries on exactly as before.
03
Settling in
as long as it takes
Your people work with it and I hear what does not hold up in practice. That is never quite what we drew on paper. Those changes go into the next phase.
04
Next phase
1 to 2 weeks
A few more features, quoted and paid separately. On like that until your system does what you need. You can stop at any point, and what is there keeps working.

Four things decide what a project costs. If you know upfront which ones weigh heavily for you, the quote makes sense too.

How much of the journey you take on
Work orders and invoices alone is a different story from the whole journey, from request through calculation and planning to production, invoice and payment. This is by far the biggest factor, and exactly why starting small pays off.
Integrations with what you already have
Your bookkeeping, payment links, your mail, or machines and measuring equipment that need to pass data along. Every integration is separate work and separate testing, and some packages cooperate more easily than others.
Who works in it
Just you is different from office, workshop and customers each having their own screen and their own permissions. As soon as people have to log in and not everyone may see everything, it gets heavier.
Where it gets used
Behind a desk is simplest. On a phone in the workshop, with gloves on, on a poor connection, or with a scan to open an order, is more work. Often the work that pays off most, though.

A system is not a website. There is a database under it, people log in, and if it stops your workshop stops. So no vague language about this.

Three months of warranty on bugs
If something does not work as agreed, I fix it free of charge in the first three months. Three instead of one, because the nasty cases only surface at your first month-end close, your first credit note, or the first time two people open the same order. Changes and additions are not covered, that stays new work.
If it breaks, you call me
I can get straight in, because the backups and logins run through me. I respond the same working day. I am not going to promise availability I cannot deliver alongside my job, so you will not read that here either.
Everything is in your name
Code, database, hosting and logins. From the day you pay, the system is yours. Want to carry on with someone else later? You take all of it with you. I work with technology any developer knows, so you are not tied to me.
There are running costs
A system needs a database, logins and backups, and that costs something every month. Count on a few tens of euros a month, depending on how much goes through it. That bill runs through your own account, not mine. With a website I could say it can be free. Here it cannot, so I say so now.

Send me a message with what you are looking for. I usually reply within a day.