---
title: "AI and automation that frees up working hours"
description: "Internal processes mapped, priced in hours and money, and automated with AI tooling. A two-week review, then a four-week build."
url: https://torn.studio/en/services/ai-and-automation
locale: en
---

# AI and automation that frees up working hours

> **Short answer:** It starts with a review that puts hours and money on your processes. Then the three that return the most get built, at a fixed price set after the review.

**From: €2,200**
**Timeline:** 2–6 weeks

## What you get out of it

- Processes mapped with hours and cost per step
- The three most valuable automations built and running
- Integrations with the systems you already use
- A record of what each automation saves

## Deliverables

- An automation review with a prioritized list
- A fixed price per automation
- Built and deployed flows
- Documentation and handover in your own repository

## Three steps, all at fixed prices

- Automation review: €2,200
- Automation build: €4,200–8,800
- Maintenance and operations: from €750/mo

[Full price guide](https://torn.studio/en/pricing/ai-automation)

## Case study

- [voxcog: AI agents that hold up in production](https://torn.studio/en/work/voxcog-ai-agents-in-production) — voxcog is a product Torn Studio built and holds a stake in. The studio ran product management, architecture and the build. This shows that an agent platform can be built so it holds up under load and can be measured. It shows nothing about what voxcog is worth in a market: the platform was handed over before launch and had no paying users at handover.
- [voxcog: product decisions with a traceable trail](https://torn.studio/en/work/voxcog-evidence-chain-product-decisions) — voxcog is a product Torn Studio built and holds a stake in. The studio ran product management, architecture and the build. This shows product management that leaves a trail: decisions can be read backwards and the reasoning survives. It says nothing about whether the market wants voxcog — the platform was handed over before launch, and that question is open.
- [Changemkr: four systems became one platform](https://torn.studio/en/work/changemkr-four-systems-one-platform) — Changemkr is a platform Torn Studio owns part of. The studio held the product role from January 2025 to June 2026 — first as CPO, later on a fractional basis — and built in the codebase alongside the role. Work after June 2026 belongs to others and is left off this page. This shows that four systems can be merged into one and held together by gates. It shows nothing about a market: the platform had not launched at the June boundary, the verdict in the repository’s own readiness log was deployable with caveats, and one of those caveats was a manual security task that no code closes.
- [27 findings from a consultancy review, worked through](https://torn.studio/en/work/consultancy-review-27-findings) — The consultancy is an independent party that evaluated the planning canvas in Changemkr, a platform Torn Studio owns part of and held the product role in. The studio received their material and did the work that followed. This shows that a sprawling body of test feedback can be turned into a plan that can be followed up row by row. It shows nothing about the product succeeding: two tickets were deferred with reasons, three are partial with the edge still there, and the three large creation journeys were never run end to end because they depend on model output that varies.

## Common questions

### Which processes can be automated?

Most processes where someone moves data between systems by hand: quotes, order lines, invoice preparation, reporting and follow-up. The review ranks them by the hours they take and what those hours cost.

### What does an automation review cost?

The review costs €2,200 and takes two weeks. You get your processes mapped with hours and cost per step, a prioritized list, and a fixed price for the top three. The material is yours even if you stop there.

### Does this work with our business system?

Usually yes. Fortnox, Visma and most modern business systems expose open APIs. The review checks the integration path before any price is set on the build, so surprises land before the quote.

### What happens if an automation breaks?

Flows are monitored and raise an alert when something fails. The maintenance agreement from €750 per month covers monitoring, adjustment and extension as the business changes.

### How long before something is running?

The review takes two weeks. The first build takes two to four weeks after that, so a first automation is normally running within six weeks of starting.

### Do we need technical staff afterward?

No. Flows are documented and handed over in your own repository, and the maintenance agreement exists for the day-to-day. If you want to take it over yourselves, everything you need is in place.