AI document automation for small business is one well-defined conversion with a human review gate. The systems webvise has shipped turn an 11-page tender PDF into an importable GAEB file in about 3.5 minutes, at one to three dollars per run. The manual version of that same conversion is about an hour of hand-keying.
If your team retypes tenders, quotes, plan quantities, or pitch documents every week, you already know which file eats the hours. What follows are two production systems webvise built, with the numbers they run on: conversion times, model costs per run, and the review rule that makes the output usable. By the end you can run the same qualification test on your own paperwork.
- One conversion, one gate. A repeated document goes in, a machine-readable file comes out, and a named person reviews every result before it reaches a customer.
- Runs cost one to three dollars. The same 11-page tender costs about $2.50 on a top model and about $1.50 on a cheaper frontier model. Optimized pipelines target 20 to 30 cents per run.
- The operating rule is absolute: no AI result goes into a quote unreviewed. The tool replaces the typing, never the checking.
- The pattern travels. The two construction tools moved to a second client, an architecture practice, in a day.
The fastest qualification test is a description: format in, format out, monthly count, current handling time. webvise's AI automation service scopes exactly this kind of bounded conversion, builds the review states around it, and hands over a system your team runs without the builder.
An 11-page tender PDF becomes a GAEB file in 3.5 minutes
MP Bau, a German construction company, receives tenders as PDF or Word files. Its estimating software, BauSU, imports GAEB files in the .d83 format. The bridge between the two formats was an estimator hand-keying positions for about an hour per tender.
webvise built a converter that reads the tender and writes a valid .d83 file BauSU imports directly. An 11-page PDF runs through in about 3 minutes 30 seconds. The public case-study metric states it as one hour down to four minutes.
The model types and checks at the same time. It verifies Ordnungszahlen (position numbers) and Mengen (quantities) against the source document and flags inconsistencies in the tender itself, unprompted. A person hand-keying under time pressure copies exactly those errors straight through.
What a run costs
Model cost per document is the first question owners ask. Here is the measured answer for the same 11-page tender, plus the standing costs around it.
| Cost item | Number |
|---|---|
| 11-page tender PDF, top model | about $2.50 per run |
| Same document, cheaper frontier model | about $1.50 per run |
| Optimization target per run | 20 to 30 cents |
| Monthly AI costs across all tools | a two-digit euro amount |
| Per-seat licenses | none |
| Manual alternative | about 1 hour of estimator time per tender |
The run cost barely registers against the labor it replaces. The real investment is the build: integrations, review states, and failure handling drive it. The AI automation cost guide breaks down what each driver adds.
The review gate: no AI result reaches a customer unreviewed
MP Bau operates every AI tool under one rule: kein KI-Ergebnis geht ungeprüft in ein Angebot. No AI result goes into a quote unreviewed. The rule costs minutes per document and removes the risk that decides adoption: a machine error inside a customer offer.
The second MP Bau tool shows the gate in daily use. It reads construction-plan PDFs and produces quantity takeoffs as an Excel file the estimator verifies line by line. One comparison came out at 92 m² from the AI against 95 m² of manual hand measurement, and the estimator resolved the difference. The app replaces the typing, never the checking.
The model also names its own missing inputs. When a plan lacks a dimension it needs, it reports the gap instead of estimating around it. A reported gap takes a reviewer seconds; a confident guess is the expensive case.
The same pattern generates documents: the Rautenberg Pitch Engine
Extraction is one half of the pattern, generation the other. The Rautenberg Pitch Engine, built for a documentary production company, takes a film idea to a broadcaster-ready DOCX in under 3 hours.
Two decisions carry the quality. The prose draws on a versioned voice corpus built from 8 real pitches, so a draft reads like the producer's past work. The DOCX rendering is deterministic: typography, template, and layout never depend on the model.
A monitor checks broadcaster portals around the clock, every 30 minutes. Newly published calls enter the next research run without anyone refreshing a portal.
The second deployment took a day
Both construction tools were later ported to a second client, an architecture practice, within a day. File formats and templates changed while the structure of intake, conversion, and review stayed. That is where the economics tilt: the first build carries the discovery and integration work, the second deployment inherits it.
webvise has delivered 25+ projects. For a document conversion, payback is plain arithmetic: time the old path, price the run, compare. The ROI calculation guide walks through that formula with real project numbers.
How to pick your first document
The systems above share four properties. Treat them as the qualification test for your own paperwork.
- A defined output format. GAEB .d83 for BauSU, Excel for takeoffs, DOCX for broadcasters. A downstream system or recipient must define what correct means, otherwise the automation has no finish line.
- A measurable old path. MP Bau could name the hour of hand-keying per tender. Without that number there is no before and after to compare.
- A named reviewer. The estimator owns the takeoff line by line. Review is a workflow state with an owner.
- Run cost far below output value. One to three dollars against an hour of skilled labor. If that ratio looks thin for your document, automate a different one first.
webvise takes on one document conversion at a time: format in, format out, the review gate, and the run price, all fixed before the build starts. Send the document type, monthly count, and current handling time through the contact page for an assessment of whether the pattern fits.
Development practices are aligned with ISO 27001 and ISO 42001 standards.