A pilot with a fixed result — reports, processors, print forms
Reports and modifications for your 1C — from a request in words
Describe what you need. The system clarifies the details, builds the file with 1C tooling on your base and prepares the result for verification. Base records and source modules are never sent to the service.
What the accountant receives
Not chat text — a file for your 1C
An external report (.erf), data processor (.epf) or print form: groupings, filters and totals over the objects of your exact configuration. Launch and control figures are verified on a base copy — against examples agreed with you.
The source code stays with you: your artifact, not a black box. Not right? Say what is wrong, and the task repeats with your remarks — within the agreed iteration limit.
Training example — not a product screenshot
Report “Stock by warehouses” (.erf)
| Warehouse | Item group | Qty | Amount |
|---|---|---|---|
| Main | Electrical | 1,240 | 386,400.00 ₽ |
| Main | Fasteners | 8,612 | 94,120.00 ₽ |
| Kazan branch | Electrical | 317 | 102,830.00 ₽ |
| Kazan branch | Consumables | 2,054 | 41,260.50 ₽ |
| Total | 12,223 | 624,610.50 ₽ | |
Who it is for
For those whose modification queue is longer than their hands
- Companies with no 1C developer
- Companies with one busy programmer
- Accounting & finance
- Executives
- 1C contractors
- Those who keep data inside
What can be discussed
External reports, data processors and print forms
.erf
External report
On the data composition system: groupings, filters, totals — over your base's objects.
.epf
External data processor
One-off data operations: filling, exports and checks.
.epf · BSP
Print form
Print from a button inside the document, your own layout — an external processor registered in BSP.
.cfe · in development
Configuration extension
Standard configurations only. Built and verified on our demo base — you install the file yourself.
How the work goes
Four steps are yours, two belong to the system
You describe the task, answer clarifications, confirm the specification and accept the result. Building and fixing compile errors is the system's work — within the agreed limit.
Consultant
A chat that knows your base
“Which register holds stock by warehouses?” — answered against your own objects, not in generic words. Answers select relevant fragments within the context budget.
Security
Base records never leave your machine
By the stated architecture, the service receives the task description, selected metadata and the generated result. Base records and source modules are never sent.
Team validation
Internal tests on verbatim exchange orders
These are the team's tests on 1CLancer, YellowHub and SpecPortal orders — not client deployments. Success criteria and attempt counts are on the investors page.
orders in the validation corpus as of Oct 15; the breakdown was counted at 281: 89 in the result-preparation profile (our markup)
supported configurations passed the clarification stage in the internal run of Aug 25; three orders reached a built file then
orders built in 1C in the repeat measurement of Oct 14 — actually formed on a demo base, not merely compiled
Honestly about readiness: in the same Oct 14 measurement, human-rated “yes” verdicts are 0 of 5 so far, while our self-service threshold is 18 “yes” of the last 20 orders. The threshold is not met — so we charge no money for the pipeline right now and run pilots with our specialist in the loop.
For investors and executives
Product stage, pilot scope, internal tests, limitations and the open economics questions.
Let's discuss your task
Demo — environment check and setup — a pilot task on a test copy of your base — your decision.