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
AI Agents vs Traditional Automation: What's the Real Difference? 🤖
Traditional automation follows instructions.
AI agents can interpret information, make decisions within defined boundaries, and choose the next step based on context.
Here's a simple example:
⚙️ Traditional Automation: A customer submits a form → the system sends an email → a CRM record is created.
🧠 AI Agent: A customer sends a message → AI understands the request → checks relevant business data → determines the appropriate action → updates the CRM or prepares a response.
Both are useful. The difference is how they handle changing situations.
And here's something important: not every workflow needs an AI agent.
For predictable, repetitive tasks, traditional automation is often faster, cheaper, and more reliable.
AI agents make more sense when workflows involve unstructured information, interpretation, and decisions that cannot easily be covered by fixed rules.
The best systems often combine both.
Build automation where rules are enough. Use AI where intelligence adds value.
What's your take — are businesses adopting AI agents too quickly, or not quickly enough?
#Automation #WorkflowAutomation
aiagentssaasartificialintelligenceAI Agent EngineerAI Chatbot DevelopmentLow-Code/No-Code DevelopmentNext.jsNode.jsPython
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
1 designer + base44 + 3 days without proper sleep = Overdrive🤍
A job tracking system for a car repair shop.
✱ One board showing every car on the floor, where each one stands and what’s holding it up.
Add a car, assign the work, and from there it tracks itself- what’s late, which parts have landed, who’s in today. Visit history, receipts, and a widget that tells you the next free slot you can offer someone.
Three days. Not smooth ones. But it’s live❗️
✱ Now the why, because none of those features were my idea.
My client owns the shop. Four mechanics, up to seven cars a day, no front desk. For months he’d complain about the same stuff whenever we talked: parts he ordered and forgot about, mechanics starting one car and getting pulled onto another, people asking when they can bring a car in and him not knowing what to say.
It was never a brief, of course, he was just talking. But one day I asked him properly: what do you need to see the moment you walk in?
✱ He said four things. And those four made sense as widgets, naturally.
Nothing on the job board gets typed in by a person. For example, a car shows as blocked because the mechanic who has it is off today- the board works that out and writes the reason on the card. He doesn’t walk around the shop asking anyone, he can just see it now.
✱ And the part nobody puts in these posts😅
→ It is my first time ever (!) using Base44 and I started without a paid plan, so I had a hard limit on how many prompts I got.
You can’t iterate your way to something like that. Every prompt had to arrive already correct, which meant almost all of the work happened before I typed anything. I designed every screen and every state in Figma first, then worked out exactly what to ask for and in what order.
I spent hours with Claude and Google figuring out how to phrase things, what would break, what to check before changing anything. I’d write a prompt and then throw it away and write a better one, because a wasted prompt cost more than the time did 🤷🏻♀️
Honestly, the constraint made it better. No aimless tinkering. Every change had a reason before it was made, and I still got every core feature I wanted in there.
✸Research: https://miro.com/app/board/uXjVEWOXy9k=/?share_link_id=813311021448
✸Walkthrough: https://www.loom.com/share/69ffa2d58ca24e7bb10676be5173cdc2
✸Overdrive live demo: https://overdrive-shop-flow.base44.app
✸X thread: https://x.com/gurvchler/status/2114517480152740121?s=20
✸LinkedIn post: https://lnkd.in/p/dysRmrNw
Well done!
And love the "no proper sleep" detail - sounds so familiar 😂
A Gentle Rhythm
A calm portal for a child sleep consultant and the families she works with
One workspace instead of a pile of spreadsheets for every client.
Parents log sleep with one tap on their phone. The consultant sees the questionnaire, diary, calculations and plan in one place.
Why I built it
Right when the Base44 Challenge started, I got a new client: a child sleep consultant who needed a website.
My first thought was that she needed more than a website. She needed a real workspace.
Her work with each family involved:
An intake questionnaire in Google Forms.
A paper sleep diary that parents fill in, often at 3 a.m. with a baby in their arms.
An Excel spreadsheet with her own formulas, where she manually copies diary entries and calculates wake windows, naps and night sleep.
A new set of files for every new client.
I looked for a ready-made platform for this niche and couldn’t find one that fit her workflow. She needed more than a generic CRM or a parent-facing sleep tracker.
So I built A Gentle Rhythm.
Two connected spaces
01 · The consultant’s workspace
Available on the web and on her phone.
All families appear in one list, with clear statuses: waiting for the family, questionnaire to review, diary in progress.
Each child’s case brings together:
The intake questionnaire.
The sleep diary.
Sleep calculations and averages.
Private consultant notes.
The plan and its versions.
02 · The family’s space
A simple, invite-only space shared by both parents—and a grandparent, if needed.
Parents can add it to their phone’s home screen and open it like an app, without downloading it from the App Store or Google Play.
Each family sees only its own child.
How it works
Step 0 · Create a space for the family
The consultant creates a case with the child’s name, date of birth and programme length: 7, 14 or 28 days.
She sends an invitation link. The parent sets a password and confirms their email with a six-digit code.
Step 1 · Get to know the family
The intake questionnaire has five chapters: General, Sleep, Temperament, Expectations and Consent.
Parents answer one question at a time, using answer chips or their own words. Their progress is saved as they go.
Before submitting, they can review all their answers. The consultant then reads the questionnaire chapter by chapter and either marks it reviewed or returns it for changes.
Step 2 · Log sleep with one tap
Parents tap “Fell asleep” and “Woke up.”
The ring turns blue while the child sleeps and warm while awake. A short follow-up asks what helped the child fall asleep: two taps, or Skip.
Both parents see the same timer live. Accidental taps can be undone, and each entry shows who logged it.
Step 3 · Let the diary do the calculations
The diary builds itself, with one line per day running from 18:00 to 18:00.
Using the consultant’s own Excel formulas, the app calculates:
Wake windows.
Naps.
Night sleep.
The longest sleep stretch.
Total sleep over 24 hours.
Averages include only complete days selected by the consultant.
She can review the Durations table on her computer or phone. If a family has a question, “Preview as family” opens their space so she can see exactly what they see.
When she needs a spreadsheet, she can export a real .xlsx file in one click.
Step 4 · Write the plan beside the diary
The consultant writes the plan alongside the diary: a letter to the family, target wake windows and tasks for the week.
Drafts stay private. When she publishes a new version, the family sees it immediately.
Step 5 · Follow progress day by day
The family keeps logging sleep. The week view brings together nights, wake windows against the plan and “before → now” progress as the programme continues.
What it saves
For the consultant
No copying paper diaries into Excel. No manual wake-window calculations. No separate set of files for every client. No chasing photos of diary pages in messengers.
One workspace for all her families.
For parents
No tables to fill in at night.
One tap. One hand. In the dark.
How I built it
Her real materials came first
I started with the consultant’s Google Form, paper diary and Excel spreadsheet.
I worked through every formula, built a test day and checked the app against her spreadsheet, number by number, until the results matched.
Design before code
Before building the app, I created a design system with:
Night and day themes.
One consistent colour rule: blue means asleep, warm means awake.
The night and dawn sky backgrounds are my own images, created with Midjourney.
Built with Base44 and Claude Code
Base44 built the application: the database, authentication, access rules and screens.
Claude Code was my design partner. It helped write the design system and implementation prompts, analyse the spreadsheets and test the live site in a real browser—checking screens, console errors and calculations.
21 batches of improvements
Credits were limited, so I grouped each round of fixes into one structured batch for Base44.
The first working version took 21 batches.
Privacy
Families join only by invitation.
Database access rules restrict parents to their own family’s records. I tested this with a second account.
The consultant’s private notes and unpublished plan drafts remain visible only to her.
All names and data in the demo are fictional.
Current stage and what’s next
This is the first working version.
The next step is for the consultant to start using it with real clients.
Longer term, A Gentle Rhythm could become a platform for other sleep consultants, each with their own practice and families.
Access for judges
1 · Explore as the consultant
Open https://gentle-rhythm-sleep.base44.app and select “Log in.”
Email: usertestanya@gmail.com
Password: Base4444
Open Marta’s case, which includes nine days of diary data.
Explore:
Questionnaire.
Diary, including the star calendar and daily Durations.
Plan, including versions and Write / Preview.
Private Notes.
Try “Preview as family” to see the parent experience, and “Export → Download for Excel” to download the spreadsheet.
2 · Explore as a parent
For the best experience, use a phone.
Open the same website and select “Log in.”
Email: usertestpavlo@gmail.com
Password: Base4444
In Kris family space:
Tap “Fell asleep.”
Choose what helped, or tap Skip.
Tap “Woke up.”
Explore Diary and Plan.
For an app-like experience, add the site to your home screen:
iPhone: Safari → Share → Add to Home Screen.
Android: Chrome → ⋮ → Add to Home screen.
3 · See both sides together
Keep the consultant’s workspace open on a computer and log sleep from the parent account on a phone.
The new entry appears in the consultant’s workspace.
All demo names and data are fictional. Please do not delete the demo family.
Links
So cool project 🚀🚀 good luck 🤞🏻
🏏 BAT RIOT — What if cricket became the ultimate night out?
SWING LOUD. STAY LATE.
For the #Base44Challenge, I wanted to build something that went beyond a beautiful landing page.
The idea was simple: take the energy of cricket, combine it with nightlife, and turn it into a complete digital experience.
Meet BAT RIOT, a Melbourne-inspired social-cricket entertainment platform where competitive games, great food, music, and unforgettable nights come together.
But I didn't want it to just look good. I wanted it to actually work.
Using @Base44, I built an interactive booking experience where visitors can explore venues, check bay availability, select a session, and make reservations.
I also built Party Captain, a group coordination experience for invitations, RSVPs, and guest preferences.
Behind the scenes, there's a staff command centre for managing bookings, scores, and waitlists. The waitlist recovery workflow can automatically generate time-limited offers when a session becomes available, helping reduce manual coordination and recover booking opportunities.
And because the visual experience mattered just as much, I went a step further.
Instead of relying on generic stock footage, I used Google Flow to create custom cinematic scenes—from cricket action and celebrations to venue reveals and food shots. I then edited and optimized the footage to bring the BAT RIOT identity to life across the website.
The goal was to connect design, functionality, automation, and storytelling into one cohesive experience.
This project pushed me to think beyond individual pages and build something that feels like a real product.
And that's what I'm most excited to share.
🌐 Explore BAT RIOT: https://bat-riot.base44.app/
Built with Base44. Cinematics created with Google Flow.
#Base44Challenge #Base44
I can see my friends loving this site. They are cricket fanatic haha.