Key takeaways
- ✓The invoice uses two guest posts on a SaaS review blog, two on a SaaS comparison site, and two niche edits on a technical SEO journal. Prices come from those catalog rows.
- ✓A 240% organic-traffic claim needs before-and-after analytics on a named site. This page does not have that customer.
- ✓Set the measurement up before the first placement, or you will not know what the spend did.
The brief
Pitch decks like a sentence such as "a B2B SaaS grew organic traffic 240% in six months." That sentence is not a result we can show. There is no customer write-up behind it. What follows is a planning model: which rows, which format, what the catalog charges, and which charts would have to move before that kind of sentence was allowed.
The imaginary buyer is a B2B SaaS with a product page that already ranks somewhere on page one or page two for a commercial query. The page has a clear definition of the product. The gap is referring domains from sites a buyer might actually read, not a DR emergency. The mix is deliberately small: six placements, then a stop.
The six-line invoice
The rows are the B2B SaaS review blog, the enterprise SaaS comparison site, and the technical SEO journal in the catalog that ships with this site. Two guest posts on each of the first two, two niche edits on the third. The table multiplies the catalog unit price by the quantity. If those seed prices change in the codebase, the total changes. It is not a negotiated quote from a sales call.
| Listing | Format | DR | Qty | Unit | Line |
|---|---|---|---|---|---|
| B2B SaaS Reviews & Founder Growth Blog (SAAS-102) | Guest post | 58 | 2 | $119 | $238 |
| Enterprise Productivity & AI SaaS Comparison Engine (SAAS-109) | Guest post | 67 | 2 | $179 | $358 |
| Technical SEO, Programmatic Growth & Content Ops Journal (MKT-112) | Niche edit | 61 | 2 | $109 | $218 |
Invoice total: $814
Why this mix: the two guest posts create URLs that can explain the product in the site's own voice. The insertions only make sense if those journal URLs already get visits. Run step 4 of the checklist before treating the niche-edit lines as real orders. The domains are masked in the table on purpose.
What would have to be true for a traffic claim
A 240% increase is (new − old) / old. If a page had 1,000 organic visits a month, 240% growth would mean 3,400. You would need the starting number, the ending number, the dates, and a reason to believe the links were involved. Seasonality, a site migration, a pricing change, and a single new ranking page can all move the total without a single placement. A honest case study shows the Search Console export and the list of live URLs. This page has the list of planned rows and no export.
- •Search Console: impressions and average position for the target queries, exported the week before the first placement.
- •The same export 90 days after the last URL is indexed. Not 90 days after you paid.
- •A row in a sheet for each live URL: index status, anchor, rel, and whether the page still returns 200.
- •Assisted conversions only if analytics already attributes them. Do not invent a revenue number to match the invoice.
Set that up before the first placement
Write the anchors first, using the brand-heavy ranges. Two of the six can be partial match. One naked URL is enough. None of them need to be the exact commercial query if the page is already known for the brand. Then place the orders far enough apart that six new referring domains do not appear on the same afternoon.
The calculator above is the spend side. Type the visits you are willing to treat as the upside and what a visit is worth in your own pipeline. If the months-to-recover figure only works when you assume thousands of new visits, the invoice is too big for the evidence you have. Shrink the order. The price read is there if you want to swap in a different band.
FAQ
Did a ChainEpic customer grow traffic 240%?
This article does not report that. It prices a six-placement plan from catalog rows. A growth claim would need a named site and an analytics export.
Can I replace the three sites in the invoice?
Yes. Keep the quantity small, pass each replacement through the vetting checklist, and recompute the total from the row prices rather than from this example.