Software is about to stop being a noun

Count the nouns on your screen right now. The CRM. The inbox. The spreadsheet. The doc. The board. The dashboard. The calendar. Each one is a thing, a place you go, a tab you keep, an app you bought and learned and now maintain. You have a drawer full of nouns.

Now count the verbs. Follow up with the lead. Reconcile the month. Brief me before the 2pm. Chase the renewal. Those are the things you actually want done. And here’s the strange part nobody says out loud: not one of your nouns does a verb. They hold state and wait. The verb is yours. You walk from noun to noun, carrying the work in your head, gluing the pieces, and at the end you call the glue “using software.”

That arrangement is about to end. Software is about to stop being a noun.

The thing you bought versus the thing you wanted

The whole history of business software is a history of selling nouns. A CRM is a noun. A project tool is a noun. An accounting package is a noun. You buy the noun, and in exchange you get a promise: somewhere inside this thing is the capability you need.

But the capability is never the thing you bought. You wanted the lead followed up. You got a place to record that a lead exists. You wanted the books closed. You got a ledger with empty rows. The noun is a container for a verb you still have to perform. Software is about to stop being a noun, meaning the day is coming when you ask for the verb directly, and the container stops being something you have to think about at all.

The key idea is simple, so let me state it plainly before I earn it: you bought tools, nouns, and assembled the work yourself; capability is becoming a verb you ask for, and the noun recedes behind the job done. The rest of this post is about why the noun was always a tax, what the verb actually requires underneath, and why this changes who in your company spends their day doing what.

The naive arrangement: you are the integration layer

Let me show you the arrangement you live in, because it’s so normal you’ve stopped seeing it.

Say a customer emails to renew. The naive flow goes like this. You read the email in the inbox, noun one. You open the CRM to check the account, noun two. You pull the contract from the drive to confirm the terms, noun three. You check the calendar to find a time, noun four. You draft the reply in the inbox again. You make a task in the board so you don’t forget the follow-up, noun five. Five nouns, one renewal, and the only thing connecting them is you.

You are the integration layer. Every app holds a third of the story, and you are the one walking it between them, re-typing what one tool already knew into the next tool that doesn’t. The work isn’t in any of the nouns. The work is in the hallway between them, and you are the person in the hallway, all day.

And notice the failure this produces. It’s not that any single noun is bad. The CRM is fine. The inbox is fine. The failure is that the seam between them is invisible and unowned. The renewal that slips through didn’t slip because a tool broke. It slipped because the verb, follow up before Friday, lived nowhere. No noun was responsible for it. You were. And you were busy in another hallway.

The work was never inside the apps. It was in the space between them, and you were the only thing standing there.

This is why “we have all the tools” never feels like having the work done. More nouns means more hallways. Every app you add is another place the verb can fall through. The tools multiplied; the person carrying them between tools stayed exactly one.

Why “more tools” never fixed it

The industry’s answer to the hallway problem, for thirty years, was integrations. Connect the inbox to the CRM. Wire the CRM to the calendar. Pipe the board into the doc. If we could just connect all the nouns, the thinking went, the seams would close.

It half-worked, and the half that failed is instructive. An integration is a pipe between two nouns that moves data. It does not move judgment. It can copy the email address from the inbox into the CRM. It cannot decide that this particular renewal is the one to chase today, draft the reply in your voice, hold the contract terms in mind while doing it, and remember on Friday that you said you’d follow up. Integrations connected the containers. They left the verb exactly where it was: in your head.

So you ended up with nouns that talk to each other and still don’t do anything. The data flows; the work doesn’t. You’re still the one deciding, drafting, remembering, just now with cleaner pipes between the things you’re deciding between. The bottleneck never disappeared. It just got a nicer diagram.

That’s the dead end the whole category walked into. You cannot reach a verb by connecting more nouns, any more than you can reach a sentence by alphabetizing more dictionaries. The capability you want isn’t a better-connected container. It’s a different kind of thing entirely, and that thing has a grammar of its own.

The verb has three parts, and a noun has none of them

Here’s the move. Instead of buying a container and performing the verb yourself, you say the verb out loud, follow up with the renewal, and the system performs it. To do that, the system needs three things that no noun has ever had. This is the whole mechanism, so I’ll go slowly.

A verb needs memory that spans every noun. To follow up on the renewal, the system has to know the email, the account, the contract terms, the last three conversations, and the fact that this customer hates being chased on Mondays. That knowledge is scattered across five apps today, and each app only sees its own corner. The verb requires one place that holds the whole story, a company brain that read all the nouns and remembers across them. Not a sixth app. The connective tissue the apps never had.

A verb needs hands that reach into every noun. Knowing isn’t doing. To actually follow up, the system has to draft in the inbox, update the account in the CRM, and file the next-step on the board, three different nouns, one continuous action. So underneath, the tools don’t vanish. They become reachable surfaces the system drives on your behalf. You stop opening five apps because something else is now opening them, in order, to finish one verb.

A verb needs a judge about when to act and when to ask. The dangerous version of this is a system that just does things, that fires off the renewal email at 2am with the wrong tone and CCs the wrong person. A verb that runs without judgment is a robocaller. So the third part is a sense of when the verb is safe to execute and when it needs your eyes first: draft the reply, hold it, surface it with the reason, here’s the renewal, due Friday, here’s the draft, send it? The verb proposes; you, when it matters, dispose.

Put those three together, memory that spans the nouns, hands that reach into the nouns, judgment about when to move, and you have something that can take a verb as input. That’s the unlock. And the instant you have it, the noun changes status. It stops being the thing you use and becomes the thing the verb uses. It recedes.

The noun doesn’t die, it recedes

I want to be careful here, because “software stops being a noun” sounds like the apps disappear. They don’t. The CRM still exists. The inbox still exists. Somebody, something, still has to record that the lead is a lead and the renewal renewed.

What changes is who looks at them. Imagine you ask for follow up with the renewal and it comes back done, drafted, sent, logged, next-step filed, and you never opened a single one of the five nouns to make that happen. The nouns all moved. You just didn’t have to be the one moving them. They went from being your destination to being the system’s substrate. From a place you go to a place the work happens, out of sight.

Think of how you use electricity. You don’t think about the grid, the substation, the transformer on the pole. You think light, and the light comes on. The infrastructure didn’t disappear, it receded behind the verb. You ask for the outcome; the nouns underneath stay busy and invisible. That’s the shape software is taking. The app isn’t deleted. It’s demoted from the thing you operate to the thing that gets operated.

And once that’s true, the question you ask when buying software inverts. Today you ask what does this tool let me do?, and then you go do it. Tomorrow you ask what verb does this do for me?, and the tool that answers with the cleanest, most trustworthy verb wins, regardless of how many nouns it quietly drives underneath. The noun was the product. The verb becomes the product. The noun becomes plumbing.

The turn: what you get back is your own verbs

Here’s the part that isn’t about software at all.

When software was a noun, the most capable people in a company spent their days as integration layers. The founder walking the renewal between five apps. The operator carrying the meeting rankings in their head. The salesperson scavenging context in the hallway before the call. We called that work “using our tools,” and we were proud of how many tools we’d mastered. But mastering nouns was never the job. It was the tax we paid because no system would do the verbs for us.

Strip that away and look at what’s left. The verbs only you can do don’t move between apps. Decide what the company should chase. Decide what “great” means for the people you serve. Decide which renewal is worth keeping and which customer was never the right fit. Those aren’t hallway work. Those are the verbs that don’t decompose into clicks across five tools, the ones that are still, irreducibly, yours.

The promise of software ceasing to be a noun isn’t that you get a faster CRM. It’s that the verbs that were beneath you, the carrying, the re-typing, the remembering of a date that lived nowhere, leave your desk, and the verbs that were always yours come back into focus. You stop being the most expensive integration layer in the building and get to be the thing only a person can be.

---

That’s what we’re building at Apollo Space, not a better noun, but the system that takes a verb. You’ll keep your apps; you’ll just stop living in them. You bought tools and assembled the work yourself for forty years. The good news is that was never the job. It was the tax, and the tax is finally something you can ask someone else to pay.