I'm Not Trying to Conquer the Moon With Another Everything App
A lot of people ask me why I’m trying to conquer the moon with another everything app. I don’t see it like that. I took the 20% of features startups actually use and built Salestrics as a unified operating layer. I’m building for the enterprises of tomorrow, not today.
I get the skepticism. Software history is littered with “we do it all” pitches that collapsed under their own weight. Deservedly so. If Salestrics were a slide that said CRM + ERP + HRIS + data warehouse + social network with a straight face, I would not invest either.
That is not what we are building.
What people mean when they say “everything app”
Usually they mean one of two things:
- Scope creep — a product that chases every checkbox on a Gartner quadrant until nobody can explain what it does.
- Consolidation — one place where work already happens, instead of five subscriptions billing you for the same customer.
Critics assume we are the first. We are aiming at the second — and we are ruthless about what belongs in the layer and what does not.
The 20% startups actually use
I spent years in sales and operations watching teams pay for suites and live in a narrow slice of them. Pipeline. Email on the record. A doc for the proposal. A ticket when something breaks. A meeting to align. A dashboard someone exports before the board meeting. Automations for the three workflows that actually repeat.
That is the daily operating system of a seed or Series A company. Not custom objects for objects’ sake. Not a thousand integrations configured once and never maintained. The 20% that moves revenue — not the 80% sold to justify enterprise pricing.
Salestrics is opinionated about that 20%. Momentum for CRM. Mail and Inbox on the graph. Workspace for docs. Resolve for cases. Connect for meetings and chat. Ledger and Insight when finance and analytics need to see the same numbers sales sees. Assistant when you want answers without opening six tabs. We have written about the alternative — the Frankenstack — and why revenue workspace beats bolt-ons for teams that have lived both.
A unified operating layer, not a feature buffet
I call it an operating layer because the point is not the app count. The point is one customer graph.
When support sees the same account sales is trying to expand, when finance invoices from the opportunity instead of a spreadsheet, when AI reads mail and pipeline before it drafts a reply — that is the layer doing its job. You do not get there by buying best-of-breed and praying Zapier stays healthy. You get there by designing for shared records from the start.
That is harder than shipping another point solution. It is also the only way the workflow feels obvious instead of orchestrated.
Enterprises of tomorrow, not today
Today’s enterprise procurement still rewards checklists: SOC reports, seat minimums, a logo wall of integrations. Tomorrow’s companies will be built cloud-native, AI-native, and allergic to tab sprawl from day one. They will not accept that closing a deal requires four logins and a prayer that sync held.
I am not optimizing Salestrics for the RFP that asks for every module under the sun. I am optimizing for the team that hires its tenth employee and refuses to recreate the software tax their last company drowned in. They will grow into enterprises. They will bring the operating model with them.
People joke about going to the moon. We have a post called Salestrics To The Moon — and it is about ambition and capital, not cramming unrelated products into one navbar. The moon is a direction. The layer is how you get there without losing your mind on the way.
What we are not building
We are not building a generic work OS that replaces every vertical. We are not building for companies that want fifty disconnected apps and a consultant to wire them together. We are not pretending one login solves culture or strategy.
We are building the place revenue work lives — for startups now and for the companies they become. Platform is Live. Every module in the launcher is Live. We ship in public on the System Status Center because the layer only matters if it works on Tuesday, not in a roadmap deck.
If you have been told you need another everything app, ask what problem that solves. If the answer is “fewer tabs for the work you already do,” we should talk. If the answer is “one vendor to rule them all,” that is someone else’s pitch — not mine.
— Austin Buhl
Founder & CEO, Salestrics