← Hub
Flowz · Working Deck · For Elad + Aviv

Mission & Vision

One sentence that says what Flowz is, who it's for, and why it's different — plus the three decisions we need to close to lock it.

3 decisions inside Category already locked

Sources: FZ · Mission & Vision v1 (2026-07-20) · Category & Naming Strategy · Discovery Assumption Register · working session 2026-08-16

✓ Locked — no decision needed

The category: Decision Intelligence
for the Experience Economy

Why this category is real

Gartner published its first-ever Magic Quadrant for Decision Intelligence Platforms in January 2026. Their definition — "combines data, analytics and AI to create decision flows that support and automate complex judgments" — is literally our loop.

Why the space is ours

Every DI leader is horizontal enterprise — Aera does supply chains, Quantexa does financial crime. Nobody has built DI for the experience economy. That empty vertical quadrant is the company.

DataInsightsActionsFlows

The loop every screen, deck and doc already uses. "Not another CRM/BI" stays our stance.

Context — from the Sinek session

The WHY behind all of it

"We believe the people who bring people together make the world better — and they shouldn't have to do it alone."

אנחנו מאמינים שהאנשים שמחברים אנשים — עושים את העולם טוב יותר. והם לא צריכים לעשות את זה לבד.

How

"Read the signal, run the flow." We turn scattered data, gut calls and sleepless spreadsheets into clarity and confident action.

What

We happen to make a decision-intelligence platform for the experience economy. Built to act, not just to store.

The loneliness insight — "alone at the front" — returns on the next slides. Keep an eye on it.

Context — how to read the next slides

The template, and the two tests

Product is for target customer who need / pain. It is a category that key benefit. Unlike the alternative, our product does what only it can do.

Test 1 · The name test

Swap a competitor's name into the sentence. If it still reads true, the sentence says nothing. We run this on slide 7.

Test 2 · Ten real users

The sentence is a guess until ten real producers react to it. Slide 8 turns it into a testable plan inside the discovery interviews.

Where we stand — written 2026-07-20

The statement we already have

Flowz is for event and festival producers in the experience economy who are losing buyers they already won — and can't see why, because their truth is scattered across ten tools and every decision lands on them alone. Flowz is a vertical decision-intelligence platform that turns ticketing, marketing, community and finance data into ready-to-run actions — insights that become flows, tasks and campaigns, fast enough to matter. Unlike generic CRMs, BI dashboards and spreadsheets — which store data and wait for you to figure it out, our product acts: it reads the signal and runs the flow, pre-loaded with event-sector playbooks and market behavior data no horizontal tool has.

✓ Five slots still feel right ⚠ One slot in play: the NEED — Elad wants it rebuilt (next slide)

New thread from the 2026-08-16 session, not in the doc yet: "moving the whole organization together, on the same mission, at the same time." It's the flip side of "every decision lands on them alone" — deciding alone hurts, but moving everyone on that decision is what breaks people. It also matches our PMF gate: org adoption, not one enthusiastic user.

Decision 1 of 3

Pick the need. Click a card — the sentence updates live.

Flowz is for event and festival producers who are losing buyers they already won — and can't see why, because their truth is scattered across ten tools and every decision lands on them alone. Flowz is a vertical decision-intelligence platform that turns ticketing, marketing, community and finance data into ready-to-run actions, fast enough to matter — unlike CRMs, BI and spreadsheets, it acts: reads the signal, runs the flow.

Keep · Jul 20

"losing buyers they already won… truth scattered across ten tools… every decision lands on them alone"

The current doc version. Leads with churn.

Claude's pickA · Cause → effects

"truth scattered across ten tools — so problems surface late, insights don't become action, and the team never moves as one"

Keeps the 'ten tools' cause, lands all three new pains.

B · Alone → together

"see problems too late, carry every decision alone, and struggle to turn each decision into one mission the whole team runs together"

Builds on the loneliness insight from the WHY.

C · Plain three beats

"spot problems too late, can't easily turn data into action, and struggle to move the whole organization on the same mission at the same time"

Elad's words, unstyled. Honest baseline.

D · Short & punchy

"have the data but not the 'what now' — and no easy way to get everyone moving on it together"

Hits hardest. Drops the 'too late' beat.

The churn pain doesn't disappear if we move off "losing buyers" — it moves to the outcome, e.g. "more of this year's crowd shows up to your next event" (softened per Elad, 2026-08-16). Your pick is saved on this device and shows on the last slide.

Proof — the name test

Swap in a competitor. Does it break?

Rule of thumb: a slot that survives every swap is decoration. Our sentence breaks somewhere for each of them — that's what "positioning" means.

Decision 2 of 3

Approve the test plan — the sentence is three guesses in a trench coat

ASM-P01 · in the register

"Losing repeat buyers is the acute pain"

Untested. If churn doesn't surface unprompted in the first three interviews, that's the quarter's biggest finding — and the need slot changes.

untested
ASM-S01 · in the register

"Operators want decisions, not dashboards"

The whole DI bet. Desert Bass usage is founder-adjacent and doesn't count as independent evidence. Ten outside producers do.

untested
NEW · needs logging

"Moving the org together is a felt, top-3 pain"

Elad's new thread (2026-08-16). Not in the register yet. If we put it in the sentence, we test it like the others.

to log

The 10-user protocol (inside the interviews we already planned)

1. Problem-first, Mom-Test style — never open with the sentence.  2. Show the sentence only at the end: "what would you expect this to do for you?"  3. Pass = they name a real, recent situation where they'd want it. Fail = polite nodding, "sounds cool."  4. First ten: Itai, Bar, Amit + the design-partner longlist. Count honestly.

Decision 3 of 3

Where does the WHY go in the client deck?

Open question since July 20 — the belief line exists but the deck doesn't use it yet.

Open with it · Slide 1

New opening beat before the product story. Strong identity, Apple-speech energy.

Risk: slows the hook for a cold client audience.

Close with it · Slide 12

Replace the closing lede — end on the belief, leave the room with the feeling.

Safe, emotional exit. The pitch stays product-first.

Leave for now

Deck unchanged; WHY stays in pitches as Elad's spoken open.

Zero work. Revisit after the first design-partner round.

Close the loop

Three ticks and this becomes v1.1

When you've decided: tell Claude the three answers → the Mission & Vision doc goes to v1.1, the Hebrew interview version gets written, and the decisions land in the Discovery registers. Ticks are saved per device.

Flowz · Mission & Vision working deck · built 2026-08-16 · canonical copy lives in the vault, this is the hub mirror

01 / 10