Skip to content

Narraitive

1 January 1970

Built by an operator.

A note from the founder.

I have spent most of my working life on the operating side of companies. I ran the Americas for Matterport through its public listing and took that business from $35 million to $113 million in three years. I ran an enterprise P&L at Notarize in identity and fraud. I ran a real estate marketplace at Xome and merchant operations at Groupon. Before any of that I played Division I basketball, where I learned that the scoreboard and the game film disagree about the same afternoon.

Every company I have worked in had two versions of itself. The first lived in the reporting: the deck, the dashboard, the weekly update. The second lived in the record: the ledger, the project system, the contracts, the spreadsheets nobody wanted to open. The first version told me what people wanted me to know. The second told me what was actually happening. When the two disagreed, the disagreement was usually the answer to the question I had walked in with.

I learned three things the hard way.

The result is almost never held back by ten problems. It is held back by one handoff. A decision waiting on a person. A delivery waiting on an approval. A number waiting on a signature. Everything downstream waits too.

The record already knows where that handoff is. Nobody reads it. There is no time, and the tools built to help report what you told them rather than read what you did.

Fixing the handoff is easy. Proving it stayed fixed is the work. Most changes are announced, not verified, and quietly come undone.

For most of my career the reading could not be done at the speed a company moves. That has changed. An AI can now read a ledger, a project system, a contract and a spreadsheet as fast as you can open them. It can form them into one picture of the company as it actually works and find the handoff. It can do this every week, for every entity, without adding a person to the payroll. What it must never do is decide. The moment a machine makes the call, the picture stops being worth having. Someone has to own the outcome, and it has to be a person.

That is Narraitive. It reads what you permit and nothing else. It writes nothing back. It scores no one. It says what it cannot see. It brings one evidence-backed change to the person who can approve it, then watches the record to see whether the change held.

Here is how I work. Every engagement is bounded and priced before it begins; there is no hourly billing. I lead every Reading myself, and I run the weekly review as your operating lead until the rhythm holds without me. I take two ongoing engagements at a time, so the ones I take get my attention. If a Reading finds nothing worth installing, I will say so, and we will stop.

If you run a company with several entities, locations or projects to reconcile every week, start with the first read. It is free, it takes five minutes, and I read every one personally.

TJ Paterick

Founder, Narraitive

LinkedIn

Operator cases

Four rooms I ran, in the shape I now read companies.

  1. Case 01

    Matterport

    Vice President, Americas

    Problem
    A hardware company becoming a software company, in the middle of going public. Revenue had to grow while the product, the pricing and the sales motion changed underneath it.
    What I did
    Ran the Americas revenue organisation through the Nasdaq listing; rebuilt the team and the motion around subscriptions while the hardware business funded the transition.
    What held
    Americas revenue from $35 million to $113 million in three years.
  2. Case 02

    Notarize / Proof

    SVP, Enterprise

    Problem
    Banks and insurers buying identity verification and fraud prevention needed one accountable owner across sales, customer success and product, not three teams pointing at each other.
    What I did
    Ran the enterprise business as one P&L: inside and outside sales, customer success, product strategy and operations, across synthetic identity, deepfake and document-forgery risk.
    What held
    One owner for the enterprise number and for the customers behind it.
  3. Case 03

    Xome (Mr. Cooper Group)

    SVP, Real Estate Monetization

    Problem
    A residential real estate auction platform built for bank-owned inventory needed to become a marketplace investors and consumers would use.
    What I did
    Owned the P&L and led the shift from an REO-only platform toward an investor and consumer marketplace.
    What held
    A marketplace with buyers on both sides rather than a disposal channel.
  4. Case 04

    Swarm Mobile → Groupon

    Senior Director, Merchant Operations

    Problem
    A young company's revenue rested on one commercial engine; after the acquisition, merchants needed point-of-sale integrations that actually redeemed.
    What I did
    Led the commercial engine at Swarm Mobile, about 90 percent of company revenue, through its acquisition by Groupon; then merchant operations: POS integrations and redemption partnerships.
    What held
    Integrations merchants used, and a redemption path that closed the loop from offer to sale.

Education — MBA, Babson College. University of Richmond, Division I basketball.

How I work

  1. 01Every engagement is bounded and priced before work begins. There is no hourly billing.
  2. 02I read what you permit and nothing else. Nothing is written back into your systems.
  3. 03Unknown stays unknown. I will tell you what I cannot see.
  4. 04No person is scored. Owners are named because accountability needs names.
  5. 05A change is finished when someone other than the doer shows the result.
  6. 06If the Reading finds nothing worth installing, I say so and I stop.