Questions about Switzerland-connected development work

Does this website mean you have a Swiss office?

No. Faith Forge Labs delivers development remotely from the United States. This site explains potential work for Switzerland-connected organisations. It does not claim Swiss premises, a local professional licence or endorsement by a bank, government body or software provider.

Which languages can a project include?

The language scope follows the actual audience and content needed to complete a task. German, French, Italian, Romansh and English may be relevant, but the project must identify suitable translation and approval arrangements. Technical coordination is in English unless otherwise agreed. Publishing a language version does not by itself establish customer support in that language.

Can a multilingual site reuse one document for several audiences?

Sometimes, if the underlying offer, audience and approval are genuinely the same. Language matching alone cannot establish that relationship. A German-language document may describe a different service or version from the one a Swiss customer needs. We define page and document families deliberately and make missing or unreviewed counterparts visible.

Can you connect our quote tool to invoicing?

That depends on the available interfaces and the records that identify the approved work. We need to establish which quote version may be billed, how revisions are handled and which system owns the invoice. The business and its accounting or legal reviewers decide commercial rules; the integration implements those approved decisions rather than deriving them from a button label.

Do you develop Swiss QR-bill integrations?

We can scope relevant technical work around the applicable SIX specification and your banking or software-provider arrangement. A QR image that scans is not proof that every field combination, document requirement or reconciliation step is correct. Version, currency, account type and reference handling need deliberate validation. Access, eligibility and fees are confirmed with the provider.

Can we preserve an application another supplier built?

An assessment can examine available source, deployment, data and operational tasks within authorised access. The result may support repair, staged modernisation or replacement. Missing documentation does not automatically justify discarding useful behaviour, but unavailable code, account ownership or export capability can materially affect the options.

Is hiding a download button enough to restrict a document?

No. The access decision needs to apply to the underlying request for the file, as well as to the interface that links to it. The review should include direct downloads, exports and relevant alternate paths using ordinary and unrelated accounts. The exact controls and data handling follow the approved project requirements.

Will a data-control project certify legal compliance?

No general certification is implied. Engineering can implement agreed collection, permission, logging and retention decisions and provide evidence of specific tests. Your organisation and qualified advisers establish applicable obligations, supplier arrangements and international access requirements. Remote development from the United States needs to be considered in that review.

How do you estimate an integration or portal?

We examine the task, source quality, record relationships, permissions, provider operations and acceptance cases. Similar screen counts can conceal very different work. A bounded assessment may be appropriate where a major dependency remains unknown. The scope page explains what should be included in the comparison.

Can an initial phase be useful without replacing everything?

Yes. A first phase might make quote revisions and their review status dependable while the existing accounting system remains in place. It should complete a meaningful part of the work and make its limits explicit. Disconnected screens that still depend on undocumented manual steps are a weaker result than a smaller complete task.

What happens after the system is handed over?

The agreement identifies routine maintenance, account ownership, operating notes and any continuing support. Content editing, access administration and technical releases require different responsibilities. Coverage hours, monitoring and response expectations are stated specifically; development does not imply round-the-clock support or guaranteed recovery times.

Can you investigate before we know the technical cause?

Yes. Describe the observable difference between the expected and actual result, with a safe example and the actions already taken. We can discuss an assessment that answers a defined question. Use the brief guide, then contact us with the detail that needs investigation.