About Ward

We scaled 400+ retail locations.
We know what goes unnoticed.

Ward came out of running LeanBox. It came out of every problem we found too late.

We lived the problem before we built the solution.

LeanBox was a micromarket retailer — unmanned locations inside offices, hospitals, and universities. We scaled it past 400 locations and 8 figures in annual revenue.

01
It broke quietly

A location slips. Spoilage creeps up. Nobody catches it for weeks.

02
Found too late

We had the data. By the time anyone spotted it, the damage was done.

03
We patched it

Dashboards, alerts, spreadsheets wired to APIs. It worked, barely.

04
There had to be more

Real-time visibility for operators, without building a data team from scratch.

Ward came out of every problem we found too late.

app.getward.ai Live demo
Acme Retail @Merchandising: VP Analyst claude-sonnet default
A

Chat

Ask anything. Ward routes to the right agent and returns cited answers.

Why did Store 37 miss target last week?
You · 9:42 AM
Schema Scout · routed to Merchandising Agent

I pulled Store 37’s last 28 days against the chain baseline. Two root causes, both compounding.

SignalFinding
labor_efficiencyRev/labor-hour −22% vs. cluster, staffing mismatch at 11a–1p peak
inventory.freshFresh fill 83%, backroom replenishment lag at 2–4p
promo.liftBOGO crackers cannibalized Brand Y by 28%, net category +6%

Recommend: re-baseline Store 37 schedule against true peak, raise replen window to 1p, and review the BOGO before next cycle.

8 parallel queries 3 sources cited confidence 0.92
Show me how to fix the staffing mismatch.
You · 9:43 AM
Labor Agent · drafting schedule diff
Querying labor_scheduling
Ask anything, Ward routes to the right agent. Cmd+K

Dashboards

Pinned views built from saved data-lake queries.

Revenue vs. forecast +4.2% WoW
Gross margin % −3.2pp
Fill rate, fresh 83%
Shrink, West region +0.8pp

Models

Browse, search, and manage data–lake model definitions for your tenant.

NameNamespaceVersion
retail_pos_transactionsretail1.0
retail_inventory_snapshotretail1.2
retail_labor_schedulingretail1.0
retail_promo_calendarretail1.1
retail_supplier_performanceretail1.0
sap_inventory_shrinkagesap1.0
ga4_daily_eventsmarketing1.0
meta_ads_ad_levelmarketing1.0

Sources

Connect external systems to the data lake.

NameTypeLast sync
sap_pos_transactionsimport2m ago
sap_inventory_shrinkageimport2m ago
sap_labor_schedulingimport14m ago
retail_inventory_weeklyimport1h ago
retail_google_ads_dailyimport1h ago
retail_meta_ads_dailyimport1h ago
retail_ga4_website_dailyimport1h ago

Architecture

Two ways to connect. Federate against your live systems, or ingest into Ward’s data lake. Toggle below.

Your systems · read-only
SAP Retail
Snowflake
BigQuery
Shopify
Toast POS
Ward Gateway
TLS 1.3 · AES-256
Querying live · data stays put
Federated answers
SELECT * FROM sap.pos
JOIN snow.inventory
WHERE store_id = 37
→ insight cards
Ward Data Lake
→ baselined per store
TLS 1.3 in transit AES-256 at rest Read-only credentials SOC 2 II in progress VPC peering · PrivateLink

Pipelines

Move data from sources into models on a schedule.

NameSourceModelStatusSchedule
sync_sap_pos_transactionssap_pos_transactionspos_transactionsenabledhourly
sync_sap_labor_schedulingsap_labor_schedulinglabor_schedulingenableddaily
sync_sap_inventory_shrinkagesap_inventory_shrinkageinventory_shrinkageenableddaily
sync_retail_inventory_weeklyretail_inventory_weeklyinventory_weeklyenabledweekly
sync_retail_google_ads_dailyretail_google_ads_dailygoogle_ads_dailyenableddaily
sync_retail_ga4_website_dailyretail_ga4_website_dailyga4_website_dailyenableddaily

Streams

Real-time ingestion pipelines.

0events / min
0streams active
0% delivered
  • pos.txn store_037, basket $42.18
  • inv.move dc_west → store_104
  • labor.clock store_022 shift_start
  • pos.txn store_211, basket $19.04

Policies

Browse and manage Cedar access policies for your tenant.

TLS 1.3 AES-256 Read-only SOC 2 II
Policy IDEffectResources
merch-read-defaultpermitModel::*
finance-read-shrinkagepermitModel::"shrinkage"
vendor-blockedforbidModel::"labor_*"
region-west-onlypermitTenant::"acme"

Entities

Principals and resources referenced by Cedar policies.

Entity UIDTypeTenant
Tenant::"acme"Tenantacme
Model::"sap.pos_transactions"Modelacme
Model::"sap.inventory_shrinkage"Modelacme
Model::"sap.labor_scheduling"Modelacme
Model::"retail.toast_pos_daily"Modelacme
Model::"retail.ga4_website_daily"Modelacme

Providers

Manage LLM API keys and the model profiles that use them.

API Keys Model Profiles
NameProviderUsed byCreated
anthropic-defaultAnthropic3 profilesApr 22
openai-defaultOpenAI2 profilesApr 22
gemini-defaultGemini1 profileApr 22
ollama-onpremOllama2 profilesApr 22

LLM-agnostic. Bring your own key, route per task. No lock-in.

Settings

Manage your dashboard preferences and account.

Appearance
Theme • Light ° Dark

Light and dark themes are available. Your choice is remembered per browser.

Account
NameAdmin
Emailadmin@acme.io
Tenantacme-retail
The platform we wished we had at LeanBox. Now building it for every retail operator.

We custom-built the entire stack. Every piece of it.

No off-the-shelf tool fit unmanned micromarket retail at our scale. So we built it all.

400+locations operated
8-figannual revenue
5custom-built systems
Custom ERP

The system of record that ran inventory and replenishment.

Self-service POS

Kiosk checkout capturing every transaction at unmanned locations.

Web & mobile ordering

Inventory and ordering unified on the same data.

Pipelines & ETL

Five systems wired together into one source of truth.

Anomaly detection

Catching drift and alerting before it hit the shelf.

It took an engineering team most operators cannot afford. Ward packages all of it into a platform that works out of the box.

Enterprise-grade systems, shipped by the team that ran the stack.

The AI breakthroughs already happened in the labs. The hard part is making them run inside a 200-store operation where the ERP dates to 2014 and the POS still exports CSV. That part we own, end to end.

From the floor and the codebase

Managed routes. Renegotiated suppliers. Found why location #247 dropped 30% in two weeks.

Shipped, not theorized

We built the ERP, POS, and data systems that ran 400+ locations through 8 figures of revenue.

The hard part is the mess

We have already shipped systems that survived multi-hundred-location retail. Ward is us doing it a second time.

AI recommends. You decide.

Ward surfaces what matters. Humans make the call. Lane assist, not autopilot.

The same team behind LeanBox and askotter.ai.

Retail operators who became data engineers who became platform builders. Ward is the latest product from a team that has shipped together for years.

Brian C.
Brian C.
CEO / Founder

Scaled LeanBox from concept to 400+ locations and 8-figure revenue. Custom-built the ERP, POS, and data stack that became the blueprint for Ward. 15+ years in growth marketing and software engineering.

Chad B.
Chad B.
Chief Product Officer

Ex-YC and Meta. Helped build and scale LeanBox's product suite. Product strategy, frontend engineering, and platform design. Turns operator pain points into interfaces that actually get used.

Edward C.
Edward C.
Chief Architect

Ex-YC and Amazon. Backend systems, data infrastructure, and cloud architecture. Designed the pipelines that process millions of retail transactions at scale.

Brian L.
Brian L.
Strategic Advisor

Investor and operator with multiple exits across consumer and technology. Advises on business development and market strategy.

Retail is the hardest observability problem nobody is solving.

Engineers have had Datadog, PagerDuty, and Grafana for years. We bring that engineering-grade monitoring to retail.

A server goes down, someone gets paged in minutes. A location drops 20%, and it sits in a spreadsheet for weeks.

Stockout prediction, shrinkage detection, demand forecasting, price optimization — running continuously across every location and every SKU, every day.

minutesto page an engineer
weeksbefore retail notices
24/7every location, every SKU

POS, Transactions & Inventory

Every sale, refund, and basket across every location, unified and watched in real time. Stock levels, spoilage, fill rates, and reorder signals run on the same view. Anomalies get caught before they hit the shelf.

Finance, Margin & Operations

Per-location P&L, COGS drift, and margin erosion get flagged automatically, not found in month-end close. Scheduling, route efficiency, and service levels surface alongside them. These are the operational signals that hit the bottom line.

We built Ward because we kept finding problems too late.

The shrinkage we couldn’t attribute. The promos we couldn’t score. See what Ward finds in your data.

Get a demo

Find out what your data has been hiding.

Tell us about your operation. We’ll show you the problems Ward catches, and the ones your current tools miss.

Step 1 of 3
What are your goals?
Step 2 of 3
About your operation
Step 3 of 3
Your contact info