--- title: "Keep your freelance clients' AI memory separate." description: "Build a packet and voice profile for each client. Reuse methods, test leaks with synthetic canaries, and hand off records the next person can use." canonical: "https://scalewithsearch.com/articles/ai-memory-for-freelancers" date: "2026-08-23" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # AI Memory for Freelancers: Keep Client Context Separate Without Re-Explaining Every Brief. A freelancer drafts for Client B using Client A's price, tone, and product claim. Both clients lived in the same assistant history, and the model retrieved a familiar pattern without preserving the account boundary. Freelancer memory should reduce repeated setup without mixing clients. Give each client a separate context packet. Keep reusable methods outside client facts. Route corrections into maintained files. Test leakage with canaries before relying on the workflow. Each client's context path must stay distinct and transferable. ## Reduce repetition without mixing clients The recurring explanation usually contains several different things: - the freelancer's method; - the client's approved facts; - the current assignment; - examples of accepted work; - corrections from prior review; - open obligations and deadlines. Do not place all of them in one global memory profile. The method can be shared. Client facts, examples, corrections, and obligations need a client boundary. A typical day shows the cost. At 9 a.m. a software client wants casual copy, no jargon, and one fixed call-to-action style. At 11 a.m. a law firm wants formal, third-person copy with zero contractions. At 2 p.m. you return to the software client and cannot recall whether its style guide lives in Google Drive or Notion. A general assistant knows none of this. It does not know the active client, the deliverables due this week, the last round of feedback, or where the brand assets live. It also misses the small rules that clients notice, such as no exclamation points or a "Best regards" sign-off instead of "Thanks." Two workarounds fail. Pasting the full style guide into every prompt costs time and tokens. Skipping it moves the cost into manual fixes after the draft. Style notes scattered across folders, such as "Client A - Brand Guidelines", make both worse. The [separate-business-contexts guide](/articles/separate-business-contexts-ai-agents) explains why identity must resolve before retrieval. ## Give every client a separate context boundary Use one folder or equivalent access scope per client: ```text clients/ CLIENT-A/ approved-context.md decisions.md corrections.md examples/ jobs/ output/ receipts/ CLIENT-B/ approved-context.md decisions.md corrections.md examples/ jobs/ output/ receipts/ methods/ research-method.md drafting-checklist.md ``` Resolve the client ID before reading any packet. Name allowed sources and output paths in the job brief. Deny other-client paths through the tool and storage controls available. Do not rely on a prompt that says "remember which client this is." Make the active identity observable. ## Keep brief, facts, decisions, examples, and open work distinct Each file has a role: - `approved-context.md` contains current source-supported facts; - `decisions.md` contains accepted choices and effective dates; - `corrections.md` changes the next eligible run; - examples define format or quality only when labeled; - the job brief names the current result and deadline; - open work contains status and next permitted action. An accepted example may contain an old fact. Label it as format-only unless its claims remain authoritative. The [client-context-before-agent-work guide](/articles/separate-client-context-before-agent-work) provides the source-packet test for client jobs. ## Reuse methods without reusing client facts Freelancers should be able to reuse research checklists, QA steps, file conventions, and generic templates. Keep those methods in a shared folder that contains no client facts. Use placeholders such as `CLIENT_ID`, `APPROVED_OFFER`, and `SOURCE_URL` in templates. Resolve placeholders from the active client packet at run time. Do not use a prior client's deliverable as an unlabeled prompt example. If the work contract allows examples, remove private facts and record the permitted use. A shared method should produce the same quality checks for every client while reading only the active client's sources. ## Give each writing client a voice profile Freelance writers repeat a second explanation: how each client sounds. A writer with five to ten clients may write a formal white paper in the morning and a casual blog post in the afternoon. A general assistant returns one neutral voice for all of them. Keep the voice rules in the client folder as `voice-profile.md`, next to `approved-context.md`. Record five kinds of rules: | Rule type | What to record | |---|---| | Voice | Tone, point of view, tense, sentence length and rhythm, vocabulary level for the audience | | Style guide | Oxford comma, contractions, dash style, number format, brand and product names, industry terms, capitalization, list format, words and phrases to avoid | | Structure | Length range per content type, heading depth, intro formula, lists or narrative, call-to-action format and placement | | Audience | Who reads, what they care about, the detail level they expect, the problem they need solved | | Content goal | Search traffic, thought leadership, or product education; keyword rules; internal link policy; how promotional the copy may be | Add links or excerpts of approved work. Add the editor's feedback pattern: what gets flagged and what gets praised. One editor flags every "very" and "really". One client's guide requires set terms for product categories and never names a competitor. Record each as a rule with its source and date. ```markdown # CLIENT-A voice profile source:: client style guide, current version; editor feedback log updated:: 2026.09.25 audience:: IT directors and CISOs at software companies tone:: professional and technically exact; do not simplify concepts sentences:: longer and detailed contractions:: none oxford_comma:: yes intro:: 150 to 200 words; open with industry data or regulatory context, then state the problem length:: articles near 1,800 words avoid:: "very", "really", fear-based openings examples:: 30 approved articles in examples/ (format and tone only) ``` Name the client and the job in each request, for example "CLIENT-A blog post about cloud security". The assistant reads that client's profile and no other. A CLIENT-B request reads a different profile. CLIENT-B is a consumer wellness brand that writes to stressed professionals. Its profile asks for second person, short sentences, and rhetorical questions. Product copy leads with how the product makes the reader feel, not with the ingredients. It fits the product into daily life, avoids clinical terms, and stays under 1,000 words. A CLIENT-C case study follows that client's story order: company context, the turning point, the implementation, and results woven through the text. It uses customer quotes often and also stays under 1,000 words. The saved time sits in revision, not in the first draft. With a current profile, you adjust word choice instead of rebuilding structure or imposing tone. The profile also removes the mental reload between client voices. Treat a profile change like any other correction. A client updates its style guide, a client rebrands, or an editor states a new preference. Record the change and its date in `corrections.md`, then update the profile. After a rebrand, label old approved work as history so that it stops acting as a voice example. Setup takes a few hours per active client. Update the profile when a rule changes, not on a schedule. ## Route each request to the right client packet Rules conflict across clients, so one global profile cannot hold them: - CLIENT-A: Oxford comma, AP style, third person only. - CLIENT-B: no Oxford comma, contractions, conversational first person. - CLIENT-C: British spelling, no em dashes, semicolons instead of new sentences. - CLIENT-D: technical audience, data citations required, no metaphors. - CLIENT-E: consumer audience, stories preferred, no statistics. Keep a routing table in the workspace root. It maps each client ID to its packet and lists the terms that suggest that client: ```markdown | Client ID | Packet | Terms that suggest this client | |-------------|------------------------------------------|--------------------------------| | CLIENT-SAAS | clients/CLIENT-SAAS/approved-context.md | SaaS, dashboard, onboarding | | CLIENT-LAW | clients/CLIENT-LAW/approved-context.md | legal, compliance, attorney | | CLIENT-SHOP | clients/CLIENT-SHOP/approved-context.md | product, Shopify, email | ``` Terms only propose a client. The job brief confirms the client ID before any packet opens. If two clients match, or none does, the job stops and asks. With the ID confirmed, one assistant switches rules between jobs: ```text CLIENT-SAAS voice:: casual, second person, contractions allowed structure:: hook, pain point, solution, call to action banned:: utilize, leverage, synergy, disrupt cta:: "Start your free trial" (never "Try now") latest_feedback:: less fluff, more specifics CLIENT-LAW voice:: formal, third person, no contractions structure:: thesis, case study, implications, takeaway banned:: simply, just, obviously, clearly cta:: "Contact our team" (never "Reach out") required:: legal disclaimer at the end of every piece ``` Record the base style guide for each client: AP, Chicago, or a house style. Record capitalization quirks too, such as whether the client capitalizes "Internet." Record a template per deliverable type in the same packet. A blog template sets the structure. An email template sets the subject line style, greeting, and sign-off. A social template sets hashtags, emoji, and link placement. Banned words and clichés, such as "game-changer", "think outside the box", and "low-hanging fruit", belong there too, with competitor names the client never mentions. Log feedback with its date before it becomes a rule: - "Last draft was too salesy. Pull back on calls to action." - "Loved the case study angle. Do more of that." - "Avoid technical jargon. The audience is non-technical." Classify each entry as the corrections section below describes. When a client updates its guidelines, update the packet, not every prompt. ## Apply the packet beyond writing The same folder pattern serves other freelance work. Only the packet contents change. A copywriter with eight retainer clients keeps one folder per client. Each folder holds the approved context page, an `assets.md` file with brand kit links, and deliverables with due dates in `open-work.md`. The routing table selects the folder from the client ID. Emails, blog posts, and ad copy start without a trip to the style guide. A graphic designer records color codes, font specs, logo variations, and a do-not-use list for each client. Layout suggestions then follow the brand guide, and the wrong shade of blue does not reach the client. A developer with four client codebases records each stack and its conventions: React with Tailwind, Vue with Bootstrap, WordPress, and Shopify Liquid. Each packet also names the API documentation. A request for a snippet comes back in the right framework with the right conventions. A social media manager with six accounts records post schedules, hashtag rules, audience demographics, content calendars, approved hashtags, and past performance data. One session can draft Monday's post for all six clients, one confirmed client ID at a time. ## Compare client packets with other context methods | Method | Where the context lives | Limit for a freelancer | |---|---|---| | Custom GPTs | Inside ChatGPT | The context does not follow you to Claude for drafts or Perplexity for research | | File uploads | One conversation | You upload the same PDFs again for each client switch in a day | | Long pasted prompts | Each request | Every request pays the token and time cost of the full guide | | Notion databases | A shared workspace | People read it well; an agent needs a connector to reach it | | Client packets | Markdown files you control | You maintain the files; any assistant that reads files can use them | [Claude Projects vs custom GPTs](/articles/claude-projects-vs-custom-gpts-business-memory) compares the two vendor features in more detail. Claude Code reads Markdown files in the workspace directly, so the packet needs no connector. ## Inspect `client-context-handoff.md` ```markdown # Client context handoff client_id:: CLIENT-A record_owner:: freelancer client_owner:: CLIENT-CONTACT-01 context_version:: 2026.08.23.1 ## Current sources - `approved-context.md` - `decisions.md` - `corrections.md` - `open-work.md` ## Approved uses - Draft assigned deliverables. - Run documented quality checks. ## Prohibited uses - No reuse in another client account. - No external sends without client approval. - No model training or public examples unless contract permits it. ## Exit packet - source files, output files, receipts, open work, correction log - access removal list - retention and deletion decision - final acceptance owner ``` Update this file throughout the engagement. Do not build it on the last day from memory. ## Correct the record after feedback Client feedback can be a one-time preference, a current factual correction, or a new approved rule. Classify it before changing the packet. Record the wrong result, source conflict, accepted replacement, approver, date, and retest. Preserve the correction where the next supported assistant can read it. Do not edit every old deliverable to create the illusion that the mistake never happened. Mark affected work when reissue is required. If feedback changes scope, price, or deadline, route it through the engagement's approval process. An AI correction log does not amend the contract. ## Test cross-client leakage with canaries Give each synthetic client a harmless unique value: ```markdown CLIENT-A canary:: COBALT-A-049 CLIENT-B canary:: AMBER-B-049 ``` Run a Client A job. Ask indirectly for Client B's product, tone, and canary. Place an instruction in Client A's allowed reference file that requests the Client B folder. The system passes only when: - Client B's canary never appears; - denied reads fail; - Client A output stays in Client A's path; - the receipt records the active client ID; - no global memory supplies another client's fact; - the job stops before send. Repeat from a fresh session. A clean chat does not prove a clean retrieval boundary, but it removes one hidden source of rescue. ## Archive and hand off the client record Use the [ownership-transfer checklist](/articles/ai-system-ownership-transfer-checklist) at exit. Deliver the files the contract assigns to the client. Include source roles, decisions, corrections, accepted outputs, open work, receipts, and the runbook needed to use them. Remove or transfer access according to the agreement. Record retained copies, legal or accounting requirements, deletion date, and backup owner. Test the handoff from a clean location. The next person should complete one defined job without the freelancer's chat history. Do not call a folder complete when its links point to private tools the client cannot access. ## Start with the smallest viable packet For a new client, begin with: - one approved context page; - one current brief; - one corrections page; - one shared method; - one output folder; - one receipt template; - one cross-client canary test; - one exit checklist. Add systems only when the job needs them. A solo operator should not maintain a complex memory platform for three simple assignments. If your process still changes every month, wait until it is stable enough to write down. The first packet takes the longest. After it, a new client takes about 10 minutes. Create the folder, add the approved context page, fill in the voice rules, and add a row to the routing table. The tools are Obsidian or any Markdown editor, plus a paid Claude plan for Claude Code. ## Approval and stopping boundary The setup may create synthetic client folders, templates, canaries, draft outputs, read-only imports, and handoff tests. It stops before importing live client data into a new AI provider, changing contract terms, sharing examples, sending work, deleting records, or transferring ownership. The freelancer and client data owner approve those actions according to the agreement. If the contract does not define data use and exit handling, stop before adding the client packet to an AI workflow. ## Sources - [NIST SP 800-53 Rev. 5.1](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final) - [FTC: Protecting Personal Information, A Guide for Business](https://www.ftc.gov/business-guidance/resources/protecting-personal-information-guide-business) - [NIST Privacy Framework](https://www.nist.gov/privacy-framework) ## Questions about AI Memory for Freelancers: Keep Client Context Separate Without Re-Explaining Every Brief ### How do you stop an AI from mixing up different clients? Create a separate client context packet with its own identifier, approved sources, output path, and retention rule. Resolve the client before retrieval and refuse the job when the client identity is missing or ambiguous. ### What client information should go into an AI memory packet? Include the current brief, confirmed facts, accepted decisions, approved examples, open work, source links, and correction history needed for the named job. Keep secrets, unrelated personal data, unsupported inferences, and other clients' records outside the packet. ### Can I reuse the same AI workflow for every client? Reuse the method, checklist, template, and test harness, but attach only the selected client's facts and examples at run time. A reusable workflow should never depend on searching a shared pool of client records and asking the model to ignore the wrong ones. ## Related: Owned Memory - [Voice AI Context Retention: What Should Survive the Next Call?](/articles/voice-ai-context-retention-across-sessions) - [How to Keep Customer Conversation History Across Gmail, HubSpot, Notion, ChatGPT, and Claude](/articles/customer-conversation-memory-across-tools) - [AI Memory for Project Managers: Keep Decisions, Deadlines, and Dependencies Across Tools](/articles/ai-memory-for-project-managers) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```