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
Man, I love product design
Good work man!! don't u think its funny how claude has overused this particular heading font so much that whenever u see someone using it in their designs it makes u think its an AI made design even though it maybe not
Haha, very true! But just because of that, we can’t stop using this font. It’s one of my favourite fonts.
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
Trending
retrofuturism
Share your favorite designs from the past exploring the distant future. Or your own take on the aesthetic 🚀
halftone
Dots. Texture. Grain. Let's see your designs using the halftone technique.
Midjourney
Creatives are showing off what they're making with Midjourney.
colorgrade
Video editors sound off: How do you enhance the mood of your video in color grading?
Related posts
It seems like the world has moved towards the subscription model. Music. Software. Entertainment. Sport.
It has its advantages and its drawbacks. But when it comes to digital and brand design, it makes a lot of sense.
Digital products live in a permanent state of re-design. Every new feature, user insight, business decision, or marketing initiative changes the product itself. And everything around it has to evolve at the same pace — landing pages, product visuals, onboarding, presentations, marketing assets, documentation, and more.
Design is no longer about creating a final solution. It's about continually re-examining what already exists and refining it as products grow.
Frankly, this makes perfect sense to us and to many of the companies we work with.
We know what it's like when a product grows faster than the internal team can keep up. One week it's a new feature, the next it's a landing page for a launch, then a pitch deck, onboarding improvements, or marketing assets. The work rarely arrives as one big project. Instead, it comes as a constant stream of interconnected design challenges.
Looking back, we didn't wake up one morning and decide to launch a design subscription. It evolved naturally. Clients kept coming back and they needed a design partner who already understood their product, brand, and goals, and could jump in whenever the next challenge appeared.
Eventually, we realized we weren't selling projects anymore. We were supporting continuous product and brand evolution.
The subscription model simply became the most honest way to describe that relationship and is now one of our main services. Check it out → https://www.insaim.design/services/subscription
The point about work rarely arriving as one big project, more a constant stream of interconnected challenges, matches what I see with most product teams. Makes sense the subscription model came from client behavior rather than a strategy decision.
A lot of products don’t have a feature problem.
They have a decision problem.
Too many actions.
Too many priorities.
Too much competing for attention.
Good product design is not about adding more.
It’s about making the right things easier to notice, understand, and act on.
That’s where better product decisions create better user experiences.
#ProductDesign #UXDesign #SaaS #UIUX #DigitalProducts
The real estate dashboard example makes the point well, four metric cards up top instead of ten means the agent actually looks at them.
Hey! I just shared a write-up on something I learned while rebuilding a product with AI agents:)
The main idea is pretty simple:
Don’t put all your product context in one giant agent file.
Keep the main file small, and put the real product knowledge inside structured docs that the AI can navigate when it needs them.
This has helped me a lot when working on a SaaS product with a lot of business logic!
Sharing the full breakdown here:
I'm offering consulting services to set this up! :)
The table-of-contents-in-the-main-file pattern is the key move here - it keeps the agent's default context small while still giving it a map to go fetch the architecture or naming-convention doc only when the task actually touches that domain.