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
I help B2B companies plan and execute trade show and conference marketing — including event selection, sponsorships, booth strategy, vendor coordination, promotional materials, lead capture and post-event follow-up. My experience includes managing ~30 industry events annually within a ~$500K event, sponsorship and membership portfolio.
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
One problem. Two design directions. Which would you choose?
For AEGIS / 001.05 . Traffic Operations, we explored two approaches to the same challenge: helping city operators understand congestion, incidents and network-wide disruptions without overwhelming them with information.
Both solve the same operational problem. Different approaches to hierarchy and interaction.
If you were behind the control desk . Option A or Option B?
#smartcities #enterpriseux #productdesign #digitaltransformation #jemirae
1 voted
33%
2 voted
67%
3 votes
Closed
I built QuickFix for the Lovable Challenge.
The idea started with a simple question:
What happens after a customer requests a home service?
Booking is only the beginning. The real challenge is managing everything that happens afterward — operations, crew assignment, service progress, and completion.
So I built QuickFix around the operation behind the service:
Customer Request → Operations → Crew Assignment → Service Execution → Completion
QuickFix is a managed home-services platform where customers submit one request, and the internal operations team manages the workflow from there.
What I built
• Customer service requests
• Centralized operations management
• Internal crew assignment
• Job and status tracking
• Service workflow management
• Operational dashboard
• End-to-end request management
The goal wasn't to build just another booking interface.
It was to build the operational system behind the service.
The product is fully developed, QA-tested, polished, and ready for the challenge.
Built with Lovable.
You send one request. QuickFix manages the operation from there.
#LovableChallenge #Lovable #BuildWithLovable #QuickFix #SaaS #ProductDevelopment
It was Tuesday, I remember... a guy named Dev sent me his demo page. He sells scheduling software to dental offices, mostly in his postal ranges. The whole page was three lines. I counted twice because I didn't believe it.
Line one said "Request a Demo." Line two said "Fill out the form and our team will be in touch." The button said "Submit."
"Be in touch" could mean a quick call. It could also mean nine emails from a guy named Kyle.
The visitor has to guess, and people don't fill out forms when they have to guess.
So we fixed it live, one small change at a time.
Change 1. say what happens
The headline became "See Chairtime work in your office." The subtext became "Book a 20-minute walkthrough with our team." Now you know what you get and how long it takes. But it still talks about the software. Nobody wakes up wanting to look at software.
Change 2. talk about the person
The new headline: "See how your front desk could stop losing 6 no-shows a week. Takes 20 minutes." The subtext: "We'll use your real schedule. No slideshow."
That last bit is on purpose. Everyone who books a demo is scared they'll get a scripted pitch from someone reading off a screen. Say the fear out loud and it shrinks.
Change 3. the button
"Submit" became "Book my walkthrough." Submit sounds like taxes. Book my walkthrough sounds like you're getting something.
Here's what I noticed after all that.
The old page was about what Dev wanted, which was a lead.
The new page is about what the visitor gets, which is 20 minutes that are actually about their office. Same form, same product.
There was a fourth change, and I've been thinking about it for a week.
Dev deleted one field from the form. Bookings went up. It was the field every sales book tells you to keep, and I still can't fully explain why it worked.
Which field do you think it was? I'll tell you if someone guesses right.
saasProduct Marketingb2bmarketingCopywritingDirect Response Copywriting Adobe IllustratorAdobe PhotoshopGoogle Docs
"Submit sounds like taxes" is going to stick with me. Change 2 is the one most of us builders miss: we describe features instead of the front desk's real problem (6 no-shows a week). I build POS and business tools, so I'm taking this straight to my own demo pages.