How to write a model brief we can actually build from
A good brief fits on one page. It names the task, shows real examples and says where the result should land. Here is what belongs in it — and what you can safely leave out.
Read the guideCustom model studio · Berlin
We are a small engineering studio on Hauptstraße in Berlin. You describe a task that slows your office down — sorting documents, reading forms, drafting routine texts — and we build a model that does exactly that task, for your material, in your wording.
Hauptstraße 47 · Berlin Open 06:00 – 20:00 030-12345678
Every model leaves our studio with a name, a version number and written documentation. It belongs to you, it runs where you decide, and it does the one job you commissioned — nothing else, nothing hidden.
What we build
These are starting points, not a catalogue. Your commission is specified around your material and your systems.
Read incoming scans, PDFs and email attachments, recognise what each document is and send it to the right place.
Pull the fields you define out of forms, delivery notes and recurring statements, and write them into clean tables.
Condense long reports and minutes into short, readable texts, and draft routine replies in your house style.
Answer staff questions from your own handbooks, guidelines and project files — with the source passage attached.
Tag and prioritise incoming tickets and requests, then forward them to the team that actually handles them.
Sketch your model
Three choices give you an indicative model class, a rough build time and a deployment note. It is a conversation starter — the written specification after your briefing sets the real scope.
Prefer to talk first? Call us between 06:00 and 20:00 on 030-12345678.
How a commission runs
A short conversation — by phone or at Hauptstraße 47 — about the task, the material and the systems involved.
You receive a written specification with scope, timeline and a fixed price in euro before any work starts.
A working prototype on your sample material. You test it with real examples before the full build.
The finished model with documentation, a handover session for your team and four weeks of included adjustments.
From the notebook
A good brief fits on one page. It names the task, shows real examples and says where the result should land. Here is what belongs in it — and what you can safely leave out.
Read the guideMost office tasks are narrow. A compact model that knows your material usually beats a large general one — and runs on hardware you already own.
Read the noteLab benchmarks flatter. We test every prototype on the class of machine it will actually run on, so the numbers in your specification hold after delivery.
Questions
The three questions we hear in almost every first call. The full list — commissioning, data privacy, hardware and support — lives on the questions page.
All questions & answersTalk to the studio
Send a short description of what should happen to your documents, texts or requests. We reply within one business day.
Request a model