@Tileo_LG

I build and run AI agents for Boutique Consulting Firms. A fractional AI Operator to Grow without hiring. My Customers Results are my Own Results and my Price.

AI Jungle
Joined April 2023
Trying to summarized my positioning in a short video, Open to feedback to improve it.
2
2
545
> Bac S > Prépa intégrée d'ingé > Part 1 mois en Inde « découvrir le monde de l'entreprise» > Reste 6 mois pour des pompes à eau automobiles sans l'accord de l'ecole. > Retour à l'école, mais préfère tenir le bar et le business de photocopies plutôt que les intégrales de Jacobiens de tenseurs d'Ishikawa ou je sais plus quoi > Part en Malaisie produire des chaînes à neige pour camions > Doit expliquer à la police l'intérêt des chaînes à neige car le camion s'est enfoncé dans le bitume sous 50 C > Retour à l'école, ouvre un bar cette fois > Valide le Précieux™ diplôme d'ingé > Transfère une techno de soudage laser du Canada vers la Chine > Finit face à la police, dénoncé par les concurrents > Se fait financer un MBA affaires internationales « en contrepartie » > Consulting data pour la maintenance des Falcon Jet depuis l'Inde > Achète un bar pour « diversifier » > Covid : se retrouve à gérer tout le cabinet indien ET canadien > Ferme le bar > Devient père de 5 chiens > Première Création boîte : bancs de test aéro et défense en Inde. > Transfert de techno defense sous contrat offset > Mariage > Restructuration d'une boîte > Ouvre son propre cabinet de consulting > Premier enfant humain : bientôt Cette fois c'est stable, promis 🤞 (Ps : Sorry Chérie, Il y aura un bar. J'aime pas perdre)
> BAC S > Prépa intégré UTT > DUT Informatique > Quelques projets en Crypto > Ecole d'ingé spé IA et Data > Alternance dans le BTP > Freelance Automatisation et création de modèle Computer vision
1
449
Everyone does the same job a different way. That is why I don't believe in standard AI solutions, and why I always build a custom one for each of my customer. @boardyai saw a potential match between a need on one side and the kind of system I build on the other, and made the introduction. Nothing more to share about that conversation, and that is how it should be. But it is a good occasion to explain how I work. A standard AI tool is like a playbook copied from another plant. It tells you where to Start, not what you will find in your own workflow. So I start from the firm's workflow and build the system around it. Depending on the need, it can: → Support the research before a call or a meeting → Identify relevant contacts and the relationship paths to reach them → Prepare the context, so nobody starts from a blank page → Help personalize the outreach The system does the preparation. People keep the judgment and decide what to send and what to commit to. Then we iterate with the users. The first version always carries assumptions about how the team works. Using it every day shows which ones hold and which ones need to change. Here is an anonymized business case from a similar customer: youtu.be/Eb28cvOj0?si=DSV9T1… If you want an equivalent system tailored to how your own team works, send me a message, or ask @boardyai to make the intro.
25
Not complaining at all but 10 Intro or Demo booked in one day when I wanted to stabilize Delivery and internal Process is a big challenge. How Do you Guys or Girl Manage the first Partner/Employee onboarding ?
1
26
Your next client could be hiding in a conversation your firm forgot. At AI Jungle, we're connecting relationships, opportunities, delivery and learning into one company brain. See the full AI-native model with This first video case study:
1
1
36
My customer tell me that he want to sell his firm to spend good time with family before being sick. Banks aren't helping because they say the business is Intuitu Personae. I need to find him a solution. I know AI can solve that. How to do it and package it is my new challenge.
18
Ok Feedback are great, They asked for a video on the case study. I will work on it but as every good marketer would have advise me First here is the Teaser of the video. I am welcoming feedback as video is out of my comfort zone.
A client Just called me now. He needs a deck for tomorrow. He trust me to do it Funny part It's not for his customers but For his peers. He had to replace another speaker at a seminar of interim management firms. A room full of the people he competes with every week. He wants to show them how his firm runs with AI, and he wants them to build the same thing to Improve their Value Proposition awareness and push the whole sector higher When we started working together, the scope was one ChatBot. it becames an Agent, then a roaster of Agent then a multi tenant collaborative systems. Tomorrow he is selling the whole system to his own industry. FIRST ,The scope we signed. One agent, one job. Watch a list of target companies for signals, draft a personalized first touch for each one, hand it to him for approval. That was it. He wanted more meetings. I wanted a first client who would let me install the thing inside a real business instead of a sandbox. Three months later: 755 executives contacted, 24% replied, 139 qualified meetings booked. Nobody hired, he handle it alone. That was the deal, and it worked. We could have stopped there. Standard agency relationships do. BUT Why we didn't. Two things in that contract that you scaling Gurus will say to avoid. A weekly call. Every Thursday or Friday. He brings what broke and what annoyed him. I bring what the agents did and what I would change. No slides, ever. And a flat monthly fee only to cover Inference and infra cost and a Variable share of his growth. Not per project, not per agent. I earn nothing extra when I ship a new one. The only way that deal stays worth it for me is if his firm keeps growing with it. So when he says "the drafts sound like a robot", that is not a support ticket. That is my renewal talking. Those two clauses did more than any roadmap. He stopped being a buyer and became a co-builder. I stopped being a supplier and became the guy whose Thursday depends on his Monday and a Partner in this Tech revolution. NOW Where the co-building went. Every Thursday one of us said "what if it also..." What if the agents kept the memory of every meeting, so nobody asks a client the same question twice. What if they watched the news of his best relationships and told him who to call this week, and why. What if each partner kept his own private memory, but the firm shared the playbooks, the objection answers, the lessons from every mission. What if the agents drafted the posts that keep him on his clients' radar between two assignments. Today his firm runs four agents with names. A rolodex agent Dun. An opportunity agent Bob. A visibility agent Hipo. An executive assistant EVA. Private memory per partner, shared memory for the firm. He explains it better than I do now, which is the whole point. Not one of those was in my proposal. Not one was in his request. They came out of a Thursday or Friday. TOMORROW is my victory. Tomorrow a client stands in front of his entire sector and says "this is how we work now, here is the system, here is the guy who built it with us". That was never the scope of our work together. It is what two aligned individuals turn into when you give them time and a weekly call and a shared goal. If there is a lesson, it is this. Pick the incentives first, then the technology. Aligned incentives produce scope creep in the right direction. Misaligned incentives produce change orders. Which of your clients would present your work to their competitors and peers tomorrow? If the answer is none, that is the diagnosis. PS. Yes, I am writing his slides tonight. Not an example but probably a very long night. He will present them better than I would. What compounds cannot be copied. It can be presented by someone else, and that is better.
1
52
Tileo | AI Jungle retweeted
A client Just called me now. He needs a deck for tomorrow. He trust me to do it Funny part It's not for his customers but For his peers. He had to replace another speaker at a seminar of interim management firms. A room full of the people he competes with every week. He wants to show them how his firm runs with AI, and he wants them to build the same thing to Improve their Value Proposition awareness and push the whole sector higher When we started working together, the scope was one ChatBot. it becames an Agent, then a roaster of Agent then a multi tenant collaborative systems. Tomorrow he is selling the whole system to his own industry. FIRST ,The scope we signed. One agent, one job. Watch a list of target companies for signals, draft a personalized first touch for each one, hand it to him for approval. That was it. He wanted more meetings. I wanted a first client who would let me install the thing inside a real business instead of a sandbox. Three months later: 755 executives contacted, 24% replied, 139 qualified meetings booked. Nobody hired, he handle it alone. That was the deal, and it worked. We could have stopped there. Standard agency relationships do. BUT Why we didn't. Two things in that contract that you scaling Gurus will say to avoid. A weekly call. Every Thursday or Friday. He brings what broke and what annoyed him. I bring what the agents did and what I would change. No slides, ever. And a flat monthly fee only to cover Inference and infra cost and a Variable share of his growth. Not per project, not per agent. I earn nothing extra when I ship a new one. The only way that deal stays worth it for me is if his firm keeps growing with it. So when he says "the drafts sound like a robot", that is not a support ticket. That is my renewal talking. Those two clauses did more than any roadmap. He stopped being a buyer and became a co-builder. I stopped being a supplier and became the guy whose Thursday depends on his Monday and a Partner in this Tech revolution. NOW Where the co-building went. Every Thursday one of us said "what if it also..." What if the agents kept the memory of every meeting, so nobody asks a client the same question twice. What if they watched the news of his best relationships and told him who to call this week, and why. What if each partner kept his own private memory, but the firm shared the playbooks, the objection answers, the lessons from every mission. What if the agents drafted the posts that keep him on his clients' radar between two assignments. Today his firm runs four agents with names. A rolodex agent Dun. An opportunity agent Bob. A visibility agent Hipo. An executive assistant EVA. Private memory per partner, shared memory for the firm. He explains it better than I do now, which is the whole point. Not one of those was in my proposal. Not one was in his request. They came out of a Thursday or Friday. TOMORROW is my victory. Tomorrow a client stands in front of his entire sector and says "this is how we work now, here is the system, here is the guy who built it with us". That was never the scope of our work together. It is what two aligned individuals turn into when you give them time and a weekly call and a shared goal. If there is a lesson, it is this. Pick the incentives first, then the technology. Aligned incentives produce scope creep in the right direction. Misaligned incentives produce change orders. Which of your clients would present your work to their competitors and peers tomorrow? If the answer is none, that is the diagnosis. PS. Yes, I am writing his slides tonight. Not an example but probably a very long night. He will present them better than I would. What compounds cannot be copied. It can be presented by someone else, and that is better.
2
1
1
2
125
A client Just called me now. He needs a deck for tomorrow. He trust me to do it Funny part It's not for his customers but For his peers. He had to replace another speaker at a seminar of interim management firms. A room full of the people he competes with every week. He wants to show them how his firm runs with AI, and he wants them to build the same thing to Improve their Value Proposition awareness and push the whole sector higher When we started working together, the scope was one ChatBot. it becames an Agent, then a roaster of Agent then a multi tenant collaborative systems. Tomorrow he is selling the whole system to his own industry. FIRST ,The scope we signed. One agent, one job. Watch a list of target companies for signals, draft a personalized first touch for each one, hand it to him for approval. That was it. He wanted more meetings. I wanted a first client who would let me install the thing inside a real business instead of a sandbox. Three months later: 755 executives contacted, 24% replied, 139 qualified meetings booked. Nobody hired, he handle it alone. That was the deal, and it worked. We could have stopped there. Standard agency relationships do. BUT Why we didn't. Two things in that contract that you scaling Gurus will say to avoid. A weekly call. Every Thursday or Friday. He brings what broke and what annoyed him. I bring what the agents did and what I would change. No slides, ever. And a flat monthly fee only to cover Inference and infra cost and a Variable share of his growth. Not per project, not per agent. I earn nothing extra when I ship a new one. The only way that deal stays worth it for me is if his firm keeps growing with it. So when he says "the drafts sound like a robot", that is not a support ticket. That is my renewal talking. Those two clauses did more than any roadmap. He stopped being a buyer and became a co-builder. I stopped being a supplier and became the guy whose Thursday depends on his Monday and a Partner in this Tech revolution. NOW Where the co-building went. Every Thursday one of us said "what if it also..." What if the agents kept the memory of every meeting, so nobody asks a client the same question twice. What if they watched the news of his best relationships and told him who to call this week, and why. What if each partner kept his own private memory, but the firm shared the playbooks, the objection answers, the lessons from every mission. What if the agents drafted the posts that keep him on his clients' radar between two assignments. Today his firm runs four agents with names. A rolodex agent Dun. An opportunity agent Bob. A visibility agent Hipo. An executive assistant EVA. Private memory per partner, shared memory for the firm. He explains it better than I do now, which is the whole point. Not one of those was in my proposal. Not one was in his request. They came out of a Thursday or Friday. TOMORROW is my victory. Tomorrow a client stands in front of his entire sector and says "this is how we work now, here is the system, here is the guy who built it with us". That was never the scope of our work together. It is what two aligned individuals turn into when you give them time and a weekly call and a shared goal. If there is a lesson, it is this. Pick the incentives first, then the technology. Aligned incentives produce scope creep in the right direction. Misaligned incentives produce change orders. Which of your clients would present your work to their competitors and peers tomorrow? If the answer is none, that is the diagnosis. PS. Yes, I am writing his slides tonight. Not an example but probably a very long night. He will present them better than I would. What compounds cannot be copied. It can be presented by someone else, and that is better.
2
1
1
2
125
Today is the kickoff with my 7th client. We're starting our partnership: estimated yearly revenue for AI Jungle is $27,5K fixed, plus another $7-10K tied to results. That means I've reached [ and blown past ] my target of $100K in signed revenue, landing at $140K for next year. Somewhere in me, I'm proud of it. Less than 6 months, in parallel with my other engagements. But I know the next challenge is to scale this and onboard partners, freelancers or other stakeholders and I will have to rebuild all my internal systems for it. Sorry for not updating you as much as I'd like. I chose to focus on signing enough engagements these past months, and it paid off. Now I have to deliver them and build some cash in the company to be able to scale the headcount one day. My headline has always been about helping Boutique Firms Grow Without Hiring, but it may evolve into something else soon.
28
To Max your AI ROI : You don't Need : - Better Frontier Model, - More LLM BS (Governance / Observability / Safety guardrails) - Understand How you embed your chunk of token in a Vectorized RAG Quantic Resistant Robotic Coffee Maker You Need to : - Think Clearly , Observe Listen, Analyze - Codify your expertise, Translate it in a system - Train Your Teams and the system Continuously. So : Why are you religiously Listening to Fable or Astra Strategy Advice ? You want to do same than the other 2.5 Billions Users ?
1
39
Kind of good tier list for end of aug 26 1 Fable as copartner / orchestrator 2 Sol as review adversorial / agent / computer-browser use 3 doer for specific task on budget. My preference for luna 4 balcksheep have a very unique cabability for some of my process I would add embedding model too here 5 if you want to loose time and mental bandwith you can try.
Rough tier list of where I'd put every major model right now
104
Tileo | AI Jungle retweeted
Rough tier list of where I'd put every major model right now
1,479
749
535
14,941
4,120,548
busy sunday. 5 demos to finish for next week. August will be remembered. I hope I will find more times to post here next month.
18
I think I found what Buzz missed. Chat-Mail-CRM-PMP-CanvaDocument-Browser in a single self hostable workspace accessible by human and Agents, local and hosted on VPS. I know they haven't deliver all of it yet but it's on the good way. I am testing it asap and will report about it
Today we're launching Macro 1.0 — a new office suite for the intelligence age. Macro is a unified workspace for your entire company, your team and your agents. 1. Fully open source. Built in Rust + SolidJS. Self-host if you want. 2. Designed as a single system: email, messaging, docs, tasks, agents, calls, and CRM all @-linked together in one tab. 3. Unified team-level memory for agents built over emails, team chat, tasks, PR's and CRM. Access the memory from Macro or AI or external agents via MCP. We built Macro for ourselves because we wanted a single system for our whole company. We didn't want to get slowed down by rate limits and 2FA'ing into 17 different tabs. Let's take a look at each block 🧵👇
54
Last week a desk research mandate landed in my inbox. European food and beverage companies preparing their entry into India, now that the EU-India trade agreement is signed. This is the kind of study a big consulting firm staffs with three Business Analysts and bills six figures. I’m running it with AI agents. And I’m testing a method I haven’t seen anyone in consulting use yet. I call it the gauntlet loop. The first move is still the classic one. You don’t start by “researching the market”. You write your gut answer on day one, then spend the rest of the study trying to kill it. My day-one hypothesis was simple: The winners of this FTA are not the biggest brands. They are the companies that sell the categories where the tariff math actually moved. Wine drops from 150% to a fraction of that. Olive oil goes to zero. Dairy is excluded entirely. That is three different games inside one “F&B opportunity”. So the scope is not an overview of India. It is a clean issue tree. Mutually exclusive buckets that cover the full question. Which categories win on tariff math. Which route to market fits each one. What the real import chain looks like. Who has already moved and what they plan next. Nothing overlapping. Nothing missing. The same discipline you would use if you were preparing a case for an MBB interview. In MBB the method has never been the problem. The problem is that this method is normally executed by a pyramid of 25-year-olds billed at partner-adjacent rates, takes six months, and often ends up too far from reality for an SMB to implement it. Most people solve this by handing the study to a research agent. I operate agent fleets every day, so I can say this plainly: An unsupervised research agent produces confident garbage at scale. Not because the models are bad. Because the agent grades its own homework. Ask it if the work is done and it says yes. Every time. It spends more time reviewing the source than challenging what the source actually claims. The real bottleneck is not generation speed. It is the quality bar, and the fact that agents drift toward the sources they found instead of staying locked on the original question. A few weeks ago a pattern started spreading in the coding-agent world: the gauntlet loop. The mechanics are simple and strict: An orchestrator that never writes the deliverable itself. Builder agents that produce. Blind critics with fresh context that judge the artifact against a concrete reference example. And the rule that makes it work: a critic never reviews a second attempt. New round, new critic. A critic who already saw draft one starts grading “better than before” instead of “meets the bar”. The loop only stops on inspectable evidence. Never when the builder declares itself done. Coders use this to ship features. I have not seen anyone run it on consulting deliverables. So that is the experiment. For this study the reference artifact is the strongest comparable market study I could find, torn down to its skeleton. One study done for another locality. Another done for the same locality but on a different sector. I looked at how the executive summary argues. How the country one-pagers are built. Where the buyer-side detail sits. That skeleton became the quality bar. One builder agent per issue-tree bucket. Each finished section goes to a blind critic that has never seen our study. Below the bar → rejected with written reasons, rebuilt, judged again by a fresh critic. A separate pass does nothing but check claims against their sources. What stays human is clear: The issue tree. The interviews (real importers do not talk to bots). The “so what” on every page. The decision to kill a hypothesis when it dies. Judgment stays human. The pyramid cost and the six-month timeline do not. This is what a mini-MBB looks like in 2026. Same scoping discipline. Agent execution. Gauntlet quality control. Partner-level judgment on top. Faster because the desk work takes hours instead of weeks. Cheaper because there is no pyramid to feed. And the same loop can run next week on a proposal, a due diligence or a competitive teardown. If you run a boutique B2B firm, the real point is this: The frameworks were never the moat. The pyramid was just the cost of the organisation. That cost is leaving the building. Some people say this is the end of consulting. I think this is how we revive it and make it usable for a much larger number of firms. I will share what the gauntlet actually catches, and what it misses, once the study ships.
1
119
If anyone is interested, Lucas is really doing a good work to make content for you around the interview. Don't be shy dm him.
Urgent ! Cherche une personne à interviewer pour publier lundi Critères : - Lancement récent - Environ 500-1000 balles de ca minimum - Bootstrap
1
57
My customer wanted to grow and test a new way to offer their service. Their competitors would have hired. And they would have sought advice from their network, probably an ex-Partner from an MBB firm. The results of that path are predictable: - $120K+ salary minimum - a service charge around $150K - Six months of ramp-up - A beautiful deck full of MECE frameworks and recommendations distilled from firms ten times their size And the risk that the person leaves… and they start from zero again. Plus weeks of the partners trying to adapt a plan that was never designed for a two-partner firm. This firm didn’t take that path. They are a two-partner executive search practice working between Europe and Asia. Senior. Credible. Completely out of hours. Their pipeline only moved when one of the founders personally pushed it. Every mandate came from their network. Everything else stalled. So I did something most people still refuse to do. I didn’t start by building an agent. I started by extracting their judgment and writing SOPs, the kind of work people usually push to an intern. I wanted to know, precisely: How they decide if someone is worth contacting. What they actually write in a first message. Which signals make them lean in or walk away. Those SOPs became the rules. Written in plain language. Editable by them or me. Only then I deploy one single agent. Not a platform. Not a suite. One agent with a deliberately small scope: research, draft, sequence. The bigger build was the approval ledger on their phone. Nothing leaves without a yes. Approve. Edit. Skip. Two taps. Scaling gurus treat this step as optional. It isn’t. It’s the entire difference between generic outreach and their outreach, at scale. By week 3 the corrections had dropped sharply. The agent had started writing like the firm. Here are the numbers that came out of that approval ledger over three months: • 755 executives contacted • 1,992 messages sent • 0 messages sent without human approval • 24% replied • 139 qualified meetings booked • 90 already held One qualified meeting for every five executives contacted. The firm didn’t buy software. They bought a version of their own judgment that could operate while they slept and still required their signature before anything went out. That’s why these numbers are verifiable. Every single meeting traces back to a message a partner approved with their own thumb. The split is simple and durable: The agent does the digging and the scut work. The partners do the judging and the decisions. Every hour they used to spend researching and drafting now goes where the fees actually live: in the meetings with their customers. If your pipeline only moves when you personally push it, you don’t have a discipline problem. You have a system problem. And systems, unlike motivation, are installable.
2
153
Today, for the first time in a long while, I got frustrated with my agents. This week is packed: 1 new enquiry for AI Jungle 1 fresh intro for a demo 1 full desk research + senior interviews for a market-entry project (delivery in 3 weeks) for Tensor Advisory. 2 no-shows on intro calls. Three potential deals on the table, each ranging from $15k to $150k per year. On paper, I should be happy. For a young advisory, this level of demand is a strong signal.But my agents decided ( on their own) to protect my focus. They let me stay 100 % on delivery and sales calls. No newsletter. Almost no posts. No internal R&D tickets. No scouting of the big news of the week (Prime Intellect’s self-evolving harness, the new Cloudflare features…). Their standing instructions are crystal clear: Priority 1 → current customer support Priority 2 → warm leads while momentum is hot Priority 3 → marketing & social presence Priority 4 → internal builds & R&D Priority 5 → testing & scouting. Everything should still happen every week. The priority list only decides where my energy goes. The agents are supposed to handle the lower ones. This week they watched me negotiate quotes and write proposals in my inbox… and stayed silent. This morning I asked: “What’s the reach of the last newsletter?” Answer: 0. Why? “Because you rejected the Sunday draft and asked for a re-research + redraft. We are waiting for your input. We didn’t flag it because you looked extremely busy with the proposals.” First time I felt my agents behave like a promising but shy junior trainee: capable, loyal… yet too polite to push back or escalate when the manager is drowning. I don’t know if this is pure mimetism (they mirror how I treat them) or if my own mental frameworks are still too tight and are holding them back. Either way, I’m fixing it with them right now. Sorry if you didn’t get the newsletter this week. I’m finishing the new draft with them as we speak and I already know it will be better than the Sunday version. If you want it the second it’s ready, just subscribe here: welcometotheaijungle.substac… The agents are learning. So am I.
58
So big. Anyone need to try. After nous research with Hermes I am glad to see other AI crack teams deliver more innovation.
Introducing Prime Agent: A self-improving RLM harness for coding and long-running autonomous tasks. Designed to be both token-efficient and expressive through programmatic tool calling, context as a variable, multi-agent messaging, and a self-modifiable harness state.
46