Valley CFO × Bloom
Welcome, Tim & Aaron.
This is the private home for our partnership — the agreement, the Week 1 proof plan, and the first payment link. Built so you can see exactly what you're paying for, every week.
The partnership
What we're building together
Bloom is engaged as Valley CFO's build partner for the sales and growth system. Tim drives sales and growth. Aaron stays looped in on approval and data boundaries where needed. Bloom develops the technical rails — and ships visible proof every week.
Sales lane
Chuck Bauer AI sales-enablement, plus Harry as Tim's personal agent.
Ecosystem spine
Valley CFO Index + Oracle — the local-first memory and search layer across the partnership.
Marketing + outreach
Social agent and sales follow-up workflows running in shadow until approved for live use.
Step one
Independent Contractor Services Agreement
A $5,000/week Growth OS build retainer between Bloom Web Services, LLC and Valley CFO. Week 1 is the first paid proof week; the recommended path is a six-week buildout with weekly proof artifacts and review points.
Agreement — current PDF
Review the full terms before signing.
Start Week 1
Agreement + first $5,000 payment
Week 1 begins after the agreement is signed and the first payment clears, or on the following Monday by mutual agreement.
Pay first $5,000Signatures
Tim McElravy
Valley CFO · Principal
Aaron Kraft
Valley CFO · Principal
Heathrow Andrews
Bloom Web Services, LLC · countersigns last
Signed electronically through BloomSign. Each signature is recorded with a cryptographic hash of the document plus IP, browser, and timestamp — the same legal weight as a handwritten signature under the U.S. ESIGN Act and UETA.
Week one
Detailed proof plan
Chuck Desktop proof for Tim: daily sales rail, Ask Chuck direction, prospects, meetings, Sales Vault, Plays, and follow-up surfaces using mock or approved low-risk data.
Marketing OS v0: source shelf, first campaign brief, creative matrix, draft content/ad/email bundle, claims review map, lead path map, and source receipt.
Website, landing, and social direction around the first qualified-conversation offer, with claims and data-boundary flags reserved for Aaron review where needed.
Meta/Facebook readiness without ad spend: account/access checklist, campaign naming and UTM plan, draft-first ad workflow, and spend approval boundary.
Existing Chuck AI repo audit: what exists, what is usable, what is placeholder, and how the web app should connect to Chuck Desktop.
Guarded lead-to-sale path from source/ad/social to landing or assessment, contact capture, booking, Chuck prep, follow-up, and proposal/onboarding handoff.
Monthly run-cost model separating hosting, software, APIs, connectors, AI usage, ad spend, and Bloom development fees.
Day 3 Tim tune-up and Day 5 proof receipt covering what shipped, what was touched, what data was used, blockers, and the Week 2 recommendation.
Kickoff scheduling is confirmed after agreement and Week 1 payment.
Weeks 2-6
Planned continuation path
Week 1 proves the direction. The following weeks harden the system into a repeatable Growth OS, with continuation confirmed in writing and paid weekly.
Week 2
Lead capture and booking engine
Turn the Week 1 lead path into a working intake, source tracking, booking, confirmation, and Chuck prep/follow-up flow.
Week 3
Chuck in Tim's sales day
Meeting prep, post-call actions, three-day follow-up queue, proposal support, Sales Vault structure, and shared contract with the existing Chuck repo.
Week 4
Marketing, ads, and playbook rhythm
Approved campaign packets, content intake, draft ad/social/email variants, landing-page pairing, claims/source review, and campaign learning memo.
Week 5
Current-stack and approval hardening
Clean up access, source-of-truth, approval, and handoff paths around the Growth OS so sales and marketing work stays controlled.
Week 6
Hardening, handoff, and next decision
End-to-end operating receipt, scoreboard, run-cost model v2, support/handoff options, productization questions, and next commercial recommendation.