
Hi, I'm David & I loveπ. Improving your business. Web Design, Wordpress, SEO, AI, Techno-humanist πͺπΌ #COYS
UK & SF
Joined August 2015
- Tweets22.1K
- Following2.3K
- Followers7K
- Likes80K
Find all of my best articles, guides, and resources in one place.
Visit: mazepress.com/resources/
#blogging #webdesign #wordpress #social
Mazepress πππ»π» retweeted
Making the most AI pilled company is the whole game:
1. make a second brain. one folder of markdown files on how you think, write and decide (obsidian)
2. talk to it. voice notes all day (wispr), and an agent files every fact, story and decision
3. make a company brain. customers, calls, numbers, pricing, playbooks, past decisions and why you made them
4. record every call and meeting (granola). the transcripts go straight into the brain
5. keep a facts file. true things about you and the company that agents are allowed to say. this kills made-up claims
6. keep a voice file. your 50 best posts, 20 you hate, and the words you never use
7. put all of it in git (github) so every change has a history
8. write one instruction file at the top (CLAUDE.md or AGENTS.md). read these files before any task, never overwrite, always date
9. give agents memory across sessions so they stop starting from zero (claude-mem, mem0)
10. pipe every data source into one warehouse your agents can query (airbyte β clickhouse). ads, analytics, CRM, payments
11. feed it data nobody else has. it's the only part a competitor can't download
the skills
12. don't start from zero. install the good ones first (anthropics/skills, obra/superpowers, mattpocock/skills, addyosmani/agent-skills)
13. grab the marketing ones too (coreyhaines31/marketingskills, cody schneider's graphed skills for static ads and UGC, boringmarketing dot com skills)
14. map every workflow in the company and rank them by money made or saved
15. do each one once while talking out loud, and record it
16. have an agent turn the recording into a skill. when to use it, the steps, the checks, the mistakes to avoid
17. one skill per job. small and boring beats one giant prompt
18. connect your tools with MCPs so agents can act and not only advise (gmail, slack, stripe, linear, notion, posthog, supabase)
19. give agents a browser (browser-use, vercel agent-browser, claude in chrome)
20. give agents a computer of their own for the tools with no API (vercel agent-desktop, orgo)
21. give your best skills away in public. it's the new lead magnet
the agents
22. run an orchestrator that never turns off (grok bot, openclaw, hermes). it manages one agent per project, and each of those runs its own sub-agents
23. use coding agents for the building (claude code, codex, cursor, t3, antigravity)
24. wrap them in a harness so they plan, test and remember (ECC, superpowers)
25. manage the whole fleet in one place (paperclip). every agent gets a job, a budget and a log
26. put the skills on triggers (n8n, scheduled tasks). daily, weekly, on every new lead, on every cancellation
27. route your models (openrouter). the expensive one plans and checks (fable 5.2, gemini 4 carbon), the cheap ones do the volume
28. cut the token bill. shorter outputs, smaller tool results (caveman)
29. run a local model for the data that can't leave your machine (gemma 4)
30. track cost per job. if a job costs more than it earns, fix it or kill it
the factory
31. build the line. spec agent β builder agents in parallel (git worktrees) β test agent β reviewer agent β deploy (vercel, railway)
32. design goes through the same line (paper MCP), and a skill strips out anything that looks AI made (unslop)
33. every annoying task in the company becomes an internal tool by the end of the day
34. every customer request becomes a pull request before a human reads it (tstack for the PR workflow)
35. reviewer agents with a named bar. "would the best team in the world ship this?" reject until the answer is yes
36. keep 50 real cases with the right answer. rerun them every time a new model drops and switch to the winner
37. humans approve, own the outcome and talk to customers. that's the 10% you keep
the loop
38. every finished job writes back to the brain. what worked, what failed, what to stop doing
39. support tickets, analytics and social comments flow in every night
40. every friday an agent rewrites the playbooks from the week's results, and you approve the diff
41. every month, rank everything by profit per human hour. kill one thing and double one thing
the growth
42. research with agents before you spend a dollar (perplexity API, last30days skill)
43. outbound runs itself. find the leads, enrich, verify, send (apollo, million verifier, instantly, phantombuster)
44. send prospects finished work in place of a pitch
45. ads run on a loop. an agent writes the creative, publishes through the facebook ads API, kills the losers and scales the winners
46. agents make the creative too. images (nano banana), video (heygen, fal), voice (elevenlabs), music (lyria 3.5, suno)
47. turn every finished job into content. the story, the number, the prompt
48. every customer makes the brain smarter for the next one. that's your network effect
49. once it works, point it at a new niche. same agents, new context
The models are the same for everyone but your context is the only part that's yours.
Acquire as much of it as you can, as fast as you can.
Build loops like this.
This is the whole game, happy playing.
Mazepress πππ»π» retweeted
single biggest thing you can do to improve your agent skills
i create most of my skills with a built in feedback loop now
basically one doc that is read every time the skill runs
whenever i have feedback about the output of the skill it gets added in there
this way my skills self-improve over time
Mazepress πππ»π» retweeted
Some of my top AI business models heading into 2027:
AI concierge: The AI consulting playbook. Master one AI tool, then sell setups to local businesses that don't have time to do it themselves.
Lead gen for agencies: Use AI to find warm leads, then sell them to agencies on a monthly retainer (tools like Grok Bot for scanning dedicated platforms like π).
Digital products: Info products and niche tools, built once and sold at scale.
Growth operator: Run π accounts (or other socials) for busy founders and brands, powered by a team of well-curated AI agents.
Content creation/distribution (the ultimate moat): Document what you learn on π and YT. Your own distribution brings warm traffic to every offer above.
Mazepress πππ»π» retweeted
This goes for all users.. B2B, B2C, Enterprise.
Everyone is lazy, busy and doesn't care about your product until it:
- entertains them
- makes them money
- elevates social status
- gets them promoted
imagine the laziest person you can think of.
if you are building a consumer social app, consider that person as your average user and design accordingly.
your killer feature needs to be on the home screen. if it is a few taps away, consider it non existent.
x users periodically cry for βi wanna see more of my friends on the feedβ yet the βfollowingβ tab is one tap away from βfor youβ tab.
Mazepress πππ»π» retweeted
Claude Fable 5.2 made this 90's toy commercial
Everything you see was made with code. Animated in Python and rendered in Blender
Mazepress πππ»π» retweeted
Every time we have a new model, I run the same simple prompt on all my projects:
"Read this entire project and find everything thatβs broken, inconsistent, inefficient, or no longer needed. Fix what youβre sure about and list the rest for me to review."
highly recommend trying
Mazepress πππ»π» retweeted
give a man a fish and you feed him for a day
teach a man to Claude Code and you financially ruin him with distracting side projects for the rest of his life
Well, I guess I'll be moving all of my clients away from LearnDash.
therepository.email/nexcess-β¦
2
46
Mazepress πππ»π» retweeted
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.
Mazepress πππ»π» retweeted
take my advice and just put this into your Claude.MD or Agents.MD
you will thank me later
Mazepress πππ»π» retweeted
Today, we're shipping real-time graphics.
Using Sol 6.1 Ultrafast we can generate custom overlays, diagrams, and even interactive 3D scenes right on a user's screen, no chat.
It's a new visual interface for AI.
Here's me learning about LLMs + hardware.
Demo:
Mazepress πππ»π» retweeted
Software ate the world, now it's learning to run it. View article


























