Who owns the SOPs PodFleet builds? (And why it matters more than you think)

The short answer: you own them. Every SOP, every dashboard, every automation we build during a PodFleet engagement is delivered to your Notion or Google Drive workspace, owned by you, forever, with no clawback.

The longer answer is why this matters more than it sounds, and how it changes the dynamics of the relationship between you and the provider.

The default in operations outsourcing

Most operations outsourcing providers (BPOs, agencies, fractional executives) treat process IP as their moat. The argument is structural: if they spend 4 weeks building the SOPs for your operation, and you keep those SOPs when you leave, they've handed you the ability to take their playbook elsewhere.

So the default contract terms protect the provider:

• SOPs are stored in the provider's system (their Notion, their internal tools)
• You can “have a copy” on request, often subject to NDA
• Dashboards live in the provider's BI tool, not yours
• Automations run on the provider's accounts (their Zapier, their n8n)

When you leave the provider, you keep your customer data (because that's yours by law) but you lose the operating layer. The next provider has to rebuild it from scratch, taking another 4-12 weeks.

This is the lock-in mechanic that makes most outsourcing relationships sticky. It is not your problem until you want to leave, at which point it is the entire problem.

Ask any outsourcing provider: if I terminate the contract tomorrow, what do I keep? Their answer is the entire honesty test of the relationship.

How PodFleet structures it differently

PodFleet's structural commitment: every SOP, dashboard, and automation is delivered to a workspace you control, from week 1 of the Pod Trial. Not at the end. Not on request. From day 1.

Specifically:

SOPs are written in a Notion workspace you own. We are collaborators with edit access; you are the owner. If you leave, you remove our access and keep the workspace.

Dashboards are built in your tool (Looker Studio, Airtable, Metabase, whichever fits) using your data. We configure them; we do not host them.

Automations run on your accounts (your n8n, your Zapier, your Make). We build the workflows; you own the accounts and the credentials.

Per-client config docs (discussed in the GHL context here) live in your workspace.

This is harder for us operationally. It means our process IP is portable, and a client who leaves can theoretically take our playbook to a competitor or run it themselves. We accept this cost because the structural commitment is what makes the relationship trustworthy in the first place.

Why this matters more than it sounds

Three reasons the ownership question is load-bearing.

Reason 1: trust during the engagement. When you know you can leave at any time without losing the operating layer, you don't have to over-scrutinize every decision. You're not building hostage value with us. The decisions get made on what's right for the operation, not on what's strategically protective.

Reason 2: continuity if we mess up. Operations providers fail. Sometimes we'd be the one failing. If we drop quality, miss SLAs, or just turn out to be the wrong fit, you have a clean exit path. The next provider can be productive in 2 weeks instead of 8, because the operating layer already exists.

Reason 3: the business is more valuable. If you ever sell the business, the buyer is buying an operation. An operation that has documented SOPs, working dashboards, and functioning automations is worth meaningfully more than one that depends on a vendor relationship that may not transfer. Our SOPs become part of your business's asset base.

What “ownership” specifically means in practice

To be precise about what you own at the end of an engagement (whether you leave or stay):

• The Notion or Drive workspace with all SOPs, with you as owner
• The metrics dashboard configured against your data
• The automation workflows running on your accounts
• The per-client config docs (for GHL whitelabel agencies)
• Any custom-built tooling (e.g., Airtable bases, no-code workflows)
• The list of every Pod member who worked on your account (so you can recruit them directly if you want; we don't enforce non-solicits)

What you don't own:

• PodFleet's internal recruiting and training materials (those produced the team but they're our IP)
• Any third-party tool subscriptions we used (you pay for the tools you keep)
• The Pod members themselves (they're our employees, but you can recruit them directly with no restriction)

The line is clean: the operation is yours; the production of the operation is ours.

How this affects the Trial decision

The ownership commitment is also why the 4-week Pod Trial is structured the way it is.

If you complete the Trial and don't continue with the retainer, you walk away with:

• The SOP library covering every workflow we mapped
• The metrics dashboard
• Any automations we configured

That's a real asset. We've had clients complete the Trial, decide not to continue, and use the deliverables as the foundation for hiring an internal ops manager who continues the work. The Trial pays for itself even on a no-conversion outcome, because the documentation has standalone value.

This is the structural backbone of why we can offer the Trial confidently and price it the way we do. We bet that you'll see enough value during the 4 weeks to continue. If we're wrong, you got an operational audit and infrastructure for a fraction of what it would cost to build internally.