Every tool I’ve ever used to run a creative business felt like it was built by someone who had never run one.
You can tell immediately. The CMS platform that handles client delivery beautifully but can’t take a payment. The website builder that looks great until you try to attach a shop. The course platform that sits on a completely different domain from your main portfolio.
Each one solves a single problem and leaves you with three new ones: extra logins, stacked monthly subscriptions, and hours spent acting as the glue between disconnected software instead of doing actual work.
I spent years living inside that patchwork. I didn't stay in it because I lacked options; I stayed because I knew every alternative was just a different set of trade-offs.
Two disciplines, one blind spot
I trained as a software architect before I picked up a camera seriously.
Software architecture is about designing systems. How data flows between services, where state is managed, how domain boundaries are drawn, and how components scale together. Every structural decision impacts the whole system. A flawed data model at the core doesn't just affect one feature; it creates technical debt across every integration downstream.
Photography taught me something different: that the work only matters if it reaches people. You can make the most technically perfect image in the world, and if it lives on a hard drive, it might as well not exist. Getting work in front of clients, delivering it professionally, selling it — that's not separate from the creative practice. It is the creative practice, for anyone trying to build a sustainable business around it.
For years, my biggest blind spot was assuming that creation and operation required entirely different systems.
They don't. They never did.
The Tuesday
It didn't start as a grand vision—it started on a regular Tuesday afternoon.
A client had just approved their final gallery. I needed to send them the high-resolution files, set up a print order for the wall art they’d requested, and invoice them for the remaining project balance.
It should have taken fifteen minutes. Instead, it took two hours of logging into four separate platforms, manually exporting files across services, and cross-referencing a payment received in one dashboard against an order created in another.
I sat at my desk afterward calculating how many Tuesdays I'd lost to that exact loop, and how many other studios were losing the same time. Brilliant creators were running their businesses on willpower and brittle workarounds—not for lack of skill, but because the software available to them was never designed to share a single data model.
That afternoon, I opened a blank document and listed what a platform would actually need to do to fix that workflow.
Building a System
The list of requirements I wrote down that Tuesday was long because the issue was structural.
A creative business isn't just a website. It’s a unified media library that feeds your portfolio, client deliveries, store items, and course materials from a single upload. It’s a client portal that shares the same authentication and asset pipeline as your main site. It’s commerce that natively understands print fulfillment, digital downloads, and subscriptions without requiring third-party checkout redirects or complex Zapier webhooks.
Most SaaS platforms try to solve this by gluing separate tools together through APIs and webhooks. But integrations are brittle. When underlying software tools don't share a core data model, you end up with sync errors, redundant logins, and broken state.
What I wanted to build with ArtInStack was a platform where those domains connected architecturally from day one. Sharing a single source of truth for assets, identity, and commerce.
Reducing the Operating Overhead
Running a studio alone or with a small team brings a specific kind of fatigue. It isn't the fatigue of making the work. That's the part most of us would do regardless. It's the friction around the work: the chased invoice, the broken download link, the third-party storefront that clashes with your visual identity, or the manual file exports required for every print order.
Individually, those friction points are minor annoyances. Multiplied across years, they become a heavy tax on energy and focus.
The objective behind ArtInStack was simple: eliminate that administrative overhead. When delivery, commerce, education, and client portals share the same backbone, you spend your energy on the work itself and the clients you serve.
Form Follows Function
In architectural studios, "form follows function" is often misinterpreted as "don't decorate." What it actually means is that the shape of a structure should emerge directly from its purpose.
We applied that principle to every technical decision in ArtInStack. Instead of asking how to plug a generic shop into a site builder, we asked what commerce should look like when it natively communicates with a media library, a portfolio, and an asset delivery system.
When software is built from that foundation, the result isn't a bundled stack of separate tools. It's an integrated system where every component knows about the rest.
Where ArtInStack Stands
ArtInStack is live and actively used by photographers, studios, and educators.
The core infrastructure. The page builder, media library, client delivery portals, native commerce, courses, and team spaces is operational and connected. We're continuing to expand deeper analytics, automated workflows, and multi-brand controls, with our technical roadmap documented publicly on our site.
That two-hour Tuesday workflow that started this project? It takes fifteen minutes now.
ArtinStack is a platform for photographers, studios, and creative businesses. If you're running your business across six tools and wondering if there's a better way — there is. Explore the platform →