FLOWZ · TECHNICAL OVERVIEW

Technology & Delivery

What's running today, what ships next, and how fast we move.
Companion to the Flowz product deck.

Data core · live Dashboards · live Channels · in process Intelligence · roadmap

AUGUST 2026 · CONFIDENTIAL

THE SYSTEM

One pipeline – from raw data to executed action

🔌

Sources

  • Ticketing systems
  • Email marketing
  • Ads & social
  • WhatsApp
  • Backoffice files
Live + growing
🔄

Sync Engine

  • API sync or dedicated parser
  • Runs every few minutes
  • Normalization & parsing
  • Identity resolution
Live
🗄️

Data Core

  • Unified customer & commerce model
  • Lifecycle & LTV computed in-database
  • Any vendor maps in
Live
🧠

Intelligence

  • Algorithmic insights – signal rules
  • Agentic insights – AI reasoning
  • Flowz – orchestrated actions
Roadmap
🚀

Activation

  • Meta & Google campaigns
  • WhatsApp · Email · SMS
  • Tasks & write-back
In process
Live In build In process Roadmap

The core loop: Data → Analyze → Insights → Flows (Actions)

LIVE TODAY

A production data platform – not a prototype

🧩Unified data model

One clean model for customers, orders, tickets, events, products, campaigns & communications. Every record keeps track of which system it came from – so any vendor's data maps into the same structure.

🔄Continuous sync

Automatic sync pulls fresh data from the connected platforms every few minutes – plus a one-shot historical backfill that loads years of past events and orders on day one.

🪪Parsing & identity

Phone-first customer identity with email fallback and cross-source dedupe – one person stays one person across systems, files and brands. Built for the messy reality of real-world event data.

📈Intelligence at the data

Lifecycle stages, retention & LTV profiles, and sales velocity vs past editions – live in the app today, computed right where the data sits instead of in spreadsheets.

In production for Desert Bass Festival· Multi-year order history· 300k+ communications synced· Zero-downtime upgrades on a live system
SYNC FABRIC

Ticketing & email – synced, normalized, acted on

🎟️ Ticketing Live

Clients, orders and full ticket history flow into a living client profile – through a live API or a dedicated parser, depending on the platform. Where the platform allows it: list creation, order edits and more advanced actions.

Currently in use Vibez · Eventbuzz · GoOut
Expansion Any ticketing platform – live in  1–2 weeks, via API or dedicated parser
✉️ Email marketing Live

Lists sync and campaigns launch directly through the client's own provider – contacts, lists, campaign history and engagement all feed the customer profile. Exporting lists is always an option.

Currently supported Smoove
Expansion Additional email providers –  1–2 weeks each
The connector playbook: one unified data model + an adapter per platform – API or parser – so new integrations land in weeks, not quarters.
THE COCKPIT

ControlRoom + three smart dashboards – live

CONTROLROOM – GLANCE · PACE GRAPH · INSIGHTS | FLOWZ

🎛️

ControlRoom

The operator's landing view – live status, sales trackers and what needs attention, in one viewport.

Live
💰

Sales

Per-event tracking, pace vs past editions, pricing views and projections.

Live
💜

LTV / Community

Lifecycle × value-tier view of the whole audience, with drill-downs and exports that match the screen.

Live
📣

Reach

Channel performance, audience growth and campaign results against targets.

Live
🖥️

v1 dashboard

The original production app – running the business daily while the new surface lands.

Live · daily use

Final touches in progress: refreshed tier definitions and per-event targets (break-even, sell-out). The insight & flow panels arrive with the intelligence roadmap.

THE KEY LAYER · ROADMAP

Insights & Flowz – where data becomes action

INSIGHT – what the data says. A read-only signal computed from the org's live data: pace, churn risk, pricing windows, budget drift.
FLOW – what to do about it. Orchestrated across marketing, sales, community and finance – with approval gates where it matters.

📚A proprietary bank, 100 items deep

50 insights + 50 flows, each specified down to its exact data needs and paired action – written from years of operating real events. The engine's curriculum, ready before the engine.

🧮Track 1 – Algorithmic insights

Signal rules computed straight from the data: pace vs target, churn flags, budget drift. The first track on the roadmap – concrete, measurable, no magic.

🤖Track 2 – Agentic insights

AI reasoning over the organization's data, grounded in the bank and market-behavior playbooks. The deeper build – sequenced after the algorithmic track proves out.

What it will look like
📉 INSIGHT – "Sales stalled: 4 days below daily target"
CRMCharacterize leaders & abandoners
MarketingSchedule pushes + content briefs
TasksAssign 3 creatives A/B/C
TrackMeasure & repeat

A roadmap item we take seriously: the bank is written, the surface is built, the tracks are defined – work on the algorithmic track starts in the coming weeks, prioritized with our design partners.

FROM INSIGHT TO CAMPAIGN

Every insight can turn into a campaign

📱 Meta Ads – Facebook + Instagram In process

Create and manage ads across feed, stories, reels and marketplace; read real-time analytics; target by age, gender, location, interests and behaviors; build audiences and lookalikes from any Flowz segment.

Via a certified technology partner – already validated · ~4 weeks
💬 WhatsApp In process

Official WhatsApp Business platform through a compliance-certified partner: broadcast to CRM segments, chat-bots, two-way conversations, and ads that click straight into WhatsApp – on the client's own number. The connection is quick; the customer-communication interface is the real build, and we're building it properly.

Via a compliance-certified partner · ~4 weeks
🔎 Google Ads Roadmap

Campaign creation and launch through a certified tech partner, with real-time spend, CTR, CPC and CPM per ad. A supporting channel by design – not the main focus.

Partner route mapped · ~4 weeks
📨 SMS / MMS Roadmap

For markets where texting leads – the US in particular – SMS/MMS over the client's own number, custom numbers on request, riding the same segment rails.

High feasibility · ~4 weeks
All channels ride the same rails: segment from the data core → template → approval → send → results back into the profile.
BUILT TO HOST MANY BRANDS

Isolated by design – owned by the client

🏢Organization isolation Built

Every client's data lives in its own isolated organization – separate access, separate connections, separate modules. One organization can never see another's data, and a user with no organization sees nothing at all.

🧬Multi-brand Optional build

Today, each brand can run as its own fully-isolated organization. A unified cross-brand portfolio view – one dashboard over all brands – is an optional build, 5–7 weeks once we prioritize it together.

🔑Client asset ownership

Clients keep ownership of their ad accounts, messaging numbers and data – always. Flowz connects with permissions the client can revoke; it never takes custody.

🛡️Security & compliance track Scheduled

A dedicated security specialist runs a full review of the stack – data rules, permissions, secrets – ahead of enterprise onboarding, once terms and roadmap are agreed. Verified, not assumed.

HOW WE SHIP

Small team. Industrial pace.

What the pace so far produced

Everything in this deck was designed, built and shipped by a two-person founding team working AI-accelerated: a full data platform, 20+ shipped features, a new product surface, and a 100-item intelligence bank.

🚀And that was the slow version

At GO, the engineering bench is ready – capacity scales the day the decision is made, not after a hiring cycle. We accelerate beyond the demonstrated pace; what remains is focus: pick the vertical, fit the demands per client, ship.

🧭The per-client assembly line

1. Survey & data inventory  →  2. Bundle assembly (core + optional)  →  3. Integration validation before deployment  →  4. Build & onboard  →  5. Usage-driven v2. Onboarding a client is a process, not a project.

New integration · 1–2 weeks New channel · ~4 weeks Multi-brand view · 5–7 weeks, optional
NEAR-TERM TECH PLAN

Hardening before scale – on purpose

🛡️Security & compliance pass

A dedicated specialist reviews the full stack – data rules, permissions, secrets, privacy practices – before enterprise onboarding. Scheduled as part of the agreed roadmap, so commitments are verified, not assumed.

🔁Rebuilt on the new surface

Utilities being brought over and hardened as the new app becomes the main one: Hebrew–English name matching, AI-powered search, and deeper operational logging.

🎯Product finishing

Refreshing the customer tier definitions and adding per-event targets – break-even, sell-out and friends – across the live dashboards. Touch-ups, not construction.

🧭Optional builds, by priority

The cross-brand portfolio view (5–7 weeks) and further modules get scheduled by the priorities we choose together – the roadmap bends to the partnership, not the other way around.

None of this blocks a pilot – it's the professional path to enterprise-grade.
THE HONEST TABLE

What ships when

CapabilityStatus todayTime to productionHow
Additional ticketing integrationsPlaybook proven1–2 weeks eachLive API or dedicated parser
Additional email integrationsPlaybook proven1–2 weeks eachProvider API
Meta AdsValidated · in process~4 weeksCertified technology partner
WhatsApp officialValidated · in process~4 weeksCertified partner + communication interface
SMS / MMS · Google AdsPartner route~4 weeksCertified partners
Multi-organization workspacesBuiltIn the appEach client – or brand – fully isolated
Cross-brand portfolio viewOptional5–7 weeksScheduled by chosen priorities
Security & compliance reviewScheduledPre-onboardingDedicated specialist
Insights & Flowz engineRoadmap · 2 tracksPrioritized with partnersAlgorithmic first, agentic after

Timelines assume parallel execution – integrations, channels and product finishing proceed simultaneously; demos ship faster than production dates.

Production-grade platform approvals key off company formation – in progress.

THE BOTTOM LINE

When it's GO – we ship.

The platform is ready

Data core and dashboards live in production, connector playbook proven, activation channels validated and already in process.

📈

The team scales on decision

Tech people ready to onboard the day it's GO – we accelerate past the pace that built everything you've just seen.

🎯

Fit is a process, not a project

Choose the vertical, map each client's demands, assemble their bundle – the same playbook that put the current deployment live.

FLOWZ

Decision Intelligence for the Experience Economy · Companion deck: product & vision

Appendix · A1

System architecture & stack

🗄️Data layer

PostgreSQL · single source of truth
  • Every table enforces per-organization access rules
  • Scheduled sync jobs run from inside the database
  • Analytics computed where the data sits – not in the browser
  • Nothing hard-deleted; history is preserved
  • Every synced record keeps its source system & ID

⚙️Sync layer

One adapter per platform
  • Live API connections where the platform offers one
  • Dedicated parsers where it doesn't
  • Incremental sync every few minutes
  • Full historical backfill for onboarding
  • Credentials stored securely, per organization

The stack

SupabaseManaged PostgreSQL database, sync services & authentication
VercelApp hosting – every release deploys automatically
ReactThe dashboard application
Certified partnersMeta & WhatsApp rails at stage A
Provider systems Adapters & parsers One unified model Lifecycle · retention · velocity Dashboards
Appendix · A2

Multi-organization & security – the plain view

🏢One home per client

Every client – or brand – is its own isolated organization. Data never mixes between organizations, full stop.

🚪Access fails closed

A user belongs to specific organizations with a specific role. No organization, no data – the default is zero access, not full access.

🔑Per-organization connections

Each organization holds its own integration credentials and sync schedule. One organization's hiccup never touches another's data or syncs.

✔️Verified before onboarding

A dedicated security pass over the whole stack – data rules, permissions, secrets – runs before enterprise onboarding, so isolation is proven, not promised.

Appendix · A3

Integration access strategy

📜Official-API-first

Every client-facing channel runs on official platform APIs – no gray channels anywhere in the offering. Compliance is an architecture choice, not an afterthought.

🔑Your accounts, your data – always

Each client connects their own ad accounts and messaging numbers through permissions they can revoke. Assets, audiences and history always remain theirs.

🤝Partner-accelerated

Stage A runs on certified technology partners who already carry the heavy platform approvals, compressing time-to-market to weeks – while the client's assets and data stay in the client's hands throughout.

01 / 15