Business Manager by Business Mate

🤝 How the handoff works

Business Manager cannot reach inside a toolkit — no web app can. So when a command belongs to one of your toolkits, Business Manager carries your words to that toolkit and opens it. The toolkit's own Mate hears the command, shows you exactly what it will do, and waits for your OK. Nothing changes anywhere without your confirmation — twice over.

🗂 Your commands

0 commands · stored only on this device.

🎙️ How it works

• Say or type one command, as the owner. Business Manager figures out which of your five toolkits owns it.
• Routing is a proposal. It shows you the command and the toolkit — you tap ✅ Send it (or say yes) before anything travels.
• The toolkit confirms again. Inside the toolkit, its own Mate shows the exact change and waits for your OK. Business Manager never changes business data itself.
• Not sure which toolkit? It asks — answer with a number, a name, or a tap ("4", or "Accounts").
• Name a toolkit to aim a command: "In Accounts, mark the rent bill paid…" or "Ask Inventory what arrives this week…".
• General questions live elsewhere. Weather, knowledge and everyday lookups belong to the household Mate Manager — Business Manager will offer to take you there with your question.

🔒 What Business Manager never does

• Never sends messages, emails or invoices for you.
• Never buys, orders or pays for anything.
• Never changes any toolkit's data itself — it only routes. Every change is proposed and confirmed inside the destination toolkit.
• Never holds business data: its only records are its command log and your settings, on this device.
• Never uploads, syncs, or shares your data.

💡 Examples by toolkit

• 🏭 Products & Development: "Move the new lamp to prototype" · "What are the product milestones this month?"
• 🧾 Sales & Marketing: "Add an invoice for Acme, $450, due Friday" · "Add a new customer, Mrs. Chen" · "Plan a spring marketing campaign" · "Schedule a meeting with Mrs. Chen"
• 📦 Inventory & Orders: "We're low on stock of boxes" · "Order 200 boxes from BrightPack" · "Add a new supplier"
• 💰 Accounts: "Who owes us money?" · "What bills are due this week?" · "Show the cash position" · "Record a payable for the rent"
• 📊 Accounting Reports: "Show the profit and loss report" · "Generate the accounting report" · "How is the business doing?"

Each toolkit has its own sign-in (name + PIN). If a toolkit asks you to sign in the first time, that's its own lock — Business Manager's PIN never opens another toolkit.

🧑‍💼 The two manager roles (required)

Every Business Mate deployment names a Data Manager and an Apps Manager — in a very small business, one person may hold both roles. The roles are required, not the headcount. Together they run the Local Sync Script Pack, which syncs the toolkits' export packages across the office — locally only, on the office PC / NAS or a Syncthing folder. Scripts never read or write a toolkit's own storage; the Export package is the only bridge.

📁 The local sync folder (on the office PC / NAS):

/BusinessMateSync/
  inbox/       ← toolkit exports land here (one file per toolkit)
  snapshots/   ← verified, dated snapshot sets (YYYY-MM-DD/)
                 — Reports imports from here
  archive/     ← rotated backups (daily ×7, weekly ×4)
  logs/        ← sync-log.txt (every run, auditable)

🗂 Data Manager — checklist

1. Export schedule: every toolkit is exported on the set schedule (e.g. end of day) into the sync folder's inbox/.
2. Run the scripts in order: biz-sync-collect → biz-sync-verify → biz-sync-stage → biz-sync-backup → biz-sync-report.
3. Collect: confirm the newest export of each toolkit is present; chase any toolkit whose export is stale or missing.
4. Verify: packages must parse, carry their expected sections, and show sane entry counts. The run FAILS if any PIN or credential field is found in a package — a failed package is rejected and reported, never repaired by hand or by script.
5. Stage: the verified set becomes a dated snapshot under snapshots/. Incomplete sets are staged as INCOMPLETE and flagged — Reports never runs silently on half the business.
6. Backup & rotation: snapshot sets are copied to archive/ (daily ×7, weekly ×4). Pruning beyond the rotation needs your explicit confirmation — every time.
7. Read the log: biz-sync-report writes each run's result to logs/ — what was collected, verified, staged, what is stale, what failed and why. It is the morning checklist and the audit trail.
8. Data quality: you own the human side of the auditing gate — the toolkits' confirmation checkpoints stop bad writes; you keep the export discipline that keeps the office in step.

🧩 Apps Manager — checklist

1. Versions: own which build of each toolkit is live — the three-way sync of live app / working file / master copy — and know what changed in each release.
2. Rollouts: roll updates out to staff devices and confirm each device is actually running the new build.
3. Sign-ins: administer each toolkit's own name + PIN sign-ins; help staff set up or reset theirs. PINs are personal — never shared, never exported.
4. Support: first line of troubleshooting. These apps are deterministic — the same command behaves identically every time — so reproduce the exact words that failed, then escalate with them.
5. Updates never touch data: an app update changes code only. If an update ever appears to change records, stop, export a backup, and escalate before going further.

👤 Account

Your PIN is never exported and never leaves this device.

📦 Your data

Export saves your command log and settings (never your PIN, and never business data — this Manager holds none). Import restores them here.

🛡 Privacy