We didn't build Creatr as a file storage app. Here's why.

The storage glut nobody needed

Walk into any freelancer's phone and you'll find the same pattern: Dropbox open in one tab. Google Drive in another. An email with client files attached. A Slack message with a reference image. Notes scattered across Notes, Notion, and three different project boards.

When we first sketched Creatr, we thought, 'Well, creatives need to store files, so we'll build that.' Standard thinking. Sensible, right?

But as we talked to photographers, designers, and videographers, something became clear. They didn't actually want another storage vendor. They wanted to stop juggling eight apps to run a single project from start to invoice. Storage was just one piece of the friction.

A designer might upload a mood board to Dropbox, email a contract in PDF form, invoice through Wave or Stripe, and track the project status nowhere at all. Then complain that they had no visibility into what was outstanding.

Building around the actual job

So we asked a different question: What if we built around how creatives actually work?

Not how enterprise teams manage assets. Not how corporate departments track workflows. But how a solo photographer runs her business from her phone at 9pm after a shoot.

She takes the photos, she curates them into a project, she sends selected files to the client, the client reviews and approves, she invoices them, they pay via card. Done.

That's the loop we optimised for. Projects. Portfolio. Client delivery. Invoicing. Contracts. Mood boards. All in one app. All designed so a single person could run it solo.

The storage part? It became less important once we handled the actual business flow. You don't need to rent storage from us when you already have Google Drive or Dropbox. In Studio tier, we let you bring your own. OneDrive. iCloud Drive. Whatever you already pay for. The app handles the orchestration. You keep the files where you choose.

A moment that clarified everything

Launch week. A Studio user messaged: 'I linked my Dropbox and it just works. I invoiced a client, they paid in Stripe, and I downloaded the receipt directly from Creatr. No switching apps.'

That single message told us we'd made the right call. Not because we'd built clever storage technology. Because we'd solved a different problem: the friction of the workflow itself.

The same user could have set up Dropbox plus Stripe plus Wave, linked them with Zapier, and fiddled with automations. Instead, she opened one app on her phone and finished a client job.

That's what 'bring your own storage' meant in practice. Not a clever feature. Permission to use what you already have, integrated into the one place you actually run your business from.

What we learned about 'features'

Here's something nobody talks about in indie app building: adding a feature because it sounds standard is a trap.

Every app has file storage now. So our first instinct was to have it too. But we realised we'd be competing on the one thing we'd lose at: Dropbox has better syncing, cheaper per gigabyte, and a decade of trust. We'd never win there.

Instead, we built something they can't: Creatr knows you're a photographer because you have a portfolio. It knows this project is a wedding because you tagged it that way. It knows you invoiced the client because the payment landed in your Stripe account. That context matters.

A mood board isn't just a folder with images. It's a client brief, tied to a project, attached to an invoice, with download analytics so you can see which concepts the client actually looked at.

A contract isn't a PDF you email back and forth. It's templated, signed, versioned, and stored where you choose. That integration only works if you're not trying to be a storage company.

The creatives we actually built for

Creatr is for people who run their creative business from a phone. A photographer on a shoot. A freelance designer between client calls. A videographer editing captions before uploading.

Not for teams with IT departments. Not for studios with dedicated project managers. Solo creatives and small studios. That's the constraint that shapes every decision we make.

When we built the Studio tier, we added custom domains and download analytics because photographers asked about it. They wanted to send clients a branded link, not a generic share. They wanted to know which image the client spent time looking at. That's when we knew we were building the right thing.

By year two, we added things like Google Calendar sync and white-label portals in Pro because the solo creatives who paid for Studio started hiring. They needed to show clients a branded experience without losing the phone-first workflow they already loved.

Every feature maps back to something a real person asked for, not to something a feature checklist demanded.

The trade-off we made

There's a choice every indie app builder faces: Try to be everything, or be the best at one thing for one type of person.

We chose the second. Creatr won't ever be a full CRM. It won't edit video or compose music. It won't manage a distributed team across timezones.

But for a solo creative? For someone juggling six apps and wanting one place to manage a project from beginning to payment? That we do better than anyone else.

The storage question was really about this choice. Saying 'no, we won't build storage from scratch' meant we could say 'yes, we'll integrate the storage you already trust.' It freed us to focus on the bit only we could do well: understanding how creatives actually run their business.

That decision still guides what we build. Every feature we add passes one test: Does it solve a specific pain point for a solo creative? Or is it just adding complexity?