Internal · July 2026 · Brainstorm

Naming the larger idea.

Eighteen candidate ideas AdapttoAI could name and own — the thing that's still true, and still ours, when the RFQ workflow is table stakes. Grouped into six families by the kind of move each one makes. Working material for a kill round, not a decision.

Raffaello & Giuseppe Follows the Cave 76 conversation + the 17-competitor messaging study
01 · The question, from the Cave 76 doc

Name the larger thing, or stay a feature.

"A tool is easy to copy and easy to outgrow. The companies that endured named a larger idea — and let the tool be the way in."

HubSpot didn't sell 'marketing software.' It named a larger idea — 'inbound' — and taught it, for free, to a whole generation. The philosophy was the moat; the software was just how you lived it.Cave 76 · slide 01
Drift & Gong sold in commoditized categories — chat, call recording. Each named a larger game instead ('conversational marketing,' 'revenue intelligence') and stopped being a feature you haggle over on price.Cave 76 · slide 01
The work: what's the larger idea AdapttoAI names — still true, and still ours, when RFQ automation is a checkbox?
02 · The reframe

A positioning claim is not a nameable idea.

Positioning claim

A sentence we say about our value. Lives in our headline. Dies when a competitor says it too.

Nameable idea

A noun the market adopts, teaches and repeats about itself. Lives in the buyer's vocabulary. The product is just how you live it.

The test: does the customer say "we're doing X" — or "we bought X"?
"We're doing inbound" passed. "We bought marketing software" never could.
  • An idea can be taught to someone who never buys — that's what makes it spread.
  • An idea names something in the customer's world — a problem, a practice, an asset — not something in our product.
  • The RFQ workflow becomes the proof, not the pitch.
03 · The open lane, from the messaging study

All four category inventions in our market are vendor nouns. Not one is a customer-side idea.

GO AUTONOMOUS"Autonomous Commerce" · "Autonomous Execution Fabric"describes their softwarevendor noun
CANALS"Operating AI"describes their softwarevendor noun
DISTRO"Agentic Sales Operating System"describes their softwarevendor noun
BURNT / OZAI"Agentic OS for food supply chain"describes their softwarevendor noun
EVERYONENobody names a problem the customer has, a practice they adopt, or an asset they ownthe HubSpot move is unattempted in this marketopen
Source: competitor-messaging-analysis-deck.html · slide 9 (category language, 17 players, live sites 2 Jul 2026). No customer ever said "we're doing autonomous commerce."
04 · The map

Eighteen candidates, six families. Each family does a different job.

Read this as a menu of roles, not a lineup of rivals. Ideas from different families don't exclude each other — they stack into one system (section 05 shows how HubSpot ran three at once). Candidates only truly compete within a family.

A · PHILOSOPHYThe why — a belief system, taught not soldAI Adaptation
B · PROBLEMThe diagnosis — a disease the buyer already has, returned as a numberBack-Office Debt · Growth Tax · Manual Tax · Shadow Payroll · Back-Office Drag · Three-Hour Day
C · FRAMEThe architecture — a two-sided divide the CTO repeats in meetingsSystem of Work · The Work Layer · The Translation Layer · The System of Flow
D · PLACEThe territory — a story the owner retells about where we live in his worldThe Second Factory · The Paper Floor · The ERP Last Mile
E · PRACTICEThe how — a method the market adopts and self-locates againstThe Autonomy Ladder · Back-Office Autopilot
F · ASSETThe thing they own — something valuable we make visible and keep safeThe Judgment Layer · The Back-Office Stack
FAMILY APhilosophy — the why

A belief system the company stands for. Taught for free, lived through the product. The HubSpot-inbound move in its purest form.

1 / 18

AI Adaptation

Against "AI Transformation" (the consultants' big-bang that fails 70% of the time) and "AI Adoption" (the vendors' word for buying tools) — adaptation is what organisms do: change gradually, keep your identity, survive. One workflow at a time. Your team keeps deciding. You pay when it's live.

Why it's ours
It's already our name. "Start Your Adaptation," "helping industrial businesses adapt to AI," the anti-FOMO voice. We'd be claiming an idea we've been carrying unlit. Bootcamp = the course; phone assessment = the diagnostic.
⚠ Failure mode
"Adaptation" can sound slow and follower-ish to a speed-hungry CTO. And it's an idea about AI, not about the buyer's business.
FAMILY BProblem — the diagnosis

Names a condition the buyer already suffers. The phone assessment returns it as a number — the number becomes the sales artifact, the article, the talk. One axis separates these six: blame direction. Debt is something you incurred. A tax is imposed on you. Drag is physics. Proud owners hear the difference.

2 / 18

Back-Office Debt

Decades of manual workarounds — retyping, Excel bridges, WhatsApp threads, knowledge in heads — accumulated exactly like technical debt, with compounding interest: slower quotes, capped capacity, judgment that leaves in a resignation letter.

Why it's ours
We're the only player built for mid-market traditional businesses — where the debt runs deepest. Every module is a repayment; the one-time connector is the refinancing. Diagnostic: "how much back-office debt do you carry?"
⚠ Failure mode
Blame points inward — debt accuses the owner of mismanaging his life's work. And a named disease invites competitors to sell against the same diagnosis.
3 / 18

The Growth Tax

The tax you pay every time you scale: every new million in revenue demands another operator, another admin, another layer of retyping. A competitor's customer says it verbatim — "Each time we added a million or two in euros, we had to add another operator" (Nefab, on Go Autonomous's site). The disease, spoken by a patient.

Why it works
Best blame direction — taxes are imposed, not incurred. CEO-native altitude: it's about growth, not ops hygiene. Diagnostic: "your growth tax rate" = added back-office cost per added million of revenue.
⚠ Failure mode
"Tax" is diluted by business writing ("the meeting tax," "the coordination tax") — needs our qualifier welded on.
4 / 18

The Manual Tax

The toll paid on every single order: minutes, errors, delay — levied on each transaction like a toll booth between the customer's email and the ERP.

Why it works
The most concrete per-order diagnostic in the family: "you pay X minutes and Y euros of manual tax per order; you processed 30,000 orders last year; here's the bill." COO altitude.
⚠ Failure mode
Names the symptom (retyping) rather than the structural condition — pulls back down toward feature altitude, the thing Cave warns against.
5 / 18

The Shadow Payroll

The share of salaries paid for work a system should do. You're not overstaffed — part of your payroll is just being spent on the wrong work.

Why it works
Plugs directly into the $1-software-$6-labor line from the Cave doc and our existing ROI frame ("one FTE back in your month"). Diagnostic: "how many FTEs is your shadow payroll?" — a number a CFO acts on.
⚠ Failure mode
Firing subtext — heard by the team, "shadow payroll" sounds like a layoff list. Cuts against our dignify-the-operator instinct.
6 / 18

Back-Office Drag

An invisible force that shows up nowhere on the P&L but is felt in everything — quote speed, onboarding time, how long month-end takes. Nobody's fault; it's just there, and it compounds with size.

Why it works
The cleanest blame direction of all — drag is physics. Speaks to the CTO (speed) and the CEO (fuel cost) in one word.
⚠ Failure mode
Softest diagnostic in the family — "drag" resists becoming a hard number, and the assessment's power is precisely the number.
7 / 18

The Three-Hour Day

From our own pitch line — "we're selling back the 3 hours a day your commercial team loses to data entry." Every back-office person has a three-hour day hiding inside their eight-hour day.

Why it works
Hyper-concrete, zero abstraction, instantly testable by the buyer against their own floor. Number-native by construction.
⚠ Failure mode
A statistic wearing an idea's clothes — easy to quibble ("ours is more like one hour") and caps us at time-savings altitude, below judgment, capacity and growth.
FAMILY CFrame — the architecture

A two-sided divide that gives us a named seat next to the ERP. The phrase a CTO repeats in the build-vs-buy meeting.

8 / 18

The System of Work

"Your ERP is the system of record. Adaptto is the system of work." Why "work" beats "action": Smartbase already runs "ERPs record the work, Nargis does the work" — but as an ERP replacer, so the "action" frame is contaminated in their direction. "Work" claims the Sequoia line — for every $1 of software, $6 goes to the labor that does the work. And there's analyst lineage: system of record → systems of engagement → the term the genre never filled.

Why it's ours
We keep the ERP and sit beside it — the version of this frame a mid-market buyer can actually say yes to. CTOs find the genre instantly credible.
⚠ Failure mode
A CTO's phrase, not a dinner-table phrase — abstract to a non-technical owner.
9 / 18

The Work Layer

The architectural variant: there's a layer between your customers and your ERP where all the work happens — and it's currently made of people retyping.

Why it works
Strong as the diagram underneath whichever name wins — the technical vocabulary, not the banner.
⚠ Failure mode
"Layer" gravity pulls toward middleware — a feature category, not an idea.
10 / 18

The Translation Layer

"Between your customers and your ERP sits a translation layer. Today it's made of people retyping." It takes messy human input — WhatsApp, PDFs, emails in six languages — and translates it into the ERP's structured world, and back.

Why it's ours
The most literal to what the product actually does. And uniquely ours geographically — we're the only player in the set whose translation claim is also literally linguistic: Southern Europe + LatAm, inputs in any language, six-language RFQ briefs already in our proof row.
⚠ Failure mode
"Translation" reads technical and narrow — an i18n feature, not a company — unless the double meaning is made to carry weight.
11 / 18

The System of Flow

"Your ERP stores. Nothing flows." Material flows through the factory because you engineered it to — decades of lean work made sure of it. Information still doesn't flow through the office: it sits in inboxes, waits in queues, gets retyped between systems.

Why it works
Borrows fifty years of manufacturing religion — "flow" is native, beloved vocabulary for ops people raised on TPS and Goldratt. The claim lands as: apply to the office what you already did to the plant.
⚠ Failure mode
Outside the ops congregation it goes soft and yoga-ish fast. And it names a quality rather than a place — harder to point at, harder to buy.
FAMILY DPlace — the territory

Names where we live in the customer's world, as a story the owner retells. The most five-second-graspable family.

12 / 18

The Second Factory

Every industrial company runs two factories. One makes the product — automated thirty years ago: CNC, PLCs, robots. The other makes the paperwork — quotes, orders, invoices, confirmations — and it still runs entirely by hand. The RFQ module is the first production line we automate in it.

Why it works
Speaks the buyer's native pride language — industrialization, not "digital transformation." Dignifies instead of shames. Carries decades of lean-manufacturing intuition for free. Customer test passes: "we're automating our second factory."
⚠ Failure mode
Metaphor discipline — it invites endless factory wordplay, and if the copy gets clever the idea gets cute.
13 / 18

The Paper Floor

The compact sibling: "Your shop floor is automated. Your paper floor isn't." Punchier, more visual, same underlying move.

Why it works
Two words, one accusation, instantly pictured. The shop-floor/paper-floor contrast does all the teaching by itself.
⚠ Failure mode
"Paper" may feel dated to a WhatsApp-and-PDF buyer — though the datedness is arguably the accusation working.
14 / 18

The ERP Last Mile

Our buyers use "last mile" every day — they know it's where logistics gets hard and expensive. Every ERP project stops at the system boundary, and the last mile — between the customer's WhatsApp, email and PDFs and the ERP — was left to humans retyping. "Your ERP project was never actually finished."

Why it's ours
One connector, four input channels, live in production. The discovery opener already says it: "Your ERP is the system of record. WhatsApp, email and Excel are the system of action. We live in the gap." Smartbase answers the same insight by replacing the ERP; we say keep it.
⚠ Failure mode
Defines us relative to the ERP — a subordinate position — and gravity pulls it back toward "integration middleware."
FAMILY EPractice — the how

A method the market adopts and self-locates against. Maturity language is the classic category-creation instrument — every buyer can place themselves on it.

15 / 18

The Autonomy Ladder

The whole market shouts the top rung — "touchless," "orders that process themselves" — as if it's day one. The ladder says the top rung is earned: AI drafts → your team approves → AI acts, exceptions surface → touchless. Chosen per workflow, at the speed of your trust.

Why it's ours
The autonomy dial is shipped product ("You decide how much the AI does"). "Drafted by AI, decided by your team" is simply rung two, named. Teach motion: self-assessment, bootcamp module, per-workflow scorecard.
⚠ Failure mode
Frameworks smell consultant-y, and a ladder graphic is copyable overnight. The moat is the dial product, not the diagram.
16 / 18

Back-Office Autopilot

We already own the sub-clause ("now on Autopilot"). The aviation metaphor quietly resolves our central tension: autopilot flies the plane, but the pilot stays in command and chooses when it's engaged — the autonomy dial in one word, with the operator dignified as the pilot.

Why it works
The most natural colloquial adoption path of anything on this page — "we put quoting on autopilot" is a sentence customers already say unprompted.
⚠ Failure mode
Half of SaaS uses "autopilot" loosely. The ownable part is the doctrine — what earns a workflow the right to go on autopilot — not the word.
FAMILY FAsset — the thing they own

Names something valuable in the customer's world that they should protect or build. We become its custodian, not its vendor.

17 / 18

The Judgment Layer

Every industrial company has an unwritten layer where the real decisions live — pricing exceptions, spec interpretation, which customer waits — invisible to the ERP, resident in three heads. Name the layer and it becomes visible, auditable, keepable. Cave's thesis 03, converted from a claim into a noun.

Why it's ours
Spec matching and rules configuration is judgment encoding. Only Distro grazes this territory ("your most experienced reps are retiring") — framed as document search. The most durable idea on this page: judgment is never table stakes.
⚠ Failure mode
The most abstract on this page — hardest to grasp in five seconds. And the person evaluating us is often the person whose head we're proposing to empty.
18 / 18

The Back-Office Stack

The front office got a stack — CRM, website, marketing tools, whole categories and budgets and a vocabulary. The back office never got one. Naming the stack tells the customer there's a thing they're supposed to be assembling.

Why it's ours
Connector + modules is a stack by construction. Customer test passes: "we're building out our back-office stack."
⚠ Failure mode
Startup vocabulary — and it frames a shopping list, which invites the buyer to fill the stack with several vendors instead of us.
05 · How they combine

These eighteen aren't competing for one slot. They stack.

HubSpot didn't pick one. It ran inbound (the philosophy) and the funnel, later the flywheel (the model everyone drew on whiteboards) and the Website Grader (the free diagnostic that returned your number). Three named things, three different jobs, one company underneath. The real choice isn't which idea survives — it's which one leads, and which jobs the others take.

The jobs, and which family fills each
THE STORYWhat the owner retells at dinnera Place — e.g. the Second Factory
THE ARGUMENTWhat the CTO defends in the build-vs-buy meetingthe Frame — e.g. the System of Work
THE NUMBERWhat the phone assessment returnsa Problem — e.g. the Growth Tax rate
THE METHODHow the rollout is governed and taughta Practice — e.g. the Autonomy Ladder
THE VERBWhat customers say once they're in"we put quoting on autopilot"
THE WHYThe belief system over all of itthe Philosophy — Adaptation
The diagnosis and the architecture close the loop between the two directions flagged so far:
"[The disease] exists because your ERP records the work but nothing does it. Adaptto is the system of work."
The buyer split maps onto the families
  • CEO / owner (wants cost, growth) → the Story + the Number.
  • CTO / ops (wants speed, control) → the Frame + the Practice.
  • Same product underneath — one idea leads per audience.
Annexable by any winner — unclaimed in all 17
  • The build-vs-buy enemy — zero players position against building in-house.
  • Southern Europe + LatAm, Spanish + Italian — every category claim in the set is horizontal or US-anchored.
  • A non-demo entry offer — 14 of 17 gate on "book a demo"; nobody enters with a diagnostic. Our phone assessment already does.
06 · Next step

The kill round.

Pick at most one survivor per family (killing a whole family is allowed). Each survivor gets developed into a one-page doctrine so we compare finished thoughts, not fragments.

PER SURVIVORThe idea in a paragraph
The enemy it names
The teachable artifact (diagnostic, ladder, number)
The homepage H1 that carries it
Inputs: Cave 76 conversation · 17-competitor messaging study · MASTER-CONTEXT.md Brainstorm, not a decision