Process automation for companies of 50 to 2,000 people
We connect the systems you already pay for and automate the work your team does between them.
Bespoke One Coworker. AI assistant. Answers in seconds, estimate in three minutes.
Connects to
From global brands to young startups: teams we have built software, AI and engineering capacity for.
Zovi
The cost of manual
What manual data work costs a year, from published research. Every figure is sourced and dated.
a year per employee: what manual data entry costs US companies
Parseur and QuestionPro survey: $28,500, at the ECB rate of 29 July 2025. As of July 2025
a year per employee moving data from emails, PDFs and spreadsheets into systems
Parseur and QuestionPro survey: 9+ hours a week across 46 working weeks. As of July 2025
a year spent closing the books at the median company; the top quarter needs under 58
APQC benchmark via CFO.com: 12 monthly closes of 6.4 calendar days (top quarter 4.8). As of March 2018
Set your own team and hours. The yearly figure updates as you go.
Your estimate, per year
€111,800
back in your budget every year
Your own estimate, not a quote. 46 working weeks a year; the 9 hours a week default is the Parseur and QuestionPro 2025 survey figure for manual data work.
How it's built
Every automation we ship is built the same way, from your data up. Each layer is documented and tested, so the system never depends on one person, us included.
Your systems of record stay the source of truth. We connect through their APIs, database views or scheduled exports, in whatever form they offer.
Typically
Connectors and one shared data model, so a customer or an invoice is one record everywhere. Every field mapping is signed off by the person who owns the process.
The process itself, written as code: rules, approvals, deadlines and retries. When a case doesn't fit the rules, it goes to a named person with the reason attached.
Where your people meet the system: an approval in Teams, a review queue for exceptions, a dashboard for the team lead. No new tool to learn where an existing one will do.
Typically
Every run is logged and every failure raises an alert. A weekly report shows volume and exceptions, so you can see what the system did and why.
What we automate
Open one to see what we'd build and the systems it usually touches.
Invoices are read as they arrive, matched to the purchase order and posted to your ERP, DATEV or Lexware. Only the ones that don't match reach a person, with the reason attached.
Typical systems
Matched invoices post themselves.
Reconciliation runs every night instead of once a month. Bank statements arrive through EBICS or FinTS, lines are matched to bookings and open items are flagged on one close checklist. Finance starts the month-end with the exceptions only.
Typical systems
The close starts with the exceptions.
One shared data model between CRM and ERP, kept in sync both ways, with a named owner for every field. When a deal closes in the CRM, the customer, the order and the invoice exist in the ERP minutes later.
Typical systems
Sales and finance read the same record.
Approval flows with rules, deadlines and a deputy when someone is away, inside Teams, Slack or Outlook. Every decision is logged with who made it, when and why.
Typical systems
Approved where your people already work.
One onboarding request creates the accounts in Microsoft Entra ID or Google Workspace, the licences, the hardware order and the first-week checklist, and confirms each step. Leavers are switched off the same way, on their last day.
Typical systems
Accounts ready on the first morning.
Reports build themselves from the source systems in Power BI, Looker Studio or Excel and arrive before the meeting. Every number traces back to the record it came from.
Typical systems
The report is ready before the meeting.
Not on the list? Tell us what's manual
By industry
Pick yours. The problem as we hear it in the first meeting, and the automation we build for it.
The problem
The front desk spends the morning on reminder calls and rebookings. Patient records sit in one system, invoices in another, and nobody sees which patients have quietly stopped coming back.
What we build
Reminders timed to treatment intervals, invoices that post to accounting, and a weekly list of patients due back.
Usually connects to
Every patient, every site, one view.
The problem
Senior people spend their evenings on time sheets, engagement letters and status reports. Knowledge lives in inboxes, so every new case starts from a blank page.
What we build
Time entries taken from calendars and mail, invoices prepared in your accounting system, client reports assembled on schedule.
Usually connects to
The firm's memory, finally searchable.
The problem
Orders arrive as PDFs and emails and get typed into SAP by hand. Planning runs on a spreadsheet that one person understands.
What we build
Purchase orders matched to invoices, planning data taken from the shop floor, supplier messages filed against the right order.
Usually connects to
Orders that reach SAP without a keyboard.
The problem
Customer service answers the same twenty questions all day. Returns are processed by hand, and by Friday the shop, the stock and the books disagree.
What we build
Returns processed end to end, stock kept in sync across channels, daily sales posted to accounting.
Usually connects to
Shop, stock and books that agree on Friday.
The problem
Bookings, changes and documents arrive by email at all hours. The team types them into three systems, and customers call to ask where things stand.
What we build
Booking confirmations read into your systems, documents generated and filed, status updates sent on their own.
Usually connects to
The customer knows before they ask.
The problem
Applications and claims arrive as documents and get checked by hand against rules everyone knows by heart. Every audit means a week of collecting evidence.
What we build
Document intake, reconciliations and reporting that record every step for the auditor.
Usually connects to
An audit trail written while the work happens.
The problem
The roadmap is full, support tickets keep pulling engineers off it, and the internal tools are scripts nobody owns.
What we build
Onboarding, billing and CRM kept in sync, with the scripts replaced by something your team can maintain.
Usually connects to
Engineers back on the roadmap.
Made and hosted in Germany
Your data stays in German data centres run by ISO/IEC 27001 certified partners, under the GDPR. We design, build and support everything from Düsseldorf.
Portals and platforms connected to the systems our clients already run.
Clinic and workforce SaaS
AI shift scheduling, mobile time tracking, absences, contracts and payroll for shift-based teams across several locations.
Enterprise platforms
A B2B platform where companies search, book and manage business flights and hotels centrally, within their own travel rules.
Enterprise platforms
A B2B portal for the corporate and bulk clients of a health insurer, with an integration layer into the clients' CRM systems.
We'd rather turn a project down than build something that won't pay for itself.
At that size a well-configured off-the-shelf tool usually beats custom automation. We'll tell you which one.
Automation pays off on work that repeats. If the process is still being invented, settle it on paper first.
We connect and automate around the systems you have. If the ERP itself is the problem, you need a selection and rollout partner, and we'll say so.
Every automation needs a named owner who answers questions within days and signs off the result. Without one, it stalls, whoever builds it.
The systems around an automation keep changing, with vendor updates and new fields. Either we run it or your team does, with our handover. Someone always owns it.
From the first call to a system in production.
The people you meet in the audit are the people who build and run it.
Free AI audit
Six short steps, about four minutes. You get a readiness score and the three agents worth building first.
Estimate
Pick a service, answer a few questions and get an indicative range with timeline and team.
