The storage decision we almost got wrong

The first instinct was always to build

When you're building a business operating system for creatives, the temptation to own every layer is real. We thought about S3 buckets, about tiered storage limits, about the infrastructure we'd need to scale. We'd have control. We'd differentiate. We'd have a moat.

What we didn't have was clarity on what problem we were solving. Creatives don't wake up thinking, 'I wish someone else would host my files.' They wake up thinking, 'I have files everywhere. Google Drive, Dropbox, OneDrive. My client just sent me raw footage on iCloud. How do I make sense of this?'

We were about to spend engineering effort and operational overhead on something the market was already solving better than we ever could. The real problem wasn't storage. It was connection.

Talking to people who actually use the app

We ran a lot of user testing before launch. Not the formal kind with a script and a lab, but real conversations with photographers, motion designers, illustrators during their actual workflow. One designer told us she spent forty minutes a week just moving files between apps because none of them knew where her deliverables lived. Another photographer said she'd abandoned three different tools because they wanted her to upload everything again instead of just pointing to where she already kept things.

The pattern was clear. These people had storage sorted. They didn't need another silo. They needed visibility. They needed a central place where Creatr could talk to wherever they actually kept their work. Dropbox for one client's files. Google Drive for another. OneDrive for internal templates. iCloud for quick captures on the phone.

Once we heard that enough times from enough different people, the decision became obvious.

What we built instead

Bring-your-own-storage isn't a compromise. It's the right solution for this problem. In Creatr's Studio tier and above, you connect to your own Google Drive, Dropbox, or OneDrive account. On Pro, you can also use iCloud Drive. Once connected, Creatr becomes the interface. You upload deliverables to your client directly from the app. You pull in files from your storage to build mood boards. Everything stays encrypted in the cloud service you already trust. We never touch it.

The infrastructure question became simpler. We don't need to be a storage company. We need to be the orchestration layer between Creatr's features and wherever someone keeps their work. That's a completely different problem to solve, and it's one we're good at.

The business case made sense too

From a business perspective, BYOS lets us scale without scaling server costs. A photographer in London uploads 50GB of work. That lives on their own drive. We don't pay for it. We don't manage it. We don't worry about it. What we do manage is the relationship between that file and Creatr's project management, invoicing, client delivery, and analytics features. That's where our value lives.

For creatives, there's no lock in. They're not trapped with us because their files are scattered across our infrastructure. Their files live where they always lived. They choose to stay with Creatr because it works better. That's a healthier relationship.

What we learned from a decision we almost didn't make

This is the lesson that stuck with me: the smartest technical decision isn't always the one that gives you the most control. Sometimes it's the one that says, 'This part is someone else's job.' We got that one backwards at first.

If we'd spent six months building and maintaining a proprietary storage backend, we'd have less time to build the features that actually matter. Better invoice reporting. Client delivery that doesn't require a download link pasted in an email. Portfolio analytics that show which pieces drive the most interest. Those are problems only we can solve because they're specific to how creatives run their businesses.