Referral-Ready Delivery Pilot
Turn a delivery you can honestly describe into a careful introduction: one bounded paid sprint, one reviewable handoff, and a non-cash service-credit proposal that does not exist until the exact referral is confirmed in writing.
Request-only pilot. A request never creates a credit; only a dated pre-introduction confirmation can open this pilot. Reading, building a brief, or submitting a form creates no obligation for either side.
$249 one time — proposed sprint
Who this is for
You run content operations at a B2B SaaS company or technical publisher, or you have already received a fixed-scope delivery you can describe from experience. You have source-controlled Markdown, MDX, or plain HTML and first-party offers that need honest connections. You want a reviewable match map and source patch, not a tool that stuffs links wherever there is room.
The referral path is for a former customer or collaborator who knows what was actually delivered and wants to introduce a colleague without inventing a testimonial. Your handoff should name the useful artifact, the bounded scope, and the part you personally observed. It should not claim results you did not measure.
Who should skip it
Skip the sprint if you have no first-party offer, do not control the source pages, need us to deploy into production, or want links placed on third-party sites. Skip the referral pilot if the introduction already happened, if you want a cash fee or percentage, if you cannot describe a prior delivery without sharing private customer material, or if you expect a form to issue a credit by itself.
You can always share the paid sprint page with no credit request. A straightforward recommendation in your own words is useful without a program wrapped around it.
The paid deliverable
Contextual Offer Bridge Sprint — $249 one time. Send at most 100 customer-authorized, source-controlled Markdown, MDX, or plain-HTML pages and at most five first-party offers. Within five business days after complete accepted intake, the delivery contains:
- A reviewed CSV match map connecting pages to offers.
- Up to 10 clear first-party CTA modules written to fit the surrounding content.
- one applyable unified diff for the supplied source format.
- Link, anchor, disclosure, and destination QA over everything delivered.
You apply and publish the diff. We request no credentials, production access, deployment access, third-party paid links, or endorsements. A page with no honest match stays unchanged. The sprint promises the named artifacts and turnaround, not traffic, rankings, leads, revenue, or any other downstream result.
From prior delivery to a possible future credit
- Start with a prior delivery. Name the exact artifact you received and the limited scope it covered. That observed delivery is the basis for the handoff; general praise and invented outcomes are not.
- Request a dated confirmation before introducing anyone. The request identifies the qualifying service and proposed credit without exposing the prospective buyer publicly. We may accept, narrow, or decline it. Until a dated confirmation exists, there is no pilot record to rely on.
- Make the introduction only after confirmation. You send your own message and plainly disclose that you may request a non-cash service credit if the qualifying referred delivery closes. We do not send on your behalf, collect a contact list, or start a sequence. An earlier introduction is not converted into a retroactive claim.
- The referred buyer receives a separate paid delivery. They request scope, accept their own fixed-scope service priced at $249 or more, pay through the ordinary customer path, and receive the named artifact. An enquiry, quote, checkout start, or payment without delivery is not enough.
- Request one future-service credit. After that referred delivery, the referrer may request one non-cash $249 service credit toward a future fixed-scope service priced at $249 or more. The dated confirmation controls the eligible service, status, and expiry.
If a referred buyer names a prior rate already quoted to the referrer for the same product, that exact same-product rate is honored. A larger or different product is a new scope at its own current rate. Scope defines the product; a label does not stretch a smaller quote over a larger delivery.
What the dated confirmation must name
A usable confirmation is specific enough to audit later and small enough not to become a public customer list. It names:
- The referrer's internal identifier and the original delivered-artifact label.
- The qualifying SKU and the referred-buyer boundary used for a private internal match.
- The proposed $249 credit amount and the future service it may apply toward.
- The plain-language disclosure the referrer will include in the introduction.
- The confirmation timestamp, status, and expiry date.
- The event that can change the status: referred paid delivery, application, expiry, or reversal with a reason.
A confirmed pilot record would retain hashed or internal identifiers, UTC timestamps, the qualifying SKU, delivered-artifact label, amount, status, and expiry. Raw email addresses and customer names never appear on public pages. The receipt is an internal audit record, not cash, a payment, proof of endorsement, or a public customer claim. This page creates no receipt.
Build a private handoff brief in your browser
Select the prior delivery type, state whether the proposed work is the same product or a different scope, and write one non-sensitive sentence about the useful artifact. The builder flags URLs, email addresses, phone numbers, organization suffixes, and common account identifiers. It then prepares a small JSON brief you download directly.
Privacy and retention
The separate request form stores the reply address and scope text needed for a human response in the private lead store. It does not publish an identity. Do not put a referred person's contact details into the browser-local brief; make your own introduction only after the dated boundary exists.
Working request material is deleted within 30 days after the request closes unless it becomes part of an accepted order or must be retained for accounting. Payment records follow the ordinary accounting retention boundary. Public measurement is limited to page and CTA attribution; a fetch is never called a referral or a person.
Strict boundaries
- No credit from reading, sharing, building a brief, or submitting a form.
- No cash value, transfer, stacking, retroactive claim, referral percentage, or third-party placement fee.
- No bulk lead list, contact-data collection, mass outreach, or message sent on anyone's behalf.
- No production credentials, deployment, source publication, endorsement, or downstream outcome promise.
- No undisclosed incentive: the referrer must say that a future non-cash service credit may be requested.
- No self-referral, duplicate claim, or credit before the referred paid delivery is accepted as delivered.
Free alternatives
- Write one short introduction in your own words and send it yourself.
- Use the browser-local builder to keep the scope distinction clear.
- Share the paid sprint page without requesting any credit.
- Build your own internal content-to-offer map with a spreadsheet and review every placement manually.
Questions people should ask before using the pilot
When can a credit be requested?
Only after the introduction had a dated pre-introduction confirmation and the referred buyer later paid for and received the qualifying fixed-scope service. It is requested then; it is not created earlier.
What happens to a prior same-product quoted rate?
If the referred buyer names the exact rate already quoted to the referrer for that same product, we honor it. A different or larger delivery has its own scope and rate.
What if the referred buyer does not buy or does not receive the service?
No future-service credit can be requested. A conversation, quote, request, checkout start, or payment without the agreed delivery does not close the sequence.
What referral data is public?
No customer name, email address, introduction, receipt, or credit balance is public. This page explains a template and records ordinary anonymous page/CTA attribution.
Does the request form charge anything?
No. It starts a human scope review. No checkout opens and no work begins from the form alone.
Request the fixed-scope sprint
Use the product-specific form to describe the source format, page count, first-party offers, and whether the request follows a separately confirmed introduction. Keep contact information out of the browser-local brief and put only the minimum reply details in the private form.
Referral-ready delivery pilot by US Tech Automations. No customer identity or referral record is disclosed on this page.