We build AI systems that quietly do the work.

Deepstill is a two-person AI studio. We build The Front Desk, an assistant that answers your customers from your own documents at any hour, and we turn processes into working software. In weeks, not quarters.

Every answer
has a source.

It answers your customers out of your product sheets, manuals, terms and past tickets. Every reply names the page it came from, so nobody has to take its word for it.

Book the call
Asked by a customer

Select a question
EU AI Act · Art. 50 ready GDPR by design EU-only hosting Handover with code & docs
A day of it

What quiet actually looks like.

A composite Tuesday, assembled from the kinds of system on this page. Eight moments across twenty-four hours, and a person is genuinely needed for three of them. Pick a point on the day.

Nobody in the room A person decides
00:0006:0012:0018:0024:00
03:12
Machine

The nightly reconcile

Two systems compared line by line while the building is empty. Six differences found and listed, ready for somebody to look at over coffee rather than discover in June.

Five of the eight needed nobody at all. The three that did are exactly the three that should: a judgement, an exception, and a signature.

The offers

Four ways to start.

Start wherever you are: we find the potential, build the one system worth building, and teach your team to carry it once it works. We agree what the work is before it starts, and again before anything is built.

01 · Audit

The Process Audit

You know something eats time, but not which system to build. We follow the work for a week or two: where the hours go, what each process costs, what a machine could take over. You get numbers and a ranked shortlist.

For
“Something must be automatable”
Duration
1–2 weeks
You get
Hours & euros per process
Yours
The report is yours to keep
Book the audit
02 · Most asked for

The Front Desk

A chat on your own site that answers your customers out of your product sheets, manuals, terms and past tickets. Awake at 23:00, in whatever language the question arrives in, and every answer carries its source so anyone can check it.

For
Your customers, on your site
Duration
2–4 weeks
Scope
Agreed before anything is built
Data
EU-hosted, yours alone
See it answering
03 · Build

The Custom Tool

You already know roughly what you need. We turn the rough idea into one working internal tool: inbox to CRM, inquiry to offer, whatever the loop is. Deployed in your stack, not in a demo account.

For
SMB & Mittelstand teams
Duration
2–4 weeks
Measured
A baseline agreed before we build
Afterwards
We run it, or your team does
Request the tool
04 · Optional

Team Enablement

Once the first system has paid for itself, we teach your team to run it, extend it, and build the next one, hands-on, on your real processes. Entirely optional, and only ever after something works.

For
Your staff
When
After the build proves itself
Format
Workshops, remote or on-site
Scope
Agreed per workshop
Ask about enablement

On automation builds we keep running what we built: hosting, monitoring, fixes and the improvements that come out of daily use.

Building a product rather than automating a process? We run MVP sprints for founders too. Ask us.

Our most-asked-for system

A front desk that never closes.

Most of what a customer asks has been answered before, in a manual, in the terms, or in a ticket from March. The Front Desk reads the documents you clear for the public and answers out of them, in plain language, with the source attached. On your site, at any hour, in the language the question arrived in.

The Front Desk
1,204 documents, every answer sourced
  • Every answer cites its source. Document and paragraph, one click away, so people verify instead of trusting.
  • Your data stays yours. EU hosting, no training on your content, contracted with every provider in the chain.
  • It never sees your internal folders. It reads one cleared shelf and nothing else. Margins and internal notes are not filtered out at the end, they were never within reach.
  • It says when it doesn't know. No answer without a source: a gap is reported, not filled in.
See it answering 2–4 weeks. Scope and a delivery date, agreed after the call.
What we build

Six kinds of quiet machine.

Most of what a small company loses to busywork falls into a handful of shapes. These are the ones we build: always on your data, in your stack, with a person in charge of anything that matters.

Inbox & request triage

Mail, forms and tickets read on arrival, sorted, answered where routine, escalated where not.

Outlook · GmailCRM · Helpdesk

Offers & documents

Inquiries turned into quotes, contracts and reports from your current price list and templates.

Word · PDFERP · Price lists

Customer front desk

A chat on your site that answers customers from your own documents, with the source next to every answer.

Contracts · ManualsSourced answers

Data out of documents

Invoices, delivery notes and forms read into clean fields your systems can actually use.

Scans · E-mailsExcel · Database

Internal tools

The small app your team keeps rebuilding in spreadsheets, properly built, with logins and an audit trail.

Web appYour stack

Agents that act

Multi-step work handled end to end, with limits, logs and an approval step before anything leaves the house.

Tool useHuman approval
See what each one looks like
Selected systems · demo builds

Quiet systems, loud results.

Three systems we built ourselves, so you can see the shape of the thing before you commission one. Pick a tab.

Email triage
38 mails sorted before 8:12 a.m.

The inbox that sorts itself.

Every mail read on arrival and sorted by intent. Routine requests get a ready-to-send draft; anything unusual goes to a person, with the reason attached.

608
Minutes of inbox work per morning
38
Mails triaged before 8:12 a.m.
See what else we build
It plugs in

Into what you already use.

E-mailOutlook · Gmail
CalendarsDates & deadlines
CRMHubSpot · Pipedrive
ERPDATEV · Lexware
FilesSharePoint · Drive
SpreadsheetsExcel · CSV
ChatTeams · Slack
Web formsYour website
Your softwareAPI · Webhooks
AccessSSO · roles

Not on the list? Almost anything with an export, an API or an inbox can be connected. And if it truly can't, we say so before you pay anything.

The method

From first call to running system, in weeks.

01

Scope call

Thirty minutes with both founders. We find the one process with the biggest leverage, and say so honestly if there isn’t one. Still unsure where the time goes? The audit finds out first.

30 min, both founders
02

Baseline & offer

Within 48 hours: exact scope, a delivery date, and the baseline we measure savings against. The meter never runs.

48 hours
03

Build sprint

We build in weekly demo cycles. You watch the system grow, live, not in a report.

2–4 weeks
04

Handover & enablement

Deployed, documented, explained. We keep it running and measure what it saves. And if your team wants to take over, that's what the enablement workshops are for.

Ongoing

Everything we build, you own.

No black box, no licence you have to keep paying us for. At handover the whole thing is yours, even if you never work with us again.

  • Source code, in your repository
  • Deployed and running on EU infrastructure
  • Written documentation, in plain language
  • A walkthrough with the people who use it
  • Access to every account and key
  • A measured baseline and what it saves
Where we stand
20 2
Minutes per offer in our own demo build
48h
To a scoped offer
100%
EU hosting · GDPR · AI Act
2
Engineers, zero account managers
Questions we get

The honest answers.

What does it cost if it doesn't work?

The audit costs you nothing but the time, and if we don’t find anything worth building we say so and walk away. Everything after that is agreed in writing before it starts, and we keep working until it does what the offer said.

Is our data safe, and does it train an AI model?

Your data stays on EU infrastructure and is never used to train anyone's model; we contract that with every provider in the chain. Whoever hosts a component, we tell you who and where before we build.

What about the EU AI Act and the GDPR?

We build for Art. 50 transparency from the start: people can tell they're talking to a machine, and the system logs what it did. GDPR is handled by design: data minimisation, a processing agreement, deletion routines. Compliance is part of the build, not a document at the end.

We're not a tech company. Is that a problem?

No. Most of our work is with teams whose expertise is anything but software. You explain the process the way you'd explain it to a new colleague; we handle the rest and hand back something your team can actually operate.

What if we want to stop, or take it in-house?

Then you take it. Code, documentation, accounts and hosting are yours from handover. If your team wants to run and extend it themselves, the enablement workshops exist for exactly that.

Do you replace people?

We haven't yet. What we take away is the repetitive part: sorting, copying, retyping, looking things up. The judgement stays with the person, which is also why every system we build has a step where a human says yes.
“Software, not slides.”

You talk to the two people who build. No handovers, no account layers, no strategy PDFs. We listen, build fast, and stay until it runs.

Thirty minutes is enough.

Tell us about your process or product idea. We'll tell you honestly whether it's worth automating.

Book a scope call Or write directly: hello@deepstill.de