Axel Freeman

Pricing

Fixed scope, fixed price, shipped artifacts

Prices are public because the scope is public — see the scope of work. There is no per-hour billing and no discovery-call gate before a number.

Agency / freelancer / marketing engineer

AgencyFreelancerMarketing engineer
Time to first artifactweeks of onboardingdepends on the queuedays — a page or a tool goes live
What you receivedecks, reports, account access they holddeliverables per taskpages, tools, data, with live links
Who owns the accountsusually the agencyyouyou, from day one
Pricing modelretainer, scope driftshourly, scope driftsfixed package, published
Measurementmonthly PDFper requestGA4 events + publish log you can audit
If nothing shippedinvoice standsinvoice standsmonth is free
Entry price$3k–10k/month$50–150/hour$900 fixed

Packages

Sprint
$900 fixed

Positioning, landing page, 5 hypotheses with kill rules, one channel live, measurement wired. 5 working days.

Start a Sprint

Engine
$1,900/month

The sprint loop running month over month: pages, a tool, articles, distribution, a read-out of what worked and what was killed.

Run the Engine

Full build
$2,900 one-time

Whole system: architecture, page set, agent-readable layer, tooling, distribution, documentation, handover. 3–4 weeks.

Scope a build

What the price is based on

Payable by card or USDT. Cancel the Engine with 14 days notice.

Related: B2B lead list building — where the 6,032 domains in the list came from and what each source family publishes.

Related: Appointment setting — what the $900 Sprint, the $1,900/month Engine and the $2,900 Full Build each produce when the outbound is appointment setting.

Related: B2B data enrichment — what the $900 Sprint, the $1 900/month Engine and the $2 900 Full Build each produce when the job is enrichment.

Related: Agency partner program — why the partner cost basis is the public price rather than a separate reseller list.

Related: Outbound pilot — the fourteen-day $900 test, written down day by day before it is paid for.

Related: lead list verification — what runs before a batch is built, and what it removes.

The order these three packages should be bought in

The prices above are ordered on purpose, and the order is the part buyers skip: the definition work is a one-off, the month is a loop, and the build is the pipeline the loop would otherwise be reporting on. The reasoning is published in full with the arithmetic that sets the ceiling — Buy the definition before the month: one strict two-variant test at a 3% base rate needs 13,914 contacts per arm (27,828 in total), which is 56 days at 500 contacts a day — so one honest test per month is the ceiling at moderate volume, not three. The same article carries the receipts from running this on my own domain, including the boring ones: 42 of 76 published articles carry a canonical tag back to this domain, and 9 clicks from 55 articles in a day is the real size of the first step. The machine-readable index of everything published is in llms.txt.

Guides