Joint Venture Proposal · Confidential
Medicare Space
Takeover
A revenue-share joint venture between My Senior Health Plan (Pete Blasi, CEO) and Adolicious LLC (signed by Kirstyn Burns, CEO).
Merge a proven, AI-cited answer-engine corpus (SeniorDirectAnswers) onto the aged, trusted MySeniorHealthPlan.com domain to drive organic Medicare traffic — calls, forms, appointments, and closed files — with zero disruption to Pete's 17-year-old web property.
Prepared by Adolicious LLC · Confidential proposal
Every figure on this page is live — drag any slider in The Economics to model the deal.
01 — The Opportunity
One property, done properly.
The goal is simple: increase organic traffic in order to generate additional Medicare business — customers, calls, forms, appointments, and closes.
Two assets combine. My Senior Health Plan brings an aged, authoritative, licensed 50-state Medicare brokerage domain. SeniorDirectAnswers brings a large programmatic "direct answers" corpus that is already indexed and cited by AI engines.
The aged domain gives the proven SDA content the crawl trust it needs. The SDA content gives MSHP a massive organic long-tail.
One property, done properly — neither asset reaches its ceiling alone.
02 — The Parties
Who is at the table.
Card A
My Senior Health Plan (MSHP)
Owner of myseniorhealthplan.com. Pete Blasi, as CEO, has full capacity to enter the agreement.
Card B
Adolicious LLC
Owner of seniordirectanswers.com (SDA). Jason Burns negotiates; Kirstyn Burns, as CEO, is the signer.
Card C
Structure
A joint-venture-type revenue-share relationship regarding the combined web property.
03 — The Economics
Clear terms, a self-curing monthly, and shared upside.
Live deal model · drag any figure
Monthly payment
To Adolicious, payable by the 5th of each month.
Publisher rate
Per closed Medicare file to Adolicious. Pete/MSHP retains all profitability above this amount per close.
Closed files / month
Model a month's volume — the bar splits it into cure closes and 50/50 closes.
FMO earning per file
True profitability per closed file — drives the 50/50 split.
External call cost (additive)
Additive — not organic. Purchased calls/transfers Adolicious sources from third-party publishers at this true cost per call, separate from the organic inbound the property generates. Primary use: Pete feeds them to his other downline centers, outside the organic flow. Optional: during ramp he can use them to help cure the monthly — but at this direct cost that's a different call count than the organic closes. When worked, true costs and true earnings are shared 50/50.
Upfront on signing
Paid to Adolicious on the date the agreement takes effect.
Number of monthly payments
Default term is four months — September through December.
Initial-term commitment to Adolicious · through the January checkpoint
$50,000 upfront + $25,000 × 4 months
An initial run — in January we recalibrate or continue, not end.
The cure mechanic · auto-computed
167 closes / mo to break evenAt $25,000/mo and $150/file, MSHP's first 167 closed files recoup the monthly. Every close after that splits 50/50.
Beyond the cure, $100 MSHP / $100 Adolicious per file — and Pete keeps his earnings above $150 per file on the cure closes.
Two ways to cure the monthly
Path A · Organic (primary)
167 closes × $150 = $25,050 — zero media cost.
Path B · External calls (ramp option)
200 calls × $125 = $25,000 — a different count than the 167 organic closes, because each purchased call carries a direct cost. Additive, not organic.
The 50/50 split
Beyond the monthly cure count, every file's true profitability splits 50/50: $100 MSHP / $100 Adolicious per file.
External calls & transfers (additive)
Purchased calls and transfers Adolicious sources from third-party publishers at true cost — additive to, and separate from, the organic flow the property generates. Primary use is Pete's other downline centers. Optional during ramp as a second cure path. True costs shared and true earnings shared 50/50.
Current gauge: roughly $125 per call — 200 calls would cure a $25,000 month.
The Initial Term — Through January
A checkpoint, not an expiry date
The upfront and the four monthly payments (September through December) are structured as an initial run — a defined window to prove the two properties working together, with the relationship's first full review at the January checkpoint.
- This is not an end date. In January, both parties come back together and decide how to move forward.
- Recalibrate or continue: adjust the fee structure against the true earnings generated over those four months — or simply keep it going as-is.
- The January date exists only to guarantee a deliberate check-in. The partnership is built to continue — and either party still holds the clean-exit at any time.
Any party may move any slider — figures are a working framework, not exhaustive.
Additional future terms to be added.
Earnings Per 100 Closes — By Source
Two revenue streams, two different maths
Closes from the organic property and closes from third-party inbound don't pay out the same way. Both split true earnings 50/50 — but inbound also shares a real acquisition cost, so the net per party is different. These update live from the FMO and Inbound sliders above.
Source A · Organic Property (Internal)
Per 100 closes — MSHP + SDA web property
MSHP
$10,000
Adolicious
$10,000
Steady-state closes beyond the monthly cure. The first 167 closes each month first cure Adolicious's monthly outlay; everything after splits 50/50. No media cost — this is organic traffic.
Source B · Purchased External Calls (Additive)
Per 100 closes — purchased calls / transfers, at direct cost
MSHP
$3,750
Adolicious
$3,750
Additive, not organic: these are calls Adolicious purchases from third-party publishers at a real, direct cost per call — separate from the organic flow the property generates. Primary use is Pete's other downline centers; optionally worked during ramp as a second path to cure the monthly. When worked here, both true earnings and true acquisition cost are shared 50/50 (drag the External call cost slider). Different provider relationships carry different costs; each is shared at true cost and true earnings.
04 — The Clean Exit
Pete can walk at any time.
Either party can pull the plug at any point and the relationship ends as of that moment — both parties simply part ways.
Pete points his DNS back to his own site and MSHP is exactly what it was before. Adolicious instantly gets SeniorDirectAnswers back — clean and done.
Before any work begins, the MSHP team makes a 100% clone/copy of the existing MSHP site so everything currently live is preserved and can be re-uploaded almost instantly if anything ever needs to be rolled back.
No lock-in. Fully reversible. Pete's existing 17-year property is never destroyed.
How the exit actually works — three steps, one afternoon
There is nothing complicated to unwind. The switch that turns this on is the same switch that turns it off — a DNS pointer. No data migration to reverse, no rebuild, no dependency on Adolicious to hand anything back.
Step 1
Pete flips one DNS setting
He points myseniorhealthplan.com back at his own original host — a single change in his DNS, exactly the record he controlled before. That's the entire action required of him.
Step 2
His original site is already there
Pete's WordPress was never deleted, and the Stage-0 clone is preserved. The moment DNS points home, MSHP is exactly what it was before — same pages, same media, same links. Nothing to rebuild.
Step 3
It propagates the same quick way
With TTL kept low, the switch back settles in minutes to a few hours — the same fast window as going live. Adolicious simultaneously takes SeniorDirectAnswers back. Clean, immediate, done.
Why it's this simple: Pete's site and the SDA corpus always stay on separate infrastructure that we only route together — never merge or overwrite. "Separating" is just pointing each domain back at its own home. Pete never has to ask for his data, wait on a migration, or trust a handover. He holds the DNS; he holds the exit.
05 — How It Works
One public website, two applications behind the scenes.
myseniorhealthplan.com is served through path-based routing. Visitors and search engines see a single website; requests are routed to the right application by path.
Existing paths → Existing WordPress
- /
- /about/
- /blog/
- /contact/
- …and all current MSHP URLs
New paths → SDA application
- /answers/
- /library/
- /plans/
Concrete mapping
seniordirectanswers.com/plans/nc/onslow → myseniorhealthplan.com/plans/nc/onslow
seniordirectanswers.com/answers/medicare-plans-in-san-bernardino-ca → myseniorhealthplan.com/answers/medicare-plans-in-san-bernardino-ca
All current MSHP URLs remain intact
✓ Same content
✓ Same URLs
✓ Same historical backlinks
✓ Same WordPress pages
✓ Same media
✓ Same redirects
✓ Same analytics
✓ Same Search Console property
✓ Same external links
We do not disrupt 17 years of online authority.
SDA URLs 301-redirect one-for-one to the matching MSHP paths.
06 — Rollout Plan
Staged release, measured at every step.
| Stage | Action | Approx. URLs |
|---|---|---|
| 0 | Clone/proxy existing MSHP perfectly | Existing only |
| 1 | Establish /answers, /plans, /library infrastructure | No mass index |
| 2 | Migrate currently indexed SDA winners + hubs | ~2–5K |
| 3 | 301 corresponding SDA URLs | Same set |
| 4 | Validate Google canonical/index behavior | — |
| 5 | Release county/data-heavy corpus | ~5–15K |
| 6 | Measure indexing/crawl/AI retrieval | — |
| 7 | Release strongest answer cohorts | ~10–25K each |
| 8 | Expand only where Google shows demand | Up to 168K if warranted |
All current MSHP pages are duplicated and re-hung on Adolicious hosting at the exact same URLs. Jason corrects existing MSHP page issues, turning the whole corpus into one properly-structured web property.
07 — Migration Safety
A deliberate two-stage cutover.
We deliberately separate two events so nothing is ambiguous.
Day 1 — Infrastructure only
Switch DNS so myseniorhealthplan.com points at Adolicious infrastructure serving the SAME existing MSHP content. To Google, nothing meaningful changed: same URLs, same content, same canonicals, same sitemap behavior. Let it stabilize.
Day 2/3+ — SDA integration
Introduce /plans/, /answers/ and /library/, along with the new sitemap and schema.
The benefit: server logs and Search Console can attribute any anomaly to the right event.
| Elapsed | Expected DNS behavior |
|---|---|
| 0–15 min | Some resolvers see the new infrastructure |
| 15–60 min | A large portion of users on new infrastructure |
| 1–6 hrs | Most traffic on new infrastructure |
| 6–24 hrs | Straggling caches expire |
| 24–48 hrs | Treat as the global propagation window |
| >48 hrs | Investigate configuration |
Lowered TTL in advance
Cloudflare proxied records automatically use a 300s TTL.
Old server kept warm
Pete's existing server stays running as a fallback for several days.
Every record preserved
A/AAAA, CNAME, MX, TXT, SPF/DKIM/DMARC and verification records are preserved, so email and services are never interrupted.
Once behind Cloudflare's edge, future changes propagate in minutes — this is the only "scary" migration.
08 — Compliance
CMS/TPMO requirements, built in from day one.
MSHP is a licensed Medicare brokerage, so the combined property follows CMS/TPMO marketing requirements. The standard third-party marketing disclaimer and non-government disclaimers are applied site-wide across the new Medicare answer and plan pages. Built in from day one.
Licensing, Entities & Authority
How MSHP is licensed & credentialed across all 50 states
A licensed, 50-state Medicare brokerage is the foundation of this property's trust and compliance. Pete completes the fields below — the registered entities, each state license, and the authority/E-E-A-T signals — which then feed the site's Organization schema, sameAs graph, and on-page trust markers that both Google and AI engines reward.
Registered entities & their licenses
50-state license numbers
Pete enters the Department of Insurance license number MSHP holds in each state.
Authority & E-E-A-T signals
These build Experience, Expertise, Authoritativeness & Trust — the signals search and AI engines use to decide who to cite.
Profiles & social (schema sameAs)
Credentials & certifications
Reputation & reviews
Awards & recognition
09 — Next Steps
Prepared for review by Pete Blasi.
If the framework above is agreeable, the next step is execution of the agreement, the upfront payment, and the Stage 0 clone of the existing MSHP site before any work begins.
Kirstyn Burns
CEO, Adolicious LLC
Pete Blasi
CEO, My Senior Health Plan