I build AI agents, small web applications and workflow automation for businesses. I start with one concrete task and agree the scope, access rights and acceptance checks with you. If a script or a connection between existing tools is enough, there is no need for AI.
Four possible directions. The choice depends on your work and existing tools, not on which AI happens to be fashionable.
Check that users can complete the task and understand how to correct invalid input.
Check sources, completeness, duplicates and usable exports.
Test retries, errors and whether incorrect data can spread unnoticed.
Compare preparation time, source links and corrections needed.
An AI agent is one option, not the whole service. For example, Gmail, Calendar, Drive and Docs can connect to an assistant you message in Telegram. Telegram is simply the chat channel. If you need a web form, a data export or a connection to different software instead, I start there.
See what I have already builtOne bounded task and the smallest useful solution. Before starting, I agree with you on scope, price, schedule, access rights and how to judge the result.
Describe the current process, a typical example and what needs to improve.
Choose the right tool. Use AI where it adds value.
Test agreed examples, exceptions and failure behaviour.
Adopt it, change it or stop. Continuation requires a separate agreement.
For teams already using AI tools without a clear picture of where data goes. You receive an inventory of tools, access rights and issues to address. No agent is built at this stage.
If the pilot proves useful, I prepare the workflow for daily use. I finalise access rights, logging and error handling, then hand over the setup and instructions.
Optional updates, smaller fixes and monitoring of an agreed workflow. Maintenance scope, response times and larger extensions are separate agreements.
Cost depends on the task, integrations, sensitive data and exceptions. The quote separates development, hosting, any model-service usage and maintenance. I cannot give a precise price without understanding the workflow.
Describe what you want to simplifyNo. If fixed rules, a script or configuring existing software is enough, there is no need for a model.
I agree a schedule with you after reviewing the task and integrations. A small tool and a multi-system integration are different scopes.
I quote for an agreed scope. Development, hosting, model usage and optional maintenance are separate costs.
I document services and data flows before enabling connections. An EU server alone does not prove an external model processes data in the EU. If EU-only processing is required, unsuitable services are excluded.
I agree with you on stop conditions, logging and recovery. Sensitive or external actions require the agreed approval. AI-drafted replies remain subject to human review.
The quote defines the handover, source code or configuration access and instructions. Third-party service licences still apply.
No. Further development and maintenance require separate agreements. Payment for the first stage follows its agreed quote.
Describe one task or missing tool, how you work today and the result you want. No technical specification needed.
For example: “Every week I collect prices from public sources and copy them into a spreadsheet. I want to see changes and know when a source could not be checked.”
I review your description and ask for any missing details. If the workflow looks suitable, I arrange a short conversation with you. Sending a message does not place an order.
Do not include passwords, personal identification numbers or confidential client information. A description of the task is enough for now.
How I use contact detailsPrefer email? Write directly to info@oej.ee.