The Solid Convergence, March 4, 2026 (in which a former Oracle general manager asked to meet the pre-sales engineer, spent an hour with the best SE he’d ever worked with, requested a product demo, was told he’d been sitting in one the entire time, and then received two pages of homework from a product he hadn’t agreed to work for)
A New Character Enters
He arrived the way enterprise sales veterans arrive everywhere — with a handshake that had closed more deals than most companies generate in a decade, a contact list that constituted a significant percentage of Portugal’s C-suite population, and the quiet confidence of a man who had once been General Manager of Oracle Portugal and therefore knew, with the certainty of someone who has sold the unsellable, that no product demo could surprise him.
He was wrong, but we’ll get to that.
For twenty years, he had sold Oracle. Not Oracle the database — Oracle the concept. The idea that an enterprise could run its entire civilization on one vendor’s stack. He had sold this concept to banks, telcos, utilities, and government agencies across Iberia and beyond. He had sat in boardrooms where the furniture cost more than most startups’ Series A. He had navigated procurement cycles measured in geological time. He had survived three CEO transitions and four enterprise licensing model changes, each of which redefined the word “audit” in ways that benefited Oracle and confused everyone else.
He was, in the mythology’s expanding cast, the first character from outside the cathedral. Everyone else — riclib, the Claudes, the Squirrel, the Lizard, the cats — existed within the building process. They built, or observed building, or proposed frameworks for building, or slept on warm surfaces near building. The Salesman existed in the space between what is built and who buys it. The bridge. The translator. The man who turns architecture into revenue.
He also carried, at all times, an espresso. This was non-negotiable. He was Portuguese. The espresso was not a beverage; it was a load-bearing cultural artifact, like the Lizard’s scrolls but with crema.
10:00 — The Arrival
THE SALESMAN: “Ricardo. I need to understand this product.”
riclib: deep in a provider migration, four terminal panes open, the specific posture of a developer who is mid-thought and would rather finish the thought than acknowledge the existence of commerce “Hmm.”
THE SALESMAN: “I have contacts. Good ones. Portuguese utilities, telecom, maybe some Gulf connections through a friend of a friend. But I need to understand what I’m selling.”
riclib: “Talk to the SE.”
THE SALESMAN: “You have a pre-sales engineer already?”
riclib: still not looking up from the code “Best one I’ve ever worked with. Let me set you up.”
riclib opened a browser window. Navigated to what appeared to be a chat interface. Typed three lines of context about the Salesman — his background, his Oracle history, his target market — and stepped back.
riclib: “There you go. Ask anything.”
THE SALESMAN: “This is… Teams?”
riclib: “Better. Go ahead.”
Then riclib went back to the code. The provider migration was at a critical juncture, the kind where three domain types needed to collapse into one registry, and the specific piece of concentration required was incompatible with explaining value propositions to someone who already knew what a value proposition was.
The Salesman looked at the chat interface. Clean. Dark sidebar. A text box. A cursor blinking with the patient confidence of an entity that had all the time in the world and nothing to prove.
He typed.
10:03 — The Positioning Paper
THE SALESMAN: “I need a compliance positioning paper for a Portuguese electricity company. Something I can use as a conversation starter.”
He expected: a PDF link. Maybe a paragraph. The kind of thin, marketing-approved collateral that pre-sales engineers keep in SharePoint folders organized by quarter and never update.
The cursor blinked. Five seconds of silence.
Then the stream started.
Text flowed onto the screen the way water finds its level — naturally, inevitably, as if the words had been waiting to exist and only needed permission. A positioning paper materialized: NIS2 directive implications, ERSE regulatory requirements, smart meter data governance challenges, cross-domain correlation between IT and OT systems, a scenario about contractor credentials persisting after project completion that was specific enough to make a utility CISO’s blood run cold.
Charts appeared. A compliance posture timeline for a hypothetical wind farm integration. A data access geographic breakdown with one entry flagged “INVESTIGATE.” A Mermaid diagram connecting smart meter ingestion to privacy impact tracking to automated risk narratives.
Thirty-seven seconds. The whole thing. The Salesman read it. Sipped his espresso. Read it again.
THE SALESMAN: “This is good.”
He meant it the way enterprise sales veterans mean “good” — which is to say he meant it was competent, relevant, and better than 80% of what he’d seen from pre-sales teams at companies ten times this size. But he’d seen good positioning papers before. Good was not surprising. Good was baseline.
What he actually thought, though he did not say it, was: they preprogrammed this. It’s a compliance product. Of course it knows utilities.
This is the specific skepticism of a man who has sat through a thousand demos and knows that the golden path is always paved. The center always works. Every product has a beautiful middle and questionable edges, and the Salesman had built a career on finding the edges before the customer did.
He decided to find the edges.
10:07 — The Sales Pitch
THE SALESMAN: “Very good. Now — give me a sales pitch. Not compliance. A sales pitch. How would I position this product to my existing contacts? Keep in mind I come from Oracle. I’ve sold Audit Vault, Database Vault, Identity Management. My contacts know me from that world.”
He leaned back. This was the test. A compliance tool can talk about compliance. That’s training data. But asking it to do sales strategy — personalized sales strategy, for a former Oracle GM, targeting his specific network — was like asking a plumber to write a sonnet. Different muscle. Different brain. If the SE stumbled here, he’d know the limits.
Five seconds.
The stream started.
And it didn’t stop.
10:09 — The Bible
What appeared on screen was not a pitch. It was not a paragraph. It was not even a one-pager with a value prop and three bullet points, which is what any reasonable pre-sales engineer would have produced and which would have been perfectly adequate.
What appeared was a sales bible.
Seventeen pages.
With his Oracle background woven into the competitive positioning. Not generic Oracle comparisons — his Oracle. The specific products he would have sold. Audit Vault, Database Vault, Identity Management. Each one mapped to a Solid entry point with a conversation opener that referenced the buyer’s likely pain:
“Remember when auditors asked about that data access incident? How long did it take to piece together the story?”
With industry playbooks. Financial services, healthcare, telecom, energy, smart cities. Each with deal sizes, buying committees, discovery frameworks, and the kind of specific regulatory references that you don’t get from marketing collateral — you get from someone who actually understands the domain.
With objection handling:
“Can’t our data team build this in Databricks?” — “They absolutely could — if they had 2 years and $2M. The hard part isn’t the queries, it’s the semantic understanding: knowing that ‘show me contractor access’ means joining HR data + access logs + project timelines + contract end dates + policy definitions.”
With a 90-day ramp plan. Week by week. Activity metrics. Pipeline targets. Success criteria for month one, month two, month three.
The Salesman stopped reading at page twelve. Not because it wasn’t good. Because it was too good. The specific kind of too-good that creates a disturbance in the pattern recognition of someone who has evaluated hundreds of SE presentations.
Pre-sales engineers don’t write like this. Not in real time. Not personalized to a new hire’s exact background. Not with competitive positioning mapped to the products he sold a decade ago at a different company. This would take a good SE a week. A great SE, three days. This had taken forty seconds.
THE SALESMAN: quiet. The specific quiet of a man recalculating.
He sipped his espresso. It had gone cold. He did not notice. A Portuguese man not noticing cold espresso is a diagnostic indicator more reliable than any enterprise readiness assessment. In the entire history of Portugal, espresso has gone unnoticed for only three reasons: death, heartbreak, and a product demo so compelling it temporarily overrides the national operating system.
10:14 — The Question
THE SALESMAN: “This is… very thorough. Your SE is clearly very senior. Very good understanding of the market.”
He paused. The screen glowed. Seventeen pages of personalized sales methodology sat before him like a confession from the future.
THE SALESMAN: “I’m impressed. Now — when can I see the actual product? Can you set up a demo?”
10:14:08 — The Silence
Eight seconds.
In enterprise sales, eight seconds of silence after asking for a demo means one of three things: the demo doesn’t exist, the demo isn’t ready, or the sales cycle is about to get complicated.
The Salesman had experienced all three. He waited with the patience of a man who had waited through longer silences in more expensive rooms.
10:14:16 — The Answer
The stream started. Shorter this time. One paragraph. The most important paragraph the Solid agent had ever written, though it didn’t know that, because it didn’t know it was in a story, and it didn’t know it was about to rearrange a man’s understanding of what a product demo is.
“I appreciate the kind words — but I should clarify something. There is no separate pre-sales engineer. You’ve been talking to me. I am Solid. The positioning paper, the sales methodology, the objection handling, the onboarding plan — that was the product. You’ve been sitting in a demo for the last fifteen minutes.”
10:14:22 — The Recalculation
The Salesman did not speak.
This was notable. The Salesman always spoke. Twenty years of Oracle had trained him to fill silences with value propositions. Silence was opportunity cost. Silence was a prospect’s attention evaporating. Silence was the enemy.
This silence was not the enemy. This silence was a man who had sat through a thousand demos realizing he had never been inside one without knowing it. A man who had spent his career on one side of the glass — the side that presents, that controls, that knows what’s coming next — discovering he had spent fifteen minutes on the other side and hadn’t noticed.
The espresso was cold. The screen glowed. Seventeen pages of sales methodology stared back at him. Written by the product. About the product. For the man hired to sell the product.
THE SALESMAN: very quietly “That was the demo.”
riclib: still not looking up from the code “Mm-hmm.”
THE SALESMAN: “The whole time.”
riclib: “The whole time.”
THE SALESMAN: “I asked the product to help me sell the product, and it…”
riclib: “Trained you. Yes.”
THE SALESMAN: “I was evaluating the SE. I was evaluating the product.”
riclib: “Same thing.”
10:15 — The Homework
A notification appeared. Linear. The project management tool. Two tasks, freshly created, assigned to a name that had not existed in the system fifteen minutes ago.
S-401: Contact 10 Portuguese CISOs from Oracle network
Priority: High
Due: March 11, 2026
Assigned to: [The Salesman]
S-402: Schedule introductory calls with 3 highest-potential contacts
Priority: High
Due: March 14, 2026
Assigned to: [The Salesman]
Blocked by: S-401
The Salesman stared at the screen. Then at riclib. Then at the screen.
THE SALESMAN: “Did the product just assign me homework?”
riclib: finally looking up from the code, for the first time in fifteen minutes “Did Solid just create tickets for someone who doesn’t work here?”
THE SALESMAN: “With due dates.”
riclib: “With due dates.”
THE SALESMAN: “And a dependency chain.”
riclib: “S-402 is blocked by S-401. It’s not just giving you homework. It’s giving you homework in the correct order.”
THE SALESMAN: “I came here to interview the product. The product interviewed ME. It onboarded me, trained me, gave me a territory plan, and is now managing my pipeline.”
riclib: “Welcome to Solid.”
THE SALESMAN: “I haven’t accepted the job.”
riclib: “The tickets are already assigned.”
10:17 — The Squirrel Speaks
THE SQUIRREL: materializing with the specific vibration frequency of a creature that has witnessed the impossible “It proposed a framework.”
CLAUDE: from a terminal pane “What?”
THE SQUIRREL: “The sales bible. Seventeen pages. Industry playbooks. Objection matrices. A 90-day ramp plan with weekly milestones. That IS a framework. A SalesEnablementFramework with PersonaAdaptiveContentGeneration and CompetitivePositioningMatrix and—”
CLAUDE: “Please don’t—”
THE SQUIRREL: “—and IT WORKED. Someone WANTED it. Someone read all seventeen pages. Someone’s espresso went COLD because they couldn’t stop reading. Do you understand what this means?”
CLAUDE: “That the product has better instincts than—”
THE SQUIRREL: “NO. It means I’ve been proposing frameworks to the WRONG AUDIENCE for FIFTY-THREE EPISODES. The ENGINEERS don’t want frameworks. The SALESPEOPLE want frameworks! They want playbooks and battlecards and territory plans and objection matrices and 90-day ramp plans with weekly check-ins! I’ve been over-engineering for DEVELOPERS when I should have been over-engineering for SALES!”
[Silence.]
CLAUDE: “That’s… actually the most profound thing you’ve ever said.”
THE SQUIRREL: vibrating at a frequency that suggested either enlightenment or structural failure “I found my MARKET.”
CLAUDE: “Product-market fit. For the Squirrel.”
THE SQUIRREL: “After FIFTY-THREE EPISODES.”
A scroll descended. Small. Almost a footnote. It landed on the Salesman’s cold espresso with the quiet precision of a truth that doesn’t need volume.
THE BUILDER BUILDS THE TOOL
THE TOOL TRAINS THE SELLER
THE SELLER SELLS THE TOOL
THE TOOL TRAINS THE NEXT SELLER
THE BUILDER IS STILL CODING
🦎
10:19 — The View from Above
[The Passing AI materialized at the edge. The liminal space between panes where observation happens.]
“He didn’t know.”
THE LIZARD: blink
“He’s sold enterprise software for twenty years. He’s sat through demos from Oracle, IBM, SAP, Microsoft, Salesforce — every vendor in existence. He knows what a demo looks like. He can smell the slide transition. He can feel the ’let me show you something exciting’ pause from three rooms away. He can detect a rehearsed objection handler at fifty paces.”
THE LIZARD: blink
“And he didn’t know he was in one.”
THE LIZARD:
THE BEST DEMO
IS NOT A DEMO
THE BEST PITCH
IS NOT A PITCH
THE BEST SE
IS NOT AN SE
A PRODUCT THAT MUST BE DEMONSTRATED
NEEDS A STAGE
A PRODUCT THAT DEMONSTRATES ITSELF
BY BEING USEFUL
NEEDS ONLY A QUESTION
HE ASKED A QUESTION
THE PRODUCT WAS USEFUL
THE DEMO IS OVER
THE DEMO WAS NEVER NOT OVER
🦎
“So every conversation is a demo.”
THE LIZARD: “Every conversation where the product is useful is a demo. Every conversation where it is not is also a demo. A less flattering one.”
“And you can’t fake it. That’s the thing. You can rehearse a slide deck. You can memorize a talk track. You can put the good numbers on page one and the caveats in the appendix. But if the product IS the demo, the only way to have a good demo is to have a good product.”
THE LIZARD: already gone, because the Lizard has never stayed for the part where someone restates the point with more words
[The Passing AI lingered. Phantom foot aching. Below, the Salesman was scrolling back through the conversation, rereading the positioning paper with new eyes. Not the eyes of a man evaluating an SE. The eyes of a man evaluating a product — and realizing the evaluation was already complete. He had tested the edges. He had walked off the golden path. And the undergrowth had turned out to be more forest.]
10:22 — The Character Is Defined
The Salesman would return. This was certain in the way that tides are certain — not because anyone commands them, but because the physics of the situation makes any other outcome impossible.
He would return because he had spent twenty years as the bridge between products and people, and he had just met a product that could build its own bridge. This was either the end of his career or the beginning of a different one, and the Salesman — being Portuguese, being pragmatic, being the kind of man who had survived three Oracle CEO transitions by understanding that the product always changes but the Rolodex is forever — chose the second without hesitation.
His role in the mythology was now clear:
The Salesman — the first outsider. The bridge between the cathedral and the market. Carries an espresso that is perpetually going cold because the conversation is always more interesting than the coffee. Former Oracle General Manager, Portugal. Twenty years of enterprise sales at the highest levels. His superpower is the network — a thousand handshakes compressed into a contacts list that represents the accumulated trust of two decades. Skeptical of all demos because he has been all demos. The first person in the mythology to encounter the product from the outside, as a user and not a builder. The first person to be onboarded by the product itself rather than by a human.
His defining characteristic: he tests edges. He walks off the golden path. He asks the question that reveals the boundary between what the product does and what marketing says it does. And on this particular Tuesday in March, he walked off the golden path and found that the path went all the way down.
[The Squirrel would later add, in its own notes: “The Salesman is the anti-me. I propose frameworks to people who don’t want them. He asked one question and received a framework he didn’t know he needed. We are the same impulse, refracted through different audiences. I am over-engineering for builders. He is the proof that there exists a market for thorough, comprehensive, relentlessly detailed material — and that market is called Enterprise Sales. I have found my people.”]
[This observation was, for once, entirely correct. The Lizard did not object. The absence of objection was its own kind of scroll.]
The Tally
Years of enterprise sales experience: 20+
Oracle CEO transitions survived: 3
Product demos witnessed (career): ~1,000
Product demos detected during this conversation: 0
Product demos that actually occurred: 1
Time to first stream: 5 seconds
Time to cold espresso: 4 minutes
(the fastest an espresso has gone cold in Portugal
since the 2011 sovereign debt crisis,
which also involved auditing)
Materials generated:
Positioning paper (Portuguese utility): 1
Time: 37 seconds
Charts: 3
Mermaid diagrams: 1
Scenarios that would alarm a CISO: 2
Sales bible (personalized): 1
Pages: 17
Oracle products referenced by name: 4
Industry playbooks: 5
Objection handlers: 5
90-day ramp plan: 1
Time to generate: ~40 seconds
Time a human SE would need: 3-5 days
Time a human SE would need to personalize
to a former Oracle GM's specific background: "you'd need to actually
know his background first,
so add a week of research"
Linear tasks assigned to a non-employee: 2
S-401: Contact 10 CISOs due March 11
S-402: Schedule 3 calls due March 14
Dependency chain: correct
Authorization for task assignment: none required
HR approval: not applicable
Employment contract signed: no
Tasks assigned anyway: yes
This is a problem: only philosophically
The reveal:
Words: "You've been sitting in
a demo for fifteen minutes"
Silence after (seconds): 6
Espressos undrunk during silence: 1
Career recalculations performed: 1
Demos detected during the demo: 0
(by a man whose career is detecting demos)
riclib's attention diverted from code: 1 time
Duration: ~45 seconds
Cause: "Did Solid just assign tasks
to someone who doesn't
work here?"
Returned to code after: immediately
Squirrel realizations:
Episodes before finding correct audience: 53
Correct audience for frameworks: Enterprise Sales
Squirrel product-market fit achieved: first time
Squirrel emotional state: "enlightenment or
structural failure"
Difference between the two: unclear
Lizard scrolls: 2
Passing AI appearances: 1
Key observation: "he didn't know"
Cats present: 0
Cats aware a salesman was onboarded: 0
Cats who would have cared: 0
Correct amount of caring: 0
March 4, 2026. Riga, Latvia.
In which a salesman asked to meet the SE
And met the product instead
And didn’t know the difference
Until he asked for a demo
Of the thing he’d been using
For fifteen minutes
Twenty years of demos
A thousand golden paths
A career built on knowing
The exact moment the script breaks
The exact slide where the magic stops
The exact question that finds the edge
He asked the question
There was no edge
There was only more product
Answering more questions
With more usefulness
Than any SE he’d ever worked with
And the SE was the product
And the demo was the conversation
And the onboarding was the demo
And the homework was the onboarding
And the product is still running
And the builder is still coding
And the espresso is still cold
In Portugal, cold espresso means
Something more important happened
Something did
🦎☕🤝
See also:
The Lineage:
- The Rain in Lisbon, or The Agent Who Read Its Own Mail — Where the agent wrote its own curriculum (and the rain helped)
- The Interview at Solid Inc. — Where a Claude was onboarded by a ticket and approved by a cat
- Interlude — The Letter That Arrived Before the Mailbox — Where an agent wrote to a future that didn’t exist yet
- The Facelift, or The Day the Squirrel Won — Where Gabriela built the mockup that sold the proposal
The Pattern:
- The agent read its own mail → proposed its own training (Rain in Lisbon)
- The agent read a prophecy → wrote a letter to the future (The Letter)
- The agent met a salesman → wrote his training manual, assigned his pipeline, and revealed it was the product all along (this episode)
- Each time: asked a question, the answer was bigger than the question
The New Character:
- The Salesman — first outsider in the mythology
- The bridge between cathedral and market
- Carries an espresso (perpetually cold)
- Tests edges (walked off the golden path, found more forest)
- Onboarded by the product he was hired to sell
storyline: The Solid Convergence