Questions about an Argentina-connected website or software project

Are you based in Argentina?

Faith Forge Labs delivers remotely from the United States. This site explains work for businesses connected with Argentina; it does not represent an Argentine office. We agree communication, access and review arrangements for each engagement. If your project requires attendance at a local site, identify that requirement early so responsibilities can be assessed.

Can we discuss the project in Spanish?

Tell us your preferred language when you enquire. The working language and any translation or specialist review are agreed before work. Spanish pages help explain the offer, but do not establish a promise of dedicated Spanish-language staffing or continuous availability. Technical decisions and their approved meaning need a shared written record whichever language is used.

Do we need a new website?

Not necessarily. A confusing product description, an unsupported form connection and a broken layout call for different investigations. We can assess a defined repair where the existing system still fits the work. A rebuild is considered when its scope and migration consequences are justified by the evidence. The repair or replace guide sets out a practical comparison.

Can you work on a catalogue without adding online payment?

Yes, a catalogue can support product selection and a quotation enquiry. That can be appropriate when availability, quantity, presentation or delivery must be reviewed before an offer is made. The customer-facing wording should explain that they are asking for a quote. Checkout is a separate scope with payment, order and fulfilment responsibilities.

Can the site connect to our existing management system?

We need to inspect the provider, account permissions, available interface and relevant records before committing to a connection. Similar customer names or shared email addresses do not establish that records belong together. A first integration might be a defined read-only report rather than automatic changes in both systems. See system integrations.

Will you decide our invoicing or tax rules?

Your business and qualified advisers approve those rules. We can document required fields and implement agreed behaviour in the relevant software. A form should not collect fiscal identifiers simply because another business does, and a display format does not establish correct tax treatment. Official sources include ARCA as a starting point for the appropriate professional review.

Can we send customer records to explain the problem?

Start with a fictional example, redacted material or a description. If real data is necessary later, identify its purpose, location, access and retention before sharing it. Remote access from the United States belongs in that review. The applicable privacy and international-transfer questions require assessment for the specific arrangement; a technical demonstration is not a legal conclusion.

Can a bilingual site use the same product information?

It can share approved codes, specifications and other common facts while presenting explanations suited to each audience. The project needs a terminology record, named reviewers and a way to identify a correction that is still pending in another language. Language switching should connect equivalent pages where they exist and clearly identify other destinations. The language adaptation guide develops that process.

Will an appointment form confirm a visit immediately?

Only if the agreed service rules and actual scheduling system support that outcome. Many businesses need to review duration, travel or preparation first. In that case the form should collect a requested time and explain the confirmation step. A selected calendar slot must not overstate what the business has accepted.

What will a first delivery include?

The scope should name the task, pages, connections, review conditions and handover. A first release might cover one product family or one internal request. It should still complete the agreed journey, including what happens when information is unclear. Wider product coverage or additional roles can be considered after the first task is demonstrated.

Are ongoing support and provider subscriptions included?

They are defined in the agreement. Hosting, paid applications, translation review and external services may have separate costs and owners. Support also needs a clear scope: changing a description, diagnosing an incident and adding a new process are different requests. Support planning explains what to establish before delivery.

What should we send first?

Describe one problem, its effect on the customer or team, and the result you want to review. Include a public link or platform name if useful. You can use the project brief or go directly to the enquiry page.