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
A faceless YouTube video still needs a voice. Sometimes an entire cast.
I built Voilà Studio on Base44 to make that production process easier.
Start with a topic or your own script. Assign voices to speakers, add sound effects and generate the conversation.
Need to change a sentence? Edit that line and regenerate just that take.
My main design decision was to make the script the workspace, keeping speakers, dialogue and sound cues together.
The walkthrough shows the result, from episode creation to playback, alongside text-to-speech, voice cloning and mobile access.
Built for creators making quizzes, mysteries and conversations.
#Base44Challenge @Base44
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
CutDesk — the client side of editing, handled
A client portal for freelance video editors that turns a brief into a quote, a review link and an invoice on its own, so the editor only edits.
I'm Muse, a freelance video editor in Lagos (reels, YouTube long-form, podcast clip packs, promo ads). Every job I've done ran over WhatsApp and X DMs: I retyped quotes by hand, counted revision rounds in a chat thread, answered "is it done yet?" and chased invoices. CutDesk is the portal I built on Base44 so that part runs itself.
What it automates
• Brief in, quote out. A public brief form prices the job live from my rate card as the client types (format, quantity, captions, extra raw footage, and a 1.5x rush multiplier under 48 hours). Submitting it creates the client and the project, sets the deadline and issues a quote page the client approves with one tap.
• Review links with timecoded notes. Every cut gets a public review link, no login. The client scrubs the cut, leaves notes at exact timecodes, and either requests changes or approves. "Request changes" burns one of the included revision rounds and moves the job back to editing; a round past the included two is priced automatically.
• Invoices that write themselves. "Approve this cut" issues a numbered invoice with 7-day terms, a printable page and a mark-as-paid flow. Overdue invoices flag themselves on the desk.
• One desk for the studio. A six-stage pipeline (brief, quote, edit, review, delivered, paid), due-next countdowns, reminders generated from the live data, and an activity trail per job.
Time saved per client job (my own estimates from how my jobs run today, not measured in a study)
• Quoting: about 20-30 minutes of back-and-forth per job becomes zero; the client sees the price while filling the brief.
• Revision tracking: about 10-15 minutes per round spent collecting feedback from voice notes and screenshots, and arguing about which round we're on, becomes a list of timecoded notes with the round already counted.
• Status chasing: about 10-15 minutes per job of "is it done yet?" messages disappears; the client has the link.
• Invoicing: about 15-20 minutes per job of writing, sending and chasing the invoice becomes one click on the client's side.
Roughly an hour to an hour and a half saved per job, and the parts that used to get lost in a chat thread (the quote, the notes, the round count, the invoice) now have one place.
How it was built on Base44
Built from scratch in a day in the Base44 editor. Base44 entities hold the clients, projects, quotes, review notes, invoices and activity; the pricing, round counting, invoice numbering and reminders are app logic on top of them. The design is a custom system I specified prompt by prompt: Instrument Serif for display type, Inter Tight for the UI, JetBrains Mono for every timecode and amount, a near-black "cutting room" palette with one record-light orange, and a playhead motif that carries the project's stage through the whole product (the landing hero scrubs itself through the six stages, every desk card carries a mini scrubber, and the client's notes sit as markers on a real scrubber under the video). Mobile-first on every page: a bottom tab bar on the desk, a sticky estimate bar on the brief, sticky actions on the review page.
The demo workspace is open: submit a brief, leave a note on the Nova Fitness cut, approve it and watch the invoice appear, mark it paid. Demo footage is royalty-free from Pexels.
Links
• Live app: https://cutdesk.base44.app
• Walkthrough video: attached (and on X)
Music: original track made with Eleven Music (ElevenLabs).
I built Motif because a film's look usually lives in scattered screenshots and notes, and a proper lookbook takes days. Paste a scene, choose a tone, and Motif returns a printed treatment: five colours, three motifs, six film references with a reason for each, lens and light notes, and margin notes against your own lines. Same As What?, a 77 second essay film made from 147 words, is the seeded example, so judges can see a finished lookbook before generating anything. Built with Base44, no images generated.
this is an excellent idea!
Loopwise — Every Complaint Deserves a Resolution 🚀
Turning customer complaints into clearer workflows and better customer experiences.
🔗 Live Product: https://loopwise-app.base44.app
🌐 Follow the Build
LinkedIn: https://lnkd.in/p/dxHKFiw3
Built with Base44 for the #Base44Challenge.
💡 The Vision
Every business receives customer complaints. The real challenge is making sure those complaints are seen, understood, and followed up on.
That's why I built Loopwise — a customer feedback and complaint management platform designed to bring customer submissions and case management together in one organized workspace.
My goal is to make the journey from a customer's problem to a team's next steps clearer, simpler, and more manageable.
🎯 The Problem I'm Solving
Customer complaints can become difficult to manage when information is scattered, context gets lost, or teams lack a consistent process for follow-up.
Businesses need more than a place to receive feedback. They need a structured way to review issues, prepare responses, preserve important information, and work toward resolutions.
Loopwise is my attempt to make that workflow simpler.
✨ What Loopwise Offers
📥 Smart Inbox
A centralized place for teams to review incoming customer complaints.
📝 Public Complaint Form
A straightforward customer-facing experience for submitting issues and feedback.
🏢 Dedicated Business Workspaces
Workspace setup with a company name, logo, and industry context.
📋 Case Management
An organized view of individual complaints and the information needed for follow-up.
💬 Response Drafts
Prepare and save customer replies directly within the case workflow.
🗒️ Internal Notes
Keep important context and follow-up instructions available to workspace members.
Each feature supports the same objective: helping teams move from receiving a complaint to managing the next steps.
🛍️ The Demo: A Realistic Customer Scenario
For my walkthrough, I created a fictional e-commerce business called NovaCart.
Imagine a customer receives a damaged product. They submit a complaint through the public support form. The NovaCart team can then locate the submission in the Smart Inbox, review the case, prepare a response draft, and document the next steps using internal notes.
The workflow is simple:
Collect → Review → Respond → Follow Up
This scenario demonstrates how Loopwise connects the customer-facing experience with the team's case-management process.
🎨 Design & Development
I built and published Loopwise using Base44, focusing on both the product's visual identity and its core workflow.
The interface combines a deep navy background, electric-lime accents, consistent branding, and a modern SaaS-inspired layout.
Rather than building only a landing page, I wanted to create a working product experience that connects customer complaint submission with the tools a team needs to review and manage cases.
🚀 What's Next?
Loopwise is a work in progress, and I see opportunities to make it even more useful.
My next priorities include:
More reliable workflow automation.
AI-assisted complaint classification and prioritization.
Further mobile usability testing.
More complete customer email integration.
These are planned improvements, and I'm continuing to develop the product toward that vision.
💚 The Takeaway
Loopwise started with one simple idea: a customer complaint shouldn't get lost in the process.
I built it to help businesses bring customer issues into focus, organize their cases, and make the next steps easier to manage.
I'm excited to share what I've built with Base44 and continue improving it.
Loopwise — Every complaint deserves a resolution.
Built with @base44
Navy and lime look sharp. Which feature are you building next?