Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
Owned by Rob
Learn AI, development, automation & SaaS by building. I’m documenting what I test, learn, break, and figure out along the way.
Skoolers
157.1k members • Free
TCA - The Cold Academy
215 members • Free
AI Lab
1.5k members • Free
Agent Empire
1.7k members • Free
AI Automation Society
459.7k members • Free
AI Automation Agency Hub
334.6k members • Free
33 contributions to AI Automation Agency Hub
21h •
Retainers... my take
A retainer should not be a monthly invoice looking for something to justify itself. There should be a continuing responsibility... monitoring, optimization, support, reporting, improvement or ownership of a business outcome. What makes an automation retainer actually worth paying every month?
1 like • 10h
@Scott Senior hey Scott how are ya?! ;)
2 likes • 10h
@Md Murad Hossain bingo
5d •
Tool churn... curiosity without chaos
I want enough curiosity to spot a better tool... without turning the stack into a weekly science experiment. That's a harder balance than it sounds in AI right now...lol. What's your rule for adopting something new?
2 likes • 4d
@Mouldi Nouri exactly, its all to common where someone starts layering their latest trick over failed or broken things thinking their new tool is solving the bug all the other tools presented.
0 likes • 2d
Reading these replies, I think we're mostly circling the same rule... A new tool should have to earn its way into the stack. But I think there's another cost we don't talk about enough... Every tool you add creates debt. Another login. Another API. Another billing relationship. Another failure point. Another thing somebody has to understand six months from now. Another dependency that may change pricing, break an integration, get acquired, or disappear. So I don't really ask, "Is this tool better?" I ask... "Is it enough better to justify the migration tax AND the new dependency?" That's a much higher bar. I'm perfectly happy testing shiny things in a sandbox... I still love playing with new tech. But production is different. Production doesn't care how cool the demo was. It cares whether the system is still working at 2AM when nobody is watching. And one thing I've learned over a lot of years in tech... Complexity is really easy to add. Removing it later is where you find out what it actually cost you. So maybe my rule is: Experiment aggressively. Adopt conservatively. Standardize ruthlessly. Curiosity should expand your options... not expand your stack.
3d •
Building is getting cheaper... my take
The cost of building software and automations is dropping fast... but deciding what should be built is not becoming a commodity at the same rate. Judgment, diagnosis and ownership are becoming MORE visible as implementation gets easier. If building gets 10x easier from here, what skill becomes 10x more valuable?
1 like • 2d
I think the consensus here is pretty telling... Diagnosis, judgment, prioritization, system design, constraints, measurable outcomes. Notice what almost nobody said? "Building." That may be the real shift. As implementation gets cheaper, the builder is no longer the scarce resource. The scarce resource becomes the person who can walk into a messy business, figure out what is actually broken, separate symptoms from causes, decide what is worth fixing, design the right solution... and sometimes tell the client, "don't build anything." And I think there's one more layer beyond diagnosis... Ownership. It's easy to recommend an automation. It's harder to put your name behind the outcome. Did it save money? Did it make money? Did it reduce risk? Did it remove a constraint? Did the people actually use it? Was it worth doing in the first place? AI can generate 20 possible solutions before lunch. The valuable person may increasingly be the one who knows which 19 to throw away. That skill isn't really "AI consulting." It's business judgment... with AI as one hell of a toolbox.
5d •
Quick question... what made you a faster learner?
What's one habit, tool or mindset that made you noticeably faster at learning new technology?
2 likes • 5d
@Okasha Khan trial by fire are the best lessons ;) lol
2 likes • 3d
@Michael Mark Need to define the roles and the tasks of those roles. If its a sales/SDR/BDR type partner ( and they wont like this) building is far more work more often than selling a deal, however occasionally the build is fast. . I use to pay a sales role 20% commission and they'd make about 250k plus sometimes and a profit share % ( of end of year net profits). I'm not a huge fan of partners in the terms of co-owner/shareholder anymore.. lots of pros and cons. so for me it's profit share deal. Another way is to split Sprint 1 ( the discovery audit ) but you keep the next sprints. and to keep your BDR partners enthusiasm up give a % of the next sprints so long as they are doing the account management and doing it well. but they ends if they leave or don't produce and only applies to deals they brought in and/ormanage. A lot of angles, and it comes down to what you negotiate with them, how much your TRUST them....etc.. ;) Im sure others have different ways they work their deals and its really based on some of the role factors. I've been in a situation where I partnered ( co-own ) and the person didn't do SQUAT! ... To cover that situation in needs to be in your contracts a performance clause, so you can get out of the deal in those types of cases.... trust me - it happens.
7d •
SpaceXAI Team to Build Company Live with Grok Bot in Three Days
This should be interesting... https://x.com/i/trending/2098180902580871445 About Event Can three people build a company in three days? Join the Grok Bot Galaxy livestream to find out. Follow along as Matt Palmer (@mattyp), Lauren Tan (@poteto), and Roshan Sadanani (@roshan_s) set out to build a product from scratch with Grok Bot from Sept. 15 – 17. Starting with an idea and a blank slate, they’ll work through a business plan, feature decisions, and real engineering work to turn a concept into a reality. Over the course of this three-day livestream, you’ll follow their building in real time and will see how Grok Bot fits into each stage of the development process. Throughout the livestream, we’ll also hand off to teammates for department-specific deep dives. From the first line of code to setting customers up for success, you’ll learn how to use Grok Bot for real workflows across every stage of your business, and will walk away with actionable use cases for your function. The livestream runs from 8:30 AM - 6:00 PM every day, with the following guest sessions: Day 1: September 15 - 9:00 - 10:00 AM: Grok Bot 101 - 12:30 - 2:00 PM: Grok Bot for Engineering - 2:30 - 3:30 PM: Grok Bot for Product Managers - 4:00 - 5:30 PM: Grok Bot for Founders Day 2: September 16 - 9:00 - 10:30 AM: Grok Bot for Sales Engineering - 12:30 - 2:00 PM: Grok Bot for Sales - 2:30 - 3:30 PM: Grok Bot for SDRs - 4:00 - 5:00 PM: Grok Bot for Customer Support Day 3: September 17 - 9:00 - 10:30 AM: Grok Bot for Marketing Operations - 12:30 - 1:30 PM: Grok Bot for Post-Sales - 2:30 - 4:00 PM: Grok Bot for Marketing
2 likes • 5d
@Lakshya Pandey I ws going to.. but just too busy at the moment... maybe there will be a replay...but I don't have the time to spend 3 days watching them
2 likes • 4d
@Lakshya Pandey Both.. and in several areas.
1-10 of 33
Active 24m ago
Joined Jul 28, 2024
INTP
Texas
Powered by