Nekohama HQ · Concept by MKSP for Nekohama
Caroline's requirements and priorities, one by one. Each line links to the screen in this concept that shows how HQ meets it. Where something is planned but not drawn yet, it says so.
aKeep customer data out of AI
Code does the maths on your systems. AI only sees totals, or text with names, emails and addresses removed first. Shown
bOnly business AI plans that don't train on your data
The AI account is opened in Nekohama's name on a business or enterprise plan, with a data processing agreement you sign. Shown
cGDPR, CCPA, APPI, and agreements with every vendor
Discovery starts with a data map: what personal data sits where, and which agreement covers it. Caroline signs off before anything connects. Partly
dEvery output traceable to its source
Every number carries a source tag and a “why?” link to the rows behind it, with how fresh they are. Contract terms quote their clause and page. Shown
eAssumptions visible and editable, never hard-coded
Lead times, buffers and alert windows live on one Assumptions page, with who changed what, when and why. Any change can be undone. Shown
fA person writes or reviews anything customer-facing
AI drafts and sorts. A person edits and sends every message, in Nekohama's voice. Nothing goes out on its own. Shown
gEverything stored in your Google Drive
Contracts, reports and exports are filed to your Drive with consistent names. HQ runs on your domain and signs in with your Google accounts. Shown
1Inventory: forecasts, reorder alerts with Japan lead times, lots and shelf life
Stock by lot and expiry, days of stock, and a reorder alert built on the full lead time, including Japan's holidays. You approve every order. Shown
2Fewer manual inputs: reports, invoices and POs, drafted correspondence
Contract terms are read for you, and replies come pre-drafted. Scheduled reports and invoice reading follow the same confirm-before-it-counts pattern. Partly
3Project dashboard
Active projects with owner, deadline and status, overdue flags and a weekly summary. Waiting to learn where projects are tracked today. Planned
4Partner dashboard: contracts, renewal and notice dates, exclusivity, one Excel sheet
Every partner and date in one place, terms quoted from the contract, Caroline confirms each field, alerts at 90, 60 and 30 days, and Excel export. Shown
5CRM for inbound leads: samples, pricing, first order, follow-ups
One pipeline from inquiry to regular, with who owns each lead, where it came from, and follow-ups due today. Shown
6Trends and data integrity: mismatches, channel trends, churn risk, margins
Mismatch checks and early churn signals (a café late on its usual reorder) already appear on Home. Full trend and margin views come once all sources are connected. Partly
7Team AI training and role-specific digests
A session on responsible AI use, then digests per role with a source link on every claim. Planned
8Customer service drafts, always reviewed by a person
Tickets sorted and routed with a suggested reply, personal details removed first. Uses the same draft-then-send pattern as the lead pipeline. Planned
Concept by MKSP for Nekohama. All names and numbers in the mockups are samples.