Questions worth settling before development begins
Can we keep our present website or CRM?
Often the useful work is around an existing system. We first need to identify its owner, supported access and the behaviour you want to change. A site can receive new content while a CRM remains the sales record. If a platform cannot represent an essential relationship, that limitation should be assessed before promising a connector.
Do you issue CFE documents or decide the tax treatment?
The service is technical investigation and development around an existing provider. Your accountant, business and provider determine applicable requirements and document responsibilities. We do not claim DGI authorisation. A website order, payment and fiscal document should have separate references and statuses where the workflow requires them.
Does a Spanish page mean the project will be conducted in Spanish?
No. Project discussions and technical delivery are in English unless separate support is agreed. The website's reader, content reviewer and project's technical contact may need different language arrangements. Identify them before including translated content in the scope.
Can we start with a catalogue that does not take online payment?
Yes. When price, availability or specifications require review, a structured quotation request can be more appropriate than an immediate checkout. The page must explain what is being requested and what the business still needs to confirm. A later commerce phase would require its own provider and operating decisions.
Who should own the accounts?
Your organisation should retain control of the accounts and recovery arrangements needed to operate its service. Named technical access can then be arranged for the agreed work. The handover should identify domains, hosting, source or configuration, subscriptions and the people authorised to make changes.
What makes an estimate change?
Examples include undocumented dependencies, additional language variants, a provider capability that differs from expectations, or source data requiring substantial cleanup. A proposal should identify assumptions and exclusions. New findings should lead to an explained choice before they become unagreed work.
How will we know the project is ready?
Use the tasks agreed in the scope. A catalogue enquiry should preserve the intended product; an appointment change should leave a clear current time; a failed connection should be visible to the responsible person. Review recovery and permission cases as well as the successful path. A presentation alone cannot establish those results.
Is ongoing support included?
Only the arrangement agreed for the engagement applies. Maintenance tasks, coverage, response expectations and provider escalation are specified separately. A development handover should still explain routine operation and known limitations even when no ongoing support arrangement is purchased.
Will a new website guarantee overseas sales?
We can define and check development outcomes, such as clearer offer information and usable enquiries. Sales depend on wider commercial conditions, demand and follow-through. We do not replace those uncertainties with an invented growth forecast.