Frequently asked questions

Most first projects are small and concrete. We pick one task your team repeats every week, for example reading supplier invoices or sorting inbound enquiries, and we build a tool that handles it from start to finish. Your existing process keeps running alongside it until the results are steady.

Four to six weeks from the first call to a tool your team uses daily. Week one is scoping and a look at your data, weeks two to four are building and testing against real examples, and the last stretch is handover, documentation and adjustments.

A first project is a fixed fee agreed after the scoping call, so you know the number before we build anything. Running costs are separate and usually modest: hosting plus the model usage your volume needs. Both figures appear in the proposal, with no percentage of savings and no long contract.

Examples, mostly. Twenty to fifty real documents or records from the process we are automating tell us more than a long written specification. If the material is sensitive we can work with redacted copies or a sample set your team prepares.

In your own accounts wherever possible: your cloud storage, your database, your workspace. Where a model provider is involved we use business terms that exclude training on your content, and we write down which service touches which data so your records stay complete.

Every tool ships with monitoring and a fallback path, so work returns to the manual route instead of stopping. Support is included for the first three months. After that you can keep a small monthly agreement or simply call us when something needs attention.

A short session is usually enough, around an hour for the people who use the tool every day. We write a one page guide in plain language for each tool and record a walkthrough, so new starters can pick it up without waiting for us.

We build around your existing systems rather than replacing them. Most tools connect through the interfaces your software already offers, and where none exists we use scheduled exports or a shared folder. Nothing has to move platform for a project to work.

One process, a working tool, a test run on real data from the past month, and a short report on accuracy, time saved and what to change before wider use. A pilot runs for two weeks and ends with a clear recommendation, including the option to stop.

Send a short note about the process that costs you the most time. We reply with a few questions, then book a call of about forty minutes. You leave that call with a written scope, a fixed price and a timeline, whether or not you decide to work with us.