Unlocking the Art of the Possible from Data Integration

    Unlocking the Art of the Possible from Data Integration

    Narrative.io founder Nick Jordan explains how data normalization, federated queries, and agentic workflows turn messy data into answers in minutes rather than quarters.

    Dave Edelman in conversation with Nick Jordan (Founder and Chief Product Officer, Narrative.io) · September 2026

    In 100 Words

    Dave Edelman talks with Nick Jordan, Founder and Chief Product Officer of Narrative.io, about why data is hard and how normalization makes it usable for marketing and AI. In full disclosure, Dave was one of Narrative's early advisers. Nick explains Rosetta Stone, Narrative's normalization technology, using examples such as misspelled dog breeds at veterinary clinics and currency conversion. He describes why large language models alone are too expensive, non-deterministic, and unobservable for billion-row data sets, and how Narrative Anywhere runs inside a customer's own warehouse or cloud. The conversation covers Block's commerce media network across Afterpay, Square, and Cash App, the NQL query language, the limits of dashboards, agentic workflows that test hypotheses, a NASA versus startup approach to data warehouses, data ecosystems such as a Home Depot bathroom renovation hub, and Nick's view that AI creates an infinite list of more interesting work.

    Full Session

    Key Learning Points

    1

    Data Comes in Infinite Forms

    Data is not one monolithic thing. Anyone working with it, from an Excel user to a team building a large language model, has to manage the complexity of countless formats and representations.

    2

    Normalization Makes Data Usable

    Narrative's Rosetta Stone technology categorizes data like a librarian would: what type of data it is, how it relates to other data, and which use cases it could solve.

    3

    Small Inconsistencies Break Analysis

    Male versus M, dollars versus euros, or golden retriever typed as olden retriever all fragment one question into dozens. Normalization turns 75 questions back into a single question.

    4

    LLMs Alone Are Not Enough

    Models are non-deterministic, expensive at billion-row scale, and not observable. Enterprises need mappings that are repeatable, governable, and observable rather than a fresh LLM call for every new value.

    5

    The Ecosystem Moves Faster Than Specs

    Multi-year warehouse and federation projects fall behind because the martech ecosystem keeps evolving. A new channel, such as advertising from OpenAI, cannot wait nine months for integration.

    6

    Data Can Stay Where It Lives

    Narrative Anywhere moves the technology into the customer's own warehouse or cloud. Moving data less helps compliance, security, privacy, and speed.

    7

    Dashboards Raise More Questions

    Dashboards presuppose the questions. The real value lies in second and third order questions, like the Titanic release driving a music store's sales, answered quickly enough to use in the meeting.

    8

    Agents Can Test Hypotheses

    Agentic workflows can take a question, propose several hypotheses, write and run queries against normalized data, and suggest follow-up questions or tactics.

    9

    Faster Cycles Change the Calculus

    At Tapad, moving from hypothesis to integrated data took quarters. Compressing that to hours or minutes means teams can act on ideas immediately instead of rejecting them as too slow or costly.

    10

    Ecosystems Become Practical

    Multi-party data collaborations, such as retailers, manufacturers, and contractors coordinating a bathroom renovation, become feasible rather than dying on the vine after the first meeting.

    Key Action Points

    1

    Name Your Biggest Data Frustration

    Identify the one data-related task from the last six months that frustrated you most and make it the first problem to solve.

    2

    Prove Value on One Small Problem

    Start with a single, contained use case rather than a sweeping program. A small success builds credibility for broader change.

    3

    Audit Inconsistent Fields

    Look for fields entered by hand or sourced from different systems, such as product names, breeds, gender, or currency, where variations quietly distort reporting.

    4

    Make Mappings Repeatable

    Use AI to suggest that X means Y, but store those mappings so the same input always yields the same output and the process stays governable.

    5

    Question Nine-Month Data Lake Plans

    Keep a system of record such as Snowflake, Databricks, or AWS, but challenge designs that require exhaustive specs before any business user can get an answer.

    6

    Minimize Data Movement

    Favor approaches that query data where it lives, especially for sensitive first-party data, to reduce compliance, privacy, and security exposure.

    7

    Design for Follow-Up Questions

    Treat dashboards as a starting point. Build the ability to answer the next question while the executive team is still in the room.

    8

    Pilot an Agentic Analysis Workflow

    Give an agent a business question, ask it to hypothesize several ways to answer it, and review the queries, answers, and suggested next steps it produces.

    9

    Map Your Partner Ecosystem

    List the adjacent parties, such as manufacturers, contractors, or retailers, whose data could combine with yours to create a new value proposition.

    10

    Check the Problem Fits the Tool

    Confirm the issue is really a data integration problem. Narrative steered a bank with an asset management need toward an asset management vendor instead.

    Full Analysis

    1. Why Data Is Still Hard: Nick Jordan has spent his career in data-related product roles, and he describes the same pattern every time: the job looks easy until day two. As data becomes more important, there is more of it, and as there is more of it, complexity grows. Narrative.io was founded on a simple thesis: make data easy. That starts with accepting that data arrives in an infinite number of forms, and that anyone using it, whether in a spreadsheet or a large language model, must cope with that variety.

    2. Normalization in Practice: Normalization projects different representations of the same thing into a single way of thinking about it. The simplest case is male versus M. Currency is another: a price in dollars means something different once translated to euros or yen. Nick's favorite example comes from veterinary clinics, where a receptionist might type golden retriever, golden, retriever, or olden retriever. If only 80% are spelled correctly, a basic trend question becomes a list of 75 questions. Narrative's Rosetta Stone technology categorizes data so those questions collapse back into one.

    3. Where Large Language Models Fit: Ten years ago, before the LLM revolution, Narrative built its own neural networks to learn the thousands of ways a dog breed can be misspelled. Today it layers in more powerful AI, but the core asset is the platform primitives that record each mapping so it holds forevermore. Nick is clear about LLM limits: they are non-deterministic, expensive when a data set has billions of rows, and not observable when two users get different answers to the same task. He expects more layers to sit on top of AI to make it capable of powerful work, often outside a chat interface.

    4. Integration at the Speed of the Market: Integrated CRM and data lakes have long been the holy grail of marketing, often pursued through large outsourcing projects. Nick, with 20-plus years in martech and adtech, points to the Lumascape as proof of how complex the ecosystem has become. A brand may have an agency of record, in-house data, and 20 to 40 platforms. Multi-year federation projects fall behind because the ecosystem keeps changing; the spec is out of date before work starts. If a team wants to test advertising on OpenAI before competitors, a nine-month integration timeline defeats the purpose.

    5. Block and Narrative Anywhere: Block announced a commerce media network built on financial transaction data from Afterpay, Square, and Cash App. Because many of those businesses came through acquisitions, the data was not harmonious, so the first step was normalizing it into one large data set and plugging it into ecosystem platforms. Block uses Narrative's off-the-shelf technology. For sensitive data, Narrative Anywhere moves the technology into the customer's own warehouse or cloud, so Narrative never touches or sees the data. As Nick puts it, the less you move data around, the faster things work.

    6. Federated Queries and the Limits of Dashboards: Data does not land in a new clean receptacle. First-party and partner data stay where they live, in their own formats. Technical users write queries in NQL, and less technical users work through interfaces. The query is federated out, normalization happens on the fly, and the result returns as a new data set or an answer. Nick argues dashboards force you to presuppose every question. When he worked at a music store next to a movie theater, the Titanic release drove sales, something no one would have built into a dashboard ahead of time.

    7. Agentic Workflows and Faster Hypotheses: Narrative is leaning into agentic workflows. A user states a question, an agent hypothesizes ways to answer it, runs three or four of them against already normalized data, and suggests follow-up questions or tactics. Nick contrasts this with his time as Chief Product Officer at Tapad, where moving from a data scientist's hypothesis to finding, negotiating, and integrating the data took quarters, so every bet had to be safe. Compressing that cycle to hours or minutes lets someone with a light bulb moment in a meeting simply go and test it.

    8. Rethinking the Data Warehouse: Nick does not expect data warehouses and data lakes to disappear. Snowflake, Databricks, or AWS still serve as the system of record. What changes is the design thesis. He compares exhaustive, thousand-page data specs to how NASA gets someone to the moon: very safe, but slow, with technology adoption measured in decades. A startup asks what it is working on for the next two weeks. With normalization on top of a system of record, business users can change their minds and get new analytics without waiting on one all-knowing database administrator. Dave and Nick agree the word for this is democratization.

    9. Ecosystems, Culture, and Infinite Work: Dave sees new competition built on ecosystems, such as Home Depot coordinating a bathroom renovation across manufacturers, contractors, day laborers, permitting, and adjacent players like Grainger. Such partnerships have historically died on the vine. Nick says the first barrier is cultural: asking whether you are happy with how things are done today. He also notes Narrative is not always the answer, recalling a bank whose asset management problem was better suited to an asset management vendor. Nick describes himself as 80% bullish and 20% scared of AI, and believes it will leave an infinite list of more interesting, career-rewarding work.

    Frequently Asked Questions

    What is data normalization?

    Data normalization projects different representations of the same information, such as male and M, or prices in different currencies, into a single consistent form so one question returns one accurate answer.

    Why not just use an LLM to clean data?

    According to Nick Jordan, LLMs are non-deterministic, expensive across billions of rows, and not observable. Enterprises need repeatable, governable mappings, with AI used to suggest them rather than to recompute them every time.

    What is Narrative Anywhere?

    Narrative Anywhere runs Narrative.io's technology inside a customer's own data warehouse or cloud, so sensitive data does not need to be shipped to Narrative and Narrative does not touch or see it.

    Do companies still need a data lake or warehouse?

    Yes. Nick expects Snowflake, Databricks, or AWS to remain the system of record. What changes is the design approach: less up-front specification and more flexible, on-the-fly analytics for business users.

    How do agentic workflows help with data analysis?

    An agent can take a business question, hypothesize several ways to answer it, write and run queries on normalized data, and suggest follow-up questions or tactics, compressing time to value on large data sets.

    Where should a company start with data integration?

    Nick suggests identifying the one data task from the last six months that frustrated you most and solving that single problem first to prove value before expanding.

    Bring These Ideas to Your Audience

    Book Dave for a keynote, workshop, fireside chat, or executive session on AI, marketing, and customer strategy.