Questions before choosing a website or software project
Is Faith Forge Labs based in Estonia?
The service is delivered remotely from the United States. This site addresses projects connected to Estonia; it does not represent an Estonian office. Project conversations and technical delivery are in English unless separate language support is agreed.
Can our website include Estonian content?
Yes, a project can include Estonian content where its preparation, review and maintenance are scoped. Identify who can confirm the factual and linguistic meaning, including errors, confirmations and downloadable material. A translated homepage does not establish that every service detail or project conversation is available in Estonian. The language-availability guide explains how to make those boundaries clear.
Do we need to replace our existing website or application?
Not necessarily. A missing explanation, incorrect configuration or isolated workflow defect may be repairable. Replacement becomes a serious option when the supported system cannot represent an essential rule, required access is unavailable or continuing maintenance is no longer workable. The decision should follow evidence about your actual tools and dependencies.
What should we bring to the first discussion?
Bring one task, a public link or safe example, and an explanation of the result you need. Include the people involved and the tool that currently holds the relevant record. Do not send credentials or private customer data. The project note helps structure this information.
Can you connect our CRM, accounting system or another provider?
Integration scope depends on the provider’s supported interfaces, your account permissions, the fields involved and the operation required. Moving a name and email address is different from creating an approved transaction or changing a record with an existing history. Discovery needs to establish those limits and how rejected or uncertain transfers will be handled.
Will a login prove that someone can approve an order or document?
A login establishes access to an account under the system’s authentication rules. The application still needs to determine whether that person may approve this particular action for this organisation or project. The business owns the authority decision; the software must enforce the agreed permission at the relevant operation.
Can you decide our tax, privacy or accessibility obligations?
The client and appropriate advisers determine the obligations and policies that apply. Faith Forge Labs can implement and test agreed technical requirements. Practical accessibility work may remove barriers in a defined journey, but it should not be described as a blanket legal or compliance guarantee. Official references provide starting points for further review.
How are prices and delivery dates agreed?
They depend on the included journeys, current system, content, external access, review work and remaining uncertainty. A proposal should connect the price to those responsibilities and explain dependencies that affect the schedule. There is no universal package assumption for a custom workflow. Read pricing and scope.
What happens when a provider is unavailable during testing?
The affected check remains unresolved unless another agreed method can establish the required result. A local demonstration can test parts of a journey, but it cannot prove that an unavailable external service accepted the intended record. Record the limitation and the person responsible for completing the check.
Is maintenance included automatically?
Maintenance and continuing support need an explicit agreement. Identify account owners, update responsibilities, content review, backup and recovery tasks, and the route for reporting a problem. The support page explains what to establish before the original project closes.
Can we send the full data export now?
Start with a description or purpose-built fictional sample. An export may contain more personal or confidential information than an initial discussion needs. If later work requires real records, agree the necessary fields, access, handling and deletion arrangements first.