• Projects -
  • Rating -
  • Rating 637

Budget: 27000 UAH Deadline: 40 days

Regarding the project. The task is clear, but we need to immediately separate the wet fantasies from the CrewAI manuals and the harsh reality of production under high load and scaling. Creating a "set of scripts" that will get banned on WhatsApp in two hours is a matter of one evening. Building a fault-tolerant ecosystem that won't crash due to API limits and will maintain the states of thousands of leads is a completely different story.

What I recommend and how it MUST be done:

ARCHITECTURE BASE. No CrewAI for production in its pure form; they are only good for demos to investors. Only LangGraph. Why? We need strict State Management, control of cycles, and determinism of the graph. Agents should not go into infinite inference and eat up your money on LLM.

WHATSAPP AND BANS. Cold sales on WA without warming up and strict policies mean death for numbers. We use a proper gateway (the same Whapi or the official Meta API, if the budget allows) + OVERLAY control. We implement Human-in-the-loop at early stages for critical actions; otherwise, the neural network will promise clients free treatment at your expense.

SCALING AND LOCALITY. If it needs to be local, we package everything in Docker Compose. Local ChromaDB is okay for a start, but for proper RAG under the laws of different countries (GDPR, HIPAA), the database will need to be correctly sectioned by metadata so that the context of Italy does not mix with Australia.

GhostFlow — Ultra-high-performance distributed tracker
  • Projects 4
  • Rating 5.0
  • Rating 1 036

Budget: 27000 UAH Deadline: 20 days

Good day, Andriy, you have quite a large project. So I will respond in order, structuring my answers:
1. I have worked with both LangGraph and CrewAI, but mostly I implement projects through PydanticAI. I can use the stack that you prefer.
2. I have also repeatedly worked with WhatsApp automation. I know how to work with their official API and Twilio. I already have ready-made Python modules for integration.
3. There are many options for searching and scraping. Let's consider this point in more detail:
3.1) Search: Vertex AI Search - for obtaining links + AI functionality for queries. DuckDuckGo API can also be used (to avoid falling into an information bubble). Brave is also available.
3.2) Scraping: for non-dynamic sites with poor/medium protection, there is Scrapling. It handles this task well and works well in combination with AI. The same can be said for Crawl4AI. For dynamic sites with strong protection — either third-party paid solutions (there are many). Or cloakbrowser — it effectively hides browser fingerprints.
4. For memory, rag, etc. — ChromaDB is decent, you can also look at PGvector and, simply, qdrant. For embedding, you can check rankings by languages and automatically select the optimal third-party service or local model based on geography.

Regarding implementation:
In principle, you have already described it in detail. I don't quite understand what relates to numerology and coaching, but I have done a project related to AI generation in the field of esotericism. The task is clear, we have various modules and groups of agents for the tasks. Each has its own memory, its own context. Each performs its own functionality. We do everything adaptively right away. We add the necessary prompts, instructions, skills, and so on. I will also add auto-tests with LLM-as-Judge for the tasks.

Current freelance projects in the category AI & Machine Learning

12:57
30 June