/en/agents · automation
Iconicompany's agent collects procurement requirements, calculates a proposal, fills out forms, and prepares a submission package. Workflow, checks, handover to development, and autonomy boundaries.
ipresale is a product of Iconicompany, an agent of its platform. It prepares commercial proposals and documents for participation in procurements: receives materials, analyzes requirements, calculates a proposal, fills out forms, and assembles a submission package.
The result is used by the manager or employee responsible for participating in the procurement. Instead of transferring data between files, they check the ready proposal, see the unfulfilled requirements, and make decisions about the company's obligations.
The agent works with b2b-center and bidzaar, as well as with materials for direct off-platform deals. Connection capabilities depend on the platform and accesses: one cannot consider any download or upload route universal.
For a procurement on a platform, the input is the procedure number or link; for a direct deal — documents and the customer's request. Additionally needed are:
Re-requesting known details is not required: the agent takes them from the profile. A missing document or fact is marked as an unfulfilled position, not guessed.
A different goal can be set — to study a procurement to understand the market. Then the agent prepares an analysis and conclusions for product development, without assembling an application for participation.
The agent records the subject, customer, and procurement deadline, downloads documents, unpacks archives, and converts files into a working format. Already saved materials are reused.
Before passing the content to the model, a mechanical check for restrictions on the use of generative AI is performed. If a ban on transferring documents or a penalty for it is found, further analysis stops until the owner decides.
Four sources are considered: documentation archive, organizer's clarifications, submission form, and comments on the procedure card. The latter may contain mandatory conditions not found in the terms of reference.
The model highlights requirements, matches them with company documents, and prepares a package: what needs to be provided, how the requirement is met, what is missing. If some sources are unavailable, this remains a visible limitation of the analysis.
The agent forms an estimate based on the scope of work and procurement conditions. For an initial decision, sufficient but not excessive detail is needed: composition of the result, deadline, assumptions, and risks. The initial estimate considers the possibility of a reverse auction and proposal refinement at the next stage; there is no universal margin percentage.
The calculation depends on the subject of the procurement. In project work, the result is estimated; in the procurement of specialists — the required positions and units of measurement. The model helps to analyze the volume, while arithmetic and filling of price forms are performed by scripts.
The agent prepares the commercial proposal, questionnaires, inquiry sheets, annexes, and cover letters. Details and permanent answers are taken from the profile, answers for a specific procurement — from its decisions.
Platform templates preserve their structure. Where rebuilding a workbook leads to platform rejection, values are changed specifically in the original file. If there is no tool for a repetitive action, the agent can write a builder, check its result, and use it in subsequent procurements.
The plan sets the composition of the submission and the mapping of files to upload fields. The agent creates a separate submission folder, an inventory, and a map of answers for platform fields. Working versions and intermediate documents remain separate.
A normal run continues until a ready package without confirming every intermediate step. Submitting the application requires explicit permission from the owner for a specific procurement: a submission is an offer. Preparing a form and sending it are different actions.
During a reverse auction, the agent receives places and current prices from the platform, recalculates the proposal according to established rules, and fills out the current template. Then it processes answers and remarks, saves the actually submitted materials and subsequent actions.
Technically, the process consists of 15 stages: passport, fetch, extract, pack, documents, price, pricelist, forms, kp, contract, assemble, submit, haggling, errors, handoff. For each, an input, result, and check are provided.
The result of ipresale is files and the recorded state of the procurement:
| Result | What it contains |
|---|---|
| Source materials | Platform or direct deal documents, available clarifications, and submission form details |
| Requirements package | Subject, conditions, document composition, risks, and unfulfilled requirements |
| Estimate and proposal | Assessment, assumptions, deadlines, commercial proposal, and required price forms |
| Documents | Filled customer forms and company annexes |
| Submission package | Only files intended for sending, inventory, and field map |
| Work outcome | Completed stages, check results, made decisions, and missing information |
In the workspace, everything for a procurement is located in work/<id>/. Sources are stored in raw/, extracted texts — in md/, analysis — in pack/, working documents — in build/, submission package — in submission/. The state of the stages is recorded in pipeline.json.
Mechanical verification confirms the structure and consistency of data. The completeness of semantic analysis, the correctness of the estimate, and legal obligations require a substantive check.
If the procurement proceeds to product creation, ipresale transfers the documents and requirements package to a separate project. If available, a prototype and links to reference implementations are transferred. Preparation of the input is performed by a common spawn_project.py tool.
Further requirements and development are handled by the product pipeline. ipresale does not duplicate its stages and does not declare the application ready just because procurement documents are assembled.
Automatic registration of every procurement in iomp is not implied here. Preparing a project from procurement materials and the development route through tasks are different parts of the platform; the specific launch method is fixed during transfer.
The model can misunderstand a condition, miss a requirement, or suggest an unconfirmed answer. Therefore, sources of facts, checks, and the ability to see what remains unfulfilled are needed.
The platform can change the interface, deadline, or template format. A new form sometimes requires tool modification. Authorization, an unavailable source, or a model provider limitation can stop processing.
The agent does not create missing licenses, experience, employees, or permissions. Non-compliance with a criterion can be shown in the application; one cannot confirm a non-existent fact. The decision to participate with incomplete compliance remains with the owner.
Submission, new obligations, and working with documents for which AI transfer is prohibited require a separate decision. The presence of an agent does not give the company the right to transfer any materials to it.
ipresale does not guarantee winning, admission, or passing to the next stage. It prepares a proposal and makes the work state visible.
In one procurement, the form contained 30 mandatory file slots. A general list of attachments did not answer the question of which document belongs to each criterion.
In the submission plan, they started specifying the signature of the required slot for a file, or several signatures if the document fulfills several points. The builder maps them with the form and includes only existing files. As a result, the employee receives an upload map, and the absence of a document is visible before submission.
Verification of the result: each mandatory file field is assigned suitable attachments or a gap is recorded. This is a specific process change; it is not a measurement of model accuracy or the probability of winning.
One must compare the entire path to an accepted package, including reading sources, fixes, and repeated checks.
| Indicator | How to calculate |
|---|---|
| Preparation time | From receiving materials to a verified package; separately account for waiting for external answers |
| Requirements completeness | Found correct requirements relative to a reference analysis of all available sources |
| Manual edits | Share of results with substantive fixes, separately from formatting |
| Critical errors | Omissions of mandatory conditions, unconfirmed facts, and incorrect obligations |
| Package readiness | Share of attempts that ended with a package accepted by the responsible employee |
To evaluate exactly the model's contribution, it is useful to compare three modes: manual work, automation by scripts, and scripts together with the agent. Tasks and verification criteria must be comparable; unsuccessful processing is also included in the calculation.
Confirmed facts of this description are the presence of stages, builders, and checks, working with four sources of requirements, and analyzing a form with 30 slots. Percentages of time reduction and win growth are not claimed without separate measurement.