Lightspeed · CFO

What a CFO gets out of Lightspeed

Ward pulls from Lightspeed Retail read-only and hands back insight cards scoped to finance. Your P&L surprises are born on the store floor.

Ward and Lightspeed for CFO / VP Finance

Your P&L surprises are born on the store floor. Ward pulls forward the inputs that change a finance decision.

How the connection works. Ward connects via Lightspeed Retail API. OAuth-based authentication. Read-only access.

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

Reporting

Pinned views built from saved data-lake queries. Every number re-derivable from its SQL.

7d13w52w
Revenue vs. forecast
$48.2M
+4.2% WoW
Gross margin %
24.1%
−3.2pp
Fill rate, fresh
83.4%
−4.1pp
Shrink, West region
2.41%
+0.8pp
Revenue vs. forecast 13 weeks actual, 6 weeks forecast, 80% interval
Actual Forecast 80% interval
% of plan 106 94 100 forecast → W−13 W−5 today +6wk
Holt-Winters + weather regressor MAPE 4.1% at 4wk Backtested 24 months Crosses plan in 3 weeks
Forecast error by horizon MAPE, 24-month backtest
1wk 2.1%
2wk 3.0%
4wk 4.1%
8wk 6.3%
13wk 8.9%
Accuracy bar for promo decisions: ≤5% at 4wk
Models in production Every forecast ships a model card
ModelHorizonMAPE
holt_winters4wk4.1%
arima_sarimax13wk8.9%
gbm_demand1wk2.1%
bayes_hiernew store11.4%

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

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::"inventory_shrinkage"
vendor-blockedforbidModel::"labor_*"
region-west-onlypermitTenant::"acme"
on Lightspeed data, live product demo.

What Ward delivers

  • GMROI tracking by category with weekly insight cards
  • Inventory carrying cost alerts when capital efficiency drops
  • Working capital optimization recommendations based on turnover trends
  • SSS decomposition into traffic, conversion, and basket components
  • Store-level unit economics cards for capex prioritization

Data Ward reads from Lightspeed

Sales transactions
Inventory counts
Customer profiles
Purchase orders
Employee performance

Why this combination
is its own problem.

Lightspeed Retail was built for transactions, not for finance decisions. The data is right there and it is in the wrong shape. Ward ingests sales transactions and inventory counts and rewrites them as a decision.

What Ward has eyes on.

Ward pulls from sales transactions, inventory counts, customer profiles from Lightspeed Retail on a read-only connection. Nothing is written back, and your POS configuration does not change. Lightspeed stays the system of record.

What the first 90 days
actually look like.

  1. 01

    Week 1: connect

    Read-only credentials to Lightspeed Retail. Ward reads sales transactions, inventory counts, customer profiles and starts building baselines. First findings land inside 48 hours, before baselines are stable, so you can see the shape of the output early.

  2. 02

    Weeks 2 to 3: baselines

    Ward needs roughly two weeks of history per store to separate a real deviation from normal variance. During this window the findings are directionally right and the thresholds are still moving.

  3. 03

    Weeks 4 to 12: steady state

    Ward hands back daily cards on a daily cycle, each with root cause and the next step. Volume settles at a level a single person can read over coffee. The measure of success is not how many insight cards arrive, it is how many get acted on.

How Ward connects to Lightspeed Retail

Ward integrates with Lightspeed Retail POS for specialty and boutique retailers. In-store transaction data powers customer behavior and assortment insight cards.

Setup: Ward connects via Lightspeed Retail API. OAuth-based authentication. Read-only access.

Data Ward reads from Lightspeed

Sales transactions
Inventory counts
Customer profiles
Purchase orders
Employee performance

Impact metrics with Lightspeed

Customer LTV
Lapsing buyers flagged
Purchase cadence and segment data reveal re-engagement windows.
Conversion Rate
Staffing-timing link found
Transaction data reveals which staff and hour combos convert.
Revenue per SKU
Whitespace identified
Underperformers and assortment gaps surfaced from sales data.
Inventory Accuracy
Count-to-velocity matched
Inventory counts reconciled against POS sell-through live.

Data lake enrichment

Ward enriches Lightspeed data with: Sales transactions, Customer profiles, Weather & events, Competitor data, Demographic data

Your P&L surprises are born on the store floor.

Pain points
  • ×Margin erosion only surfaces at month-end close
  • ×Inventory carrying costs are a black box
  • ×Working capital tied up in slow-moving stock nobody is watching
  • ×Same-store sales comps lack decomposition into actionable drivers
  • ×Capex decisions for store remodels lack unit-economics evidence
How Ward helps
  • GMROI tracking by category with weekly insight cards
  • Inventory carrying cost alerts when capital efficiency drops
  • Working capital optimization recommendations based on turnover trends
  • SSS decomposition into traffic, conversion, and basket components
  • Store-level unit economics cards for capex prioritization

Inventory distortion, overstock and out-of-stock combined, costs retailers $1.77 trillion globally. Source: IHL Group

Frequently asked questions

Ward connects via Lightspeed Retail API. OAuth-based authentication. Read-only access. Data points include: Sales transactions, Inventory counts, Customer profiles, Purchase orders, Employee performance.

Your P&L surprises are born on the store floor. Ward solves this with automated insight cards: GMROI tracking by category with weekly insight cards. Inventory carrying cost alerts when capital efficiency drops. Working capital optimization recommendations based on turnover trends.

First insight cards arrive within 48 hours of data connection. Ward needs approximately 2 weeks to establish stable baselines for your specific operation.

No. Ward sits on top of your existing stack. It is the proactive intelligence layer that watches your data continuously and delivers insight cards, so your team acts on findings instead of hunting for them.

See what your stores are hiding.

Root causes, not just alerts. See it on your data.

Read-only to start · your LLM keys · SOC 2 Type II underway · or book a call directly

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