We start with the work people need to do. Then we decide what to build, what to test and who stays responsible.
An alert sent is not a task completed.
The question is whether the operation moved forward. That shapes both the system and the way we assess it.
Who does the work, what starts it and what counts as done?
We map the actual steps, exceptions and systems with the people involved. A process owner and an observable starting point come first.
A process map and acceptance criteria.
Where does AI help, and where is a rule enough?
We separate interpretation from execution. We define permissions, the information required and the decisions that stay with a person.
A solution design with explicit boundaries.
What happens when the expected input does not arrive?
We connect the required tools and test normal work, missing information and exceptions. We review what actually happens, including how to recover from a failure.
An integrated system and recorded test results.
Is the system being used, and is the process moving?
We agree on the rollout, responsibilities and follow-up. We review usage and incidents within the contracted scope, then prioritize changes.
A rollout and follow-up plan with named owners.
The exact controls depend on the system and the agreed scope. We document them before treating them as a promise.
We do not promise universal controls. These are the ones in production today, and where.
What is not in the catalog does not get classified: the system asks.
In Grupo ILT’s system, a message that does not match the catalog changes no status. A person is asked.
Every change carries an author and a time; nothing is rewritten.
In two of our production systems, corrections are appended to the log. Delete and rewrite are revoked for every role, ours included.
Before a client is notified, there is time to cancel.
In one of those systems, every client notice waits ten minutes before it goes out. If something is wrong, it stops.
Our own brake, on record.
On August 4, 2026, an outreach engine we built for a client measured a 5.8% bounce rate against a 4% limit. It stopped itself, wrote down why, and sent nothing for six days, until a person fixed the cause and restarted it.
Records H-083 · H-115
AI has no shortage of promises. These are the ones you will not hear from us:
Not before we measure your starting point. Without a baseline, any saving is an invention.
It runs with rules, with an owner on your side and someone on ours who looks after it.
We tell you which controls it has, what we tested and what we did not. Nobody serious promises zero risk.
We do not publish any client’s data without written permission, and we will not publish yours.
Comparing times that were not measured the same way is comparing apples and oranges. We give you a calendar with dates and with what depends on whom.
We tell you what we are good for and what we are not.
If you ever read one of these lines with our name on it, tell us: it is a mistake and we will correct it.
With one bounded process that has an owner, not with the technology. The first moment with Teckel is defining that process: mapping the current work, deciding where to intervene and agreeing on how to check it improved.
Each moment is quoted by scope, after we understand the process. We do not price an implementation without knowing the work, the tools and the data involved.
The repetitive, high-volume ones with clear rules: typing the same thing into two systems, following up, notifying, classifying. Decisions that need judgment stay with a person, and the system asks.
Security depends on the design, the providers, the contracts and the type of data. Before implementing we assess controls, responsibilities and the legal requirements that apply. We do not assume compliance.
It depends on scope, integrations and adoption. Before promising a timeline we define deliverables and acceptance criteria. A previous case does not guarantee the timing of another.
An agency usually delivers campaigns. Teckel designs and implements systems inside the operation and reviews their use against agreed criteria. We do not take adoption for granted: we instrument it and check it.
Bring a process, a pilot or a question. You talk directly with the people who will build it.
Opens Calendly in a new tab.
AVA asks a few questions so you arrive with your case in order.