Everything you might be wondering.

We're an AI Operations Partner: we bring AI agents into your operation, each with a specific job —answering enquiries, following up, entering data, building reports— and we run and measure them every month. Before building anything we measure where the hours go, and where a simple rule is enough, we use a simple rule. We don't ship a build and disappear: the important part of the work comes after.

We don't deliver technology without a measurable operational goal. We bring in AI agents that join your operation and carry out a specific job, with rules, a person who approves what matters and a number that measures the work. The difference is who owns the outcome: a build ships and is left alone; a Trascend agent is one we keep running, fix when something changes and improve with what real usage shows. It's a digital workforce, not a software project.

It's a way of working, not a product. Instead of selling you a closed project and leaving, we take ongoing responsibility for a slice of your operational improvement: what gets automated, in what order, with what measured impact and what happens when something breaks. Explained in full here.

Partner: we build it with you. We map your operation and build to fit on the tools you already use. Labs: it's already built — you configure it and use it. Finished products with their own panel, today AGE, with no project or discovery phase in between.

No, and that isn't what we do. We take repetitive work off the team so it spends time on the work that needs judgement. If what you're after is headcount reduction, we're not the right vendor — we'd rather say that now than find out in month three.

Yes. We work remotely with companies in Uruguay, the rest of LATAM and the United States, in English or Spanish. We're based in Uruguay and we don't have an office elsewhere — we say it that way because a convenience address helps nobody.

With a discovery call: thirty to forty-five minutes to look at how your team works today and decide whether there's anything worth doing.

Yes, and it usually makes the most sense. An automation sprint is exactly that: one specific process, tightly scoped and agreed in writing before we start. If it works, we move to the next one.

Almost never. We work on the tools you already pay for and automate around them. When a change really is worth it, we say what it costs and what it replaces — and the decision is yours.

Yes. If you have your own team we slot in: we agree who does what, where the code lives and which standards we follow. In several cases it's the best scenario, because long-term maintenance stays with the people who know the business.

It depends on the size of the operation, the number of processes and the tools we have to review. Before we start you get the scope, the deliverable and the fixed price in writing. Tell us your case and we will say which engagement applies.

We show where our main services start, so you know whether we fit your budget before we talk. The final price depends on scope: after discovery you get, in writing, what is included, what is not and a fixed price. The proposal is valid for 15 days and, once signed, the price does not move for the agreed term.

Fixed-scope projects bill against milestones agreed in the proposal; recurring services bill per period in advance. Currency, payment methods and instalments are set per case and agreed in writing before we start.

Efficiency audit: about a week from the session. Automating one process: one to two weeks. Integrating several tools: three to four weeks. QA Express: 48 to 72 hours. Those are typical ranges, not commitments — the actual date goes in the proposal.

Most of it lives in your systems: your CRM, your spreadsheets, your database. What we store is the minimum needed for the flow to run and be auditable. Details in security and in the privacy policy.

No. We don't use one client's data for another client or to train our own models. The model providers we work with don't train on commercial account content. Only what the process needs to answer reaches the model — not your database.

You do. The automations, configurations and documentation we build for your business are yours, run on your accounts and stay with you if we stop working together. What does not transfer is our platform software — the CRM, the portal, the Labs products — which is used while the service is active.

Not about anything with consequences. AGE answers using the information your company approved, logs the opportunity and classifies it on interest signals. It doesn't close deals, approve terms or commit your company. Anything beyond its rules goes to a person.

When the enquiry goes beyond what the script covers, when the contact asks for a person, when a sensitive topic comes up, or when the scoring says so. Your team can also take any conversation at any time from the panel and hand it back afterwards.

We publish the real status of every capability, including what is not ready: see the capability table on the Labs page or on the AGE page. "Available" means you can use it today without anyone finishing a build.

When a flow stops reporting or starts returning errors, an alert fires on our side — usually before you notice. What can be retried is retried automatically; what can't is reviewed. With Managed Operations, fixing it is part of the service.

Everything we deliver comes with 30 days of warranty from handover: if it doesn't do what the proposal says, we fix it at no cost. With Managed Operations that coverage continues for as long as the service runs.

With an active recurring service, yes: response times are agreed in writing based on how critical each flow is, and they go in the contract. Without a recurring service we answer in order of arrival, during business hours, with no committed turnaround. Our baseline times are on the continuity and support page.