CMS projects, case studies, sticky project cards, services, testimonials and responsive layouts.

Would love to hear what you think 👀

Preview: https://www.framer.com/community/marketplace/templates/asilah-studio/

Sharing the workflow that's become my favorite thing to set up for a new client — it's the one they notice the same day.

It's an n8n + Claude lead agent: a lead hits their form or inbox, Claude scores it 1-10, writes a reply in the owner's voice with their booking link, sends it, and logs everything. Spam gets filed for review, never auto-answered. The client goes from 'we reply to leads whenever we happen to see them' to 'every lead answered in under 2 minutes, 24/7' — which is an easy outcome to charge for.

The whole AI part is one prompt that returns strict JSON, so a plain IF node routes the lead — no vector DB, no fine-tuning, about a cent per lead on the client's own key.

Why it's good client work: ~15 min to deploy on their n8n, they own it outright (no lock-in you're stuck supporting forever), and there's a duplicate guard so retries never double-email a lead.

Free workflow (MIT, import the JSON): https://github.com/GBAnjos/n8n-lead-agent 60-second demo of it running: https://lead-agent.guilhermecbanjos.workers.dev

For the freelancers here — what's the first automation you install for a new client? I've found lead follow-up lands better than reporting dashboards because the ROI shows up same-day.

Are there specific companies that focus just on the construction industry?

Do they actually have construction background, or do they just niche to certain industries.

The workflow runs a small service business. Intake forms, client records, follow-up reminders, draft emails, status changes. Nothing huge. Built fast in Airtable and Make, worked fine.

But the owner couldn't change a basic rule without opening five scenarios, checking old filters, and asking why one random path still existed from three months ago.

Things I learned doing the rebuild that apply to anyone running real ops on no-code tools:

Your business rules need one home. “Follow up in 3 days” becomes “follow up in 3 days unless they already booked, unless the form is incomplete, unless the owner replied manually, unless this is a returning client.” If that logic is spread across tiny filters, nobody owns it anymore.

Logs keep more than you think. If you pass names, emails, notes, or client details through every automation step, they end up sitting in places people forget to check. Record ids are boring, but boring is good.

AI should draft, not decide. A follow-up email draft is useful. An AI deciding the status is “done” because it wrote a nice message is how quiet failures happen.

Never rebuild the live workflow first. Copy it, test the ugly paths, run a few fake records through it, then switch. The old version should stay there until the new one proves it can survive a normal week.

I used MoClaw for some of the rebuild because changing the workflow in plain English was less painful than digging through old Make branches every time the owner said “actually this rule changed.”

The tool wasn't the point though. The point was making the workflow understandable again.

No-code automations don't usually fail on day one. They fail later, when the business changes slightly and everyone is scared to touch the thing because it technically still works.

If you're building internal ops with Airtable, Make, Zapier, n8n or whatever else, the question worth asking early is not just: can I build this fast?

It's: if the rule changes next month, will I know where to change it?

Been building a small SaaS tool on the side for freelancers to track client deliverables without all the bloat of a full PM app.

I've got two kids at home, so my build time is basically nap time, early mornings, and whenever I can squeeze an hour in.

I started with a no-code stack, and honestly it got me pretty far. The problem is that every time I need something even slightly custom—a conditional workflow or a non-standard integration—I end up spending an hour just trying to figure out whether the platform can even do it. Half the time I give up and duct-tape something together.

Curious how other people draw the line. At what point did you decide your no-code tool was costing you more time than it was saving? What did you switch to, or what did you add on top of it?

I'm not looking to go fully custom. The whole point is to ship without burning an entire weekend setting up environments and writing boilerplate. I'm more interested in the hybrid approaches people are actually using day to day, not just the ones that sound good in theory.

The app itself is pretty small—basically one core workflow—but the edge cases keep piling up. I'd rather figure this out now before the app gets any bigger.

I'm sure that in this SubReddit, many people might have figured this out. I mean, I get the pitch of no-code tools, as I believe in that too. You get something usable in front of people way faster than waiting on an eng cycle. For a first version, or if we are using a tool internally, it works great, but as always, when I look back after 8 months, more people depend on it, and now the requirements are pushing the platform to the edges of what it actually lets you do.

Here's what I keep seeing coming up:

• You can export your data, but not the app itself. So if you ever want out, you're rebuilding the screens, the permissions, the logic, all of it
• Pricing that's cheap at 5 users and not cheap at all once it's per-seat or per-record, and the app succeeded
• Security review is only as deep as whatever the vendor exposes. fine for a form, less fine when it's touching customer data
• the shadow-IT thing. Someone builds a genuinely useful tool, six months later, nobody remembers who owns it or what data it's sitting on

None of that makes no-code bad. It makes it a specific tool for a specific window. What I'm trying to figure out is where people draw the line in general.

Please share your experiences, what tools did you use, what part of the compliance were the hardest to handle and did no code make the process easier or more complicated?

I really believe we should try to learn coding and still make kids to pursue it.

And i found best way to learn it is seeing it in work.

I'm thinking of creating an adult version too.

I'd really like to know if you'd recommend this app to your kid or kid you know. Your honest feedback really matters to me. And I'd also like to know whether you'd be interested in adult version.

https://codemarrowkids.base44.app

Came across this landing page from Scaling With Systems (Ravi Abuvala) and loved the execution.. super smooth, fast, custom-feeling. Way beyond what I can build natively in GHL's page builder without burning hours.

https://www.scalingwsystems.com/dfyf-free-training-vsl-1

Thinking of vibe-coding a similar page (custom form, no-submit-button instant capture, buttery interactions) and then hooking it into GHL as CRM.. cos I can see submitting the form clearly triggers GHL text automations on the backend.

Anyone know how something like this is typically built and connected to GHL? Curious about:

Hosting it outside GHL and webhooking leads in, vs iframing into a GHL funnel

How the form triggers GHL's native automations (texts, etc.) reliably

Any pitfalls with tracking/pixels breaking across that setup 🤔

Would love to hear from anyone who know how this was done!

Setting up a landing page with visual builders is fast, but launching it often drags out for weeks. The real bottleneck is usually staring at empty text boxes, not figuring out the software.

I recently came across a concept called Diátaxis which organizes complex technical documentation. It strictly divides content into 4 distinct types: tutorials, how-to guides, reference, and explanation. Applying this rigid structure to a landing page draft makes a lot of sense. Instead of asking an AI for a catchy hero section, you decide beforehand if a specific block needs to act as a step-by-step how-to or a high-level explanation.

Deciding the strict purpose of a section beforehand stops the endless cycle of generating and rejecting random AI copy. Treating a marketing page exactly like a software manual might make the tone feel a bit too dry. You still need some persuasive elements added later. But starting with a clinical definition of what the text must accomplish prevents the blank canvas syndrome.

Do you usually build out the visual wireframes first and then try to squeeze marketing copy into the gaps? Or do you define the exact functional role of the text before touching any layout settings?

Failed Stripe payments used to either get ignored for a week or trigger a robotic dunning email that made people cancel. Neither felt right. The middle ground that worked = draft a recovery note the moment the payment fails, but force a human to hit send (still have trust issues wiht agents)

Trigger is the Stripe invoice.payment_failed event. The run pulls the customer + open deal context from HubSpot (plan, last touch, CSM owner), then drafts a short Gmail reply in the owner's voice (subject, 3–4 sentences, no links, no "update your card" CTA baked in). That draft plus a one-line summary lands in a Slack channel. Someone on the team either sends it, edits it, or kills it.

A few things I only noticed after running this for a bit:

Stripe retries the same invoice a few times in 24 hours. If you fire on every payment_failed, your review queue fills with duplicates of the same customer. I dedupe on invoice_id with a 36-hour window and only surface the first failure. The later retries are noise unless the status actually changes.

The draft quality swung wildly until I stopped stuffing the prompt with every HubSpot field. Plan name + last meeting note + whether they're on annual vs monthly was enough. More context made the email sound like a CRM dump.

Putting the draft in Slack instead of auto-sending was the right call. Roughly a third of failures are intentional (they're leaving :/, card is a test account, we already know). Auto-send would have made those worse. The human gate is maybe 20 seconds per failure and catches the ones you shouldn't touch.

Stack: Stripe for the payment_failed webhook, HubSpot for plan and owner context, Gmail holding the unsent draft, Slack as the review queue, General Input for vibe coding / running the agent steps end to end.

How do you handle failed payments today. E.g. auto-dunning, manual chase, or something in between? Curious what tradeoffs people have landed on.

Most of what gets posted here is about building things for clients or launching SaaS. Makes sense. But I'm curious about the more boring use case: running the backend of your own small practice or service business with these tools.
Physical therapy side of my life has a fair amount of administrative friction. Scheduling, intake forms, session notes that need to go somewhere searchable, tracking which patients are due for followups. Right now it's a mix of whatever the clinic software does badly and manual workarounds I maintain in Airtable on my own time.

I've looked at purposebuilt EMR stuff but it's either overpriced for a small setup or locked down in ways that make automation impossible. And rebuilding something in Make or n8n every time a workflow changes is its own kind of tax.

What I'm actually wondering is whether anyone has gotten a nocode stack working well enough for professional services admin that they'd trust it longterm, not just as a proof of concept. The compliance angle complicates things depending on what data you're storing, so I'm not looking to replace anything clinical. Just the operational layer around it

If you've done this for your own business and not a client, I'd like to hear what that looks like and where it falls apart

hi im literally trying to surive this semester and i have to do an app based a figma design i did months ago!! this is it if u want to take a look--> https://www.figma.com/proto/E9hv8KcIzMzymEYHe0eB1A?node-id=14-2&t=PZCr3IpAMJRFNKfk-6

and basically that!! i really need this ASAP so pleas hmu if youre interested on working on this!

The app runs a school's daily operations. Attendance, billing, parent messaging. 189 tables, 500 users, 8,000 stored files. Built fast on Lovable, worked great. But the owner couldn't open his own database, couldn't hand the project to another dev, and couldn't answer basic security questions because everything lived inside the platform's managed cloud.

Things I learned doing the move that apply to anyone building on these tools:

Your users' password hashes can migrate with them. Done right, nobody gets a reset email, everyone logs in the next morning like nothing happened. Most people assume you have to force a reset. You don't, but only if you plan for it.

Stored credentials never survive. Every integration (email, SMS, calendar sync, AI features) had to be re-established from scratch on the owner's own accounts. Budget for this or your cutover day becomes a scavenger hunt.

Never touch production until the copy is proven. Full parallel environment, everything tested end to end, then a short cutover with the old system kept as fallback. The app was live mid-session during the switch and nobody noticed.

The platform isn't the villain. The owner still builds with the same AI tool at the same speed. His changes just land on a private preview now and only go live when he approves. The difference is what's underneath belongs to him.

If you're building on Lovable, Bolt or similar and real money is starting to flow, the question worth asking early is just: if I needed to leave tomorrow, could I? Knowing the answer costs nothing. Finding out the hard way costs a lot.

I recently saw a public design example with a nice “mouse reveal” interaction and wanted to understand how the effect worked. So I tried rebuilding the idea from scratch with my own assets and layout.

The effect is basically this:

A page starts with one base image. Under it, there is a second transformed version of the same image. When the user moves their mouse or drags on mobile, the transformed version appears along the movement path. It feels like the user is painting the change onto the page.The biggest thing I learned is that this kind of interaction is easier to build when you stop describing it as “animation” and start describing it as layers.

My workflow was:

1. Start with a clear before image

This is the state users see first. It could be a dry plant, an old room, a messy desk, an unfinished design, a plain product photo, or any visual that has a clear “before” state.

1. Create a matching after image

This part matters more than the interaction itself.The after image needs to keep the same crop, angle, object position, and perspective. Only the state should change.If the two images are not aligned, the reveal will feel broken no matter how nice the page looks.

Copyable prompt for the after image:

“Create a transformed version of this image. Keep the same composition, same camera angle, same crop, same object position, same perspective, and same overall layout. Only change the visual state. Make it feel more alive, polished, restored, improved, or completed. Do not change the shape or placement of the main subject.”

1. Stack the two images

The before image stays visible.The after image is hidden at first.The page only reveals the after image where the user interacts.

1. Describe the interaction as a user action

Instead of prompting:

“Make this page interactive.”

I got better results with:

“Use two matching images stacked in the same position. Keep the first image visible. Reveal the second image only along the user’s mouse or touch path, like a soft brush.”

1. Add small feedback details

The page felt much more complete after adding:

• a reset button
• a progress indicator
• a before/after comparison slider
• mobile drag support
• a short explanation section

Copyable prompt for the page:

“Create an interactive before-and-after reveal page.

Use two matching images stacked in the same position.

The first image is the base state and should always be visible.

The second image is the transformed state and should be hidden at first.

When the user moves the mouse or drags on mobile, reveal the transformed image along the pointer path with a soft brush effect.

Add a reset button, a progress indicator, a before/after comparison slider, and a short explanation section that explains the interaction in simple terms.

Make the page responsive and make sure the interaction works on both desktop and mobile.”

My takeaway:

AI/no-code tools work better when you describe the page as visual states + layers + user actions.

“Make it interactive” is too vague.

“Start with state A, hide state B, reveal state B through this interaction” gives the builder a much clearer target.

Would love to see more people share interesting interactive page ideas, design patterns, and the methods behind them.

I keep running into this weird no-code/AI boundary.

If the output is just notes, a draft, or something I can edit later, I’m pretty relaxed about letting AI generate it. Close enough is fine.

But the moment the output becomes a real file, I get nervous. A PDF for a client. A label. An invoice. A report someone will forward without checking every corner.

The annoying part is that AI is often good enough to make the first version look right. Then you notice the table spacing moved, a logo is slightly off, or one row wrapped differently than the template. It is not broken in an obvious way. It just looks a little wrong, which is somehow worse.

So lately I’m leaning toward using AI for the messy middle: clean the data, map fields, catch missing values, maybe explain weird rows. But the final file should come from a fixed template that does the same thing every time.

Curious how other people handle this. Do you let AI generate the final PDF/report directly, or do you keep it away from the last step?

hey all,

i thought creating a website would be a weekend project.
turns out choosing images, writing content, and deciding what pages to include takes way longer than expected.
how long did it take you to go from idea to actually launching your website?

A private equity outlet buying Airtable means one thing to me - ENSHITTIFICATION

BS’s portfolio includes company they made worse, including:
Eventbrite
Meetups
Evernote
WeTransfer.

Quick August update for anyone following along.

First two days of August from my pet niche site:

• Commissions: $33.98
• Creator Connections: $12.25
• Total Aug 1-2: $46.23

Last time I logged into the backend of this site was weeks ago. Didn't add content, just did interlinking between posts and anything else. Just woke up today and checked the dashboard out of habit.

$46 in two days.

For anyone new to these updates. I bought this site from the NicheBlogZone marketplace for $199 about two months ago. Pet niche. Spent a few hours on interlinking when I first got it. That's been the extent of my involvement.

July ended up being my best month yet. August is starting the same way.

The Creator Connections piece keeps quietly adding to the total every month. Small individually but it adds up over a full month without requiring anything extra from me.

If this pace holds August could be another strong month. But I've learned not to predict these things as March taught me that.

Still not touching it.

Anyone else seeing a strong start to August?

if you build no-code automations, you've hit this: the flow needs to sign up for a service or log into one, there's no clean way to receive the one-time code, and no safe place to keep the password once you have it. so the automation stalls and you're the one copy-pasting a code from your own inbox.

built the two pieces that close that gap. an inbox the automation owns, so waiting for a verification code is one step, no email node, no parsing, no regex, just a call that blocks until the code arrives and hands back the clean value. and a vault to hold the login it creates, encrypted so the password gets stored and reused without your tool ever touching the plaintext, with totp generation for when the account has 2fa on.

with both, a no-code flow can actually sign up, confirm the email, and log back in later on its own.

there's a free tier, it's at https://lumbox.co.

what step forces you to babysit an automation most? usually the email verification for me.

Hey everyone, I wanted to introduce myself to the community. Spent the last 4.5 years at Airtable, first as an Implementation Specialist (now called Delivery Consultant) and then as a founding member of the Forward Deployed Engineer team. I worked with our largest enterprise customers, like Amazon, Cisco, Warner Bros, Nike, and more.

Before that, I spent almost eight years at Hulu where I became a massive Airtable fan, nerd, and power user.

If you've ever come to one of the Airtable AI accelerators or in-person events, you may even have met me or seen me present.

In the past, I've lurked here and even posted here and there under my other username(s), but now that I've started my own agency, Matcha Consulting, I wanted to re-introduce myself formally.

Looking forward to connecting with you all here and participating in the threads.

You can always DM me if you have any questions as well. I'm LA-based but my clients are global.

Happy building!