SOURCE

Pricing Framework (with Examples)

Properties1
tagslocal-seo, caleb-ulku, course, agency-pricing, pbn, core-30, client-acquisition
AUTHOR
Caleb Ulku
ORIGINAL
view original

5 min read

Pricing Framework (with Examples)

Author: Caleb Ulku | Published: unknown | Source: transcript

Summary

Caleb argues most agencies price by copying competitors and then have unpredictable margins. His method is scope-based pricing: break the delivery sequence into components, attach a real cost to each, add a desired margin, and quote that — not “what the market charges” or “what you think they’ll pay.”

Cost stack he enumerates:

  • One-time setup (amortized over the first few months, not billed as a separate setup fee): create a project in Claude or a custom GPT; client information sheet (details, target keywords, specs); GBP audit; GBP landing-page audit; LeadSnap setup.
  • Per-article production (repeats monthly): copywriter research/write/edit; Schema Markup (Structured Data) implementation; AI image generation; internal and external authority-link sourcing, including “the external PBN link cost per article”; developer time to publish/format; QA of the developer’s work; then updating existing content to add internal links to the new articles (the step he says teams skip, and which he calls critical for ranking).

He targets 50–70% gross margin because one-off client requests (feedback, extra edits, unscoped small tasks) are not in the base price. Delivery shape: month one front-loads setup and ships fewer articles (~5) so the client sees foundational work immediately; month two+ is content production at ~9 articles/month. No separate setup fee. Scale is linear for standard projects: 7 articles → ×7 of the unit cost; 15 → ×15.

Exception: do not use per-article pricing on broken sites — his example is a site with 500 indexed URLs ranking 20th in its own lobby (a Houston plastic surgeon with major technical issues). Price diagnostic time, developer work, and testing separately from content. Common mistakes: ignoring revision rounds, underestimating technical work, fixed price regardless of scope, competing on price. Sales presentation: lead with scope and outcomes, then price; offer good / better / best (low / mid / high budget) with gross margin dropping as scale grows, each tier still profitable. Proper pricing, he says, is how you avoid unprofitable clients who demand more work than you can afford.

Key Claims

  • Price from actual component costs + margin, not competitor rate cards.
  • Setup is real work (Claude/custom GPT project, info sheet, GBP + landing-page audits, LeadSnap) but is rolled into month one, not a separate fee.
  • Unit of ongoing work is the article, fully loaded: writer, schema, AI images, external PBN link, publisher, QA, internal-link pass.
  • Target 50–70% gross margin as a buffer for unscoped revisions.
  • Default package shape: month 1 = setup + ~5 articles; month 2+ = ~9 articles.
  • Linear scale for standard Core-30-style production; custom/technical quotes when the site is bloated and ranking ~20 at the pin (500-URL Houston surgeon example).
  • Present good/better/best; let margin % fall as dollar volume rises; never unprofitable at any tier.
  • Lead the sales conversation with scope/value, then price.

Notable quotes

“Include the external PBN link cost per article.”

Why citable: The course’s on-the-record admission that paid PBN links are a line item in delivery, not a hypothetical. Central exhibit for the PBN-vs-wiki-consensus tension.

“Please do not use the same per article pricing when you’re essentially having to rebuild a site’s technical foundation.”

Why citable: Ties pricing to the same “don’t Core-30 a broken site” rule as the Core 30 lesson (450–500 URLs, rank 20 in the lobby). Useful as an operational boundary, not just a rate card.

Connections

Entities mentioned: Caleb Ulku, Google Business Profile, LeadSnap, Claude, ChatGPT Concepts referenced: Local SEO, Core 30, Schema Markup (Structured Data), GBP–Website Alignment (Consistency Signals), Local Link Building & Authority

Contradictions / Tensions

  • Explicit PBN cost-per-article vs. this wiki’s existing consensus that PBNs are harmful and vs. Google’s link-spam policies. This is the named conflict to put on Local Link Building & Authority (and any PBN/icecreamtruck note). He also sells “not AI slop links” via icecreamtruck.shop in YouTube videos — treat PBN and that shop as the same commercial link pipeline unless a later source separates them.
  • “Don’t trick Google” (agency-process / Google-and-AI lessons) vs. budgeting a PBN link onto every article. Direct values clash.
  • ~9 articles a month as the default retainer vs. “blogging is useless for local SEO.” These “articles” are Core 30 category/service/geo pages in his system, not blog posts — aggregators must keep that distinction or the corpus looks self-contradictory.
  • 50–70% gross margin and good/better/best with falling margin % are agency-finance claims, not ranking claims. Don’t let them leak onto factor pages.
  • Spoken “cloud or custom GPT” is almost certainly Claude or custom GPT (he uses Claude everywhere else).

Notes

New concepts to flag: agency-pricing / scope-based-pricing; PBN usage (icecreamtruck / external PBN link cost per article); internal-linking (the post-publish in-content link pass is called out as ranking-critical). Transcript: GPP = GBP; “plastic surge in Houston” = plastic surgeon. Commercial: LeadSnap setup is a billed-into-month-one cost, i.e. the tool is in the P&L. This lesson does not give dollar prices, only structure.