Sirv Studio includes a DAM, product data, supplier intake, workflows, an API and an MCP server. I built the first version of that scope in seven months. A competitor can use the same tools.
The quarterly rule
Fast implementation cuts both ways. A tool, screen or integration that took my agents a month can take another team a month too.
That led to one rule in Studio’s strategy notes:
Anything an agent fleet can rebuild in a quarter is not a moat.
Features still matter. Customers need the product to work. A feature list just won’t protect the business for long.
What can protect it is anything that takes calendar time or other people’s participation. None of what follows is proven yet. It’s what Studio has to accumulate, and the rest of this post is how I plan to find out if it does.
Apply the rule to Studio
Copyable in quarters
- AI tool count Most tools call models available to competitors.
- Workflow step types Useful, but straightforward to reproduce.
- UI polish Necessary for sales and use, but visible to anyone.
- MCP support A protocol implementation, not a lasting advantage.
- Model access and prompts Mostly rented from the same vendors.
Takes real time
- Operational history Approvals, publishes, rollbacks and supplier submissions.
- Product relationships Assets, variants, channels and their current state.
- Supplier participation People who already know and use the workflow.
- Safety record A history of correct changes to live stores, still to be earned.
- Direct distribution Customer relationships and channels the business controls.
What takes time
Operational history answers questions a fresh competitor cannot answer. What was live during a sale? Who approved an image? Which supplier repeatedly fails the same check? That history only appears after people use the system.
Product relationships are valuable only when they stay accurate. If Studio’s product and asset data drift from Shopify, the same data becomes a liability. That makes sync and drift detection real product work.
Supplier participation can create a network effect. A supplier who already serves several merchants through Studio makes the system easier for the next merchant to adopt. This works only if the supplier experience is fast and clear.
A safety record cannot be generated on demand. Any competitor can write “safe publishing” on a landing page. A history of correct publishes and tested rollbacks takes time. One destructive incident can damage it quickly.
Direct distribution gives the team time to keep building. Search rankings, store listings, customer relationships and referrals take longer to earn than a feature takes to copy.
The decision it changed
The July action plan put a freeze on new tools, channels and workflow step types unless an exception was explicitly approved. It gave priority to getting ten merchants through a complete loop: connect a catalogue, run a fix, review the result and publish.
The same plan said to measure time to first approved publish and operator hours per merchant. Those two numbers say more about whether Studio is useful than any amount of code.
The cost was real. Features I wanted stayed on the list while the team did boring work: limits, onboarding and verification. And a freeze on paper only works if someone enforces it.
Rules for product work
Record history when the event happens. Approval, lineage, supplier provenance and publish state belong in the data model. Missing history cannot be reconstructed later.
Make export easy. Customers should be able to leave with their data. The reason to stay should be the working system around that data, not fear of losing it.
Prefer repeated use over another feature. Ten merchants running the complete workflow every week creates more useful evidence than ten new tools nobody uses.
Measure what is accumulating. Every quarter, check if usage, history, supplier participation, safety and direct distribution grew.
| What to track | What it would test |
|---|---|
| Workspaces with 90-day history | Whether useful records accumulate through repeat use |
| Products under management | Whether product relationships remain useful at scale |
| Suppliers working across workspaces | Whether participation extends beyond one customer |
| Incident-free publish runs | Whether the safety claim survives repeated operation |
| Organic funnel entries | Whether distribution brings relevant users |
Challenge each claim
These advantages are not permanent.
- Operational history can be attacked by better import tools.
- Product relationships can be replaced if Shopify exposes richer data.
- Supplier participation can move to a supplier-first competitor.
- Distribution can disappear after an algorithm change.
- The safety record can be damaged by our own mistake.
So I keep asking one question: if a competitor matched every feature tomorrow, why would a customer stay?
Right now, one enterprise supplier workflow runs on Studio in production. That’s a start. The network effect, the retention and the safety record are still ahead of us.
Related: The programmer who stopped typing and the Sirv Studio case study.