External Artifacts
Three Things That Don’t Fit in a Layer
The Blur Framework has four layers: Foundation, Measurement, Action, and God. Each layer has a clear purpose and a clear boundary.
But as you build the system, you’ll notice three critical resources that don’t belong to any single layer - because every layer needs them.
These are the External Artifacts: the SOP Library, Offers, and the Client Library.
They live outside the layer structure because they serve the entire system. They’re the shared infrastructure that everything else depends on.
When Sarah first built her Blur Framework, she kept her SOPs inside her Ops Head. Made sense - most of the SOPs were for client delivery. But then her Marketing Head needed to reference the “client brief” SOP. And her Sales Head needed the “discovery call” SOP. And her Customer Service Head needed the “weekly update” SOP.
She found herself copying SOPs between Heads, and within weeks the copies had diverged. The Marketing team was using version 1.0 of the client brief SOP while Ops was on version 1.3. Nobody knew which was current.
“You need a library,” Jay told her. “One copy. One source of truth. Everyone pulls from the same place.”
That was the moment Sarah understood why external artifacts exist. They’re not “extra” - they’re essential infrastructure.
Artifact 1: The SOP Library
The SOP Library is the centralised collection of every standard operating procedure your business has defined. It is the agency’s operational playbook - and possibly the most valuable asset you’ll build.
If you read the prerequisite article on Systems and SOPs, you already know what an SOP is and how to build one.
The SOP Library is where they all live. One repository. One source of truth. Every project across every Head pulls its SOPs from this single library.
Why Centralisation Matters
When SOPs live inside individual projects or Heads, they fragment. Version 1.2 in Ops, version 1.0 in Marketing, an undocumented variation in Sales.
Nobody knows which is current. Nobody knows when the last update happened. Quality drifts because the instructions are different depending on who’s reading them.
A centralised library eliminates this. One SOP, one version number, one owner. When the SOP gets improved during the monthly review, every future project that uses it gets the improvement automatically.
Key properties: Centralised (one library for the entire business). Reusable (the same SOP can serve multiple Heads). Versioned (track changes over time). Managed by the Founder (at the God Layer). Running projects use the version they started with unless explicitly updated.
Alex’s SOP Library started with five SOPs: client onboarding, LinkedIn content creation, weekly reporting, discovery calls, and client offboarding. That covered about 60% of his work.
Each monthly review surfaced gaps. By month three, he had twelve SOPs. By month six, twenty. By month nine, he had twenty-eight SOPs covering everything from “how to handle a client scope change” to “how to create a case study from a successful engagement.”
The library didn’t grow because Alex scheduled SOP-writing sessions. It grew because the monthly review kept revealing moments where he or his team had to improvise - and each improvisation became a documented process.
Artifact 2: Offers
Offers are your service packages - the things your business sells. Each Offer describes a defined scope of work that you can deliver to a client. They’re the bridge between what clients buy and how your system delivers.
What an Offer Contains
An Offer defines what the client receives, what your agency delivers, the expected outcomes, and the pricing model. It also specifies the SOPs required to deliver it (cross-referenced from the SOP Library) and any standard constraints, timelines, or requirements.
This is where the framework’s pieces start connecting.
Your SOPs inform what Offers are possible - if you have strong SOPs for LinkedIn outreach, content creation, and lead qualification, you can offer a “LinkedIn Lead Generation” service.
And your Offers inform which SOPs are most critical - when you define a new Offer, you identify which existing SOPs support it and whether new ones need to be created.
The Offer Lifecycle
Offers aren’t static. They evolve through the monthly review cycle.
Defined - created based on your capabilities and market needs. Active - available to clients, projects being delivered, performance data being collected. Refined - scope, pricing, or underlying SOPs adjusted based on data. Retired - no longer aligned with the business direction or consistently underperforming.
Rishi started with one Offer: “Brand Identity Package” at $2,500 - logo, colour palette, typography, and a basic style guide. After three months of data, he noticed something: every client who bought the brand identity package also asked for social media templates within two weeks.
So Rishi created a second Offer: “Brand Identity + Social Kit” at $4,000. It included everything from the first Offer plus twenty social media templates. The underlying SOPs were mostly the same - he just added two additional SOPs (social template design and social asset export).
By month six, 70% of new clients chose the premium Offer. Rishi’s revenue per client went up 60% with only 30% more delivery work. That’s the compound effect of well-structured Offers backed by a solid SOP Library.
Artifact 3: The Client Library
The Client Library is your CRM - but not in the way most people think about CRMs. It’s not a spreadsheet of names and emails.
It’s a repository of deep context about each client.
For every client, the library captures: basic information (company, contacts, industry), brand voice and communication preferences, past project history and outcomes, specific requirements and sensitivities, relationship notes and context, standing agreements or special arrangements, and feedback history.
This matters because when a new project starts for a client, the project’s orchestration layer pulls context from the Client Library.
The person (or AI agent) doing the work doesn’t start from scratch - they start with everything the business already knows about this client.
Alex hired a new contractor to handle some of his LinkedIn outreach work. On the first day, Alex dreaded the onboarding - he’d have to explain every client’s preferences, voice, quirks, and history. It usually took a full day of calls and screen shares.
But this time was different. Alex had built his Client Library over the past four months. Each client had a profile with their brand voice guidelines, content preferences, do’s and don’ts, past campaign results, and relationship notes.
He sent the contractor the Client Library access and the relevant SOPs. Two hours later, the contractor sent a draft LinkedIn post for Alex’s biggest client. It was on-brand, on-tone, and hit every preference Alex had documented.
“This is the best onboarding I’ve ever had,” the contractor said.
That moment was worth every minute Alex had spent building the Client Library.
Who Maintains It
The Customer Service Head (if you have one) is the primary maintainer. Every client interaction - onboarding, feedback, requests, complaints - contributes to the client’s record.
If you don’t have a Customer Service Head, the responsibility falls to whoever manages client relationships.
The critical point: the Client Library is not a one-time reference. It’s updated continuously. It persists across multiple projects for the same client.
It gets richer over time. And that richness is what makes every future project for that client smoother than the last.
How the Three Artifacts Connect
The three external artifacts don’t exist in isolation. They form a triangle of relationships that powers the entire system.
SOP Library and Offers cross-reference each other. Your SOPs inform what Offers are possible - you can only sell what you can reliably deliver.
And your Offers indicate which SOPs are most critical - the SOPs behind your best-selling Offer are the ones that need the most attention.
Offers and the Client Library connect through projects. When a client purchases an Offer, a project is created in Ops.
That project pulls the client’s context from the Client Library and the delivery process from the Offer’s associated SOPs.
The Client Library and the SOP Library have an indirect relationship. Patterns across multiple clients - observed during monthly reviews - can inform changes to SOPs.
If three clients have the same complaint about the onboarding process, that’s a signal to update the onboarding SOP.
The SOP Library in Practice
Let’s make this concrete. Here’s what a real SOP Library might look like for a small marketing agency six months into the Blur Framework:
Alex’s SOP Library - Month 6
Client Delivery (12 SOPs)
Client onboarding v2.1 / Discovery call v1.3 / LinkedIn content creation v3.0 / LinkedIn outreach sequence v2.0 / Lead qualification v1.1 / Weekly client report v1.4 / Monthly performance review v1.2 / Client scope change handling v1.0 / Client offboarding v1.1 / QA review for LinkedIn content v2.0 / Case study creation v1.0 / Client feedback collection v1.0
Marketing (5 SOPs)
Blog post creation v1.2 / LinkedIn personal brand posting v2.0 / Newsletter writing v1.0 / Content repurposing v1.1 / SEO keyword research v1.0
Sales (4 SOPs)
Inbound lead response v1.3 / Outbound prospecting v1.0 / Proposal creation v2.0 / Contract and onboarding handoff v1.1
Orchestration (4 SOPs)
Sales-to-Ops handoff v1.2 / Ops-to-Marketing case study trigger v1.0 / Client escalation path v1.1 / Monthly review process v1.3
Finance (3 SOPs)
Monthly invoicing v1.0 / Expense tracking v1.0 / Contractor payment processing v1.0
Total: 28 SOPs. Started with 5. Grew by 3-4 per month through the review cycle.
Offers in Practice
Offers evolve as your SOP Library grows and your understanding of your market deepens. Here’s how Rishi’s Offers developed over time:
Month 1: One Offer - “Brand Identity Package” at $2,500. Logo, colours, typography, basic style guide. Backed by four SOPs.
Month 3: Added “Brand Identity + Social Kit” at $4,000. Everything from the first Offer plus twenty social media templates. Two additional SOPs.
Month 5: Retired the standalone Brand Identity Package after realising 80% of clients wanted the social kit anyway. Replaced it with “Brand Quick Start” at $1,500 - a lighter-touch option for startups who needed basics fast. New orchestration SOP for the faster turnaround.
Month 7: Added “Brand Retainer” at $1,000/month - ongoing social media template updates and brand consistency reviews. Recurring revenue backed by two simple monthly SOPs.
Each Offer change was driven by data from the monthly review. Not guesswork. Not inspiration. Data.
Notice the pattern: Offers don’t stay static. They’re living products that evolve with the business.
The monthly review surfaces what’s working, what’s not, and what clients are actually asking for. Offers respond to that data.
The Client Library in Practice
A Client Library entry doesn’t need to be complicated. It needs to be useful. Here’s what a real entry might look like:
Client Profile: Meridian SaaS
Basic Info: B2B SaaS, HR tech, 120 employees. Primary contact: Jamie Torres (VP Marketing). Secondary: David Chen (CEO, involved in strategy calls only).
Brand Voice: Professional but approachable. No jargon. They hate buzzwords - especially “synergy” and “leverage.” Prefer data-driven claims over emotional appeals. Target audience is mid-market HR directors.
Communication Preferences: Weekly email updates (not Slack). Jamie prefers bullet points over paragraphs. David only wants to see monthly summaries. Response time expectation: 24 hours for non-urgent, 4 hours for urgent.
Project History: LinkedIn lead gen campaign (June-August). Generated 47 qualified leads, converted 8 to demos. They were happy with lead quality but wanted more volume. Currently on Month 2 of expanded campaign.
Sensitivities: Previously burned by an agency that missed deadlines without communication. Proactive updates are critical. If anything is going to be late, tell them first - they’d rather know early than be surprised.
Standing Agreements: 10% discount on annual contracts (agreed with David). Free monthly strategy call (30 min) as part of ongoing relationship.
With this profile, any team member - or any AI agent - can step into work for Meridian SaaS and immediately know the context.
No guessing about tone. No stumbling over communication preferences. No repeating past mistakes.
The Maintenance Rhythm
External Artifacts need regular maintenance. Left alone, they decay - SOPs go stale, Offers drift from market reality, Client Library entries become outdated.
The monthly review cycle handles this.
SOPs: Reviewed Monthly
During every monthly review, the founder evaluates which SOPs are working, which are causing problems, and which need updates.
Signals come from the Measurement Layer (metrics suggesting process issues), escalations (problems that reached the founder), and direct observation.
Offers: Reviewed Monthly
Which Offers are selling? Which ones have the highest client satisfaction? Which ones are the most profitable? Which ones are underperforming?
The data from the Measurement Layer drives Offer refinement - adjusting scope, pricing, or underlying SOPs.
Client Library: Updated Continuously
Unlike SOPs and Offers (which are reviewed on a cadence), the Client Library is updated continuously. Every client interaction adds context. Every project adds history. Every piece of feedback gets logged.
The Customer Service Head - or whoever manages client relationships - keeps this current as a natural part of their work.
Think of it this way: SOPs and Offers are strategic assets that evolve monthly. The Client Library is an operational asset that evolves daily. Both are critical. They just operate at different speeds.
The Mistakes That Fragment Your System
Mistake 1: Duplicating SOPs Across Heads
The moment you copy an SOP into a specific Head instead of referencing the library, you’ve created a fork. That fork will diverge. Within weeks, you’ll have two versions of the same process.
Centralise everything. Reference, don’t copy.
Mistake 2: Offers Without SOPs
Sarah got excited about a new service idea - “AI Code Review” - and started selling it before she’d built the delivery SOPs. The first client loved the pitch. The delivery was chaos. Sarah’s team had no process for AI code review, so they improvised. The result was inconsistent, late, and below the quality standard her other Offers maintained.
“Never sell what you can’t systematically deliver,” Jay said. “Write the SOPs first. Then create the Offer. Then sell it.”
Sarah rebuilt the Offer with proper SOPs, and the second client had a completely different experience.
Mistake 3: Ignoring the Client Library
The Client Library feels like busywork - until a contractor makes a mistake that the library would have prevented. Until a client gets the wrong tone in a deliverable. Until you lose a client because nobody remembered their sensitivity about missed deadlines.
The library is insurance against institutional amnesia.
Mistake 4: Treating Artifacts as Static
SOPs that don’t evolve become obstacles. Offers that don’t adapt lose market fit. Client profiles that don’t update become misleading.
The monthly review cycle exists specifically to prevent this. Use it.
The Key Principle
External Artifacts exist outside the layers because they serve the entire system, not just one part of it.
Keeping them separate prevents duplication - one SOP Library, not one per Head. It ensures consistency - one Client Library, not one per project.
And it makes maintenance centralised - the founder manages SOPs and Offers from the God Layer, and the Customer Service Head manages the Client Library from the Action Layer.
The layers are the architecture. The External Artifacts are the infrastructure. Without them, the layers have nothing to run on.
The Complete Picture
With the External Artifacts, you now have the full Blur Framework: four layers (Foundation, Measurement, Action, God) and three shared resources (SOP Library, Offers, Client Library).
Together, they form a complete operating system for a service business.
The Foundation tells you who you are and why the business exists. The Measurement Layer tells you where you’re going and how you’ll track progress. The Action Layer does the work. The God Layer designs and tunes the system.
And the External Artifacts - the SOPs, Offers, and Client profiles - provide the shared infrastructure that makes it all run.
The next step is yours. Build the first layer. Write the first SOP. Define the first Offer.
The framework isn’t a theory to admire - it’s a system to build. And the best time to start is before you need it.
Ready to Build Your System?
You’ve now seen every component of the Blur Framework - the four layers and the three External Artifacts.
The BlurOps Bootcamp takes you through building each piece, step by step, with AI-first tools and hands-on implementation. Stop reading about systems. Start building yours.
BLUROPS.COM
Start From the Beginning
Systems, SOPs & Processes