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
Removing my Expert Badge just because I wasn't active while I was on a trip is unfair. That badge helped build client trust, and losing it has already cost me work.
Please review my case and fix this.
#Framer #FramerExpert
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
Congrats!!
AI solved your building problem.
It made your positioning 10x worse.
• I went through a Reddit thread this week.
• Founders comparing vibe-coded apps
• The ones who make money
• vs those stuck at zero.
Same AI tools.
Same weekend builds.
Products that look almost identical.
The split had very little to do with the code.
The apps earning money had a sharp answer to one line:
↳ "Who is this for, and why would they pay today?"
The apps at $0 were built for "anyone who..."
↳ their founders hoped the product would explain itself.
It never does.
When anyone can ship in two days,
the build stops being your edge.
Positioning decides who keeps scrolling
and who pulls out happily paying.
Before you write your next prompt ↓
→ Talk to people who have the problem.
→ Ask what they pay for today without you.
→ Pick a niche small enough to name in one sentence.
→ Write the line your buyer would repeat to a colleague.
→ Charge from day one. Free users tell you what they like.
↳ Paying users tell you what works.
→ Cut every feature nobody asked for.
Your first paying customer will teach you
More than your next 50 features do.
If your app is live and still sitting at $0,
↳ send me "MVP", and I'll lead the conversation.
Project update: a safer way to move cards to "Paid" in a CRM
For a financial advisory firm, I built a feature in GoHighLevel that makes paying referral partners faster and harder to get wrong.
What it does: when a card is dragged to Paid, the system finds every other card due for the same partner and shows a checklist. The assistant ticks the cards to pay together and confirms once. With a single card, it asks a simple confirmation instead.
How I made it reliable: a small backend on Vercel re-checks every card before moving it (same partner, still due, only into Paid). A failed card is named in a message while the others still move. If the list can't be loaded, the plain question is asked, so nothing moves silently.
What I did: designed the flow, wrote the browser script and the backend, and tested the cases that go wrong, not only the happy path.
Tools: GoHighLevel, JavaScript, Node.js, Vercel, GitHub.:
