Questions about commissioning and maintaining the work

Do we need a complete specification before contacting you?

No. A description of the person, the task and the present difficulty is a useful start. A catalogue entry that repeatedly produces the wrong question may reveal more than a long feature list. Include a public or anonymised example and explain what a successful result would allow someone to do. We can identify missing decisions before treating them as development requirements.

Are you based in Italy?

Faith Forge Labs delivers remotely from the United States. This site is for work connected to Italy; it does not establish an Italian office, professional registration or an on-site service. If a project depends on physical attendance, local inspection or a regulated professional decision, that requirement needs an appropriate arrangement outside assumptions about website development.

Can the website include Italian content?

Yes, with an agreed content and review process. We identify who approves terminology, product meaning and commercial wording, and who maintains each language after handover. English is normally used for project communication and technical documentation. Additional communication or translation support should be agreed explicitly rather than inferred from the language of these pages.

Can you work with our current website or software?

We can assess an existing system when its relevant access, code, configuration and dependencies can be inspected. A supported repair may be appropriate; a replacement may be justified when the current platform cannot meet the requirement or has become impractical to maintain. The assessment should distinguish an observed limitation from a preference for a different technology.

Can a catalogue become an online store later?

Potentially, but purchasing adds decisions a catalogue does not settle. The merchant must identify the saleable range, prices, fulfilment rules, payment arrangements and customer terms. A product that is safe to describe may still require an individual quotation. We can structure the catalogue so references are dependable without promising that every item will later be suitable for unattended checkout.

Will an integration work with our accounting or management system?

That depends on the actual product, account, supported interfaces and permissions. An integration plan needs sample records and an explicit relationship between the website's information and the receiving system's records. We also need to establish how errors and repeated requests are handled. A provider's general API page does not prove that your account can perform the required operation.

Do you use AI?

AI can assist research, drafts, code and tests, with the work checked rather than accepted automatically. An AI feature for your own application is a separate scope decision. We consider the permitted source material, access rules, review requirements and the consequence of an incorrect answer. Drafting an internal response is different from approving a product specification or sending a commitment to a customer.

Who decides privacy, tax and accessibility requirements?

The organisation and its relevant qualified advisers establish the requirements applicable to the project. Providers determine the capabilities and eligibility of their own services. We can help document data flows, implement approved rules and investigate specific usability or accessibility problems. A developer's technical check is not a blanket legal assessment or a certification of the whole service.

How are fees and dates agreed?

We first define the work, the information available and the people needed for review. Content preparation, language review, provider access, migration and handover can affect both effort and sequence. The scope page explains the questions to resolve before a proposal, including how later changes should be discussed.

What happens after handover?

The project should leave clear account ownership, editing instructions and an agreed maintenance boundary. Support is scoped separately: which components it covers, how to report an issue and what access is needed to investigate it. A handover does not imply continuous monitoring or an unspecified response guarantee. See support for the practical information that helps an investigation.

What should we send first?

Use the enquiry page to describe one task and its intended result. Do not include credentials or private customer data. If several tasks are connected, show the sequence and identify the point that creates the most confusion. That gives us a concrete basis for deciding where to start.