What is built, what is not, and how I take on work.
Most software pitches are vague about their stage on purpose. You would ask anyway on the first call, and you would be right to. So here it is in advance, along with how a deployment actually works.
The mechanism is real. You can click through all of it.
A working demonstration, written from the ground up and running on my own infrastructure. Full 3D model with corner-cut section view, millimetre dimensioning, profile system, glazing, hardware, finish range across uni colours, wood decors and brushed metals, live price recalculation on every change, basket, currency and language switching.
The same engine built out for dimensional signage: specification, live pricing from fabrication rules, quotation generation and plotter output. Access provided on request.
Hosted and maintained by me if you have no infrastructure of your own, or deployed into yours if you do. Your customers see your site throughout.
Five things a brochure would imply and I will not.
If any of these is a dealbreaker for you, better that we both know now.
I would not sell it in its current form, and I am not going to show you a case study that does not exist. Everything on this site is my own build, and a deployment starts from your catalogue rather than from a template.
Enough to show the mechanism working end to end. It is not a finished product range, and it is not pretending to be one. A real catalogue is exactly the work that a first deployment consists of.
The rate card behind the demonstration is illustrative, not a commercial price list. The pricing engine is real (cost by area, by component, by finish surcharge, by discount tier) but it is running placeholder numbers until it runs yours.
Minimum and maximum sizes, opening-type constraints and the rest of what your workshop can physically make are still being built out properly. This is the part that has to be right, and getting it right needs a real manufacturer's constraints, not my assumptions.
That means direct access, fast changes and no account-management overhead. It also means you should ask me about continuity and source-code escrow, and I will answer straight rather than deflect.
How a deployment works, and what a development partner gets.
A configurator is only worth what its catalogue and its rules are worth, and those cannot be invented from the outside. I therefore work with a small number of manufacturers as development partners: your range, your constraints and your pricing shape the product, and the terms reflect what that contribution is worth.
Development partner pricing
Substantially below standard, in exchange for the contribution your catalogue and constraints make to the product. Agreed in writing before any work starts.
The product gets built around your business
Your size rules, your pricing structure, your opening types and your finishes become how the product works, not a customisation billed on top of it.
A reference, and nothing beyond it
Your name usable as a deployment, and a call with a prospect once or twice a year. No case study you have not approved, no logo where you did not agree to it.
And a way out
If it does not do what I said it would within the agreed scope, you do not pay the balance. I would rather carry that risk than ask you to.
A development partner takes on early-stage software from a small supplier. That is a real consideration and I am not dressing it up. What you get for it is pricing that does not come round twice, a product shaped around your business rather than someone else's, and a developer who answers the phone himself. If that trade does not suit you, waiting is a reasonable decision and I will still be here.
Twenty minutes, then a fixed figure in writing.
On the call: what you make, how you price it, and whether a configurator fits the way you actually sell. Afterwards you get a scoped plan, a timeline against your specific catalogue and a fixed cost, before anything is committed on either side.
I build 3D product configurators and quoting systems for window and sign manufacturers. The software is mine, written from the ground up.
Correspondence EN · IT · ES · FRCalls in English