Surge Cost Architecture V2 — Compression Model

The Four-Layer Cost Model

1
Time Backbone
Blue Ocean + Surge
97h atomic baseline
from 179 parsed items
2
Compression Coefficient
Team Lead
0.6× – 1.0×
based on practitioner skill
3
Rate Variable
Kalyn / CEO / Accounting
$/hr per role
NOT set by us
4
Value Markup
Sales
What the market bears
Separate from cost

Master Formula

Total Cost = labor cost + software cost

Labor cost = (time backbone × compression) × rate

Software cost = Surge scans + crawler license + API credits + platform fees (does NOT compress)

Price = total cost × value markup

Entity = (97h × coefficient × rate) + software line items

+ Keywords = (20h × coefficient × N pages × rate) + (per-scan cost × N)

We own Layers 1 + 2. Accounting owns Layer 3. Sales owns Layer 4. Software is a separate fixed line.

Select Practitioner Tier

Who is doing the work? Click to see compressed estimates.

Junior / First Time

1.0×

No compression. Following the blueprint for the first time. Every step is new. This is the atomic baseline — the "worst case" that guarantees nothing is missed.

Entity: 97h · Per page: 20h

Experienced Practitioner

0.7×

Has done 5+ entity optimizations. Knows to batch schema work in one sitting, GBP tasks in one session, content writing in focused blocks. Nearest-neighbor compression is natural.

Entity: ~68h · Per page: ~14h

Expert with Templates

0.6×

Has personal templates for schema, FAQs, GBP optimization. Runs Surge scans in sleep. The blueprint is a checklist, not a learning exercise. Maximum nearest-neighbor + context compression.

Entity: ~58h · Per page: ~12h

Entity Base (Compressed)

97h68h

Brand query · one blueprint

Per Keyword Page

20h14h

Additional per target page

10 Keyword Pages

297h208h

Savings: 89h

Compression Savings

30%

~89h saved on 10-page engagement

Hospital Items

Diagnostic — not compressible

Task Items

138

Compressible via clustering

Three Types of Compression

Type 1: Nearest-Neighbor

Same file / same dashboard

Schema blocks in the same <head>. GBP tasks in the same dashboard. Meta title + description on the same page. You're already there — the second item takes less time because there's zero navigation cost.

40–50% on cluster

Type 2: Mental Context

Same domain expertise

A Dev-SEO doing six schema tasks in a row is in "schema brain." No context switching. Batching by role and skill type eliminates the cognitive ramp-up between dissimilar tasks.

15–25% on batch

Type 3: Template Reuse

Keyword pages 2–10

First keyword page FAQ set = 4 hours from scratch. Pages 2–10 adapt the pattern = ~2 hours each. Schema blocks are copy-paste-modify. QA checklist is faster after first pass.

20–30% on subsequent pages

Nearest-Neighbor Clusters (Where Compression Happens)

These clusters group items that share a physical location (same file, same dashboard, same platform login). A skilled practitioner does them in one sitting. The atomic total is what V1 estimated. The compressed total is what actually happens when you batch them.

Role Breakdown: Atomic vs Compressed

Role	Entity (Atomic)	Entity (0.7×)	Entity (0.6×)	Per Page (Atomic)	Per Page (0.7×)	Per Page (0.6×)	Why Compressible

The Per-Page Multiplier (All Tiers)

Scope	Junior (1.0×)	Experienced (0.7×)	Expert (0.6×)	Savings vs Junior

What Is NOT Compressible

Health check items (41 total) — diagnosis takes the time it takes. You can't speed up reading Surge scores or verifying GBP status. The measurement is the measurement.

Business Owner verification — confirming addresses, license numbers, warranty terms. These require human knowledge that can't be templated.

Creative production — filming video, recording audio. Setup + retakes + editing have hard physical floors. A 4h video estimate might actually be 6-8h in reality.

Review responses (406 reviews) — each review needs a genuine, specific response. Templates help with structure but each answer is unique. 35 seconds × 406 = ~4h is already compressed.

The compression coefficient is an average across the full blueprint. Some clusters compress 50%. Some compress 0%. The coefficient smooths this into a single multiplier.

Software Requirement Classification

The CEO asked: which items require special software, and which are just a skilled person logging in and editing? This matters because software-dependent items carry additional fixed or variable costs (subscriptions, licenses, API credits) beyond labor hours. Manual items have zero tool cost — labor only.

Manual Only (Login + Hands)

134

~75% of items · Cost = labor only

Free Tools Required

~14% · Google tools, validators — $0

Proprietary Software

~11% · License/subscription required

Manual Only — No Software Cost

Content writing — FAQs, entity declarations, meta titles/descriptions, H2 stacks, service descriptions, process sections, blog posts, GBP posts. A person with a keyboard and the Entity Fact Sheet.

GBP optimization — description, products, services, photos, hours, categories, attributes, messaging, review responses. All done inside the GBP dashboard — one login, no external tools.

Directory profiles — Yelp, BBB, Bing Places, LinkedIn, Houzz, Thumbtack, Nextdoor, Chamber of Commerce, manufacturer locators. Each is a web form with the same Entity Fact Sheet data.

Schema implementation — copy-paste JSON-LD blocks into <head>, replace bracketed values with entity data. No special tool — just a text editor and the templates from Surge.

Internal link building — editing page HTML to add contextual links. Text editor only.

Creative production — filming video, recording audio, designing infographics. Camera, microphone, Canva. No subscription required beyond what most teams already have.

Business owner verification — confirming facts, license numbers, warranties. Human knowledge, no tools.

Reddit community engagement — answering questions in subreddits. Browser and keyboard.

NAP consistency fixes — logging into each platform and updating address/phone/name. Manual edits across tabs.

~73h of the 97h entity base = manual labor

Free Tools — No License Cost

Google Search Console — URL inspection, re-crawl requests, indexability checks. Free with Google account.

Google Rich Results Test — schema validation. Free, no account needed.

Schema.org Validator — JSON-LD validation. Free, no account needed.

PageSpeed Insights — Core Web Vitals measurement. Free, no account needed.

Google Analytics 4 — traffic tracking, UTM attribution. Free with Google account. Setup takes time but no cost.

W3C Feed Validator — RSS feed validation. Free.

Spotify for Podcasters (Anchor) — audio hosting. Free tier available.

Canva (free tier) — infographic creation. Free for basic usage.

~12h of the 97h entity base = free tools

Proprietary Software — License/Subscription

Surge V3 (Darrell) — runs the diagnostic scan, produces structured scores + blueprint. Required for items #0, #1, and the entire diagnostic intake. Per-scan cost or subscription.

Screaming Frog / Sitebulb — site crawling for link audits, architecture verification, internal link validation (#25, #23). Annual license ~$200–$250.

Veracity Hub (EVH) — entity management, field claims, Admin Verify, health state tracking, Surge import, score history. Our platform — built cost, not license.

Citation Engine / Neo Maps — citation monitoring, local presence verification, NAP consistency automation. Our platform.

Live Drive — client-facing portal, report delivery, project status. Our platform.

DataForSEO — AI citation measurement, SERP analysis (used by Surge under the hood). API credit cost.

Apify — review scraping, GBP data extraction (future). Per-actor-run cost.

~12h of the 97h entity base = software-dependent

Why This Classification Matters for Pricing

Manual items (134 of 179): Cost = hours × rate. No other variable. No fixed cost. This is the labor backbone.

Free tool items (25 of 179): Cost = hours × rate. Tools are free. Slight learning curve for junior practitioners but no subscription or license cost.

Software items (20 of 179): Cost = hours × rate + software cost. This is where fixed costs enter the equation. Surge scans, crawler licenses, API credits, and our own platform costs must be accounted separately from labor.

The calculator must separate these. When Kalyn or the CEO builds a quote, they need to see: "This engagement is 68 compressed hours of labor at $X/hr, PLUS $Y in software costs (Surge scan credit, crawler license pro-rata, API credits)." The software line items are fixed or per-use — they don't compress with practitioner skill.

Software-Dependent Items (Detailed)

#	Item	Software Required	Cost Type	Time	Notes
0	Run Surge V3 scan	Surge V3	Per scan / subscription	30m	Per query — brand + each keyword
1	Identify top gaps from scores	Surge V3 output	Included in scan	30m	Reads Surge structured data
23	Confirm hub-to-spoke architecture	Screaming Frog / Sitebulb	Annual license	30m	Site crawl for architecture map
25	Re-crawl site and verify links	Screaming Frog / Sitebulb	Annual license	30m	Post-change verification crawl
53	Build corroboration inventory	Citation Engine / Neo Maps	Our platform	2h	Catalog every external mention
61	Monthly AI citation monitoring	DataForSEO / Surge	API credits + subscription	30m	Perplexity, Bing, ChatGPT, Google AI
139	Check Surge Feed Engine availability	Surge V3	Included in subscription	15m	Feed automation check
148	Log core geo SERP baseline	DataForSEO / rank tracker	API credits	30m	Pre-expansion measurement
150	Assess expansion readiness	Surge V3 + DataForSEO	Per scan + API	30m	6 criteria require measured data
172	Record measurement baseline	GA4 + DataForSEO	Free + API credits	30m	20+ values across tools
173	Set up GA4 tracking	GA4 (free)	Free	1h	Property creation + script install
179–182	30/60/90-day behavioral diagnostics	Surge V3 + GA4 + DataForSEO	Per re-run cost	3h total	Compare to baseline — requires re-scan
183–189	MD Import diagnostic vitals (7 items)	Veracity Hub + Surge	Our platform + scan	1.75h	Signal Health, GBP Status, Entity Alignment, etc.
190	Build MD file upload in EVH	Veracity Hub	Development cost	4h	One-time build — enables all MD imports

The Bottom Line for the CEO

75% of the blueprint is a skilled human with a browser. No special software. Just logging into GBP, writing content, filling directory forms, responding to reviews, editing HTML. The Entity Fact Sheet and Surge templates guide the work — the software already did its job producing the blueprint.

14% uses free tools that Google provides (Search Console, Rich Results Test, PageSpeed, GA4). Zero cost beyond the person's time.

11% requires proprietary software — Surge for scanning, crawlers for auditing, our platforms (EVH, Citation Engine, Live Drive) for management, DataForSEO for AI citation tracking. These have fixed or per-use costs that must be line-itemed separately in the quote.

Labor compresses with skill. Software costs do not. The calculator must keep them on separate lines.

What This Means for the Calculator Build

Calculator Inputs

1. Number of keyword pages — slider or input (0–50)
2. Practitioner tier — dropdown (Junior/Experienced/Expert)
3. Rate per role — 5 input fields (Writer, Dev-SEO, Marketing-PR, Business Owner, Designer)
4. Value markup % — optional, for sales layer
5. Software line items — Surge scan cost, crawler license (pro-rata), API credits (DataForSEO), platform costs (EVH, Citation Engine, Live Drive). These are fixed/per-use — they do NOT compress with practitioner tier.

Calculator Outputs

Total labor hours — by role and total (compressible)
Total labor cost (hours × compression × rate) — what it costs us in people
Total software cost — line-itemed, NOT compressible
Total cost (labor + software) — our true cost
Total price (cost × value markup) — what we charge
Per-role breakdown — who does what, how long
Manual vs software split — shows 75/14/11 breakdown per engagement

Surge Cost Architecture V2 — COMPRESSED