Collaboration

The best number for sales, marketing and finance - built on evidence.

Sales, marketing, finance and your customers add their input to one live plan. Deep Sensing logs every input with its owner and evidence, scores it against what really happened, and gives inputs with a track record more weight.

One plan
Week 12 · Retailer North
Deep Sensing live
Every input logged with its owner and evidenceSales, marketing, finance and customers, on one plan Scored against what really happenedInputs with a track record carry more weight next cycle Sales · CRM updateMarketing · campaignFinance · budgetCustomer · WhatsApp Added valueMade it worseNo effectAdded value HZN-1 baseline6,200Best number7,200weighted by track record
Added valueMade it worseNo effect
Next cycleWeight
Launch dates from salesMore weight
Adjustments without evidenceEvidence first
Haircuts without a reasonUnchanged
Output
One best numberWhose input added valueCredit for good judgment
Every input on the record · every cycle
1best number

for sales, marketing, finance and customers

SMFC
7,200 units
4steps

every input logged, scored, weighted and credited

LoggedScoredWeightedCredited
<24hours

up and running with Horizon Instant

ConnectMapPlan24 h
One planweighted by track record SalesMarketingCustomersFinanceCustomer-level risk and upsideCampaigns and market shiftsUpdates over WhatsAppBudget and latest estimate
Planone plan, weighted by track record
SalesCustomer-level risk and upside
MarketingCampaigns and market shifts
FinanceBudget and latest estimate
CustomersUpdates over WhatsApp

What you can do

Every voice in the plan, every input accounted for.

Consensus

One consensus number for sales, marketing and finance

  • Sales adds its own read on customer-level risk and upside, account by account, backed by the CRM.
  • Marketing feeds in campaign, launch and market-shift assumptions before they show up in the sales numbers.
  • Finance checks the demand outlook against budget and the latest estimate, on the same plan.
Consensus plan
Week 12 · Retailer North · one plan for every team
HZN-1 baselineProprietary AI engine · best blend for this item6,200 Customer-level upsideSales · backed by a CRM update+600 Campaign at Retailer NorthMarketing · campaign brief+400 Budget and latest estimateFinance · checked on the same plan✓ In line CONSENSUS PLAN · WEEK 12 6,2006,8007,200 BaselineSalesMarketing ✓ Checked by finance

Deep Sensing

Input read where it’s already written, no re-keying

  • Deep Sensing reads updates where teams already write them: CRM opportunities, emails in the CRM and sales chats.
  • Each update is linked to the right items, customers and locations, and recalled against similar past events.
  • Its impact is quantified per item, DC and week, and every number traces back to its source.
Signal to number
One CRM update · Retailer North · illustrative
CRM · 08:12 · OPPORTUNITY UPDATERetailer North: launch moves from week 14 to week 12Confirmed by the customerKey account manager 1 · ReadLaunch to week 12 1 · ReadLaunch to week 12 2 · Link14 items, 2 DCs 2 · Link14 items, 2 DCs 3 · Recall3 earlier launches 3 · Recall3 earlier launches 4 · QuantifyPer item, DC, week 4 · QuantifyPer item, DC, week WEEK 12: HOW THE NUMBER WAS BUILTHZN-1 baselineLaunch volume · CRMEarly reorders · event memory30,000+38,000+2,000Plan, week 1270,000 Same data, same answer · traced back to its source

Customer collaboration

Customers update the plan, even over WhatsApp

  • Customers log in to the same platform and see their own demand and order data, not a file emailed last week.
  • No login needed: a customer can text an update in plain language over WhatsApp.
  • Horizon checks it against the plan straight away and flags it back if the item or location doesn’t exist.
  • A valid update lands on the planning board with old and new value, reason and a discussion thread.
Customer update
Customer Italy · WhatsApp to planning board · illustrative
CUSTOMER PORTAL · ITALYYour demandYour open ordersOnly your own data WHATSAPP · NO LOGIN NEEDED Update item 5287 at location 15,customer Italy, Jan-26 → 20,00009:14 ✓ Checked against the planItem 5287 · location 15 · customer Italy found PLANNING BOARD · LIVEItem 5287 · location 15 · Jan-2616,500→20,000Reason: customer update · old and new value kept · 1 comment in the thread

Forecast value added

Every input scored against what really happened

  • Every input is logged with its owner and the evidence behind it, not folded into an anonymous adjustment.
  • Each one is scored against actuals: added value, made it worse, or no effect.
  • When two inputs disagree on the same item, Horizon raises the conflict instead of averaging it.
Decision ledger
Week 41 · scored against actuals · illustrative
INPUTBYBACKED BYEFFECT Launch moved to week 12Key account managerCRM update Added value +12% on garden rangeRegional salesNothing Made it worse Phase-out pulled forwardProduct managerLife cycle update Added value −5% consensus haircutS&OP meetingNo reason No effect TWO INPUTS DISAGREE · GARDEN RANGE, WEEK 12Regional sales: +12%Marketing: no changeRaised for review, not averagedOwner asked for the evidence

Weighting

The plan learns whom to trust, every cycle

  • See whose input adds accuracy this quarter: HZN-1, CRM and email signals, sales input and planner overrides.
  • Inputs with a track record carry more weight next cycle; overrides that cost accuracy get asked for a reason first.
  • Good judgment gets the credit: when your forecast beats the override, the record shows it.
Whose input adds accuracy
Forecast value added in points of accuracy · illustrative
POINTS OF ACCURACY ADDED · THIS QUARTER HZN-1 baseline +3.1 pts The baseline CRM signals +1.4 pts Weighed more Email in the CRM +0.9 pts Weighed more Sales input +0.6 pts Weighed more Weather +0.3 pts Unchanged Planner overrides −0.4 pts Asks for a reason FINALLY, PROOF YOU WERE RIGHTYour forecastSales overrideWhat actually sold1,2001,4501,180✓ Credited to you

Access

Access down to role, page and saved view

  • A new role, like Customer, inherits from a base access level; permissions pass down automatically.
  • Each module or page can be visible, hidden or view-only, down to who can make a change.
  • Customers log in under their own account type and see only their own demand and order data.
  • Planners save their own favourite views, on top of role-based access.
Roles and access
Edit, view or hidden, per module · illustrative
ROLEFORECASTORDERSBUDGETADMIN Planner Edit Edit View Hidden Sales Edit View Hidden Hidden Finance View View Edit Hidden Customernew role · from ViewerViewEditViewViewHiddenHidden Customer Italy sees only its own demand and order data SAVED VIEWS · PLANNERAll itemsMy key accountsLaunch watch✓ Saved
FAQ

Demand planning collaboration, answered.

How do sales, marketing and finance work on one plan?

Horizon builds one number for sales, marketing and finance, based on evidence, so everyone works from the same plan.

How does Horizon decide whose input to trust?

Deep Sensing scores every input against what really happened, so the plan learns whom to trust and weighs each input by its track record.

Do colleagues need to work in Horizon to give input?

No. Deep Sensing reads input where it already lives: CRM notes, customer emails and Excels, sales chats and call notes. Ori follows up with the people who know when something needs clarifying.

What happens when inputs conflict?

The Scenario engine models the options with their drivers and assumptions, and Ori ranks the decisions that matter by impact. Within boundaries agreed with you, Horizon acts on its own; decisions outside them go to your planners.

One plan for everyone, on your own data.

Horizon Instant: up and running in less than 24 hours.