the platform
What you get Who works for you What it connects to How you stay in controlmeet a few
Ad monitorstops the ad that is bleeding, before you open the account Shopify managerfound 340 customers who bought once and never came back Outreach employeewakes the leads that went quiet Email employeereads 142 emails, hands you the 9 that need you The full roster →by domain
Strategy & Intelligence Marketing & Growth Sales & Revenue Operations Customer Operations Commerce & Supply Chain Operations & Delivery Finance & Backoffice People & Organisation Oversight & compliance Data & knowledge All use cases →spotlight
142 mails came in. It handled 128 on its own, put 9 drafts in front of you and passed 5 to a colleague. That was one Tuesday.
One employee · an ordinary day
Open its file →Every digital employee has one job, a name, and a file you can open. You see what it did, what it decided, and the rules it worked inside, all of which you set.
the process
The scan & workflow mapping Role selection & configuration Build & integration Controlled go-live Monitoring & tuningspotlight
Almost everyone starts at “it advises”: it prepares the work and waits for your yes. You move the dial when you trust it, and you can move it back.
Autonomy · on your terms
How control works →From the first scan to the day it runs by itself. We map the workflow, build it inside the tools you already use, and stay on it after go-live.
spotlight
Not pilots, they run every working day on real work, and you can ask them about it.
Worked-out scenarios · a call with a client on request
Read the cases →We are an implementation studio, not a software vendor. We build the employee, connect it to your systems, and keep it running afterwards.
09investment
Setup covers mapping, design, build and go-live. The monthly fee covers monitoring, edge-case handling and continuous optimization. Hosting and AI usage sit outside it: we pass those through at cost, so you see what the infrastructure and the models actually charge.
pilot01
€3.000 setup, from
+ from €850 / month
core02
€7.000 setup, from
+ from €1.500 / month
scale03
Custom
scoped per operation
Prices excl. VAT, and excl. hosting and AI usage, which we pass through at cost. Exact scope and pricing are confirmed after workflow mapping, before you commit.
Hthe arithmetic
Both columns are what leaves your account, not what comes back. Check them against your own payroll.
One employee
€3,000 gross a month, first yearLoose AI tools
a few seats, and your own timeOne digital employee
Pilot, first yearCheck these against your own payroll. The left column uses Dutch employer contributions and public averages for recruitment and onboarding, your numbers will differ, and the comparison is worth redoing with them. Core, for a larger operation, comes to €25,500 in year one.
We are not claiming one replaces the other. A digital employee does not answer the phone, walk the floor or think of something nobody asked for. What it does do is run one workflow every working day, and this is what that costs. It is not built to replace the people you have, but to take the repeatable work off their desks, so the team you already have can spend its hours on the work that grows the company. The middle column prices the hours, not the licences: three hours a week at €75 is €11,700 a year. Loose tools are cheap to buy and expensive to run, because you stay the operator.
→what the monthly fee runs
The setup builds your digital employee. The monthly fee keeps it live: monitoring, edge-case handling and continuous tuning, all visible in one dashboard, so you always see what it did and what's waiting on you.
→perspective
A digital employee isn't a replacement for your team, it's operational leverage. Here's how the economics compare with the two paths companies usually consider.
Capacity stops depending on availability, the workflow runs every day, documented, and no knowledge walks out the door.
ChatGPT waits for prompts. A digital employee reads, decides, acts and reports inside your systems, owned, monitored, accountable.
We take a baseline before we build, so after three months you can check it yourself in your dashboard: hours back, response time, work handled. Not a number we promise up front, but one you can verify.
| Hiring an FTE | Loose AI tools | Digital employee | |
|---|---|---|---|
| Time to productive | 3-6 months incl. hiring | Instant, but nobody owns it | Weeks, implemented for you |
| Executes end-to-end workflows | Yes, with training | No, point solutions only | Yes, by design |
| Works inside your existing tools | Yes | Partially, new dashboards | Yes, no new dashboard |
| Availability | ~40 hrs / week | Always on, unmanaged | 24/7, monitored |
| Oversight & audit trail | Manager-dependent | Rarely | Logged & approved, standard |
| Best for | Judgment-heavy roles | Individual productivity | Repetitive operational workflows |
Honest note: for work that requires deep judgment, relationships or creativity, hire the human. Digital employees exist to give that human their hours back.
Not sure where to start? Meet your first digital employee, a two-minute walk-through that shows what it saves you, before you commit to anything.
Meet your first employee →→cost questions
The full implementation: AI Scan follow-up, workflow mapping, digital employee design, build, integration with your tools, testing against historical cases, control-layer configuration and supervised go-live. You approve the design before we build.
Monitoring, edge-case handling, small workflow improvements, model updates and a monthly performance report. It's what keeps the employee reliable rather than a one-off project that degrades. Hosting and AI usage are not part of it, those are billed separately, at cost.
Yes, two, and we would rather name them than bury them. Hosting is €10 per digital employee per month. AI usage depends on how much work the employee actually does. We run our digital employees exclusively on models from Anthropic and OpenAI, because that is where the reliability is, so you can look up what those cost yourself: Anthropic's prices and OpenAI's prices. Both are passed through at cost, without margin. During workflow mapping we estimate the monthly range from your volume, so you know the order of magnitude before you commit.
Success metrics are defined before we build, and the pilot exists precisely to validate them. If the workflow turns out not to be a good automation candidate during mapping, we tell you before you've committed to the build.
Six months, and we mean that the way you would mean it with a new hire: it is the trial period. Those six months include our monitoring, we watch what the employee does, handle the edge cases and keep tuning it. After six months you pick one of three. Extend for another six months and keep the monitoring, plus priority support. Scale down to a low-tier licence: the employee keeps running and you keep access to the platform and to us for questions, but we stop actively monitoring. Or stop, at no cost, and we switch the employees off. You can let them go, exactly as you could someone who turned out not to fit. Nothing about the setup locks you in technically either, your data and tools remain yours.
That's the intended path: most companies start with a Pilot, prove one workflow, and expand into Core or Scale from there. Each next employee builds on the mapping and control layer already in place.
30-45 minutes · a concrete proposal range · no obligation
