In the first article, we shared a raw SaaS idea to help WordPress site owners clean up their unused media and cut storage costs — without needing to install a plugin.

Now it’s time to answer a different question:

“If we were actually building this… what would the product look like?”

And more importantly:

What screens would exist, and why?

First Things First: A Wireframe Is Not a Design

Let’s get this clear up front:

Wireframes are not UI design. They’re a tool to explain logic and user flow — nothing more.

We use Balsamiq for this. It’s fast, simple, and ugly by design — and that’s a good thing.

It forces us to focus on function, not visuals.

Wireframes are not for showing “how it will look” — they’re for showing “what it will do.”

If you give a wireframe to a UI designer and say, “make it exactly like this,” you’re doing it wrong.

But if you say, “this is the user journey and what we want to achieve on each screen,” now you’re thinking like a product owner.

The Core User Flow

Here’s what we expect a user to do:

1. Log in or sign up
2. Add a WordPress site using an API key
3. Scan the site to find unused media
4. Review a report showing how much space can be cleaned
5. Clean the junk with one click
6. Choose how (and if) they want us to store deleted files
7. Restore files later if needed

That’s it.

Clean, simple, valuable.

Key Screens We’d Wireframe

Here’s a breakdown of the main screens we’d plan in Balsamiq:

• Home (Logged Out): Explains the product and leads to signup
• Login / Signup Page
• Dashboard (Logged In): Lists connected sites, usage stats
• Add Site Screen: Paste API key and verify connection
• Scan Results Page: “We found 85 GB of unused files”
• Cleanup Confirmation Page: See which files are going to be deleted
• Storage Options: Choose how deleted files will be stored
• Restore Page: Recover files individually or in bulk

Smarter Storage Flow (Automated Lifecycle)

We want to make file storage simple and affordable — without forcing users to micromanage every file.

Here’s how we’d handle it:

• First month of storage is included with the scan.
• If the user continues paying, we’ll automatically move older files to cheaper storage tiers over time.
• After 3 months of no activity, files go to cold storage (e.g., Glacier).
• After 6–12 months, if a file has never been accessed, it goes to deep archive.
• After 1 year of total inactivity, the file is deleted permanently.

We’ll warn users before permanent deletion. But let’s be honest — if no one touched a file for 12 months, it’s probably junk.

This way, users:

• Save money
• Don’t need to manage storage manually
• Can still recover files during a fair window

It’s like having an automatic file decluttering assistant.

What’s MVP and What Can Wait?

We don’t need to build everything at once.

Here’s what’s critical for the MVP:

• Connect via API
• Scan the site
• Show storage waste
• Clean files
• Store files
• Restore files

That’s enough to deliver real value.

Features like:

• Team access
• Scheduling
• White-label dashboards
• Automatic monthly scans…can come later, based on demand.

Closing Thoughts

Planning a SaaS doesn’t start with a fancy UI — it starts with a clear, clean flow.

In this article, we mapped out the core experience of our hypothetical WordPress cleanup tool.

Next time, we’ll talk about pricing, positioning, and how this product could make money.

Stay tuned for Part 3.