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
Make switches an instant-trigger scenario off after its first error, and it stays off until someone notices.
In this demo a home-services company sends quote requests from its site to Google Sheets, urgent jobs to Slack and the rest to sales. One Gmail hiccup stopped the scenario, and every lead after that went nowhere. The audit found 11 problems, including a live API key in a request URL and an "urgent" filter that missed "Urgent". After the repair the same review finds 0.
The company and its blueprints are invented for the demo.
https://contra.com/p/MAFANOA6-make-scenario-audit-11-problems-found-and-fixed
Does your scenario tell you when it stops, or do you find out from a customer?
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
Finally got around to sharing this fun campaign I got to work on with Heidi Health earlier this year 🎉
Check it out here → https://contra.com/p/lm3vrvbo-heidi-or-evidence-campaign?r=alexpresa
You nailed the overall mood here. The details just reinforce it nicely.
A Webflow to Framer migration and website overhaul for pliability, the #1 mobility app in the world. Custom code components, scroll animations, CMS-driven landing pages for campaign launches, and over 400 CMS items migrated from Webflow.
pliability provided the new website design, and @Mason Price and I brought it to life in Framer. Huge shoutout to Mason for collaborating; he has the highest level of mastery when it comes to Framer development.
This is beautiful!
We rebuilt TechFoundry's website in a week. The brief that mattered most wasn't "make it look good". It was "make ChatGPT and Gemini able to find us".
Buyers ask an AI before they search now. So all 110 pages (26 pages, 80 Aerless™ hardware parts, 4 articles) are server-rendered with real content and structured data a model can cite: Product schema with SKU and MPN on every part, BlogPosting on articles, CreativeWork on case studies, and a robots.txt that lets AI crawlers in.
Three other decisions I'd make again.
1) One hand-coded WordPress theme, three "surfaces": corporate hub, /ai, /aerless. Each gets its own nav, palette and CTAs; the same codebase decides which company you're looking at. No page builder, no front-end framework. Homepage Lighthouse: 98 / 100 / 100 / 100.
2) Leads go where the team already is. Every form posts straight into a Microsoft Teams channel and creates a record in a lightweight CRM I built inside WordPress. Nothing lives only in an inbox.
3) Claude Code and ChatGPT alongside hand-written PHP and JS. That's how one person ships 110 pages in seven days.
What I'd fix on day one next time: reserve space for the animated heroes so mobile doesn't shift layout, and ship an llms.txt next to the sitemap.
If you're rebuilding a site this year: are you designing for AI search yet, or still just Google?
Appreciate the honesty on the mobile layout shift. Are you fixing it with explicit CSS aspect ratios to push that mobile score back above 90?
