One thing we love doing - uplifting @gregisenberg high-energy #Saas growth manifesto into a step-by-step playbook 🔥 📖 #AI#Startup
https://t.co/9oyQoM6adQ
so I just got roasted on reddit for an hour…
these were my favorite comments:
> "maybe you can use some of that revenue to make a platform that actually works consistently"
> “your website builder is actually shitty"
> “I’m moving to Ghost once my annual subscription is up"
I love getting trolled on Reddit, but some of them made great points. a lot of the criticism is fair
I firmly believe that perfect is the enemy of progress
the fastest way to build the best product in the world is to listen to feedback (like those from the AMA) and ship with as most velocity as possible to address it
the good: high shipping velocity leads to constant updates and improvements across the platform. we listen to users feedback and address it faster than any company I know
the bad: when we have 40+ engineers (all remote) shipping dozens of updates per day to the codebase, some things slip through the cracks. all of the major releases get tons of QA and love, but there's unintended consequences with some of the smaller ones
the result: some trolls on reddit trying to keep me honest
there's always room for improvement, and we are investing more into QA and processes than ever before. in fact, the platform today is 1000x more stable and performant than it ever has been (the data backs this up)
what's important is actually listening to feedback rather than running away from it. I didn't have to do an AMA, and I don't have to listen to the trolls ... but it makes us better.
we're still a super young company (4.5 years old) with a whole lot to improve
but I don't take for granted that we had hundreds of people show up to participate in the AMA. the @beehiiv community is real, and I can't wait to show them what's coming next
ps. yes, my reddit name is flyGrandama 🖤
We've built 40+ AI agents and internal tools. The hardest part is Context Creation.
AI runs playbooks and makes judgment calls for you. But without your company's context, you get slop.
Context Creation means extracting the subject matter expertise and playbooks that live in people's heads, not in LLM training data, or even your tools.
As forward deployed engineers (FDEs), we create context and turn it into code. We evaluate the business impact, how it aligns with the dev roadmap, and come up with creative solutions.
We built The FDE Factory to replace ourselves. It drives AI adoption inside our clients' companies by running discovery sessions using prototypes to create context.
Here's how it works:
We put a prototype in front of a stakeholder. The stakeholder gives feedback via voice while they're using or reviewing it.
Then our FDE Factory Agents builds in their expertise in minutes:
> Context Agent reviews the codebase and feedback, extracts the requirements, and creates a spec
> Scope Agent checks the spec against the development roadmap, validates it, and hands it off
> Engineering Agent builds a new feature and wires the integration
> QA Agent runs tests to prove to itself it works
> PR merges, feature goes live, product updates itself in real time
It's like the nontechnical stakeholder wrote the code without even knowing it.
Coding agents are great at turning good development plans into code, and they're getting better at turning context into good development plans in collaboration with professional engineers.
But nontechnical people are capped on what they can build without product people and engineers.
The bridge that takes nontechnical people from vibe coding basic apps to building production AI tools that run on first party context is FDEs. Our new FDE Factory gives you the system to go from idea to production.
Context Creation is the first and most important step in our FDE lifecycle, and we just automated it.
Now clients get the right agents and tools built for them, customized to their unique business and encoded with their expertise.
PS: If you're building AI agents within your company, reply "Playbook" and I'll DM you the entire FDE playbook we've run with 30+ companies. It covers finding high-impact AI use cases, building them, and deploying them across the org.
I wish Slack was:
- Agent-first
- Beautiful to use
- Integrated with agents natively so your Hermes or OpenClaw lives inside it
- Huddles worked seamlessly and were fun
- Built for teams of 1-3, not just teams of 300
- Truly a second brain similar to Obsidian
- Searchable without wanting to throw your laptop
- Designed around async, not constant interruption
- Voice first for mobile
- A place where I could see who's working on what right now without asking anyone
- Smart enough to know the difference between "I need you right now" and "whenever you get to this"
- A workspace where my agent could tap someone else's agent on the shoulder and coordinate without involving either human
- Designed so the new hire on day 1 has the same context as the person who's been there 3 years
-Something that felt like walking into a room of people building, not walking into a room of people typing
- A place where decisions are first-class objects
- Able to auto generate SOPs, skills, agents etc from conversation history
- Something that rewards deep work instead of punishing it with 47 unread notifications
🧱 I read an 80-page report from Tencent Research Institute on "Super Individuals" — based on field research across Anthropic, Block, Kimi, Anker & dozens of AI-native teams.
88% of orgs say they've adopted AI. Only 1% consider themselves AI-mature.
The gap isn't tools — it's that nobody redesigned the org.
10 counter-consensus lessons I took away 🧵
Stripe is now live in Zite.
You can build apps that take payments, manage subscriptions, and keep commerce data connected to the rest of your business.
A few things this unlocks:
One-off checkout for products, services, bookings, and deposits.
Subscriptions for memberships, plans, trials, and ongoing services.
Dashboards and portals powered by Stripe customers, subscription status, renewal dates, and access rules.
Available on all plans at zite dot com
Zite apps now connect to the Google tools you use every day.
Three new integrations: Gmail, Drive, and Analytics.
Send and read mail through a connected Gmail account
Save and pull files from a Google Drive folder
Track page views, signups, and conversions in Google Analytics
All 1 click integrations without the need to manage API keys.
Live now at zite dot com
A beautiful soul supported Screenforge today and left me this message.
I don’t usually know how to react to things like this except with a genuine thank you.
Screenforge is free, there is no expectation to support it, and nobody owes me anything. So when someone still goes out of their way to do it, it genuinely means a lot.
Afham, thank you brother ❤️
Support like this is more than just a donation. It is encouragement, kindness, and a reminder that people value the countless hours that go into building something for others.
My heart genuinely goes out to you.
@zite now integrates with Notion and Mailchimp
Build apps on top of your existing @NotionHQ pages and databases
Sync contacts to your Mailchimp audiences and trigger email or SMS messages from your Zite app
Live now at zite dot com
New in Zite ✨ Webhooks
Any tool that sends webhooks can now kick off a Zite workflow.
Stripe charges, GitHub events, calendar bookings, billing updates, automation triggers or even a Fillout form!
Zite generates a unique webhook per workflow and helps with the setup.
Available on all plans at zite dot com
Scheduled Workflows just landed in @zite
Now your apps can run background automations
Set up recurring jobs once: reports, digests, reminders, cleanups
Or let users trigger one-time schedules directly from inside the app
Build it once. Your app keeps working, even when you’re not
That's not a dashboard. That's an org chart.
He used to pay $15,000/month in salaries. Now he doesn't.
42 AI agents. One canvas. Hundreds of thousands worth of employees, without a single salary.
The researcher passes context to the email writer. The call analyst feeds the follow-up drafter. They talk to each other. They compound.
That's not 42 separate chatbots. That's an org chart that runs itself.
A 10-person ops team costs more than $15,000/month.
Lead qualification. Support. Invoices. Reports. Content. Competitor intel. Meeting prep.
All automated. All running while he builds the next department.
He's on day one of the world's first AI workforce.
Most businesses are still on day one of hiring humans to do what this canvas already does.
@jacobgrowth Won’t be long before shirt sponsors / logos will ‘change’ - depending on where you watch the game. Already done it with perimeter ad boards.
Chance could be alt sponsor, or different branded msgs.
@zite I find this feature powerful - because it often siggests options you’d not considered and are well worth testing. Plus the messaging provides sensible approaches and guardrails from “over/buulding” too much at once.