building in public, part 2. last time i told you we had zero paying customers. now we have one! I've seen somewhere the "distance" between 0 -> 1 -> 10 -> 100 -> 1000 is the same, do you agree?
the funny part: it didn't come from google ads. the first customer found us through a video on my channel about web3. we spent weeks tuning ads and the sale came from youtube. interesting.
a few things we changed before it happened.
price. we ran a black friday campaign with a cheaper price. maybe that was it, maybe not. we don't know yet.
landing page headline. 16% of visitors open a free lesson now, it was 8.4%. we're 5 days into a 7 day test, so i wouldn't trust it yet.
who is clicking. you told me to talk to the people who drop off, so we added a few questions inside the first lesson to learn who they are.
one sale proves nothing. we changed price and headline at the same time, so i can't say which one helped. the headline is its own experiment now.
full video (in portuguese): https://t.co/2qkhxlMHE0
@readfoundedco sure jay! yes, i'm curious about that as well. i have some hypothesis in mind, but want to calm this same mind as "a builder wanna build" however sometimes we forgot to sell! i guess iterahq is a good product, so i'll keep talking to myself: dont lose focus.
building in public, part 2. last time i told you we had zero paying customers. now we have one! I've seen somewhere the "distance" between 0 -> 1 -> 10 -> 100 -> 1000 is the same, do you agree?
the funny part: it didn't come from google ads. the first customer found us through a video on my channel about web3. we spent weeks tuning ads and the sale came from youtube. interesting.
a few things we changed before it happened.
price. we ran a black friday campaign with a cheaper price. maybe that was it, maybe not. we don't know yet.
landing page headline. 16% of visitors open a free lesson now, it was 8.4%. we're 5 days into a 7 day test, so i wouldn't trust it yet.
who is clicking. you told me to talk to the people who drop off, so we added a few questions inside the first lesson to learn who they are.
one sale proves nothing. we changed price and headline at the same time, so i can't say which one helped. the headline is its own experiment now.
full video (in portuguese): https://t.co/2qkhxlMHE0
@HeyEthanLiu@vibe_metrics perfect ethan, will keep that in mind. one doubt i have is about testing other "branches" in parallel, like testing other kind of content combined with different ads or maybe a different ICP. what do you think about it?
@PrinceOwems thanks prince! yes, we're tracking the users with tools like umami ans clarity and reviewing the recording every day to refresh our hypothesis
@mohabbuilds the old one was like focused in the method (microlearning) while the new one is focused on the transformation: "become a professional developer quicker". hookie mistake but yes, we're learning
@vibe_metrics correct, will double the bet on youtube. regarding the experiments, we're not spending a lot (like 50 bucks a month), so it was that or slowing the whole process. any tips?
@vincent_koc cool vincent I'm playing with it as well. are you balancing/routing tasks that need frontier models with the ones that dont? I' trying to explore this now and would like to know your experience
good summary, 50 items, 1 prompt to start and some years to acquire the knowledge.
i've explored most of this, pending the loop engineering part.
for one-man-bands it's much easier to implement than real companies with culture, processes and people with diverse points of view. at the end, team that can adapt to it succesfully will win.
as the op said, happy playing!
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.
last one from the advices i have for anyone getting into blockchain: be a user first. that's how i started.
put 10 or 50 dollars on chain. install a wallet. make a swap on uniswap. go to events, join the discord of the companies in the ecosystem, help people with their questions.
the market wants devs who understand the ecosystem, not just the code.