Owner Insights Dashboard

One place to see the whole business — every location, every channel — by unifying Toast and DoorDash data into a single, owner-friendly view, with an AI layer that surfaces what to do next.

▶ Live prototype: dashboard-demo/index.html (clickable, with sample data)

Why build it

The case in one paragraph

Today the business lives in two separate portals (Toast and DoorDash) and nobody sees the whole picture. The dashboard unifies them so the owner can answer the questions that actually move money: Which location is under-performing? How much is the DoorDash marketplace really costing us? Who are our best customers and are they coming back? What should we promote, and when? It also makes the "own vs. rent" story concrete — putting a dollar figure on marketplace leakage every month.

Positioning: most web freelancers stop at a website. A living view of the business — plus AI insights — is a differentiated, higher-value layer that deepens the relationship and is hard to churn out of.

Where the data comes from

Data sources

Source	What it provides	Access path
Toast API	Orders, item-level sales, guests, loyalty/rewards, revenue by location	Toast developer/partner credentials, an approved connector, or scheduled exports
DoorDash Reporting API	Marketplace sales, operations & finance; aggregate customer analytics (new vs. returning, zip heatmaps)	Merchant Portal API access, direct or via partner (e.g. ItsaCheckmate)
Google Business Profile (optional)	Views, searches, direction requests, calls, review trend per location	Google Business Profile API / Performance API

Reality check: the data is accessible, but exact access tiers and any fees are plan-dependent and must be confirmed with Valentino's Toast and DoorDash reps. This spec assumes read-only reporting access — no changes to their POS or menus.

What it shows

Core views (v1)

📊 Business overview

Revenue, orders, avg ticket, returning %, loyalty growth — filterable by location and date range.

🚗 Channel mix & leakage

First-party (Toast) vs. DoorDash marketplace, with the monthly commission + lost-data cost quantified in dollars.

👥 Customer health

New vs. returning, repeat rate, lifetime value, and a win-back list of lapsed customers.

🍕 Menu & items

Top items by margin × popularity — the stars to promote and the laggards to fix or cut.

⏰ Timing heatmap

Order volume by day & hour to target slow windows with promos instead of discounting peak.

🤖 AI insights

A weekly Claude-generated summary: what changed, what's at risk, and one or two concrete actions to take.

How it's built

Technical approach

🧱 Stack

Astro on Cloudflare Pages — the same low-cost, easy-to-hand-off stack as the website.

🔌 Data layer

Scheduled jobs pull each API into a lightweight store (Cloudflare KV/D1); dashboard reads from that cache — fast & API-friendly.

🔐 Access

Read-only, password-protected, owner + managers. No customer PII leaves the client's control.

How we'd build it

Phased plan

Access & foundation ~1 wk · low

Confirm Toast + DoorDash API access, stand up the Astro/Cloudflare shell and data store, wire the first pull.

Core dashboard ~2 wks · med

Build the overview, channel mix/leakage, revenue-by-location, and customer-health views on live data.

Menu, timing & polish ~1 wk · med

Add item margin analysis, the day/hour heatmap, filters, and mobile layout.

AI insight layer ~1 wk · med

Weekly Claude summary of trends, risks & recommended actions — delivered in-app and optionally by email.

Estimate: ~4–5 weeks to a live v1 once API access is granted. Delivered incrementally — the owner sees value from Phase 2 on. Exact scope & pricing to be set in the SOW.

To get started

Access checklist

Toast — developer/API access or an approved reporting connector (via their Toast rep)

DoorDash — Merchant Portal / Reporting API access for all three stores

Google Business Profile — manager access to the three listings (optional, for the traffic view)

Confirmation of which metrics matter most to the owner, to prioritize v1