Frequently asked questions

There are six lines: Software Factory for an end-to-end project, agile cells embedded in your team, co-creation when the product is built and operated together, consulting and quick wins with fixed scope, AI and agents in production, and our own products. They combine well: starting with a diagnostic and continuing with a cell is common.

A fixed-scope project has defined scope, timeline and price, and ends on delivery. A cell is continuous capacity: a stable team embedded in your operation that prioritizes with you month by month. Clear scope favors the project; permanent evolution favors the cell.

It is assessed case by case. In co-creation Gatblac funds the development, so a specialist team reviews the viability of the initiative with metrics and market analysis before committing. When a case qualifies, the client gets the solution as a service without financing the development; when it does not, we propose the right alternative instead, an end-to-end project or an agile cell embedded in your team.

No. We do not sell loose hours or isolated profiles: a cell has defined roles, responsibility for the outcome and its own ceremonies. In practice, we answer for what is delivered, not for someone's attendance.

There is no headcount minimum. The lightest entry point is the Digital Diagnostic and Opportunity Matrix, from 12 UF, which maps where it pays to invest before committing to development. From there it scales to a project or a cell.

With a conversation and, if needed, a short diagnostic. Then comes a proposal with scope, timeline, assigned team and way of working. Once agreed, the kickoff sets boards, ceremonies and acceptance criteria.

The first weeks already deliver reviewable increments, because we work in sprints with partial deliveries. In co-creation there is also a working demo on your real case before signing, so the decision is made on something usable.

Detailed scope with what is and is not included, assumptions, a phased work plan with timelines, the assigned team, payment milestones, warranty and commercial terms. The quote is the document that anchors the project: what is written is what gets built and later certified.

Between 15 and 30 days from issue, depending on the type of proposal. After that we review team availability and pricing before reconfirming. For subscription services, the fixed fee stays stable during the first 12 months from signature.

In UF, the Chilean inflation-indexed unit. Invoices are issued in local currency using the UF conversion on each issue date. Proposal amounts are net, so VAT is added at invoicing.

Against milestones defined in the proposal, for example a percentage at kickoff and the rest against certified deliveries. Each invoice has a 30-day payment term, under Chile's 30-day payment law. Subscription products are billed monthly or annually, depending on the plan.

With the contract signed and the purchase order or contract annex already issued. With that we schedule the kickoff, both sides name their counterparts and the first phase begins. It helps to issue the purchase order early, since invoicing and payment terms depend on it.

It can be done. The agreed scope and the test plan define what the original budget covers, they do not prevent growth: a new feature, or redefining a requirement against the initial definition, is handled through a change control or an additional quote. You always see the price and the impact on the timeline before deciding.

The business goal, the systems to integrate with, regulatory or infrastructure constraints, a sense of volume and who the counterpart will be. When the requirement is still fuzzy, we start with a short diagnostic and quote on what we found, not on assumptions.

In custom development, cloud, licenses and third-party services stay under the client's name, and the client provides the access needed to operate. In our subscription products, infrastructure is included in the plan, except third-party consumption, which is passed through at the amount actually invoiced by the provider, with no markup.

The industry's leading models: Anthropic Claude, OpenAI GPT and Google Gemini. The choice depends on the use case, cost and latency, not on fashion. LARA Suite orchestrates them, so switching models does not mean rebuilding the solution.

Yes. When regulation, data sensitivity or latency demand it, we deploy open models on the client's infrastructure, on premise or in their private cloud, and orchestrate the solution just as with a cloud model. Data does not need to leave the organization.

No, and that is part of the judgment. Most business problems are better solved deterministically, with traditional software. AI comes in where it adds measurable value: natural language, classification, assistance and automation of repetitive work.

It is a transfer of practices so your team works with AI, not a one-off talk. It follows the AI Fluency framework and its four dimensions, with hands-on sessions for key areas, a working toolkit and support during the first months.

With context engineering: the agent gets the right, bounded context, answers are validated against your own sources and every interaction is traced. Where errors are costly, a person stays in the loop and the agent proposes rather than decides.

Building software with agents orchestrated by software engineers: the agent speeds things up, the engineer defines, reviews and answers for the result. It applies even to systems that use no AI, because it changes how we build, not the final product.

A sprint is a fixed period of work that starts with an agreed commitment and ends with working software you can review. Ours run from 2 to 4 weeks: 2 when we have full control of the project, 3 or 4 when several teams, or teams in different countries, have to be orchestrated. Ceremonies include the client; they are not one-way reports.

With shared boards, constant software increments and progress documentation. Scope is refined sprint by sprint, and every change is recorded with its impact on timeline and effort.

A designated counterpart empowered to decide, a weekly tracking session and timely answers on validations. Agile timelines depend on approvals arriving on time; when they slip, it is recorded in the tracking with its impact on the plan.

It depends on the model. When we build for the client, the intellectual property is 100% theirs and the code lives in their repositories from day one. For our own products, the source code belongs to Gatblac and the client gets the solution in use, under license or subscription. In co-creation we fund the investment and therefore hold the intellectual property of the tool: the client gets the solution to their problem as a service, without having to finance the development.

Yes. Projects include a functional warranty equal to 30% of the project duration, starting after formal acceptance. It covers fixes on what was delivered and certified, as long as the definitions and the certified environment do not change. New features are quoted separately.

With quality engineers inside the team, and their job is not only testing: they define the test plan, the key document that works as a delivery checklist of the agreed functionality. That plan bounds what was agreed and prevents later ambiguity about what was in scope. Certification runs against that plan before production, and on critical systems we add non-functional testing and architecture review.

With the execution of the test plan, the client's validation and formal acceptance of the deliverables. The warranty starts from that point. Depending on the project, we also hand over technical documentation, user manuals and deployment guidelines.

We work with the client's standards and, where appropriate, inside their own environments with least-privilege access. We sign confidentiality agreements, and personal data handling is described in our privacy policy.

Yes. We have our own NDA template that we share for signature, and we also work with the client's NDA: in that case our legal team reviews it and, once approved, we proceed to sign. The agreement covers the team assigned to the project, not only the company.

With the same standard already applied to corporate email or any industry cloud service: enterprise plans whose terms exclude client content from model training, access limited to what is needed, and data handling written into the contract. When data cannot leave the organization, the alternative is a local model on the client's own infrastructure.

Yes. Much of our work happens in capital markets, banking and asset management, where regulatory compliance, traceability of every operation and narrow change windows are the norm. That is the context we have worked in for years.

The team holds Scrum certifications (Developer, Product Owner and Professional) and FinOps Certified Practitioner. On security, our management framework is built and operated in line with ISO/IEC 27001, supported by the NIST Cybersecurity Framework and CIS Controls v8, and certification is under way. We answer supplier risk assessments with evidence document by document, as banking and capital markets require.

Capital markets, banking, asset management and payments, machinery and industry, transportation and mining, technology, plus specific projects in automotive, education and events. Each industry has its own page with the projects behind it.

Yes. We arrange references by industry and project type. We also publish cases on the blog, with the context, the solution and the outcome of each one.

No. The portfolio includes holdings and regulated companies, and also mid-sized firms and early-stage products. Fit comes down to two things: software being central to the problem, and budget capacity to develop it professionally, with a real team, quality and support behind it.

We are in Santiago, Chile, with a registered address in Las Condes and an office in Providencia. The team works mostly remotely, and we have run projects with subsidiaries in Peru and Colombia, in the same time zone or on agreed hours.

Mostly remotely. On projects we arrange on-site sessions for key moments, such as kickoff, functional discovery and production releases. For agile cells and squads there is also the option of a hybrid or on-site setup at the client's offices, subject to feasibility.

Yes. They are all professionals employed by Gatblac, in compliance with Chilean labor regulations. That continuity is part of what you hire: the team that starts the project is the one that finishes it, rather than a rotating pool of third parties.

Yes. We have teams and client communication in English, and documentation can be delivered in the language the project requires. This site is available in English too.

It is our own multichannel intelligent agent platform: web, WhatsApp, app and APIs, with an admin panel to monitor conversations, take over and train with documents. It runs today in banking, automotive and capital markets.

Yes. LARA Suite, Ivento and the Micro-SaaS solutions have subscription plans, with enterprise setups when custom integrations or a dedicated SLA are required. We can show them in a demo on your case.