LunaSys™
All is well overall. The day's plan is below — pay attention to Financials (thin margins heading into the fall loss months) and keep the Ideal go-live emails moving. Detail lives in each pane.
Your day, managed
The Computer's marching orders, rebuilt every morning. Complete clears it; Edit reshapes it and tells the Computer.
Task status
Open tasks by phase
System recommendations 0
Things the Computer thinks would improve the system — data fixes, process tweaks, upgrades. YES queues it for execution and clears it from this list; Edit changes the plan first; Dismiss makes it go away. New recommendations appear here from every scheduled sweep.
Deal & Legal Ball in your court
LOI signed with Mike 8/18 and already in Dillon King's hands (sent from your personal Gmail with the signed LOI attached). Dillon replied Wednesday evening: conflicts cleared, engagement letter arriving today or Monday. DocuSign checked — nothing pending there yet. He asked for your preferred address for the file, still unanswered, and how the CPA meeting went.
- For the working session once engaged: retained liabilities, disclosure schedules, indemnity scope, 1250 Dewey real estate, your personal exposure including the SBA guarantee.
- Sequencing: engagement + planning now; heavy drafting spend positioned to fire once Aero closes ~9/10.
CPA & Tax One action
Robert E. Donnell III, CPA engaged; first meeting done 8/20. He sends the secure document-intake link once you email him. Queued behind the portal: Aero-proceeds tax reserve, opening balance sheet, inventory valuation, payroll/sales-tax continuity, first-month close.
Financing & SBA Critical path
Sequencing rule: Aero closes ~9/10 → equity funds → MLSC closes 10/1. Plan everything, spend nothing major until then. Huntington/SBA underwriting is active but undocumented on your side — no written condition list on file. Only ~3 weeks between funding and close, so appraisal, insurance binders and entity docs must be prepped before 9/10. Working-capital line inclusion still unconfirmed.
Deal files Temporary home — retires after close
Open questions 6 critical
- What conditions remain with Huntington/SBA? — need the written list (see Financials).
- Exact cash-to-close beyond the $100k contribution — down payment vs. fees vs. escrows vs. working capital.
- Which pre-close liabilities stay inside the company after the stock purchase?
- Inventory valuation method and closing adjustment mechanics.
- Are AR/AP/cash retained at close? (CPA)
- Confirmed Ideal go-live date relative to legal closing.
Calculator Shop unit · works today
When we go live on Ideal, this corner also gets the shop's real quick-quote math — tax, margin and MAP checks baked into the keys.
Next 7 days Calendar
Loading your calendar…
Mail — needs a reply Outlook
Recent incoming mail with no reply sent yet. Where the Computer already has a draft waiting, review it here — nothing sends until you approve it, twice.
Loading your inbox…
Open Outlook · Open Gmail — Gmail replies still send from Gmail; this in-System approve/send is Outlook-first.
Sticky board This device · back up to cloud anytime
Drag to arrange, double-click to write, ✕ to toss. Notes live in this browser; Back up saves them to SharePoint so any device can Restore them.
All tasks — live from the Command Center Loading…
📅 shows the real due date for every task — computed from the plan's T-minus / Day-N windows against the Oct 1 close (a ~ marks a converted window; red = past due). The original window still shows in each task's detail.
Loading tasks from MLSC_Acquisition_Command_Center.xlsx…
New task
New tasks queue to the Action Queue and are added to the Command Center by the executor, so the workbook stays the single source of truth.
OPERATIONS: GREEN
All signals normal — full staffing baseline, no inventory flags, no open operational issues. The Computer re-scores this every morning sweep.
The Computer's operations overview Rebuilt every sweep
All is well — we're operating at full planned capacity. Shop days hold Tue–Thu next week; the install-day / observation-day / access-walkthrough split still fits the no-spend gate. Nothing in the task base, weather outlook, or queues is blocking operations today.
How the light gets its color — staffing: team members' 365 calendars are checked each morning; everyone in = green baseline, one short = yellow unless coverage is arranged, two+ short or no counter coverage = red. Inventory: a stock-out on a high-velocity item (oil, blades, trimmer line, fuel) or a missed incoming order flags yellow; a showroom hole (no mowers to sell) flags red. Issues: any open operational issue the Computer knows about (equipment down, weather damage, systems outage) can force yellow/red with the reason shown above. Staffing feed goes live when the team's calendars are on the tenant; inventory feed at Ideal go-live.
Operational knowledge input Feeds the whole deck
Brain-dump anything you learn at the shop — how Mike prices trade-ins, where the Stihl chain stock hides, which customers get callbacks, what broke today. The Computer works it into the System, the Command Center, and the institutional-memory docs. This is how tribal knowledge becomes company knowledge.
Margins Sample
Wholegoods carry the revenue; parts and service carry the profit. Watch blended GP — it falls when unit sales spike without attached parts/service.
The Computer's read Sample
- Month is soft (−4.1%) against last August's pace — consistent with the heat-driven walk-in dip, not lost customers: ticket count is down, average ticket is up.
- Service labor is the bright spot — bay hours are booked 8 days out. Revenue ceiling is technician hours, not demand.
- Parts attach rate slipping on unit sales — units are leaving without blades/oil/PPE add-ons that carry 42% margin.
Clear path Recommended this week
- Counter script: every unit sale gets asked one attach question ("blades + oil bundle?") — recovers ~3 pts of blended GP at zero cost.
- Book the service backlog forward: pre-sell September tune-up slots at today's counter to convert the heat lull into scheduled work.
- Morning-weighted staffing while 95°+ holds: strongest counter person on 8–11 AM, restock and callbacks after 2 PM.
Numbers above are SAMPLE placeholders. At Ideal go-live the ticker pulls daily sales from Ideal and financials from QuickBooks; the read, margins and path are recomputed by the Computer every refresh — this pane is built to be watched all day.
Revenue vs expenses — monthly Revenue: diligence data · Expenses: sample until QBO
Seasonality is stark — March alone is ~10× January; expense placeholders follow the same curve until QuickBooks feeds the real P&L. The gap between the two columns is the business.
Where sales intelligence goes next Post go-live
- Ideal feeds daily sales pace, category/brand mix, average ticket.
- TargetWeb/Shopify adds the online catalog and e-commerce once Ideal product sync completes.
- Brand focus per your strategy: STIHL, Exmark, RedMax first.
- Customer reconnection campaign is staged in the Command Center — 35-row log ready for pre-close visits.
Where these numbers come from Placeholders until Ideal go-live
Every tile above maps to an Ideal service-module field: open service orders by category (handheld vs. mower), status = ready-for-pickup, ticket revenue and tech cost by day/week/month, and the completed-unit counts that drive turnaround and monthly-average math. The variables get wired the week Ideal starts transacting — the layout is ready now so day one looks like this, with numbers.
Stock levels vs goals High-velocity items · Ideal feeds the %s
Goals get set with Mike's knowledge of what the shop burns through; the bars turn live at Ideal go-live and go yellow/red when a high-velocity item slips below goal (which also flags the Operations status light).
Floor counts Showroom & wall · Ideal at go-live
Ideal & opening inventory Date not locked
Implementation kickoff done (Jill Bruso PM, Troy Simon training, Jeff Plecity accounting, Sheila Schons price files). Go-live has slipped with deal timing; latest signal points to October, exact date TBD. The conversion plan is written: close the shop Friday noon, Chris defines areas and calls out parts, Brittany labels and bulk-counts, you enter structured records into Ideal.
- Brittany's task to reconfirm the go-live/training calendar is dated Sunday 8/24 — will slip silently unless intentional.
- Duplicate PartSmart monthly billing raised in multiple threads; no resolution found in the mailbox.
- Remaining 50% implementation payment — plan the dates now; payment timing is gated (see Acquisition).
- Five core-training sessions must land T-21 to T-14 with at least half the staff.
The Computer's price watch AI · refreshed every sweep
Once manufacturer price lists load through Ideal, every sweep compares them against the last list on file and against what the big boxes and nearby dealers show online — anything that moved lands here as a short call-out: "STIHL raised MS 271 list $20 — our tag is now $30 under Home Depot's, room to move" or "Lowe's dropped Ego 21″ push mowers $50 — watch walk-ins comparing."
Until the price files land, drop any price sheet or rep email into Operational Knowledge and the Computer starts the comparison file early.
Price checking Reputable comparisons, one click
Pricing used equipment Trade-ins & consignment
For a trade-in or used unit on the floor, triangulate three sources and price in the middle: sold listings (what buyers actually paid), live listings (what the market's asking), and auction results (the wholesale floor).
Ask the Computer on any pane: "price a 2019 Exmark Lazer Z 60in, 1,100 hrs" — it sweeps these sources and returns a range with the comps it used. Mike's gut prices go in Mike Knowledge so the two can be compared.
Pricing groundwork Waiting on Mike session
Task on the board: confirm cost, list, retail, matrix/markup, dealer pricing and special customer pricing rules before go-live. Mike knows which common products sell below MSRP — that knowledge lives in his head and needs to land in Ideal's pricing setup.
Live margin and price-exception metrics connect once Ideal is transacting.
Vendor action items —
Rebates to chase, programs to verify, events, swag asks, relationship moves. Complete clears it; Edit/Ask talks to the Computer. Every scheduled sweep watches vendor emails and adds what it finds.
Add a vendor item
The lines
Reps, terms and notes fill in as the Computer learns them — tell it rep names and numbers on any card, or drop them in Operational Knowledge.
Search the archive Invoices · estimates · POs · rebate forms · warranty registrations
This is the store's paper memory: anything tied to a customer that ever hit a printer — invoices, estimates, purchase orders, rebate forms, warranty registrations — scanned, read by the Computer, and searchable by customer, phone, email, serial, model, date, or vendor. Every result links back to the original scanned document.
How documents get in here
- One-touch (primary): the ScanSnap. Press Scan — ScanSnap Cloud drops the PDF into OneDrive → ScanSnap, and the AI agent takes it from there. One-time setup: in ScanSnap Home/Cloud settings, set the OneDrive destination folder to /ScanSnap and turn on searchable PDF (OCR).
- Alternate: drop files straight into 07 - Customer Records → 00 - Scan Inbox from any device (OneDrive mobile scan works too).
- The AI agent sweeps both inboxes on every scheduled run: extracts customer, phone, date, vendor, model/serial and amount; writes the searchable record with a confidence rating; archives a copy to 01 - Archive and moves the ScanSnap original to ScanSnap → Processed. The scan is never the only copy of the evidence.
- Uncertain reads are flagged, never guessed — low-confidence records show a review badge and link the source doc so a human settles it.
This is the historical-memory layer from your MLSCI roadmap (§12) — the Archive holds the paper trail; live customer and equipment records stay in Ideal's CRM at go-live. Decades of paper join the Archive one scanning session at a time.
Financial grade Sample · scored live from QBO at go-live
Cash position healthy and the line of credit is untouched, but net margin runs thin (planning model: 1.7% annual) and the fall loss months are ahead. Graded on: balances vs. operating floor, LOC headroom, net margin trend, upcoming-expense coverage, and AR/AP once live.
P&L review Sample · from the planning baseline
The P&L button lands on the report itself, not the report list. Until QBO carries real transactions, figures follow the 12-month planning baseline (worksheet linked above): $2.8M revenue, 1.7% net, March ~10× January.
Upcoming expenses — next 30 days Sample schedule
Feeds from QBO bills + recurring schedule at go-live; the Computer flags anything that would push Operations Checking below the floor.
The Computer's financial read AI · refreshed every sweep
- Health: stable, thin-margin. Balances cover the 30-day committed expenses ~2.3× — comfortable, but the planning model says Sep–Nov run at a loss, so today's cushion is the winter's fuel.
- Watch the COGS card vs. inventory turns — inventory replenishment is 57% of revenue, the single biggest lever in the business.
- LOC untouched is the right posture — keep it for the spring inventory build (March is ~10× January), not fall operating gaps.
Financial tasks From the Master Plan
Loading financial workstream tasks…
QuickBooks — Mel Luna Saw Company Live connection
Checking QuickBooks…
The company file is live and this pane reads it directly. Bank feeds connect after close — from that point this card shows the month's P&L summary (income, expenses, net), receivables aging, and one-click into the full QBO report for the PDF.
Recommended responses AI · refreshed with the feed
- Heat pattern (now): shift demos, deliveries and callbacks to 8–11 AM; keep cold water at the counter — small thing, customers remember it.
- Revenue play: late-season service special ("beat the fall rush — blade sharpening + tune-up") converts slow walk-in afternoons into booked bay work.
- Expense play: hold whole-goods reorders through the demand taper; spring units bought now sit as trapped cash until March.
- Storm posture: any named Gulf system → same-day count of generators, chainsaws, bars/chains, fuel cans; pre-stage a "storm prep" endcap.
Live radar
The System's security sandbox doesn't allow embedding outside feeds directly in the page, so radar opens in a tab — one click, always current:
Current temperature and the 7-day strip refresh through the business day via the weather pulse; the pressure rating and recommendations are recomputed each run from actual conditions.
The MLSC weather model Rules → calibration
Weather is what fills or empties this parking lot. Rain grows grass, grass wears equipment, worn equipment walks through the door. These are the rules the System applies to every forecast at 1250 Dewey:
- Rain ≥ 0.5" → the counter gets busy 2–4 days later. Grass surges, mowers run hard: blades, trimmer line, filters and small repairs follow. Staff the counter and check blade/line depth the week after a wet spell.
- 3+ dry weeks → mowers stay parked. No growth means no mowing, no wear, no urgency. Throttle whole-goods reorders, push service specials, and let parts/service carry the stretch.
- Named storm in the Gulf → saw and generator run within 48–72 hrs. September 10 is the statistical peak of hurricane season. Standing rule: any Gulf system = same-day count of generators, chainsaws, bars/chains and fuel cans.
- 95°F+ days → the lot goes quiet after lunch. Buyers show up 8–11 AM; put your best counter coverage there, run deliveries and callbacks in the afternoon heat.
- First frost (mid-Nov here) → last-cut and winterization rush, then the floor flips to chainsaws, blowers and pre-spring service specials.
Live 7-day numbers still render in Power BI V1 (Open-Meteo). The morning refresh populates this pane's forecast tiles when its weather source validates; it never shows unverified numbers.
Photo gallery — Office Operations › Photos Live from SharePoint
Photos load straight from SharePoint at full resolution, so the first view of a big image takes a moment; loaded ones are cached. Click any photo to open the original. iPhone HEIC files can't be shown in-browser — they appear as a link instead.
Office Operations One click to the files
Library & system
Browse inside the System When you don't want to leave
People & HR Two decisions pending
Handbook baseline is drafted (Intranet → HR → Handbook - Policies); needs your policy choices, counsel review, and a Version 1.0 date. Payroll is the open decision — provider, first payroll date, and funding deadline are unset, and MLSC currently runs payroll manually.
- Fold handbook counsel review into Dillon's engagement rather than sourcing separate employment counsel.
- Offer letters, job descriptions, and the benefits overview are captured in the Command Center so they don't get lost.
Onboard a new hire Automation
Fill this in and GO — within ~30 minutes the Computer builds the six-document MLSC-branded packet into HR → Employees → <name>: Welcome & Offer Letter, Employee Information Form, Direct Deposit Authorization, Handbook Acknowledgment, Equipment & Key Issue Form (all with signature lines and DocuSign anchor tags baked in), plus the internal onboarding checklist. Government forms (I-9, W-4, MS 89-350) stay on their official versions — the checklist links them, never copies them.
DocuSign: once the one-time "MLSC Onboarding Packet" template exists in your DocuSign account, the Computer also creates a prefilled draft envelope addressed to the new hire — you open DocuSign, glance, and hit Send. (Template not set up yet — see the checklist the Computer leaves in the folder, or ask it for the setup steps.)
Offboard an employee
Generates the separation checklist and the access-revocation list (Ideal, Microsoft 365, 1Password, alarm/cameras, vendor portals) and files it under the employee's HR folder.
Final paycheck: the Computer pulls the employee's pay rate, last payroll run and pay-period dates from QuickBooks Payroll and builds a Final Paycheck Worksheet — hours through the last day, rate, gross estimate, plus PTO-payout and deduction lines — clearly marked NEEDS VERIFICATION. Nothing is filed with payroll until you and Brittany verify the worksheet and run it in QBO yourselves. (Mississippi has no state law forcing an early final-check date, but the worksheet targets the next regular payday.) Until payroll is live in QBO post-close, the worksheet self-marks "no payroll data — rate from the roster" instead of guessing.
HR files
Employees is where the automations file each person's documents — onboarding packets, verifications, coaching notes, offboarding checklists. Both buttons open right here in the System's file browser.
Quick HR actions
Each quick action opens a one-line instruction — tell the Computer who and what, and it's queued with the right template.
Draft a post The Computer tailors it per platform
Type the raw idea — a photo you took, a promo, a storm-prep reminder, a mower that just hit the floor. The Computer writes platform-fitted versions (short + hashtags for IG/TikTok, longer for Facebook, review-friendly for Google), files them in the content calendar, and brings them back for your approval. Nothing posts on its own.
Content calendar From social_calendar.json
Drafts the Computer prepares land here with dates and per-platform text — approve, copy, and post. Loads when opened from claude.ai.
Incoming messages DMs · comments · reviews
Everything customers send through the platforms, and where to answer it. Direct in-System replies switch on with the social APIs (below) — today each button lands you in that platform's inbox, already filtered to what needs a response.
Unified inbox, in-System: on the self-hosted build the Meta Graph messaging API + Google Business API feed DMs, comments and reviews straight into this card with a reply box on each — same pattern as the Workspace mail module, nothing sent without your tap. TikTok's DM API is invite-only; it joins when they open it. Spec'd with the social module in Blueprint v2.
Post from one place Today's honest toolset
Until direct APIs land (below), these are the real control rooms — the System drafts the words, you paste and publish:
One-click posting Coming with the self-hosted build
Why not yet: Facebook/Instagram and TikTok only accept posts through their APIs (Meta Graph API, TikTok Content Posting API), which need registered app credentials and a server to hold them — the same claude.ai security rule that gates the softphone. There is no connector in the registry today that posts to consumer social platforms.
On your own webserver: the serverless proxy from Blueprint v2 Phase B gets a social module — approve a draft in the calendar and it publishes to FB + IG (Graph API) and TikTok directly, with scheduled posting and the storm-season calendar driving it. Meta app registration is free; TikTok's API needs a developer account. Spec'd as Phase E½ alongside the softphone. Until then: the Computer drafts, Business Suite publishes.
Dialer Rings through Teams / your default calling app
Desktop dials through whatever handles phone links (Teams, Zoom Phone, RingCentral…). On your phone it rings the native dialer.
Quick dial
After-call note
Built-in softphone Coming with the self-hosted build
Why not yet: a true in-page softphone needs a live audio connection to a VOIP provider (WebRTC/SIP), and claude.ai locks published pages down so they can't reach outside servers. That's a platform security rule, not a missing feature of the deck.
On your own webserver it's fully doable: pick a VOIP provider with a WebRTC SDK — Telnyx, Twilio Voice, Zoom Phone, RingCentral, or a hosted 3CX — and the System gets a real handset right here: inbound ring with caller ID matched against the Customers index (their history pops before you answer), click-to-call from any customer or vendor card, hold/transfer to the counter, and call recordings filed to SharePoint next to the customer's scans. Spec'd in Blueprint v2. Until then, every number in the System is click-to-dial through Teams or your cell.
Preferences This device
Preferences live in this browser. Reset cached data clears the task cache, dismissed recommendations, and agenda done-marks (sticky notes are kept — use the board's own ✕). The sidebar menu can be rearranged by dragging items — put Weather on top if that's your morning; Reset menu order puts it back.
Change requests Batched · processed in working sessions
Log ideas from any pane with the 🛠 button (top right, next to the bell). They stack up here, indexed and dated, so we evaluate and build them in batches instead of one-at-a-time. When you're ready: open a working session and say "process the change request batch" — the Computer reads the index, implements what's approved, and marks each one done.
Documentation & versions
Connections & data sources Everything LunaSys depends on
Every data source LunaSys reads or writes is listed here with its status. On the self-hosted build, connections are managed in Azure & Entra (link above); each runs with the signed-in person's own credentials, so Microsoft's permissions are the real security layer.
Scheduled runs
Edit opens the LunaSys chat to change a run's timing — the Computer updates the schedule for you. (Schedules live on your account, not baked into this page.)
Users & permissions Coming with the self-hosted build
Today: the System is private to your claude.ai account. If you share it, each viewer signs in as themselves and every data call uses their Microsoft credentials — so SharePoint/M365 access control already decides who can see what data. What doesn't exist yet is role-based presentation (hiding panes per person).
Planned: the self-hosted version (your own domain, Microsoft Entra SSO) adds a real admin area here — add users from your M365 tenant, assign roles (Owner / Manager / Counter / Tech), and per-pane visibility per role. The full design lives in the Blueprint v2 document in MLSCI Documentation.
Search what Mike knows 59 years of it
The knowledge base is empty until the first transcripts and notes are processed — drop Otter exports in the transcript folder and the Computer builds this index automatically, one topic at a time, each linked to its source.
Capture something Mike said
Dictate uses this browser's speech-to-text — talk and it types into the box for you to fix up before capturing. For full meetings, Otter is still the right tool: record there, export, drop the transcript in the library below.
The library
- Otter recordings: export transcripts from Otter (text or PDF) and drop them into 00 - Otter Transcripts — every scheduled run mines new ones for knowledge, files distilled topics into the searchable index and the KB docs, then moves the transcript to Processed. Nothing is ever deleted.
- His written notes: scan or photograph them into 01 - Mike's Notes (ScanSnap works — just move them to this folder, or drop directly). They get the same treatment, with the original always preserved and linked.
- The goal: when Mike walks out in month six, everything he knows about this shop — customers, vendors, pricing habits, where the bodies are buried — lives here, searchable at the counter.
GO creates a ready-to-send draft in your Outlook or Gmail — nothing sends until you hit Send. Data refreshes each weekday morning from a full sweep of connected sources.