Straight answers, no brochure.
Everything decision-makers usually ask before the first call — services, pricing approach, delivery model, security and ownership.
What does a Digital FTE actually do?
Owns a defined job end to end — lead qualification, ticket triage, report drafting, appointment booking — using your tools, on your schedule, under human gates for anything irreversible.
How is this different from hiring or from a chatbot?
A chatbot answers questions; a Digital FTE completes work with artifacts you can audit. Compared to hiring, you get capacity without headcount — but only for jobs that are repetitive, rules-based and measurable.
What industries do you work with?
Any workflow that is repetitive and structured: support, sales ops, finance ops, reporting, internal tooling. [TODO: name the industries where you have live deployments.]
How do you price it?
Pricing is scoped per workflow — a build fee plus a monthly run fee. [TODO: confirm whether you publish a floor or fixed tiers, and whether a 14-day pilot is standard.]
How long does it take to get the first worker live?
A scoped first worker typically moves from brief to supervised pilot in weeks, not months. [TODO: confirm your target number — e.g., 2–4 weeks — once you have run enough of them to say it credibly.]
Where does the worker actually run — our cloud or yours?
Your choice. We can deploy inside your cloud account or VPC for sensitive data, or operate it for you under a managed subscription. [TODO: state your default and which you prefer.]
How do you keep our data out of the model providers?
We route through provider APIs under enterprise terms with zero training on your data where the provider supports it, and we gate access to secrets and personal data. [TODO: add your exact provider list and DPA posture.]
What if the worker gets something wrong?
Every worker ships with an audit trail and a human gate on irreversible actions. If an output is wrong, the gate catches it or we fix the spec and re-run — the cost of a mistake is a rejected suggestion, not a broken customer.
Can we start small — one workflow, one team?
That is the only way we start. One workflow, one owner, one written success metric, one human reviewer. Prove it, then expand.
Who owns the worker afterwards — us or you?
Ownership is part of the design: your instance, your credentials, your data, our operating playbook. Where you license the system, terms are spelled out in writing before the build starts.
Do you work on-site, remote or hybrid?
On-site, remote or hybrid — we match the client's constraints. [TODO: state your default and any travel policy you want clients to hear.]
What happens if we want to stop?
No lock-in by design: the worker runs on your credentials or can be exported, the specs and skills are documented, and your team keeps the operating knowledge. We do not bill you to leave.
Still deciding?
Bring one workflow to a 30-minute call. Worst case, you leave with a clear read on what a Digital FTE would — and would not — do for you.
Book a 30-minute call