The New Normal Analytics

    Becoming an AI-native business

    We make your business AI-native. Your team gets hours back, every week.

    Four layers, built in order: your data in one trusted place, your company's knowledge in a context layer that keeps itself up to date, your people working with AI every day, and agents doing the routine work while you sleep. Answers you can trust, in minutes, not weeks. Reports drafted before you arrive. No extra headcount.

    Built by ex-Bloomberg, EPAM and Pfizer people, from startups and scale-ups to Fortune 500 companies. We know the problems of each stage, and build for the next one.

    Agentsanswer · watch · act
    Your team, enabledworking with AI daily
    Context layerself-updating knowledge
    Data foundationsone source of truth

    01 · Where every company is today

    Your business already knows the answer. It just cannot find it.

    Where things stand, why that decision was made, which number is right. It lives in inboxes, chat threads, spreadsheets and three people's heads. So we hire, and the new person spends three months learning what everyone else already knows.

    Then AI arrived.

    02 · What most companies did next

    We pointed AI at the mess. It answered with confidence. And it was wrong.

    A chatbot on top of ten systems that disagree gives you a fast, fluent, incorrect number, and forgets it by tomorrow. The problem was never the intelligence. It was what we gave it to work with.

    So we build in a different order.

    03 · How it is built

    Four layers. One story. Keep scrolling.

    FIRST

    The numbers agree.

    Every system into one source of truth in your cloud. Every metric defined once. AI is garbage in, garbage out: give it data that disagrees and it answers with confidence, and wrongly. So this comes first.

    How data foundations work →
    THEN

    The company remembers.

    One context layer for the whole company, with a space per client, project or team where you want one. Everyone's calls, emails, documents and data are filed into it on autopilot, filtered, dated and sourced, so it is always up to date. Anyone asks what the latest is and gets the answer with its source.

    How the context layer works →
    THEN

    Your team, empowered.

    Each person set up one to one on their own work, in Claude, ChatGPT or a bespoke web app. They ask the data and the context layer, draft in minutes, and learn to automate the next task themselves. Workshops and one-to-ones until it sticks. The layer most AI projects skip, and the reason they die.

    How team enablement works →
    FINALLY

    The routine work does itself.

    Agents run overnight on the same facts: the report drafted before you arrive, the invoices matched, the chasers written, the numbers watched. A person approves what matters.

    How agents work →
    Agentsanswer · watch · act
    Why did trial-to-paid drop last week?
    Reading the context layerdefinition v12 · the pricing test
    Querying the warehousebilling · app · web · ads
    Checking what changed last weekpricing test · 28 Oct · iOS paid social
    Trial-to-paid is 26%, down 5 points. The drop is iOS sign-ups from paid social since the pricing test on 28 Oct. Other channels are flat.4 sources · definition v12
    Monthly client report · Acme06:40 · overnight
    Live numbers from the warehouse
    Context layer3 decisions · 2 calls · one budget change
    Drafted in your templatea source on every number
    Ready for review12 pages, before you arrive
    Priya Shah · Acme09:02
    Launch timing
    Hi Maya, can we move the launch to December? The board wants it after the results.
    Reading the context layerlaunch date · budget · last call
    Checking the plancreative v3 approved · nothing else moves
    Re: Launch timingDraft · for your approval
    Hi Priya, yes, 2 December works. The budget stays at $120k and creative v3 is already approved, so nothing else moves. Maya
    Your team, enabledworking with AI daily
    Context layerself-updating knowledge
    Data foundationsone source of truth

    Here is what that feels like.

    04 · What your team gets back

    Hours back, every week. For everyone.

    The same jobs, the way they are done today, and the way they are done in a company that remembers.

    A question about last montha ticket to the analyst and a weekan answer in a minute, with the source
    The board packtwo days of assembling numbersforty minutes of review
    A client report or presentationthree hours in slidesa draft in your template in ten minutes
    Preparing for a client meetingan hour of digging through emaila brief that wrote itself
    Matching supplier invoicesa day at month enddone overnight, exceptions on a list
    A new starter's first monthforwarded threads and shoulder tapsone context layer to read

    And then

    It keeps opening doors.

    Every new use case is a skill or an automation on the same data, the same context layer and the same enabled team. Hours and days, not months or quarters. Most of them your team builds without us.

    And everything that matters stays with a person.

    05 · Secure by design, human by default

    Agents draft. People decide. Your data stays yours.

    Access by role

    People, and the agents acting for them, see only what they are allowed to see. Set per project, per team.

    Your data is never training data

    It stays in your cloud and your accounts. It is not used to train models. Personal data is masked before any model sees it.

    Nothing sent, paid or changed on its own

    Agents draft and prepare. A person approves anything that leaves the company, every payment, and every change to a system of record.

    Every step on the record

    What was done, by what, and why. Permanent and auditable.

    Which leaves one question. Where to begin.

    06 · Where to begin

    Fixed scope. Fixed price. Agreed before we start.

    Discovery first, in every tier. Then the context layer and data foundations, then your team, then new use cases as you ask for them. One project at a time, each smaller than the last.

    FIRST

    Discovery

    1 to 2 weeks

    Your systems, your team and the first use cases, mapped. Everything after it is fixed scope, fixed price.

    THEN · TOGETHER

    Context layer and data foundations

    3 to 10 weeks, by tier

    The context layer and the data, built side by side.

    The context layer →Data foundations →
    THEN

    Team enablement

    3 to 6 weeks, by tier

    Workshops, one-to-ones and daily routines until it sticks.

    What is in it →
    ON REQUEST

    New use cases

    1 to 4 weeks each

    Agents and automations, each one scoped in discovery and priced on its own.

    What is in it →

    Which tier you are in

    The tier follows how many people you have and how many data sources you run on, and how much they disagree. Not your revenue.

    By company sizeFocused10 to 50 peopleUp to 5 data sourcesScaling50 to 150 people5 to 12 data sourcesComplex150 to 300+ people12 or more data sources
    Discovery1 week1 to 2 weeks2 weeks
    Context layerabout 3 weeks3 to 4 weeks4 to 6 weeks
    Data foundations3 to 4 weeks4 to 6 weeks6 to 10 weeks
    Team enablementabout 3 weeks3 to 4 weeks4 to 6 weeks
    Each new use case1 to 2 weeks2 to 3 weeks2 to 4 weeks

    Discovery comes first in every tier and fixes the scope and price of everything after it. A 30-minute call tells you which tier you are in. Your own cloud and AI usage costs are paid to your vendors directly.

    Proof

    We run our own company this way. So do our clients.

    AI-native healthcare media agency · 10+ people

    Digital Peloton

    Every process from brief to final report mapped and moved onto a context layer, with agents for pipeline, reconciliation and reporting. Running the agency with AI, without adding headcount.

    John EvansCEO, Digital Peloton
    Read the case study →
    Series B healthtech · $119m raised · 100+ people

    Hilo

    Ten-plus systems connected into one platform and the commercial team's definitions written once. “We went from cluttered, manual reporting to becoming a data-driven organization.”

    Stefan PetzingerCEO, Hilo
    Read the case study →
    B2B · private equity exit · 25+ people

    Engage

    Data and AI systems built through to a successful exit. “The clarity and depth of reporting gave our acquirers full confidence in our metrics.”

    Mary McGregorCo-founder, Engage
    Read the case study →

    Who builds it

    Senior people. The ones on the call are the ones on the build.

    Ex-Bloomberg, EPAM and Pfizer, from startups and scale-ups to Fortune 500 companies. We know the problems of each stage, build for the next one, and stay the same people from discovery to the last agent.

    Questions

    Asked by most people who see this.

    Which AI do we use?

    Whichever fits you: Claude, ChatGPT, Gemini, or a bespoke web app on any model. The context layer and the definitions are plain text, so you can switch models without starting again.

    Where does the context layer get its knowledge?

    From the tools you already use: your meeting note-taker, email, documents, chat and your data. The AI reads them on a schedule and files what matters, with dates and sources, filtered by rule so private and sensitive material stays out. Nothing is filed by hand, so it is always up to date.

    Is our data safe?

    It stays in your cloud and your accounts. It is never used to train models. Access is set by role, so people and agents see only what they are allowed to see. Personal data is masked before any model sees it, and every action is logged.

    What never gets automated?

    Payment. Sending anything outside the company. Changing a system of record. Relationships and judgement. AI drafts and prepares; a person approves.

    How quickly do we see something?

    Discovery takes one to two weeks. The context layer is live about three weeks after that, your team is set up in the weeks that follow, and the first agent lands one to four weeks after it starts.

    The companies that win the next decade will not be the biggest. They will be the ones that became AI-native first, all the way through.

    Where it starts

    Let's make your business AI-native.

    Thirty minutes. We map your systems and your team onto the four layers, show you where the first project starts, and tell you which tier you are in.

    Or email anton@thenewnormalanalytics.com