Nothing New Let’s talk

Operator-led consultancy · Operations · Payments · E-commerce

Your operationisn’t brokenin a new way.

It is broken the way operations always break. Growth outran the process. Ownership went vague. The systems stopped agreeing with each other. Nothing New comes in, establishes what is actually happening, and builds the version that holds after we leave.

  • Fractional operations lead
  • Project lead
  • Implementation partner
  • Interim cover
  • Sparring partner

01 What we do

Companies rarely call us because something exploded.

They call because everything technically works and nobody can say how. These are the conversations we get pulled into — and what is usually underneath them.

Revenue grew. The process didn’t.
Every new market, product line or provider was absorbed by whoever was nearest at the time. Each decision was reasonable. Together they are now the operation.
Everyone is involved. Nobody owns it.
The same issue is raised in four channels over a week, by people who are each individually right. No name is attached to it, so it survives every meeting.
The reporting says healthy.
Most reporting confirms that a job ran. It rarely confirms that the outcome landed. The distance between those two is where money leaves quietly.
Two systems, two answers.
The CRM says one thing, the provider portal says another, and the number in the board pack came from a third place. Someone picks a source. Usually not the operational one.
Payments became complicated.
More providers, more entities, more rules, more limits — and routing decisions made against capacity nobody can actually see. The first symptom is normally an approval rate nobody can explain.
Support costs grow faster than revenue.
Ticket volume is the symptom. The cause sits upstream: unclear billing, no self-service, refunds and cancellations handled as a negotiation instead of a flow.
Everything routes through the founder.
Decisions queue behind one calendar. The team is capable; the structure doesn’t let them commit to anything. Nothing moves in the weeks that person is busy.
There is a document for it.
Written once, during a quiet week, and never used since. A process nobody follows isn’t a process. It’s archaeology.

We work in environments like that and leave them with named ownership, systems that agree, processes people actually use, and the work finished.

02 Capabilities

Where we are strongest.

Eight areas, one job: making the operation do what the business has already promised it will do.

01

Operations & operating rhythm

Ownership, cadence and a way of running the week that doesn’t depend on heroics.

  • Ownership maps and decision rights — who decides, who executes, who is told
  • SOPs written from the real process, not the ideal one
  • An operating cadence: what gets reviewed, by whom, how often
  • Reporting a management team will actually read and act on

02

Payments & fintech operations

Payment operations end to end — onboarding, providers, routing, reconciliation.

  • Merchant and entity onboarding, applications and documentation packs
  • Acquirer and PSP relationships: capability, pricing and limits, established in writing before signature
  • Portfolio structure, routing logic, caps and capacity management
  • Settlement, fees and reconciliation — including when the provider and your system disagree
  • Provider migrations and new rail launches without losing a week of revenue

03

Risk & transaction monitoring

Know your numbers before a scheme programme tells you what they are.

  • Fraud-to-sales and dispute ratios: how they are actually counted, not how they feel
  • Prevention and deflection — alerts, order intelligence, cancellation and refund paths
  • Thresholds, controls and change control on live payment configuration
  • Evidence, documentation and monitoring that holds up in front of a third party

04

Customer operations

Support that scales because the upstream cause was fixed, not because headcount doubled.

  • Ticket flows, tagging, routing, macros and automation rules
  • Escalation paths with named first responders and real time limits
  • Refunds, cancellations and retention designed as flows
  • QA, measurement and cost per contact — then removing the contacts

05

Systems, CRM & data

One operational version of the truth, and the plumbing that keeps it true.

  • CRM and workflow design against how the business actually sells and bills
  • Reconciliation between platforms that report the same thing differently
  • Instrumentation: measuring outcomes, not activity
  • Getting numbers out of the tools and into decisions people can defend

06

Automation & AI in the operation

Automate the volume work. Then verify it actually happened.

  • Deciding which work should never be done by a person again
  • AI-assisted support, voice and internal agents doing real process load
  • Operational tooling: scripts, dashboards, bridges between systems that don’t speak
  • Verification by default — an automation without a check on its output is a liability

07

Organisation & accountability

Roles, handoff lines and the authority to act on them.

  • Structure built around stages of work, not job-title inflation
  • Handoff lines between teams — written down, then tested
  • Delegation that survives the week the founder is unavailable
  • Hiring shape, onboarding, and an honest view of what to stop doing in-house

08

Projects & transformation

From “we need to fix this” to running in production, with an owner.

  • Restructures, consolidations, migrations, market and product launches
  • Project lead or interim operational owner for the duration
  • Vendor selection, due diligence and negotiation support
  • Handover: documentation, named owners, and a measure that shows drift early

03 The difference

Advice has to survive contact with reality.

Most consulting output is correct and useless at the same time. Correct, because it was written at a distance. Useless, because the operation has constraints the document never met: the person who owns the fix has four other jobs, the system can’t do what the plan assumes, and the change has to happen without taking revenue offline for a day.

We work from inside instead. People, process, systems, data, ownership and commercial reality — and specifically how those six argue with each other on a Tuesday afternoon, which is where every real operational problem actually lives.

Then we build it. We are the ones in the tool writing the flow, on the call with the provider, testing whether the thing we changed an hour ago genuinely works. No 100-page strategy document, no handover to a junior team, no disappearing at the point where it gets difficult.

A plan governs what hasn’t happened yet. A rule governs the next fifteen minutes. Most operations need the second one first.
  • Reality over reporting

    We verify that the outcome landed, not that the job ran. Almost every silent failure hides in that gap.

  • Ownership before process

    A process with no name against it is a suggestion. We assign it, in writing, before we design anything.

  • Get it in writing

    Capabilities, limits, prices and commitments — confirmed before the signature, not reconstructed after the incident.

  • Boring beats clever

    The solution a tired person can follow correctly at 17:00 on a Friday is the better solution. Every time.

  • Finish things

    A half-implemented change costs more than no change. We would rather do three things completely than eleven partially.

  • Leave it working

    Success is the operation running well without us in it. If you still need us to run it, we didn’t finish the job.

04 How we work

Four steps. No theatre.

  1. 01

    Get inside it

    We sit in the tools, read the tickets, follow the money and talk to the people doing the work. Usually two to three weeks. You get a written read of what is actually happening — including the parts nobody wants to put in an email.

  2. 02

    Decide what matters

    Not everything gets fixed. We separate what is costing money now from what is merely untidy, attach a name and a date to each one, and agree the order. Short list. Specific. Yours to approve.

  3. 03

    Build it

    Processes written, systems configured, flows tested, providers pushed, people trained, documentation that matches what the operation does. In your tools, with your team, at the speed the business can absorb.

  4. 04

    Hand it over

    Named owners, working documentation and one measure per process that shows drift before it becomes an incident. Then we stay as long as it is useful — and not longer.

05 Who we work with

Complexity, and a real operation behind the product.

We are most useful where money moves, customers keep paying, and several systems and people have to agree for that to happen.

  • Subscription & e-commerce businesses

    Where billing, refunds, disputes and support have quietly become the actual operation.

  • Payments & fintech

    PSPs, acquirers, payfacs, platforms and merchants of record — and the teams that have to run them daily.

  • Technology companies

    Where operations grew as a side-effect of engineering and sales, and now needs to be a function.

  • Multi-entity groups

    Several companies, providers and jurisdictions, and no single trustworthy view across them.

  • Companies mid-restructure

    Consolidating, separating, winding down or being integrated — with a business still trading through it.

  • Teams outgrowing one head

    Where the operation no longer fits inside one person’s memory, and that person is usually the founder.

The name

Almost nothing here is new.

The problems repeat. Across companies, industries and continents, operations break in a small number of recognisable ways, and most of the answers are old, unglamorous and already known.

The value is not a new idea. It is recognising the pattern quickly, stripping out the complexity that was added by accident, and doing the ordinary work properly — which is, in practice, the rarest thing in operations.

06 About

Built from the operator’s chair, not the consulting bench.

Nothing New is led by Camilla Norman Bønke, from years spent running group-level operations in payments, e-commerce and technology: merchant and entity onboarding, acquiring and PSP relationships, risk and transaction monitoring, customer operations, CRM and internal systems, automation, vendor negotiation, and rebuilding teams and processes while the business kept trading.

That is where the method comes from. Onboarding portfolios of merchants and moving volume between providers. Taking apart reporting that looked healthy and wasn’t. Rebuilding support so that cost per customer fell instead of headcount rising. Writing the documentation for the people who were about to inherit the process. Removing manual work that had accumulated over years of moving fast, and putting controls where there had only ever been trust.

Nothing New exists so other companies can use that experience directly — as an operational advisor, a project lead, an implementation partner or an extra pair of hands with executive judgment attached. Based in Denmark, working across Europe, in English and Danish.

Based
Denmark · working across Europe
Languages
English · Danish
Engaged as
Advisor · fractional lead · project lead · interim
Sectors
Payments · e-commerce · fintech · technology

07 Contact

Have an operation that needs fixing?

Describe what is not working in your own words. Messy is fine — messy is usually more accurate. You will get a direct answer on whether we can help, and if we can’t, a view on who or what probably can.

First conversation costs nothing and comes without a deck.

Phone
+45 40160112
Telegram
@Camilla_PPG

Replies normally within one working day.

Or write directly to nneweu@protonmail.com.