FAQ

KINTO is an AI, product-hacking and growth agency, operated by KINTO LLC in the United States. It turns a company's operations, such as WhatsApp sales, ERP, catalog and ad spend, into agentic systems that run routine work on their own, with approval or validation before anything moves money. It works in English and Spanish.

KINTO publishes its work by type of company, never by name, to protect its clients. Each case explains the problem, how it was understood, what was built and what changed, with figures as ranges and a stated source. Each also lists what KINTO does not know yet, so results are not inflated.

Forward deployed engineering is a model where engineers work inside a customer's own systems and data to build and run solutions in production, instead of advising from outside. Palantir says it pioneered the role, and it is now common at AI companies. KINTO applies it to WhatsApp sales, ERP, catalog and ad spend, with approval or validation before anything moves money.

KINTO does not publish a price list. Scope and price are defined after a diagnosis of your operation, because projects range from a one-page site to an ERP replacement. Where a measurable baseline exists, payment tied to results is an option KINTO can propose; it is not the default model.

No. KINTO's case studies report measured results as ranges with their source and say plainly what is still unknown; several have no evidence yet of later sales. Any commitment is defined per project after the diagnosis, and a result-based fee is only possible when there is a measurable baseline.

It depends on scope. In KINTO's published cases, a one-page site took about three working days, a community radio's streaming migration about a month, a store migration about two months, a study-abroad site of over 100 pages about six weeks, and an agentic ERP about six months. Each case lists its period.

Book a call from the contact page or write to [email protected]. KINTO then runs a diagnosis of your operation: processes, data and where value is stuck. From that diagnosis come the scope, the plan and the price. You do not need to know the solution in advance, only the problem.

An agency delivers a campaign or a site, and a consultancy delivers a recommendation. KINTO's engineers build and operate the system inside the client's operation, starting read-only, with approval or validation before anything moves money. Its published cases state what was measured and what is still unknown.

KINTO's agents read authoritative data first. What moves money or changes the books or the ad accounts is approved by a person or validated against the previous system before it goes live; routine work that code can verify runs on its own. The privacy policy states that KINTO does not sell personal information.

KINTO starts read-only: it reads conversations, ERP records, invoices or ad accounts to diagnose before it builds. What moves money or changes the books or the ad accounts is approved by a person or validated against the previous system before it goes live; routine work that code can verify runs on its own. Scope and access are agreed after the diagnosis.

Often, yes, but it depends on the ERP and its access. KINTO has put agent layers over ERPs in real estate and auto parts. It starts read-only, and on an existing ERP writes to the books go through a queue a person approves. In one case access restrictions stopped the project, so access is verified first.

KINTO designs agents so they do not need to. Price and stock are looked up in the system of record, delivery dates are calculated by code, and when a product has no data the agent says so. This reduces the risk, but it does not remove it, which is why agents are tested with simulated conversations before each release.

Yes, as a design goal: keep the same paths where possible and redirect the rest with 301s. In one migration KINTO inventoried every store URL first and about 98% stayed on the same path; in another, 301 redirects covered the old URLs. None of its migration cases yet has evidence of later sales or rankings.

GEO, or generative engine optimization, is structuring a website so AI assistants can understand, trust and cite it. KINTO builds sites with llms.txt, structured data, hreflang sitemaps and answer-first writing, and applies the same approach to kinto.co. It cannot guarantee that any assistant will cite a site.

An agentic ERP is an AI layer on top of a company's ERP that reads its data, shows what is missing and proposes actions. It starts read-only because a wrong write to the books is costly. What moves money or changes the books is approved by a person or validated against the previous system before it goes live.

Not exactly. KINTO's product hacking is its forward deployed engineering applied to a growth question: it starts from the client's own data to find where growth is stuck, then builds the smallest change that tests it. Forward deployed engineering is the wider way of working; product hacking is its growth-focused part.

KINTO works in English and Spanish for companies in the United States, Colombia and the rest of Latin America. Its published case studies cover Colombia, the rest of Latin America, the United States and clients with international operations. Colombia has the most cases; the United States has fewer, and the regional pages say exactly which.