FREQUENTLY ASKED QUESTIONS
Answers to the questions we hear most often.
Direct answers to common questions about working with CREANODE — how projects work, how pricing is determined, what the platform is, and what happens after a project is delivered.
Projects
How long does a project take? A focused tool or automation: two to six weeks. A full management system or client portal: two to four months. Larger multi-module systems: four to eight months or more in development phases.
How does the process start? With a conversation. You describe the problem; we ask about the operation, the constraints, and the outcome you need. From that we can tell you what we think the right approach is and what it might cost — with no commitment required from you.
Do you work remotely? Yes. All projects are managed remotely. We communicate through video calls and written documentation — no wasted travel time for either party.
Pricing
Do you have fixed prices? No. Every project is different. We price based on scope, complexity, and the collaboration model that fits the work. We provide clear pricing before any development begins.
What collaboration models do you offer? Dedicated project (defined scope and price), subscription (ongoing development at a monthly rate), maintenance retainer, and modular development. See the pricing page for details.
Is there a minimum project size? No formal minimum. A well-defined small project is as welcome as a large one. We assess every inquiry on its merits.
Platform
What is CREANODE OS? The platform we've built that powers client systems — providing authentication, permissions, audit logging, module management, and operational infrastructure. Most projects are built on this platform so they don't need to rebuild these foundations from scratch.
Are you locked into CREANODE OS? No. If a project requires a different technical stack, we use one. The platform is the default because it reduces cost and increases reliability — not because it's mandatory.
Who owns the code? You do. Completely. Every line of code we write for a project belongs to the organization that commissioned it.
After Delivery
What happens after the project is delivered? We offer maintenance and support through a monthly retainer — covering bug fixes, security updates, dependency management, and operational monitoring. This is optional but recommended.
Can we add features after delivery? Yes. Additional modules and features are added through the same process — scoped, priced, and built. The system is designed to grow.
What if we want to take the system in-house? You own the code. Full documentation of the architecture and codebase is part of the delivery. Handover to an in-house team or another contractor is fully supported.
More Questions
If your question isn't answered here, the contact form gets you a direct, specific answer — not a sales call. We respond to every inquiry and tell you honestly whether and how we can help.