Mile-High Rebuild: I Ditched a $400/Month SaaS Portal Somewhere Over Kansas
Photo: San Diego Air & Space Museum Archives, Public domain, via Wikimedia Commons
There's a particular kind of clarity that comes from being trapped in seat 24C with nothing but a half-charged laptop and a grudge against your monthly software bill.
Mine was a $400/month client portal — the kind of polished, white-labeled SaaS tool that freelancers across the country pay for because it makes them look bigger than they are. It handled file sharing, project status, invoices, and client messaging. It also handled $4,800 a year of my revenue, which felt increasingly hard to justify for a client roster of seven people.
So on a Tuesday flight from O'Hare to Denver, I decided to rebuild the whole thing in no-code. This is the unfiltered audit.
The Setup: Softr + Airtable, Budget Airline Edition
I'd used Softr before for a landing page, so I knew the drill: Airtable as the backend, Softr as the front end, and enough patience to wire them together without a second screen. Total tooling cost? Softr's $59/month plan plus an Airtable seat I already had. Call it $70 all-in against $400 out.
The first forty-five minutes went suspiciously well. I cloned my portal's core structure — clients, projects, files, invoices — into Airtable before the drink service reached my row.
What Broke First: File Previews
Around the Missouri border, I hit wall number one. My old SaaS rendered PDFs and images inline, beautifully, right in the client dashboard. Softr's list details block? It shows a download link. That's it. Clients click, they download, they open it themselves.
Is that a dealbreaker? Honestly, no. Is it a downgrade my clients noticed within a week? Absolutely yes. My workaround was embedding a Google Drive folder view on a per-client page, which restored previews but added a second login surface — and one client immediately asked why she now needed "two places."
What Broke Second: Permissions at Scale
Here's the thing nobody tells you about no-code client portals: row-level permissions are the entire game. My old tool handled access control invisibly. In Softr, I spent the flight's final hour wrestling with filtered pages and logged-in user conditions, making sure Client A couldn't stumble into Client B's invoices.
It works now. But I tested it the way you test a smoke detector — nervously and more than once. If your freelance practice touches anything sensitive (contracts, financials, HIPAA-adjacent health work), budget a full weekend for this section, not an in-flight sprint.
What Broke Third: My Ego, Via Client Messaging
The old portal had threaded client messaging. My rebuild uses a comments-style Airtable synced block, which is... functional. Clients can leave notes. Nobody's confused. But it lacks the notification polish that made the old tool feel like a real product, and one client told me the new setup feels "simpler" — which I've chosen to hear as a compliment.
The Actual Math
Let's talk numbers, because that's why you're here:
- Old SaaS: $400/month = $4,800/year
- New stack: ~$70/month = $840/year
- Annual savings: roughly $3,960
- Time invested: about 5 hours on the flight, plus 3 hours of cleanup and permissions testing that week
At a conservative freelance rate of $75/hour, the build cost me around $600 in billable time. The break-even point lands about two months in. Every month after that is profit.
Who Should Make This Move — and Who Shouldn't
If you're a solo operator with under fifteen clients and a portal doing basic file-sharing, status updates, and invoicing, the no-code rebuild is a no-brainer. The savings are real and the capability gap is smaller than vendors want you to believe.
If you need airtight audit trails, e-signatures, or compliance certifications, stay put. No-code gets you 85% of the way there for 20% of the cost — but that last 15% is exactly what enterprise SaaS is selling.
My portal has now been live for six weeks. Zero client churn, one mildly confused onboarding email, and a subscription I canceled from the baggage claim at DIA. Sometimes the best product decisions happen at 35,000 feet, mostly because there's nothing else to do.