Questions
The ten we get before every first conversation — answered without the hedge words.
What does Mask actually deliver?
An agent engineered for one job: the model work, the tools it calls, the guardrails around it, the integration into your systems, a trial with your team, and the monitoring and controls that let you run it after we hand it over.
Where can an agent be deployed?
Four common destinations: behind the company (intake, routing, follow-up), inside your app, on your public website, and inside internal operations. If the job lives somewhere else, tell us — the destination changes the build, not the discipline.
How long until one is live?
It depends on the job, and anyone who quotes a number before scoping is guessing. Recon tells us the tasks, the systems and the stop conditions; from there we give you a plan with a real timeline before any code is written.
Do you build on our stack?
Yes. Agents are built against the systems you already run — APIs, webhooks, your data layer, your helpdesk and internal tools. We do not migrate you onto a platform of ours, and your team keeps access to everything that gets built.
What do you need from us?
Access to the systems in scope, an hour or two with someone who knows the job, and a person who can approve what the agent is allowed to do. During the trial, someone who will watch it work and say when it is not good enough yet.
Is the demo on this site real?
No — and it is labelled that way. The transcripts, meters and clocks on this site are synthetic illustrations of how an agent works. There are no customer names, metrics or results anywhere on the site, because none were supplied to us.
What happens to our data?
Access is scoped to the job: the agent touches what the work needs and nothing beyond it, and we design that scope during recon rather than discovering it in production. The exact controls are set per project against your policies — we do not claim certifications we do not hold.
What does it cost?
Pricing follows scope. We quote after recon, when the tasks, systems and guardrails are known — a fixed number before that would be theatre.
Can we turn it off?
Yes. Handover includes the controls and the documentation to stop it, change it, or run it without us. An agent you cannot stop is an agent you do not own.
What if an agent is the wrong answer?
We will say so. Plenty of jobs are a script, a form or a headcount — scoping exists partly to find that out early, before it becomes a project.
Still holding a question?
Ask it in the brief — the ones worth answering get answered before any scope is agreed.