1 · Detect
The system watches for an event — a new enquiry, a ticket, a due report.
We automate the routine. You keep the decisions.
We automate one defined repetitive workflow, with human approval gates before any irreversible or legally significant action — built around the tools in scope after a short scoping call.
one workflow · approval gates · founding-client rates
THE DIFFERENTIATOR
How the checkpoints work
2 · Draft or act
It prepares the action or a draft, using rules agreed with you.
3 · You approve
Every action that changes a record or sends a message is blocked until you approve it.
WHO THIS IS FOR
Who this is for
Operations teams and small businesses drowning in repetitive steps — intake, routing, first-pass replies, recurring reports.
Repetitive intake
Incoming enquiries and messages sorted and prepared, instead of by hand.
First-pass drafts
Reply drafts prepared for a person to review and approve.
Task routing
Tickets and tasks suggested to the right person by an agreed process.
Recurring reports
Regular summaries assembled by code on a schedule, not by hand.
Good first automations
Incoming enquiriesTicket routingWeekly reportingData entry between toolsQuote preparation
Castel Studio runs its own operations on the same approach — automation with checkpoints, in daily use.
WHAT YOU GET
What you get
- Process mapping & written scope
- One workflow automated — a defined, bounded process
- Human approval gates at every high-stakes step
- Scheduled reporting on workflow status and agreed operational fields
- Optional care plan — remote-first support, by appointment
LIVE DEMO — SIMULATED
See it route a task
Try a sample request below. This preview shows how the automation classifies and routes a task — not a live connection to a production system.
Response will appear here once you send a request.
OPERATIONS EXAMPLE
What a controlled automation leaves behind
A professional automation is not only the action. It leaves a readable trace: what ran, what was blocked for a person, and what the operator receives at handover.
RUN LOG
Weekly lead follow-up run
- 09:00startedNew replies imported from the agreed mailbox and matched against the lead sheet.
- 09:02checkedDuplicates removed, missing company names flagged, risky wording excluded from automatic drafting.
- 09:04blocked12 follow-up drafts prepared, but sending is paused until a human approves the batch.
HUMAN APPROVAL CHECKPOINT
Before anything leaves the system
The operator sees the proposed message, the source lead, and the reason the system wants to send it. One click approves, rejects, or sends it back for edits.
- Approve the batch
- Edit selected drafts
- Reject and keep a note in the log
HANDOVER NOTE
What you receive after delivery
Workflow: weekly follow-up preparation from inbox replies.
Owner action: review the approval queue every Tuesday before 11:00.
Maintenance note: if the mailbox label or lead sheet columns change, pause the run and update the mapping before restarting.
Example data, not a fake client claim. In a real build, the run log fields, approval wording and handover note are written around your process and tools.
CASE STUDY
A first automation we built
First-pass lead qualification
- What was automated:
- Incoming cold-outreach replies were sorted and a first-pass qualification draft prepared.
- Where a person stayed in charge:
- Every qualified lead and every outgoing message was reviewed and approved by the operator.
- What it produced:
- A clean, de-duplicated shortlist and a weekly status summary.
PROCESS
How we work
- 01Scoping call (20 min)
- 02Process map + fixed quote
- 03Build & connect
- 04Acceptance test + handover
- 05Care plan (optional)
PRICE & ACCEPTANCE TEST
Book a scoping call
Build from 990€ · optional care plan 290-490€/mo
Founding-client rates — reduced while we build the public portfolio. Limited slots.
The acceptance test
Before we build, we define an acceptance test together — in writing — with a verifiable criterion (for example, classification accuracy on a sample set). If the automation doesn't meet the agreed criterion, you don't pay the implementation fee for that build. Business outcomes are not guaranteed.
FAQ
Common questions, honest answers
Will it send things without me seeing them?
No. Every action that changes a record or sends a communication is blocked until you approve it. Drafts and internal, reversible steps can run automatically; anything irreversible waits for you.
What kinds of process can you automate?
Bounded, rule-based operational steps — intake, routing, first-pass drafts, recurring reports, data entry between tools. We agree the exact scope on the scoping call.
Does it run on my infrastructure or yours?
Where appropriate, deployment can be designed so your data stays under your control. You remain the data controller; Castel Studio acts as a data processor, and we sign a Data Processing Agreement (DPA) before any work on your data.
Does it integrate with my tools?
It's built around the tools in scope after the scoping call — not a promise of any integration. We confirm what's feasible before you commit.
What if a step breaks?
The optional care plan covers bug fixes and adjustments within the existing scope, remote-first and by appointment. It typically responds within a few business days — no same-day uptime promises.
What this is not
- Not full autonomy — a person approves anything that carries risk.
- Not a replacement for your team — it removes the busywork, not the judgment.
- Not a compliance or legal service — you remain responsible for GDPR and for the terms of service of any third-party platform involved.
Book a scoping call
Book a scoping call
Prefer email? contact@castel.studio
Automation may involve processing personal data — you remain the data controller, and we sign a DPA before working on your data. You are responsible for compliance with applicable platform terms.