The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
For a SaaS homepage, I always think about one question:
“Can a visitor understand what this product does in 5–10 seconds?”
If not, adding more animations, sections, or fancy effects won't fix the real problem.
Clarity beats complexity.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
What if you can make interactive videos for the FAQ section on your website? that too without hiring a model and spending a fortune on production.
Thats exactly what I did for this brand called "Hertz"
Just bunch of text on FAQ is okay but a person explaining all that in a video on the side is the cherry on top.
The fastest SaaS products we've built didn't use the newest stack. They used the most boring one.
What we reach for when a founder needs a working product:
• Next.js App Router, React, TypeScript and Tailwind
• Supabase Auth and Postgres, Prisma for the schema
• Stripe subscriptions kept in sync with webhooks
• Transactional email for the moments that matter
• A marketing site in Webflow or Framer the team can edit
What we skip at MVP stage: microservices, Kubernetes and anything the first 100 users won't notice.
Every novel choice is one you'll debug at 2 a.m. Save the novelty for the part customers pay for.
Founders: what did you over-build in your first version?
Really agree with keeping the stack simple early on. Curious, how do you decide when a SaaS product has outgrown its MVP architecture? Would love to exchange thoughts on this in DMs.
Use of 3D and 3D camera is lit. Crazy smooth animation🔥