Good fit
The request has a clear audience, a useful question, enough source context, and a deliverable that can be reviewed before payment or scheduling.
Service Intake Brief
A structured first email for paid research briefs, script systems, and archive reviews so service requests arrive with enough context to evaluate fit.
Use this before asking for a quote
The intake brief keeps service inquiries practical. It does not create an order, guarantee availability, quote a price, collect payment, or promise traffic, rankings, AdSense approval, sponsor acceptance, or revenue.
A useful first message should make the audience, topic, timeline, deliverable, source constraints, and commercial boundaries visible enough to decide whether a paid scope makes sense.
Status. Manual-review intake page; not a form backend, checkout, or contract.
Pre-read. Review starter scopes, service samples, the scope guide, quote factors, the engagement guide, and the procurement guide first.
Email. Intake replies go to luketrodriguez1@gmail.com.
What to include
Copy these fields into the first service email or use the prefilled email link.
- Service interest: research brief, script system, archive review, or unsure
- Audience: who the finished video, article, or archive needs to serve
- Topic or archive URL: include any channel, article, product, or source links
- Desired deliverable: brief, outline, checklist, review notes, or implementation plan
- Timeline and depth: deadline, urgency, number of pages/scripts/topics, and review expectations
- Commercial constraints: sponsors, affiliates, product claims, disclosure needs, or restricted topics
Send the brief
The mail link opens a structured draft in your email app. It does not submit anything automatically from the site.
Open intake emailHow fit is reviewed
These signals help a buyer understand why some requests can move toward scope and others need clarification or rejection.
Needs clarification
The request has a broad topic, missing links, unclear timeline, or no defined output. A reply may ask for a narrower brief before any scope is discussed.
Not accepted
Requests built around hidden endorsements, scraped rewrites, invalid ad activity, unsupported claims, or guaranteed revenue/platform outcomes should be rejected.