Budget: 25000 EUR Deadline: 30 days
The timeline is from 3 to 6 weeks for a working first version, provided there are clear scenarios, access, and a description of the logic. The budget is approximately 120,000 UAH for the first stage, which includes architecture, assembling the main workflows, integrations, and testing.
We can approach this not just as executors of individual chains in n8n, but as a team that builds a reliable AI system - agents, memory, roles, data sources, checks, error handling, logging, and proper recovery logic. It's important not to just create a nice demo, but to ensure it doesn't fail on the first non-standard request. The machine should serve the person, not the person serve the machine - it's a bit grandiose, but in automation, it's very practical =)
We have relevant experience:
> https://business.ingello.com/vorfahr - AI automation and product logic with integrations
> https://business.ingello.com/fractal - agent-based approach and complex automated processes
> https://business.ingello.com/tts - AI service working through models and APIs
The main page for FLH - https://systems-fl.ingello.com
Implementation vision:
> short design - roles of agents, scenarios, data, points of failure
> assembling the foundation in n8n or on an agent framework - depending on load and required flexibility
> integrations with OpenAI, other models, Supabase, REST APIs, webhooks
> RAG - if knowledge from documents, databases, websites, or internal materials is needed
> testing on real cases to avoid getting a system that is only beautiful in presentation
You will need to provide access to n8n, Supabase, API keys, a description of target scenarios, and examples of input data. Note, there is a nuance - if there will be multiple agents, it's important to decide in advance who makes the final decision and how the quality of the response is checked.
I would like to clarify 2 questions:
> what specific tasks should the bots perform - sales, support, processing applications, documents, analytics, or something else
> is persistent memory and RAG needed for your data, or is it sufficient for now to have scenario-based automations through the API
Overall, it's fine to start with the first stage - design plus a working prototype, without trying to compress the entire future platform into one bid.