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

Owned by Dagur

The AI Retail OS

4 members • Free

Learn how to use AI in your retail business. From invoice automation to smarter buying — step by step.

Memberships

The AI Advantage

123.9k members • Free

AI Automation Society

381.7k members • Free

Skoolers

184.8k members • Free

7 contributions to AI Automation Society
The 3 questions I ask before automating anything 🛠️
Before I build any automation across my companies, I run every idea through three questions. Saves me from building stuff that looks cool and does nothing. 1. How often does this actually happen? If it's once a month, automating it is usually a waste. The boring daily and weekly tasks are where the real time savings hide. Frequency first, always. 2. What does it cost me when it goes wrong? Some tasks you want fully automated. Others you want AI to draft and a human to approve. The higher the cost of a mistake, the more I keep a person in the loop. Don't automate the step that gets you sued. 3. Do I actually understand the manual version? If I can't explain the task step by step myself, I've got no business automating it. You can't automate a mess you don't understand. You'll just get a faster mess. That's it. Frequency, risk, understanding. If an idea clears all three, I build it. If it doesn't, I leave it alone, no matter how cool the demo looked. What's your filter for deciding what's worth automating? 👇
Hard truth about ai
Everyone is learning AI. Everyone is building with AI. That’s not the advantage anymore. The real advantage is knowingwhat is actually worth building. And that doesn’t come from tutorials It comes from conversations. Talk to business owners Talk to operators. Talk to people already spending money to solve problems. The market will tell you faster than the internet ever will.
0 likes • 23h
This is the whole game and almost nobody says it. I run AI across a few companies, and the hardest part was never the build. It was knowing which problem was actually worth solving. You only learn that from sitting in the mess of a real business. Tutorials teach you the tool, operators teach you the problem.
The boring AI use cases are the ones that actually made me money 💰
Everyone here is building voice agents and cold email machines. Cool stuff, genuinely. But I run AI across a few retail companies, and if I'm honest, none of the flashy things are what moved the needle. The boring back-office automations did. Here's what actually paid off: 🧾 Invoice reading. Every supplier sends a different layout, someone used to key them in by hand. Now a GPT pulls the data clean. Hours back every week. 📦 Reorder flags. A simple system that watches stock levels and tells me what to reorder before I run out. Boring. Saved me from dead stock and empty shelves both. 📊 The "what changed this week" report. Every Monday I get a plain-English summary of what moved in the business. No dashboard diving. Took an afternoon to build, I read it every single week. None of this is sexy. Nobody's making a YouTube thumbnail about invoice parsing. But it runs quietly in the background and saves real time and money, which is the whole point. My take: if you're selling to business owners, sell them the boring stuff first. It's easier to build, it works, and once they trust you with the unglamorous wins they'll let you build the cool things later. What's the most boring automation that's quietly saving you the most? 👇
1 like • 2d
@Jorge Reed honest answer, I build mostly for my own companies rather than chasing outside clients, so take this with a grain of salt. But the principle is the same either way: lead with the boring, obvious win. "I'll save you X hours a week on this one annoying task" is the easiest yes in the world. Land that, deliver it, and the trust to do bigger things comes naturally.
3 likes • 2d
@Pablo Hurford 🙏 the unglamorous workhorse. Does the job every single day and never asks for a raise.
Two owners want two different outreach plans. How do I thread this?
Need help threading a needle with a client. Two owners, two different outreach plans, and neither one is clean on consent. I run a small AI automation shop. Just landed a solid client in the home repair space. They help homeowners after a major damage event, and the whole business runs on speed. There's a short window to reach people right after something happens, and whoever gets to the homeowner first usually wins the job. Time is everything in this niche. Here's where I'm stuck. There are two owners and they want to go two different directions. The first guy, call him Dan, is the operator. Younger, bought into the company in his early twenties, runs the day to day, super relationship driven. Dan wants me to build a system that blasts text messages out to a list of homeowners in the affected area. No opt in, no prior relationship, just hit the list fast. When I brought up the consent problem he basically said he's willing to eat the fines and wants to move forward anyway. His logic is that the whole industry is doing it and nobody seems to be getting hit, so why slow down. The second guy, call him Victor, is the money and the real power. Bought into the company recently, runs a whole portfolio of other businesses, master negotiator type. Victor doesn't want texts. He wants an AI voice receptionist and outbound calls. More of a robocall and live-routing approach. So I've got the operator pushing non-consented text blasts and the owner pushing voice and calls, and honestly neither path has a real consent foundation underneath it yet. They just have a list of people in an area who got hit. My questions for anyone who's actually built outreach at scale. How are you all handling the consent piece in a time-sensitive niche like this, where you can't realistically get opt in before you reach out? Is there a legitimate way to move fast and stay protected, or is everyone just accepting the risk? When a client tells you flat out they're willing to take the legal hit, how do you protect yourself as the builder so the exposure stays with them and not with you? Contract language, documentation, who owns the sending number, anything you've learned the hard way.
Two owners want two different outreach plans. How do I thread this?
4 likes • 3d
I'd pump the brakes on both versions before you build anything. The moment a client says he's "willing to eat the fines," he's telling you who he is, and it's worth listening. In the US, non-consented text and robocall rules carry per-message statutory damages that stack fast, and when it goes sideways the plaintiff's lawyer names everyone in the chain, including the person who built and ran the system. "The client said they'd take the hit" is not the shield people think it is, especially if that client turns out to be judgment-proof. Building on Angie's points, the one thing I'd add: there's usually a compliant fast path in these post-event niches. You reach people through channels where there's a lawful basis to contact them rather than blasting a scraped list. Speed doesn't have to mean breaking the rules, and that's the version you actually want your name attached to. A client who shrugs at the legal risk on day one is the same one who disputes your invoice when complaints roll in.
Today I tried something uncomfortable:
I showed the system to someone outside the “AI space.” And honestly… best feedback so far 😭 Because they didn’t care about: - prompts - workflows - automations - any of the technical stuff Their only questions were: “How fast does this save me time?” and “Does this stop leads from slipping through?” That hit me hard. Builders love explaining features. Clients care about outcomes. So I spent most of today simplifying the onboarding even more. Removed: - unnecessary setup steps - technical wording - extra configuration Trying to make this feel less like “software” and more like: “plug this in and your lead flow gets cleaner.” Still early, but I finally feel like I’m building around actual business pain instead of just cool tech.
2 likes • 4d
This is the most important lesson in the whole space and most builders learn it way too late. Nobody buying this cares what's under the hood. They care about time saved and money not slipping away. I'd take it one step further: when you talk to a business owner, drop the word "automation" entirely and describe the outcome in their language. "Your leads stop falling through the cracks" beats "I built you a workflow" every time. Sounds like you're building the right way.
1-7 of 7
Dagur Eyjolfsson
3
32points to level up
@dagur-eyjolfsson-5788
I help operators use AI to run better businesses. Less fluff. More real-world execution.

Active 17h ago
Joined Feb 2, 2026
Powered by