Activity
Mon
Wed
Fri
Sun
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
What is this?
Less
More

Owned by Mitchell

AI Survivors
153
$47/month

Make companies AI-first. Get your first paying client in 90 days. Learn the method I use myself.

19 contributions to AI Survivors
Welcome to AI Survivors. Here's where to start.
I'm Mitchell. This community is for entrepreneurs and professionals who want to earn money by making companies AI-first. You might run your own business or work as a freelancer. You can also do it inside the company you work for.\n\nAt a large Dutch grid operator I am making my own team AI-first. I have worked in data and AI for 10 years. My own work runs AI-first every day. With AI Survivors I help other companies get there too. Here you learn my method and use it on a real company, with your first paying client in 90 days as the goal.\n\nYour first step takes two minutes. Post in Introductions: who you are, and which company you want to make AI-first. That can be your own business or a company you want as a client. Your employer counts too. I read every introduction and reply.\n\nWant me next to you? The three plans are here: skool.com/ai-survivors/plans
0
0
At a client, look for the one task that changed
The first thing I check in a team is one task where people now split the work with AI. For quotes that can look like this: AI writes the first draft and a colleague checks it before it goes to the customer. Before AI, one person wrote the quote from start to finish. A team can have licences for everyone and no task like that yet. That team is experimenting, and that is where your work starts. At a client or in your own company, which task would you ask about first?
0
0
At a client, look for the one task that changed
Starting with AI as a team costs time first
Starting with AI as a team costs time first, often a few months. After that it pays off. Drawn as a line it looks like a J. My current team is working out where AI fits in the whole process. We change tools and processes at the same time, and we have to agree on both. The business wants to see value, and right now we can show little. I look at how fast the team picks up something new and gets it all the way through the process. That speed is where the value comes from later. If you lead a team in its first months with AI, measure that speed now. Then you have a number to show while the business waits. Is your team still in those first months? What do you measure?
0
0
Starting with AI as a team costs time first
AI feels free right now. That's the most expensive assumption you can make.
The first time AI really took over a chunk of my work, it felt like magic. And it felt basically free. A few euros of credit, a subscription, done. Then I set it loose on real jobs, all day, and looked at what it had actually spent. Every small task was quietly costing money. On your own that is pocket change. Across a team doing it all day, it is a real line on the bill. Here is the strange part. Most people just make an account, pay one flat monthly fee, and that is it. Simple and capped. But the moment you start plugging AI into your own systems, an app you build, your automations, a tool your team runs, you switch to paying per token (think: per chunk of text it reads and writes). And per token adds up a lot faster than a flat fee. That is the jump almost nobody warns you about. Now here is the part even fewer people have clocked. The reason AI feels cheap is that you are not paying what it costs to run. For every dollar you hand over, the providers are spending more than that to serve you. OpenAI has been running at well over a dollar spent for every dollar it earns, by its own numbers. They do it on purpose, to win you while the market is still being decided. And they have already started walking that subsidy back. Here is the uncomfortable bit. Nobody can tell you when the investor money runs out or the hype cools. But when it does, the price that moves is the one you pay per token. And it moves up, not down. So the number you plan around today is a promo price. This is the survival part, and it is why this community exists. Surviving the next few years with AI means using it heavily without letting the cost quietly drain you. The ones who come out fine learned to run it cheap before the price caught up. The ones who did not are the ones who get an invoice that scares them off the whole thing, right when everyone else is pulling ahead. You do not need a finance degree for any of this. Four habits cover most of it. 1. One chat per topic.
0
0
AI feels free right now. That's the most expensive assumption you can make.
AI will lie to your face with total confidence. Here's how I stop it
A while back Claude handed me a block of code built around a library that does not exist. Forty clean, well structured lines, using functions from a package I could not find anywhere online. It never once hinted it was making it up. I lost an hour before I realised the whole thing was fiction. That was not a one off. I have had it give me a SQL job that reported a result while nothing actually ran underneath. I have had it cite sources that were not from where it claimed, or were not real at all. Every single time it sounded certain. That is the dangerous part. It is never unsure. Here is what is going on. When a model does not know something, it does not stop. It fills the gap with the most likely looking answer. A plausible function name. A plausible date. A plausible source. It is built to always produce something, and "something" wins over "I don't know" every time, even when the something is wrong. Here is a live one. I asked for the EU AI Act key dates two ways. Straight from memory it told me the Act was in full force on 1 January 2025, with bans from mid 2024. Confident. Wrong. Then I forced it to work from sources only and search first. It came back with: in force 1 August 2024, bans apply 2 February 2025, GPAI rules 2 August 2025, fully applicable 2 August 2026. Every date now had a link I could open and check. Correct. Same model. Same question. The only difference was whether I let it guess. Here is why I care, and why you should. Everything you send or publish on a model's word carries your name, not the model's. The wrong figure in a report. The fake reference in a proposal. The library that does not exist in code you shipped. Right now people forgive it because "the AI wrote it". In six to twelve months that excuse is gone, the same way "sorry, autocorrect" stopped working. What you send this year is what people remember. So here is how you stop it. 1. Make it search before it answers. Do not ask "what are the EU AI Act dates". Ask "search for the EU AI Act dates and answer only from what you find". No result, no answer.
0
0
AI will lie to your face with total confidence. Here's how I stop it
1-10 of 19
Mitchell van Rijkom
3
32 points to level up
@mitchell-van-rijkom-8778
Founder of AI Survivors. I make teams AI-first and teach professionals to do it for clients. 10 years in data and AI.

Online now
Joined Feb 12, 2024
The Netherlands
Powered by