BuildDecision and build
Implementation
For operations. Phase 1 tests the solution through a pilot on a real use case, before you decide on the Phase 2 build. Each phase has its own scope and price in the written offer.
For IT. We define the API integration, data access and model boundaries. You approve the acceptance criteria and operating responsibilities.
The first conversation is free. We reply within 3 working days.
Price and boundaries
Phase 1: Architecture
From 960 EUR excl. VAT
Baseline
Discovery and specification for one bounded outcome.
What can change the price
- Systems involved
- Data access
- Acceptance criteria
Discovery does not include the production build.
Phase 2: Build
From 960 EUR excl. VAT
Baseline
One bounded production build after approved discovery.
What can change the price
- Integrations
- Operational risk
- Acceptance requirements
The agreed scope sets the final price.
Indicative planning range, not an offer.
Prices are estimates in euros, excluding VAT. The proforma invoice and the invoice are issued in lei, at the National Bank of Romania (BNR) rate on the day of issue.
Details: Terms and Conditions, 4.2The first conversation is free. We reply within 3 working days.
- Architecture and integration
- Acceptance criteria
- Operating procedure
- Documentation
- The AI Act requirements that apply to the system, built in from the start: labelling AI-generated content, logging and human oversight, where the law requires themFormal legal audit: not included.
- Unlimited development
- Ongoing operation (AI Care can take it over)
Sometimes the answer is no AI. If Phase 1 shows that a clear rule or a simple integration solves the problem, that is what we build. We did the same for aifocus.ro.
A system connected to what you already use
We design API integrations with existing applications and with data from CRM or databases, within the access available. We document which data reaches the model, which provider handles it and who has access. The criteria below are agreed for each project.
- Your systemsCompany dataCRM, databases, approved documents
- Application and authorised API
- What we build and document · the agreed access boundaryApplication and authorised APIapproved access only
- AI model
- Logging: Logs and incidents
- AI modelchosen for the use case, documented provider
- Validation and rules
- Validation and ruleswhat fails is stopped
- Designated operator
- Logging: Logs and incidents
- Who decidesDesignated operatorthe person you name approves
- approval: System action
- Your systemsSystem actiononly after approval
- Logging: Logs and incidents
- What we build and document · the agreed access boundaryLogs and incidents
What the acceptance criteria cover
Agreed for each project; they are not test results already achieved for a client.
- Data access
- Who may read each source and what access is denied.
- Model output
- Which examples are used to assess it and what threshold it must meet for acceptance.
- Agent actions
- What the agent may execute, what needs approval and how it is stopped.
- Outage
- What happens when the model, API or source system does not respond.
- Handover
- Who operates the system and which documents confirm the handover.
What changes
The workflow is designed, integrated, verified and handed over with explicit responsibilities.
What the company gains
You approve the architecture and the criteria for accepting the system, so the second phase starts from a plan you approved.
What the team gains
The operator receives the system with the guide and the operating procedure, so they know how to use it and what to do when something goes wrong.
Is this right for you?
This is right for you if
When this comes up
There is a priority case, an owner and clear outcome criteria.
Who it is for
Organizations that know the desired outcome and can name the operational owner.
The problem
The experiment is not yet a system people can understand, govern and use.
This is not right for you if
- You do not yet know where AI makes sense in your company.AI Roadmap
- You already have a working system and only want it maintained.AI Care
How we work
The two phases are described above. The conversation, the offer and the acceptance are at the end of the page.
- Discovery and specification
- A small trial on a real case
- Build, integration and acceptance
- Handover and review
- A priority case and a named operational owner.
- Clear criteria for the result.
- Access to the systems and the data involved.
What you receive
- One signed outcome and scope
- Handover to the operator, guide included
- Unlimited development
- Ongoing operation (AI Care can take it over)
Sometimes the answer is no AI. If Phase 1 shows that a clear rule or a simple integration solves the problem, that is what we build. We did the same for aifocus.ro.
What you can check
- Completion evidence
- Acceptance criteria pass, and operation, boundaries and handover are documented.
- Availability and capacity
- Active scoped engagement shaped around the agreed outcome. Discovery, the trial on a real case and the production build are used as needed; AI Roadmap is not a prerequisite.
Questions about Implementation
Any other questions? Let's talk
Do you work with the systems we already have?
Yes. Integration into your systems is part of the build, and the number and complexity of integrations can affect the price.
Can we stop after Phase 1?
Yes. The offer treats the two phases separately. Phase 1 ends with the specification, the pilot on a real use case and the acceptance criteria. Then you decide whether we start the build.
Who operates the system after handover?
The person responsible for operation, whom you designate at the start. We hand the system over to them with the operating guide. Ongoing operation is not included; AI Care can take it over.
Do you sign an NDA?
Yes. We sign our standard non-disclosure agreement (NDA) before the first conversation if you ask for one. A company's own agreement is negotiated and can change the price.
Where this goes next
Where it can go next
The system can move into AI Care or, if you want a team to take ongoing responsibility for the AI initiatives and systems, into the External AI Department.
Which workflow do you want to automate? For the first conversation, you only need to tell us what the team does by hand today and what outcome you want.
- First messageWhat the team works on and what needs to change.
- DiscussionWe establish the outcome and who owns it in operation.
- Offer and acceptanceThe offer covers the two phases separately; acceptance fixes the signed scope.
The first conversation is free. We reply within 3 working days.
Or e-mail us directly at office@aifocus.ro
How we teachA complete free lesson on YouTube.


