July Monthly Management
Lead Scout, content, documents, and reporting in the same Aim High Systems workspace BEE is already used to.
July Monthly Management activeFiles and media
Client-ready files, media, reports, and packets stay in one admin-synced library.
Library
Preview
Choose a file from the library.
Preview appears here after a file is selected.
No file is open.
Type a message, or start a voice call and ask it anything a customer might.
Automated weekly pick
Waiting for the next social sync to pick the weekly winner.
Lead snapshot
Bottom line
The client view should stay simple: what is live, what changed, and what needs approval. Employee tasks should stay in Admin where ideas, leads, ads, and follow-up can be managed without cluttering the client page.
No raw task queue unless Aim High enables it.
Operational details belong in the admin side.
Reports
BEE can see what is coming online, what is ready for owner review, and where cached Meta, organic, website, and form reporting connect as campaigns go live.
Updated Jun 29, 2026
Property leads are coming online from the service-area map and account research.
Meta and organic reporting reads cached Supabase metric rows. Platform tokens stay in Vault.
Organic reach, campaign traffic, forms, and report views can be tied back to the monthly workspace.
Meta Ads and local awareness campaigns roll into one client-facing report when cached rows are visible.
Coverage assurance
BEE sees a clean report layer. Aim High keeps the raw parcel universe behind the scenes and classifies every address into mapped leads, review queue, or not a fit.
Coverage source status loading.
Universe sync loading.
Shows how many property leads are live, how many have unit-count support, and how many are ready for review.
Use this section for Meta Ads, organic reach, website form submissions, calls, and monthly comparison from the cached reporting layer.
The report should answer one question first: what qualified leads exist now, and what is the next useful action.
Lead analytics
Organic reach, Meta clicks, form submissions, and website lead activity update from the cached Supabase reporting layer.
Not synced
Analytics source waiting.
Map
Map data
Contact machine
Lead Scout ranks named people and approval roles first: property manager, regional manager, asset manager, owner principal, registered agent, HOA board contact, or facilities contact.
Property manager, regional manager, asset manager, or facilities contact tied to the account.
Tax owner, parcel, mailing address, and county source link.
LLC principal, registered agent, or owner representative that can approve access.
Association manager, board contact, or emergency contact source when the property is an association.
A only when a named person or proven approval role has a usable channel and source proof.
Property data loop
Discovery keeps the 3+ unit map populated. The loop keeps ranking records until owner, manager, direct contact, unit, and visual proof are attached.
Visual proof
Attached evidence packet
Source search results
Not runLeads
Company contacts, service context, and customer records will sit here when the client workspace expands beyond the current lead package.
Content Studio
Pick an idea, refine the wording, set it up, and mark it used so the same angle does not repeat. Teleprompter opens only when a script needs to be read.
Unused ideas stay at the top. Used ideas can be hidden from the queue.
Idea
Choose an idea from the queue.
Caption will appear here.
CTA will appear here.
Choose what happens next for this idea.
Teleprompter
Summaries show recommended accounts, market movement, service-area coverage, and owner-safe next steps.
Directory
Use this as the simple module directory for the BEE client profile. Home gives the snapshot, Leads tracks property opportunities and website activity, Documents keeps files and media, and Reports shows progress.
Same Aim High Systems structure, with BEE-specific modules inside it.
Monthly status, lead snapshot, next decision, and the simple client-facing summary.
Visible Leads Lead ScoutMap, filters, qualified property records, owner path, manager path, and selected-account detail.
Core Documents Files and mediaIG stories, FB and IG posts, blog posts, monthly reports, lead packets, and client-ready documents.
Active Content Ideas and teleprompterApproved angles, scripts, content queue, and reusable ad or social wording.
Synced Reports Lead and ad reportingLead progress, source coverage, monthly reporting, view analytics, and ad reporting readiness.
Monthly Settings Workspace controlsCoverage, source readiness, run cadence, visibility, exports, and admin-managed guardrails.
ManagedLead Scout keeps the account list moving, Documents stores client-ready files, and Reports keeps BEE focused on progress without exposing raw admin clutter.
Imports, source review, contact cleanup, and bulk research belong in admin. The BEE profile should stay clean enough for the client to use.
Settings
Control what BEE sees, what Aim High manages in the background, and how property lead data keeps moving from map discovery into review-ready records.
Crystal Lake corridor
30 minute map checks while open
Home, leads, documents, reports
Lead Scout
Coverage
Automation
Data sources
Owner, parcel, class, and address evidence for qualified buildings.
ActiveBuilding candidates, unit tags, and address context for map coverage.
ActiveManager path, website, source notes, and direct-contact follow-up.
QueuedProperty photos and sign context used as review evidence, not final proof by itself.
ReviewVisibility
Reports