CEO at Unlayer, Mailmunch. Entrepreneur, Software Engineer.
San Francisco, CA
Joined March 2009
- Tweets376
- Following351
- Followers551
- Likes152
Pinned Tweet
Most teams underestimate how much work goes into "just adding an editor."
It quickly becomes builders, templates, rendering, permissions, storage, personalization, and now AI.
That’s what we’re solving with Unlayer.
Excited to launch on @ycombinator today 🚀
Most products eventually need users to create content.
Emails. Pages. Documents. Templates. PDFs.
What starts as "just add an editor" quickly becomes a full content creation stack.
Today we’re launching Unlayer on @ycombinator: AI-powered content creation infrastructure for apps.
Watch the video and upvote us here 👇
ycombinator.com/launches/QkK…
Adeel Raza retweeted
We asked the AI to send a follow-up.
It promised 12 new features.
The demo starts in 6 minutes.
Engineering was not consulted.
What’s the wildest thing sales has promised on your behalf? 👇
Great interview. So much to learn from @haroon on entrepreneurship and scaling.
youtu.be/K9pTzZx7Yts?si=A50J…
Adeel Raza retweeted
Turns out there are a lot of incredibly talented builders out there.
We knew that already, but the Build With Elements Challenge gave us a chance to see it first hand.
Over the past few weeks we've seen builders create some incredibly creative projects, all using Elements in ways we hadn't even imagined.
The range of ideas, attention to detail, and overall quality of the submissions made choosing just three winners a genuinely difficult task.
To everyone who participated, explored Elements, shared feedback, or simply gave the project a chance, thank you. We genuinely appreciate the support.
With that said, here are the three winning projects and the talented builders behind them 👇🏻
Adeel Raza retweeted
a random dm turned into a weekend side project
thanks @RicoDC95
built this using @unlayer:
3 business docs, 1 data object each, 9 renders (email + web + pdf).
every chart, qr code and stamp is hand-drawn in html tables. zero images, zero fonts, zero cdn, zero js.
ci actually screenshots the qr codes and decodes the pixels to prove they scan.
live: asterix-elements-kit.vercel.…
code: github.com/adityasarade/aste…
#BuiltWithElements
This is awesome!
Built REWIND with @unlayer Elements. 🏃♂️
It's a running year-in-review that renders as:
✉️ Email
🌐 Live web page
📄 Print-ready PDF
...all from a single React component tree.
My favorite part is renderToJson(). It outputs the exact JSON consumed by the Elements editor, so templates built entirely in code can be opened, edited, and customized by non-developers in a real WYSIWYG experience. I even round-tripped the generated output through the live editor to prove it.
The template is also data-driven. A deterministic engine analyzes your running activity and automatically changes the story:
• Hot streak → Heatmap
• Big comeback → Trend chart
• Long run → Route highlight
Same template. Different story for every runner.
Huge thanks to @unlayer and @adeelraza for building such an impressive SDK.
GitHub + live demo in the first comment.
#BuiltWithElements
Adeel Raza retweeted
Built REWIND with @unlayer Elements. 🏃♂️
It's a running year-in-review that renders as:
✉️ Email
🌐 Live web page
📄 Print-ready PDF
...all from a single React component tree.
My favorite part is renderToJson(). It outputs the exact JSON consumed by the Elements editor, so templates built entirely in code can be opened, edited, and customized by non-developers in a real WYSIWYG experience. I even round-tripped the generated output through the live editor to prove it.
The template is also data-driven. A deterministic engine analyzes your running activity and automatically changes the story:
• Hot streak → Heatmap
• Big comeback → Trend chart
• Long run → Route highlight
Same template. Different story for every runner.
Huge thanks to @unlayer and @adeelraza for building such an impressive SDK.
GitHub + live demo in the first comment.
#BuiltWithElements
Plot twist: AI didn't learn to write like humans. Humans learned to write like AI.
Someone called my launch copy "AI-written."
I wrote it. 😭
Adeel Raza retweeted
Introducing the Proof Built with Unlayer Elements
Proof is a multi-product studio that lets you compose once and render everywhere.
As a developer, building the same thing three times never made sense to me.
An email template. A web page. A PDF.
Three different templates, layouts to break
So I built Proof.
One JSON → Every channel.
🔗: proof-elements.vercel.app/
It comes with three studios:
-> ProofFolio — Career Kit
Recruiter emails, portfolio pages, resumes, and certificates.
-> ProofCampaign — Launch Kit
Campaign emails, archive pages, and one-pagers.
-> ProofInvoice — Billing Kit
Invoice emails, web invoices, and printable PDFs.
Manage everything in one place with a single JSON file.
@unlayer #BuiltWithElements
Unlayer is live on @hackernews
We were part of W22 @ycombinator, so this is a late HN launch.
At the time, Unlayer was an embeddable email editor, and we did not think we had the right broader story for HN yet.
Since then, the product has expanded into a more general content creation layer for products, including emails, pages, documents, APIs, open-source developer projects, and AI-assisted workflows.
This feels like a better moment to bring it to HN and ask for feedback.
We operate in one of those areas where a lot of people have strong opinions because they have been burned by editors, email HTML, document editing, or simple content workflows before.
We would love to hear what resonates, what sounds wrong, and what you think we should be thinking harder about.
Join the conversation and weigh in: news.ycombinator.com
Adeel Raza retweeted
This was an interesting experiment.
Took one of my old threads and turned it into an actual email newsletter using post.email.
I never expected it to be that good, but the result is awesome. I would say 80-90% job is done. In fact I can edit and add whatever I want.
Feels like the easiest way to build an email list from content you've already written.
🤝 Paid partnership
🚀 Introducing post.email
Paste any X post or thread.
It instantly becomes a beautiful, fully editable email newsletter.
No prompts.
No starting from a blank page.
Just your content, ready for the inbox.
Perfect for creators, founders, marketers, and anyone building an audience beyond the algorithm.
Try it: post.email
Show me your favorite X post, and I'll turn it into a newsletter.
Adeel Raza retweeted
I NEVER REPURPOSE MY X POSTS. TOO MUCH WORK.
tried post.email today
pasted in one of my threads.
it came out as a clean, formatted newsletter.
→ headers stayed
→ line breaks stayed
→ barely touched it
if you already write on X, your email list is basically already written.
you just haven't moved it yet.
🤝 Paid partnership
🚀 Introducing post.email
Paste any X post or thread.
It instantly becomes a beautiful, fully editable email newsletter.
No prompts.
No starting from a blank page.
Just your content, ready for the inbox.
Perfect for creators, founders, marketers, and anyone building an audience beyond the algorithm.
Try it: post.email
Show me your favorite X post, and I'll turn it into a newsletter.
🚀 Introducing post.email
Paste any X post or thread.
It instantly becomes a beautiful, fully editable email newsletter.
No prompts.
No starting from a blank page.
Just your content, ready for the inbox.
Perfect for creators, founders, marketers, and anyone building an audience beyond the algorithm.
Try it: post.email
Show me your favorite X post, and I'll turn it into a newsletter.
A lot of people already write their best content on X.
Writing the newsletter afterward feels like doing the same work twice.
That is the problem post.email solves.
We've spent years watching teams rebuild the same content stack again and again.
Emails. Pages. PDFs. Templates.
Now AI agents are going to hit the same problem even faster.
That’s why we’re open sourcing Elements. React primitives for content creation.
Introducing Unlayer Elements
The open-source React content layer for developers and AI agents to create emails, web pages, and PDFs from the same codebase.
Write once. Render everywhere.
Build emails, landing pages, invoices, reports, documents, templates, previews, and exports with one shared component system.
GitHub: github.com/unlayer/elements
We’d love any feedback you might have.
Read on for a deep dive 👇🏻
⚽ My GitHub season as a player card: BRONZE tier, 58 OVR - “El Deployador”
Check it out: githubfc.com/adeelraza
Swap github.com to githubfc.com to get your scorecard.
I stopped asking Claude to write code this week.
Instead, I asked it to simulate support tickets.
Example:
"Generate 50 angry customer tickets from developers integrating @unlayer SDK."
The output is gold.
You immediately discover:
- confusing APIs
- poor docs
- missing callbacks
- terrible naming
- onboarding gaps
We've found product improvements this way that never came up in user interviews.
Turns out Fable is an incredible QA engineer if you ask the right question.
