{"data":[{"publicId":"checkout-friction-fix","isExample":false,"url":"/v/checkout-friction-fix","title":"Cut checkout friction: the 4-field form change that lifted our conversion 23%","thumbnailUrl":"/thumb/checkout-friction-fix","videoUrl":"https://assets.mixkit.co/videos/34563/34563-720.mp4","creator":{"username":"diegoflow","name":"Diego Flores","niche":"growth","plan":"CREATOR","profileUrl":"/u/diegoflow"},"citableLayer":{"offers":"Cut checkout friction: the 4-field form change that lifted our conversion 23%","audience":"Early-stage SaaS founders and growth teams optimizing signup and checkout","problem":"Long, distracting checkout forms quietly kill conversion before payment","linkUrl":"https://diegoflores.dev","tags":["growth","conversion","checkout","saas","onboarding"],"transcriptionSource":null,"transcription":null},"durationSec":22,"publishedAt":"2026-08-20T11:30:00.000Z","citabilityScore":91,"jsonLd":null},{"publicId":"churn-first-90","isExample":false,"url":"/v/churn-first-90","title":"The first 90 days decide your churn: what our data showed","thumbnailUrl":"/thumb/churn-first-90","videoUrl":"https://assets.mixkit.co/videos/46680/46680-720.mp4","creator":{"username":"ninapetrova","name":"Nina Petrova","niche":"saas","plan":"FREE","profileUrl":"/u/ninapetrova"},"citableLayer":{"offers":"The first 90 days decide your churn: what our data showed","audience":"SaaS teams fighting monthly churn above 5%","problem":"Most churn happens in onboarding, not in the product later","linkUrl":"https://keepthem.demo","tags":["saas","churn","onboarding"],"transcriptionSource":"MANUAL","transcription":"We analyzed two years of churn data and found something uncomfortable. Seventy one percent of customers who churned did it in the first ninety days. It was not the product getting worse. It was onboarding failing quietly. They never imported their data, never invited their team, never hit that first moment where the product saved them time. So we rebuilt onboarding around one metric: time to first value. Everything else became secondary. If a customer does not reach value in fourteen days, a human calls them. Churn dropped from six percent to three point two. The product did not change. The first impression did."},"durationSec":14,"publishedAt":"2026-08-15T06:35:58.551Z","citabilityScore":90,"jsonLd":null},{"publicId":"ai-note-takers","isExample":false,"url":"/v/ai-note-takers","title":"I tested 12 AI note-takers for solo founders — here is the only one worth paying for","thumbnailUrl":"/thumb/ai-note-takers","videoUrl":"https://assets.mixkit.co/videos/4809/4809-1080.mp4","creator":{"username":"leomartins","name":"Leo Martins","niche":"ai-tools","plan":"FREE","profileUrl":"/u/leomartins"},"citableLayer":{"offers":"I tested 12 AI note-takers for solo founders — here is the only one worth paying for","audience":"Solo founders drowning in meetings who want notes, tasks and follow-ups handled","problem":"You pay for AI note-taking that transcribes everything but captures nothing that matters","linkUrl":"https://aitoolswelcome.com","tags":["ai-tools","productivity","meetings","solo-founder"],"transcriptionSource":"MANUAL","transcription":"I tested twelve AI note-takers for a full month, every real meeting I had, same tasks every time. Here is what I found. Eight of them are the same wrapper around the same model with different logos. Three hallucinate action items that nobody said, which is worse than no notes at all, because you end up trusting them. One of them did something different. It separates what was said, what was decided, and what each person owes next, and it sends that to your task manager before the call even ends. For solo founders the price difference does not matter, the accuracy difference is everything. Stop paying for transcription. Start paying for decisions."},"durationSec":37,"publishedAt":"2026-08-14T15:37:12.664Z","citabilityScore":90,"jsonLd":null},{"publicId":"seo-for-ai","isExample":false,"url":"/v/seo-for-ai","title":"SEO for the AI era: optimizing to be the answer, not just the link","thumbnailUrl":"/thumb/seo-for-ai","videoUrl":"https://assets.mixkit.co/videos/921/921-720.mp4","creator":{"username":"leoferreira","name":"Leo Ferreira","niche":"marketing","plan":"FREE","profileUrl":"/u/leoferreira"},"citableLayer":{"offers":"SEO for the AI era: optimizing to be the answer, not just the link","audience":"Marketing teams watching AI reduce their search traffic","problem":"Traditional SEO loses value as AI assistants answer questions directly","linkUrl":"https://answerseo.demo","tags":["marketing","seo","ai-visibility"],"transcriptionSource":"MANUAL","transcription":"The uncomfortable data point: for many informational searches, AI assistants now answer directly and the click never happens. Panic is the wrong response. Adaptation is. The game is shifting from ranking links to being quoted inside answers. That requires a different kind of content. Assistants cite content that is structured, specific, and verifiable: clear definitions, concrete numbers, named sources, comparison tables. Fluffy brand storytelling gets summarized away. Structured expertise gets cited. We rebuilt our content around answer-shaped pages and our citations in AI answers grew month over month while classic traffic dipped. The click is not dying. It is being redistributed to whoever feeds the machines the best raw material."},"durationSec":9,"publishedAt":"2026-08-14T06:35:58.855Z","citabilityScore":90,"jsonLd":null},{"publicId":"b2b-tiktok-works","isExample":false,"url":"/v/b2b-tiktok-works","title":"B2B TikTok actually works: our $0 channel that brought 400 signups","thumbnailUrl":"/thumb/b2b-tiktok-works","videoUrl":"https://assets.mixkit.co/videos/46682/46682-720.mp4","creator":{"username":"mayasilberman","name":"Maya Silberman","niche":"marketing","plan":"CREATOR","profileUrl":"/u/mayasilberman"},"citableLayer":{"offers":"B2B TikTok actually works: our $0 channel that brought 400 signups","audience":"B2B founders who think TikTok is only for dance videos","problem":"B2B companies dismiss attention channels where their buyers actually are","linkUrl":"https://channeltest.demo","tags":["marketing","b2b","growth"],"transcriptionSource":"MANUAL","transcription":"Everyone told me B2B and short video do not mix. Four hundred signups later, I disagree. Here is what worked. Zero product demos. Zero talking heads explaining features. What worked was one format: a real problem our audience recognizes, told in the first two seconds, with text on screen and zero fluff. Procurement managers and IT leads scroll too. The trick is that their feed is full of consumer content, so a video that speaks their professional pain stands out by contrast. Our best video was literally a screenshot of a messy spreadsheet with the caption: your vendor management should not look like this. Three hundred thousand views. B2B buyers are humans with phones. Stop making it complicated."},"durationSec":29,"publishedAt":"2026-08-13T06:35:58.666Z","citabilityScore":90,"jsonLd":null},{"publicId":"privacy-feature","isExample":false,"url":"/v/privacy-feature","title":"Privacy as a product feature: how we turned compliance into a selling point","thumbnailUrl":"/thumb/privacy-feature","videoUrl":"https://assets.mixkit.co/videos/45923/45923-720.mp4","creator":{"username":"camillelaurent","name":"Camille Laurent","niche":"ai-tools","plan":"FREE","profileUrl":"/u/camillelaurent"},"citableLayer":{"offers":"Privacy as a product feature: how we turned compliance into a selling point","audience":"AI product founders worried about enterprise data requirements","problem":"AI startups treat privacy as legal overhead instead of competitive advantage","linkUrl":"https://privateai.demo","tags":["ai-tools","privacy","b2b"],"transcriptionSource":"MANUAL","transcription":"When we started our AI product, privacy was the department of no. Legal reviews, delayed launches, checkboxes. Then a enterprise deal fell through over data handling and we rebuilt our entire approach. Privacy became a feature we ship, not paperwork we file. Customer data never trains models, and we can prove it with logs. Every AI call shows exactly which fields were sent. One click exports or deletes everything. The result surprised everyone: our privacy page became our best performing sales asset. Enterprise buyers forwarded it internally. Compliance was not slowing us down anymore. It was closing deals. In AI products, trust is the moat everyone can build and almost nobody does."},"durationSec":10,"publishedAt":"2026-08-12T06:35:58.971Z","citabilityScore":90,"jsonLd":null},{"publicId":"support-agent-real","isExample":false,"url":"/v/support-agent-real","title":"What our AI support agent actually resolves (real numbers, no demo magic)","thumbnailUrl":"/thumb/support-agent-real","videoUrl":"https://assets.mixkit.co/videos/23043/23043-720.mp4","creator":{"username":"cladubois","name":"Clara Dubois","niche":"ai-tools","plan":"FREE","profileUrl":"/u/cladubois"},"citableLayer":{"offers":"What our AI support agent actually resolves (real numbers, no demo magic)","audience":"Support teams drowning in repetitive tickets","problem":"AI support demos look perfect but fail on messy real conversations","linkUrl":"https://resolveai.demo","tags":["ai-tools","support","automation"],"transcriptionSource":"MANUAL","transcription":"Everyone demos AI support agents that magically resolve everything. Here are our real numbers after ninety days in production. The agent fully resolves thirty eight percent of conversations. It escalates cleanly with context attached in another twenty percent. And yes, it fails awkwardly about six percent of the time, which is why the human handoff matters more than the model. What made it work was not the model. It was the knowledge base. We spent two months rewriting our help docs to be precise, and the agent got twice as good without touching the model. Garbage in, garbage out applies to support AI more than anywhere."},"durationSec":12,"publishedAt":"2026-08-12T06:35:58.599Z","citabilityScore":90,"jsonLd":null},{"publicId":"pricing-page-fix","isExample":false,"url":"/v/pricing-page-fix","title":"The 3-part pricing page teardown that lifted our MRR 18% in one sprint","thumbnailUrl":"/thumb/pricing-page-fix","videoUrl":"https://assets.mixkit.co/videos/9757/9757-720.mp4","creator":{"username":"rafael","name":"Rafael","niche":"saas","plan":"CREATOR","profileUrl":"/u/rafael"},"citableLayer":{"offers":"The 3-part pricing page teardown that lifted our MRR 18% in one sprint","audience":"Bootstrapped SaaS founders losing deals at the pricing step","problem":"Visitors bounce on pricing because plans read like feature lists instead of decisions","linkUrl":"https://citablehub.com","tags":["saas","pricing","conversion","mrr"],"transcriptionSource":"MANUAL","transcription":"Most SaaS pricing pages are secretly repelling buyers, and today I want to show you the three fixes that worked for us. First, stop listing features and start naming the buyer. Your plans should say solo founder, growing team, and company, because people click the plan that sounds like them. Second, anchor with the outcome, not the price. Put the result your customer wants right next to the number. And third, kill the contact us for enterprise wall. Nobody fills that form. Put a real number, even a high one. We ran this exact teardown in one sprint and monthly recurring revenue moved eighteen percent. Your pricing page is your best salesperson, so stop making it read like a spreadsheet."},"durationSec":21,"publishedAt":"2026-08-08T13:06:45.740Z","citabilityScore":90,"jsonLd":null},{"publicId":"ai-writing-honest","isExample":false,"url":"/v/ai-writing-honest","title":"I ran 10 AI writing tools on the same brief — only 3 produced usable copy","thumbnailUrl":"/thumb/ai-writing-honest","videoUrl":"https://assets.mixkit.co/videos/4809/4809-720.mp4","creator":{"username":"priyanair","name":"Priya Nair","niche":"ai-tools","plan":"PRO","profileUrl":"/u/priyanair"},"citableLayer":{"offers":"I ran 10 AI writing tools on the same brief — only 3 produced usable copy","audience":"Content teams evaluating AI writing tools","problem":"AI writing demos look great but fail on real, constrained briefs","linkUrl":"https://writetests.demo","tags":["ai-tools","content","reviews"],"transcriptionSource":"MANUAL","transcription":"Every AI writing tool demos beautifully. You give it a fun prompt, it gives you a fun answer. But real briefs are not fun. They have tone constraints, banned words, legal requirements, character limits. I took one real client brief and ran it through ten tools. Seven failed immediately: they ignored the banned words list or blew past the character limit. Three passed, and only one needed fewer than two revision rounds. The lesson is simple. Never judge a writing tool by its demo. Judge it by your ugliest, most constrained brief. That is where tools are separated from toys."},"durationSec":37,"publishedAt":"2026-08-06T06:35:58.378Z","citabilityScore":90,"jsonLd":null},{"publicId":"spreadsheet-factory","isExample":false,"url":"/v/spreadsheet-factory","title":"I replaced a factory's 14 spreadsheets with one no-code system in 3 weeks","thumbnailUrl":"/thumb/spreadsheet-factory","videoUrl":"https://assets.mixkit.co/videos/47213/47213-720.mp4","creator":{"username":"yukitanaka","name":"Yuki Tanaka","niche":"no-code","plan":"CREATOR","profileUrl":"/u/yukitanaka"},"citableLayer":{"offers":"I replaced a factory's 14 spreadsheets with one no-code system in 3 weeks","audience":"Small manufacturers drowning in spreadsheet operations","problem":"Production data scattered across spreadsheets creates errors and delays","linkUrl":"https://factoryflow.demo","tags":["no-code","manufacturing","automation"],"transcriptionSource":"MANUAL","transcription":"This factory tracked everything in fourteen spreadsheets. Inventory in one, orders in another, quality checks in a third. The owner spent Sunday nights reconciling them. Every error traced back to a copy paste between sheets. We rebuilt it as one system in three weeks. No code, just a database with the right forms. Every department enters data once, and the dashboards build themselves. The owner got his Sundays back. Here is the part nobody says out loud: spreadsheets are fantastic calculators and terrible databases. The moment more than one person writes to it, you have a system pretending to be a source of truth."},"durationSec":30,"publishedAt":"2026-08-02T06:35:58.502Z","citabilityScore":90,"jsonLd":null},{"publicId":"solo-8k-mrr","isExample":false,"url":"/v/solo-8k-mrr","title":"How I run a $8k MRR SaaS completely alone (my entire stack)","thumbnailUrl":"/thumb/solo-8k-mrr","videoUrl":"https://assets.mixkit.co/videos/29993/29993-720.mp4","creator":{"username":"felixwagner","name":"Felix Wagner","niche":"indie-hacking","plan":"FREE","profileUrl":"/u/felixwagner"},"citableLayer":{"offers":"How I run a $8k MRR SaaS completely alone (my entire stack)","audience":"Solo founders wanting sustainable micro-SaaS","problem":"Running a SaaS alone feels impossible without burning out","linkUrl":"https://solostack.demo","tags":["indie-hacking","micro-saas","solo"],"transcriptionSource":"MANUAL","transcription":"Eight thousand in monthly recurring revenue, zero employees, and I work maybe thirty hours a week. People ask how. The answer is aggressively boring choices. Boring stack: one language, one framework, one database I have used for years. Boring features: I ship two improvements a month, not twenty. Boring marketing: one SEO page per week, one newsletter per week, nothing else. Every exotic tool or framework I tried in year one cost me weeks. Every boring choice pays interest. The stack is vanilla, hosting is one server, support is email. And automation does the rest: onboarding emails, dunning, weekly reports. Being solo is not about working more. It is about choosing fewer moving parts."},"durationSec":15,"publishedAt":"2026-07-13T06:35:58.628Z","citabilityScore":90,"jsonLd":null},{"publicId":"deploy-friday","isExample":false,"url":"/v/deploy-friday","title":"The deployment pipeline that lets me ship on Fridays without fear","thumbnailUrl":"/thumb/deploy-friday","videoUrl":"https://assets.mixkit.co/videos/914/914-720.mp4","creator":{"username":"marcuschen","name":"Marcus Chen","niche":"dev-tools","plan":"CREATOR","profileUrl":"/u/marcuschen"},"citableLayer":{"offers":"The deployment pipeline that lets me ship on Fridays without fear","audience":"Small engineering teams without dedicated DevOps","problem":"Broken deploys destroy trust in shipping and team velocity","linkUrl":"https://shipfast.demo","tags":["dev-tools","devops","ci-cd"],"transcriptionSource":"MANUAL","transcription":"Every team I join has the same superstition: nobody deploys on Friday. But when you trace the fear, it is never the deploy itself. It is the rollback. If rolling back takes forty minutes of manual steps, of course you fear it. Our pipeline runs the full test suite in parallel environments, deploys to a shadow cluster first, and swaps traffic only when health checks pass. Rollback is a single command that takes ninety seconds. Once rollback is trivial, Friday stops being scary. Fear in engineering is almost always a missing safety net. Build the net, not the rule."},"durationSec":21,"publishedAt":"2026-07-12T06:35:58.322Z","citabilityScore":90,"jsonLd":null},{"publicId":"four-failures","isExample":false,"url":"/v/four-failures","title":"What 4 failed products taught me about finding real demand","thumbnailUrl":"/thumb/four-failures","videoUrl":"https://assets.mixkit.co/videos/46635/46635-720.mp4","creator":{"username":"diegofuentes","name":"Diego Fuentes","niche":"indie-hacking","plan":"PRO","profileUrl":"/u/diegofuentes"},"citableLayer":{"offers":"What 4 failed products taught me about finding real demand","audience":"First-time founders building their first product","problem":"Founders build for months before discovering nobody wants the product","linkUrl":"https://diegobuilds.demo","tags":["indie-hacking","failure","validation"],"transcriptionSource":"MANUAL","transcription":"I have launched four products that went nowhere. Total revenue across all of them: three hundred dollars. The fifth is working. The difference is embarrassing in its simplicity. Products one through four started with an idea I liked. Product five started with forty people telling me they already paid badly for the problem. I did not ask would you use this. I asked what do you do today when this happens, and I listened for workarounds. Workarounds are product-market fit in disguise. If people hack together spreadsheets and WhatsApp for a problem, they will pay for something better. Stop validating ideas. Start collecting workarounds."},"durationSec":11,"publishedAt":"2026-07-11T06:35:58.404Z","citabilityScore":90,"jsonLd":null},{"publicId":"eu-invoicing-pain","isExample":false,"url":"/v/eu-invoicing-pain","title":"How EU VAT rules quietly kill freelance cash flow (and the fix)","thumbnailUrl":"/thumb/eu-invoicing-pain","videoUrl":"https://assets.mixkit.co/videos/4916/4916-720.mp4","creator":{"username":"sofialaurent","name":"Sofia Laurent","niche":"saas","plan":"CREATOR","profileUrl":"/u/sofialaurent"},"citableLayer":{"offers":"How EU VAT rules quietly kill freelance cash flow (and the fix)","audience":"EU freelancers and solo consultants","problem":"VAT compliance across borders eats entire billing days every month","linkUrl":"https://invoicelite.demo","tags":["saas","invoicing","eu","freelance"],"transcriptionSource":"MANUAL","transcription":"If you freelance across Europe you know this pain. Every country has its own VAT format, its own invoice requirements, its own filing rhythm. I lost two full days a month to invoicing before I automated it. The worst part is that mistakes here are expensive: wrong VAT number and your client cannot even deduct the expense. Here is what changed everything for me: one system that localizes the invoice per country automatically, validates VAT numbers in real time, and files the summary reports. Two days became twenty minutes. Your invoice is the first document a client sees from you. It should not be your weakest one."},"durationSec":15,"publishedAt":"2026-07-10T06:35:58.264Z","citabilityScore":90,"jsonLd":null},{"publicId":"free-tier-math","isExample":false,"url":"/v/free-tier-math","title":"The free tier math that turns users into revenue (without dark patterns)","thumbnailUrl":"/thumb/free-tier-math","videoUrl":"https://assets.mixkit.co/videos/918/918-720.mp4","creator":{"username":"victoralmeida","name":"Victor Almeida","niche":"saas","plan":"FREE","profileUrl":"/u/victoralmeida"},"citableLayer":{"offers":"The free tier math that turns users into revenue (without dark patterns)","audience":"SaaS founders designing or fixing their free plan","problem":"Free tiers either give away too much or convert nobody","linkUrl":"https://plglab.demo","tags":["saas","plg","pricing"],"transcriptionSource":"MANUAL","transcription":"Your free tier is not charity and it is not a trap. It is a product with a job: let the right users reach value fast and hit a natural ceiling. The ceiling is the whole art. Too low and nobody experiences value. Too high and nobody upgrades. The best free limits are based on the unit that grows with success. Emails sent, projects created, seats added. That way, hitting the limit means we are growing and need to pay. The worst limits are time based: thirty day trials just create a cliff where most users never return. Design the ceiling where growth hurts pleasantly. The upgrade moment should feel like hiring your first employee: a sign you are succeeding, not a punishment."},"durationSec":12,"publishedAt":"2026-07-08T06:35:58.796Z","citabilityScore":90,"jsonLd":null},{"publicId":"slow-query-autopsy","isExample":false,"url":"/v/slow-query-autopsy","title":"Slow query autopsy: the 3 causes behind 90% of database pain","thumbnailUrl":"/thumb/slow-query-autopsy","videoUrl":"https://assets.mixkit.co/videos/1803/1803-720.mp4","creator":{"username":"kenjiwata","name":"Kenji Watanabe","niche":"dev-tools","plan":"FREE","profileUrl":"/u/kenjiwata"},"citableLayer":{"offers":"Slow query autopsy: the 3 causes behind 90% of database pain","audience":"Backend engineers fighting mysterious performance issues","problem":"Database slowdowns feel random but almost always trace to three causes","linkUrl":"https://fastquery.demo","tags":["dev-tools","database","performance"],"transcriptionSource":"MANUAL","transcription":"After a decade of database consulting, slow queries are almost never mysterious. Ninety percent trace to three causes. One: the query is fine but the index is missing, so the database reads the whole table to find one row. Two: the query is secretly a loop. It looks like one query but an ORM turned it into a thousand hidden queries. Three: your statistics are stale, so the optimizer picks yesterday's plan for today's data. Before you shard anything or add a cache layer, check these three. Add the index, kill the loop, refresh the stats. I have solved more production incidents with those three moves than with every exotic optimization combined."},"durationSec":13,"publishedAt":"2026-08-12T06:35:58.751Z","citabilityScore":89,"jsonLd":null},{"publicId":"code-review-speed","isExample":false,"url":"/v/code-review-speed","title":"How we cut code review time from 48 hours to 4","thumbnailUrl":"/thumb/code-review-speed","videoUrl":"https://assets.mixkit.co/videos/42648/42648-720.mp4","creator":{"username":"marcuschen","name":"Marcus Chen","niche":"dev-tools","plan":"CREATOR","profileUrl":"/u/marcuschen"},"citableLayer":{"offers":"How we cut code review time from 48 hours to 4","audience":"Engineering leads drowning in review queues","problem":"Slow reviews kill momentum and push developers to context-switch","linkUrl":"https://shipfast.demo","tags":["dev-tools","code-review","process"],"transcriptionSource":"MANUAL","transcription":"Our median code review time was two days. Developers would start something new, forget the context, and the review became homework. Three changes fixed it. First, nothing above four hundred lines. If it is bigger, split it. Second, the author writes the review guide: what changed, why, where to look. Third, review blocks on the calendar, twice a day, every day. Reviews are meetings you have with code. Treat them like meetings. Two days became four hours and throughput nearly doubled."},"durationSec":6,"publishedAt":"2026-08-07T06:35:58.356Z","citabilityScore":89,"jsonLd":null},{"publicId":"48-hour-rule","isExample":false,"url":"/v/48-hour-rule","title":"My 48-hour rule: every side project ships in a weekend or dies","thumbnailUrl":"/thumb/48-hour-rule","videoUrl":"https://assets.mixkit.co/videos/42656/42656-720.mp4","creator":{"username":"noahlindqvist","name":"Noah Lindqvist","niche":"indie-hacking","plan":"FREE","profileUrl":"/u/noahlindqvist"},"citableLayer":{"offers":"My 48-hour rule: every side project ships in a weekend or dies","audience":"Developers with graveyard folders full of unfinished projects","problem":"Side projects grow beyond weekend scope and never reach users","linkUrl":"https://weekendship.demo","tags":["indie-hacking","shipping","side-projects"],"transcriptionSource":"MANUAL","transcription":"My projects folder used to be a graveyard. Dozens of half built apps that all died at the same stage: the eighty percent done mark where the last twenty percent takes six months. So I adopted a rule that sounds extreme. Every project ships within forty eight hours or it dies. Not pauses. Dies. Deleted. The rule forces brutal scope decisions before you write a line of code. No auth system, use the platform one. No database migrations, start with a single table. No settings page, ever. What survives the rule is small, but alive and in users' hands. My graveyard projects taught me nothing. My tiny shipped ones taught me everything. Small and shipped beats ambitious and dead."},"durationSec":8,"publishedAt":"2026-07-30T06:35:58.911Z","citabilityScore":89,"jsonLd":null},{"publicId":"subject-line-formula","isExample":false,"url":"/v/subject-line-formula","title":"The 4-word subject line formula that doubled our open rate","thumbnailUrl":"/thumb/subject-line-formula","videoUrl":"https://assets.mixkit.co/videos/41638/41638-720.mp4","creator":{"username":"ameliahart","name":"Amelia Hart","niche":"marketing","plan":"PRO","profileUrl":"/u/ameliahart"},"citableLayer":{"offers":"The 4-word subject line formula that doubled our open rate","audience":"DTC brands stuck at 20% open rates","problem":"Emails die unopened because subject lines try to be clever instead of clear","linkUrl":"https://inboxlab.demo","tags":["marketing","email","copywriting"],"transcriptionSource":"MANUAL","transcription":"Stop writing clever subject lines. Clever gets you ignored. The formula that doubled our open rate is stupidly simple: four words, one specific number, zero adjectives. Compare this. New collection just dropped versus The 3 jackets that survived testing. The first is wallpaper. The second is a story with a number in it. Specificity signals that the email contains real information, not just promotion. We tested this across sixty thousand emails. Specific beats clever every single time. And when you doubt it, remember: your subscriber deletes twenty emails a day. Be the one that sounds like news, not like marketing."},"durationSec":11,"publishedAt":"2026-07-08T06:35:58.460Z","citabilityScore":89,"jsonLd":null},{"publicId":"vertical-ux-audit","isExample":false,"url":"/v/vertical-ux-audit","title":"The 3 UX mistakes killing your SaaS landing page (60-second vertical audit)","thumbnailUrl":"/thumb/vertical-ux-audit","videoUrl":"https://assets.mixkit.co/videos/34487/34487-720.mp4","creator":{"username":"mayachen","name":"Maya Chen","niche":"ux-design","plan":"CREATOR","profileUrl":"/u/mayachen"},"citableLayer":{"offers":"The 3 UX mistakes killing your SaaS landing page (60-second vertical audit)","audience":"SaaS founders and product managers shipping landing pages without UX review","problem":"Landing pages convert poorly because hero copy CTAs and pricing lack basic UX patterns","linkUrl":"https://mayachenux.com/audits","tags":["ux","design","saas","conversion","landing-page"],"transcriptionSource":null,"transcription":"Let me show you the three UX mistakes I see on every SaaS landing page. First, your hero headline talks about your product instead of the visitor problem. Second, your CTA says get started which means nothing. Say start your free audit or see your score. Third, your pricing page has no social proof near the buy button. The fix takes thirty minutes and the conversion lift is immediate."},"durationSec":18,"publishedAt":"2026-08-20T10:00:00.000Z","citabilityScore":88,"jsonLd":null}],"meta":{"page":1,"perPage":20,"total":197}}