Questions about a website or software project for Chile
Must we replace our existing application?
No decision should rest on its appearance alone. A repair review follows a failing task, checks the relevant account role and inspects what the application stored. We explain the supported repair, the useful behavior to retain and any dependency that makes a broader change necessary.
Can the first project be only a website?
Yes. A website can be a complete scope when it helps customers understand the service and sends usable details into an existing office process. A new portal or field application is not required merely because the business may benefit from one later.
Can you build tools used away from the office?
We can assess and develop that work. The brief needs representative devices, the information permitted on them and what should happen during an interruption. A saved local draft, a submitted update and a report visible to the office must have distinct meanings. Offline behavior is scoped and tested explicitly.
Does a comuna selection confirm service coverage?
Only if the business has expressly designed and approved that meaning. Often it supplies a location for assessment. The form and its response should make clear whether the organization is collecting details, offering a quotation or confirming a visit.
Can a customer see quotations and reports?
A customer area can provide that access when users, organizations and document states are defined. We review which version is approved, who may see it and what happens to invitations or saved links after access changes.
Can you connect our accounting or payment provider?
We first inspect the product, account permissions, supported interface and available test environment. Your accountant and provider decide the required financial and fiscal-document arrangements. A job completion event does not itself establish that a payment succeeded or a document was issued.
Are technical discussions in Spanish?
Our technical discussions and delivery are in English unless another arrangement is agreed. Spanish public information is available, and customer-facing Spanish can be included with an appointed language reviewer. Meeting, documentation and support languages belong in the project agreement.
How do we review accessibility?
The scope identifies the relevant journeys and review methods, such as keyboard use, labels, error recovery and the devices or assistive technologies to include. Technical checks and user review address the agreed requirements; they should not be presented as independent certification.
How are fees and dates established?
They depend on the inspected system, deliverables, content readiness, account access, external dependencies and acceptance work. Scope and pricing explains how to compare those responsibilities. Support and recurring provider costs are identified separately.
What is safe to send first?
A public link and a fictional example of the problem. Avoid credentials and confidential records in an ordinary inquiry. Use the contact page to describe the task; access arrangements can follow if they are needed.
