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
What it is: RNA Studio Scope (https://rna-scope-flow.base44.app) — a live software project scoping, risk-scoring, and automated client onboarding app built with @Base44.
Who it's for: Startup founders planning a new software build, and freelance developers or agencies scoping client projects.
The problem it solves: Agencies and founders lose days to unpaid discovery calls, vague requirements, surprise scope creep, and manual onboarding setup (writing SOWs, creating Slack channels, and setting up sprint boards by hand).
How it works:
• For Clients (Client Portal View): Pick a 1-click preset (like HIPAA Telehealth or FinTech Treasury) or toggle modules to get an instant week-by-week sprint roadmap and fixed-fee estimate.
• For Agencies (Command Center View): Score client intake risk (0–100), compare in-house hiring burn vs. fixed sprints (-84% cost), and click once to run a 7-step onboarding automation (locking the Markdown SOW brief, provisioning Slack, scheduling kickoff, drafting the Stripe deposit invoice, and seeding Sprint 1).
Built by RNA Tech (https://rnatech.in) #base44challenge
Would love your feedback! When you're scoping a new client build, what takes up more of your week right now — estimating sprint timelines/pricing or setting up the onboarding workflow (SOW, Slack, invoicing, sprint board)? Try the live app at https://rna-scope-flow.base44.app and let us know what you'd add next!
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
Ripcord. One pull for the day you can't go in.
You wake up ill. Client meetings, a deadline, people waiting on you. The worst part isn't the fever. It's the admin.
So I built a cord. Drag it down, say how long you're out, and Ripcord does the rest:
Moves your real Google Calendar meetings to your next free slots
Shifts your deadlines by the days you lose
Writes one short note per client in your voice, sent from your own Gmail
Plans your first morning back
Keeps a receipt for every change. Hold to undo any of it.
Can't face another app? There's an MCP server too. Tell Claude "I've got the flu, clear my week" and it pulls the cord for you.
Built entirely on Base44: entities with owner-only security, 27 backend functions, Google Calendar and Gmail connectors so each user connects their own account, InvokeLLM for the notes, and an hourly workflow for the heads-up and welcome-back emails. I tested it on my own calendar: the meetings moved, the notes landed, and undo put everything back.
The design is a "Signal Room": one glowing red cord on an LED wall. It works on your phone, one-handed, from bed.
Try the demo, no sign-up: https://ripcord.base44.app/demo/week
Great work as always, AJ 😊
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).
Pulen is a take-a-number app for a roti mochi bakery in Bandung. The bakery is fictional, the problem is real: the line starts at 6:40, people wait 45 minutes, and the cheese one sells out before nine.
You fill a box from home and pay, and your number only exists once the card clears, so nobody can hold buns with a fake order. Your paper ticket follows the oven and tells you when to start walking. In the kitchen, every tray of 36 is planned from paid boxes first. Unpaid holds, missed boxes, sold-out flavours and the owner's closing summary with an AI suggestion all run on their own.
If Bandung is asleep when you visit, press "Play the morning" to watch a whole morning in 70 seconds. To try ordering, use the Stripe test card 4242 4242 4242 4242.
Built in Base44 from 12 plain-English prompts.
I'd test the last cheese bun with two payments completing at once. Does Pulen reserve stock during checkout and release it on expiry, or allocate only after payment with a refund path if that flavour has sold out?