FAQ / BEFORE WE START
What to know before starting your project
What do you need to start a project? How are requirements, integrations and delivery defined? Explore common questions about working with Codplex so you can begin the conversation with a clear understanding.
What needs to be clear
Which problem should be addressed first.
Which systems, people and data are affected.
How to assess whether delivery meets the need.
01 / FAQ
Before the first meeting.
You do not need a detailed technical document. A specific description of the task and its difficulties is helpful.
- An everyday example of the process.
- The tools and roles involved.
- Essential functions and any timing constraints.
02 / FAQ
What is agreed for each project.
Implementation needs a shared view of scope and responsibilities.
- Deliverables, acceptance criteria and review points.
- System access, data handling and third-party obligations.
- Usage rights, documentation, operation and support.
FAQ
Can you work with existing software?
Documentation, access permissions, data and available integrations are reviewed first. Technical feasibility must be confirmed before agreeing an extension or replacement.
Is there a fixed price or delivery time?
Estimates depend on scope, constraints and dependencies. Clarification comes before a specific proposal; there is no general published price list.
How are changes handled during development?
Changes are recorded along with their effects on priorities, deliverables and timing. They are agreed before being included in implementation.
What happens to source code and rights?
Usage, handover and access terms are explicitly agreed for each project, alongside third-party licensing obligations. No universal transfer of rights is implied.
Is maintenance included after handover?
Support, the operating environment and extensions are defined in the agreement. There is no automatic promise of continuous availability or a particular SLA.
Are the product and project examples real?
In this preview the examples are visibly labelled as fictional. They are not available products, actual customers or evidence of results.
Do I need a website or a web application?
A website usually suits service information and enquiries. Users, data, approvals or complex processes may call for a web application. Analysis may combine both.
How do we choose between a CMS and custom development?
We assess who updates content, which features are essential and what integrations are required. The choice includes licensing, upgrade and maintenance assessment.
Can an ERP update our online store?
Where suitable interfaces and access exist, products, prices, stock and orders can be assessed. A clear source of truth and failed-transfer handling are required.
Can a solution use open-source software?
Yes. Depending on the use case, we assess CMS platforms such as Umbraco CMS or Orchard Core on .NET and Payload CMS or Strapi Community on Node.js, commerce tools such as WooCommerce or the open-source Medusa core, and ERP/CRM tools such as Odoo Community or ERPNext. Versions, dependencies, licences and maintenance are reviewed before selection.
What is needed for an initial proposal?
A goal, main users, essential features, existing systems and priorities. An indicative timeframe and budget range help where available; do not send credentials or sensitive data.
Can a website include Greek and English?
Multilingual support is defined in the project scope. Greek/English versions need equivalent content, localised metadata, correct page pairing and checks in each language.
How much does custom software or ERP development cost?
The estimate depends on functional modules, users and permissions, integrations, data migration and deployment and support requirements. We clarify requirements first, then prepare a quote with a defined scope and deliverables.